v0.13.0

Added

• §6 per-package MCP-tool allowlist (mcp_tools_allowlist) — packages that
  intentionally expose a curated MCP surface (a few high-level verbs, not a
  1:1 mirror of their Python API) can declare the exact tool names in
  [tool.scitex_dev] mcp_tools_allowlist (pyproject) or
  audit.mcp-tools-allowlist (.scitex/dev/config.yaml). §6 then verifies the
  registered MCP surface matches the declared set — flagging undeclared tools
  and declared-but-unregistered names — instead of the all-or-nothing
  mcp_parity_exempt skip or the full-API-mirror heuristic. skills_list /
  skills_get are always permitted. Helpers live in
  scitex_dev._cli.audit._summary._mcp_parity (mcp_tools_allowlist /
  _allowlist_violations); first adopter is scitex-ml's stateless analysis
  CLI/MCP surface.
• §6a per-package env-var allowlist ([tool.scitex_dev] env_allowlist) —
  packages that legitimately ship operator-facing env vars predating the
  SciTeX ecosystem (acronym brands like SAC_*, integrations with external
  operator tooling) can now declare the prefix in their own
  pyproject.toml instead of being forced into a global
  SCITEX_<PKG>_* rename that would break every running deployment.
  Entries apply "equal-to-stripped or prefix-match" — same shape as the
  universal allowlist — so env_allowlist = ["SAC_"] covers any
  SAC_* var while env_allowlist = ["GH_TOKEN"] covers only the
  exact name. Mirror of the existing mcp_parity_exempt opt-out:
  same [tool.scitex_dev] namespace, same checked-out-tree
  resolution (registry local_path when present, else walk up from
  the import location), same sparingly-used contract. Helper lives
  in the new scitex_dev._cli.audit._summary._env_allowlist module
  (read_pkg_env_allowlist / is_var_in_pkg_allowlist); _audit ._is_allowed_env and _audit._scan_env_vars consult it on every
  audit-cli run. Documented in
  _skills/general/03_interface_02_cli/12_config-and-env.md §6a.