refactor: remove implementation-plan phase references from code
The "Phase N" tags referenced the phased implementation plan under
docs/implementation-plans/2026-04-17-labeler-report-stage/. Now that
the plan is finished, these cross-references are dead weight that
force a reader to look up a historical document to understand what
the comment means.
Rewrite each to describe the actual subject instead:
* create_report.rs: module doc, control-flow comments, and the
"Phase 6/7 now", "Phase 7/8 fallthrough", "Phase 4 Task 0
IdentityFacts", and "Phase 7 pollution-avoidance" comments are
rewritten to name the affected checks or data directly.
* create_report/self_mint.rs: "Phase 1 Task 0 direct dep" →
"carried as a direct dependency".
* pipeline.rs: the "Phase 4 / Phase 8 populates" comments on
self_mint_signer and pds_credentials describe the actual gating
condition (self-mint viability and --handle/--app-password).
* identity.rs: subject_collections doc re-explains retention as
"future pollution-avoidance refinements" instead of "Phase 7".
* tests/labeler_report.rs: "Phase 5/6/7/8" comments and the
ac4_5_non_viable_skip_matches_phase_6_reason test name now use
"no-JWT negatives / self-mint negatives / self-mint positive /
PDS service-auth" instead.
Runtime-protocol "backfill phase" / "live-tail phase" references in
subscription.rs and "probe phase" references in did_doc_server.rs /
self_mint.rs stay — they describe actual behavior, not the plan.
No logic changes — comments, doc comments, and one test rename only.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
authored by