docs(src): refresh comments and docstrings

Comment-only changes outside learn/, plane/ and cli.py:

- model/pipeline.py: the `judge` its docstring contrasts with is the deleted
  model/judge.py, now named as such.
- fusion.py: the panels are deterministic and only review and vote; the
  "critique and revise" step belonged to the retired LLM panels.
- mcp.py: hunter tools stay inside the scan's stages, not "harness stages".
- fusion, mcp, gate, redaction, skills: their "Phase N" tags now say which
  plan they cite (the retired openrouter-sast-harness).

Requirement citations to retired specs stay: they explain where the code
came from. No behaviour change; the byte-identical benchmark golden passes.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01EmM1j46qgKMh3zqD1QMwEo

src/openultrasast/fusion.py

@@ -1,11 +1,11 @@
-"""Fusion adjudication — OpenUltraCode-style two-panel deepening (Phase 13).
+"""Fusion adjudication — OpenUltraCode-style two-panel deepening (Phase 13 of the retired openrouter-sast-harness plan).
 
 Fusion is the deepening mechanism for findings that need more reasoning than the
 ranker → hunter → verifier → mapping loop provides: critical/high severity, verifier
 disagreement, static-vs-semantic evidence conflict, findings that gate a risky fix or
 disclosure, or an explicit high-assurance request. Two panels independently review the
 bounded evidence (one steel-manning the vulnerability case, one the false-positive
-case), critique and revise, vote, and a decider issues the final disposition.
+case) and vote, and a decider issues the final disposition.
 
 The panels and the decider are deterministic and auditable. Every fused finding receives
 exactly one of the five dispositions, and the decision discloses panel roles, votes and the