S531 task-ledger reconciliation audit

Owner-requested (S531). Read-only lane; verdicts applied to task files in the same session, each citing this report. Ground: canonical HEAD past 1ed12099a through the S531 retirement commits; docs-site task files; git history. No DB queried, no suite run by the lane — population claims are absent by design.

Verdict table

Task	Verdict	Core evidence
id-303	CLOSE	4 of 6 named scripts deleted; `grep "from('content_items')"` zero repo-wide. Residual re-homed: quality-gate.ts still unwired to CI.
id-344	RETIRE (done-by-events)	Gold fixture + runner deleted `14a4d4e36`; Option C executed by the wave. Residue: 3 orphan baseline JSONs + `eval-register-suites.ts` legacy registrations (infra-skip, verified NOT a nightly break).
id-373	CLOSE h1 / carry h2	`show_coverage_matrix` zero hits; `kb://coverage` gone; `coverage_targets` dropped. {373.3}‘s MCP-surface question carried into id-421.
id-389	UPDATE	New dependency: `mock_llm.py` discriminates on `prompts.py`’s 4 extractor shapes; Python classification’s potential retirement changes the routing.
id-132	UPDATE	Close-out must record FOUR producer grains, not five — the domain-subtopic topic grain deleted S531 (DR-125 expiry).
id-243	UPDATE	soffice, if ever wanted, lands in id-416’s Dockerfile — the {66.7} GHCR build it names is being replaced.
id-369	UPDATE	{369.5} F6 gone, F5 half-gone, F10 lost batch-reclassify sites; F3/F4/F7/F8/F9 verified alive.
id-372	UPDATE + Q	`__tests__/integration/queue/` no longer exists (`1a752b48d`, `3349ce79f`). Q verbatim: what requirement did lifecycle (1266 ln) + concurrency (462 ln) serve, and is it still live? The wave’s own scope note does not explain those two.
id-392	UPDATE	AC-1 reader list shrank again (batch-reclassify, /api/extract, summaries/generate gone). Survivors for the closing sweep: review/queue route + source-document-revision adapter. Re-measure AC-4 verdict.
id-401	UPDATE	id-406 + id-408 now done (blockers spent); `d6574ab02` parked the find-tool spec; AC-8 still blocked on the duplicate-aria-label defect — no task owns it.
id-402	UPDATE	record-run KEEP verdict re-measured and SURVIVES on 3 live call sites (the cited census named 5 deleted ones). AC-6’s taxonomy-consistency subject now has no write surface — requirement-first question the AC does not ask.
id-162	UPDATE + Q	Premise holds (ai_keywords written; no keyword array on q_a_pairs). Q verbatim: what requirement does a q_a_pair keyword array serve that scope_tag overlap does not, and is it still live?
id-363	UPDATE	id-370 done → D7 precondition discharged; re-measure the class-A volume before {363.3}. DR-125 obligation now explicit (see id-422 seam).
id-315	UNDECIDABLE	Q verbatim: does the {132.34} extraction gate still exist in the shape this task describes, and did {132.36} change the answer?
id-71	UPDATE (material)	{71.7}/{71.8}/{71.16}/{71.22} delivered-then-deleted; classify_content retired S531 = a FIFTH rebuild id-71 never scoped; {71.30}/{71.31} target deleted tools — retire as written, carry their content requirements into the rebuild.
id-163	UPDATE (material)	{163.10}‘s signed-off wave documents 4 MCP tools, ALL retired (classify_content, find, get, get_procurement_detail) — blob-pinned citations no longer exist at HEAD; {163.11} assertions cannot round-trip. Nothing published.
id-409	UPDATE	Consumers #11 (get_document_versions MCP) + #12 (review-cadence cron) gone. NEW: `__tests__/mcp/get-document-versions.test.ts` stays green testing an INLINED MIRROR of deleted code.
id-416	UPDATE	taxonomy-sync.yml is trigger-less: its route deleted `3349ce79f`, `dispatchTaxonomySync` has zero production callers — a production-load-bearing asset (extraction.py:129 import-time read, 47 transitive importers) regenerates only by hand. taxonomy tables now have NO write surface.
id-140	UPDATE	Three new escape axes for its checklist: trigger-deleted workflow; test-inlined mirror of its subject; orphan emitter kept alive by its own test.
id-421	UPDATE (process)	Invisible to ordna — only task of 155 the CLI cannot see. Leading hypothesis: `depends_on: [147]` (bare int vs `[id-N]`). Fixed this session.
id-349	UPDATE	quality-badge + quality-score-breakdown gone with the wave; expiry-date-display gone S531. review-cadence-badge doubly orphaned but review_overdue has 4+ live readers — id-420’s call, not a liveness delete.
id-353	UPDATE	Sequence after id-420 — two of seven params route to /review, which the faceted rebuild moves.
id-46	UPDATE	{46.7} carve-out (batch-reclassify handler) discharged at `0267cea37`.
id-128	UPDATE	{128.2}‘s eval:entity pointer + {128.21}‘s id-372 completion pointer both dangle.
id-418	UPDATE	Taxonomy-seeding question gains a mechanical argument: no admin write surface, orphaned sync trigger.
id-292	UPDATE	Class-2 writer count halves (content.ts deleted).
id-245, id-411, id-417, id-419, id-420	UNCHANGED	Verified current.

Process defects (outside the ledger)

taxonomy-sync.yml trigger-less (see id-416 row) — needs an owner decision on the regeneration path.
id-421 ordna invisibility — measured; frontmatter hypothesis fixed S531.
get-document-versions.test.ts — green against an inlined mirror; the shape evades tsc, the suite AND knip. Filed to id-140’s checklist evidence.

Not assessed

~90 open tasks covered only by concept-name grep (zero-hit list in the lane transcript); no archived/done reopen review (id-402 AC-1 owns it); the three-way ownership of sidecar-mime-coverage.integration.test.ts (id-245/id-392/id-415) flagged, not adjudicated; no DB reads, no suite runs.