DR-034 — The content_items-era coverage feature is RETIRED, not re-pointed

get_coverage_matrix / get_coverage_summary, their routes and the unattended coverage-alerts cron are retired with the content_items model — do NOT rebuild them onto q_a_pairs/L-records. Owner ruling (S449, on the 131.19 GO escalation): the coverage signals critical to retain are template-completion coverage and governance; anything beyond that re-enters only as a deliberate future feature, not a migration re-point.

Route scope (narrowed S498). Retired: app/api/coverage/route.ts, .../gaps/route.ts, .../guides/route.ts. Retained: app/api/coverage/templates/* — that is the template-completion coverage this ruling explicitly keeps. The original app/api/coverage/* wildcard read as if the whole path were dead.

MCP surface adjudicated (owner ruling, S499). The surviving MCP surface — show_coverage_matrix (lib/mcp/tools/apps.ts:47), kb://coverage (lib/mcp/resources.ts:440) and ui://coverage-matrix/app.html — is in scope of this retirement: it rebuilds the forbidden matrix onto source_documents + record_lifecycle. It was never a post-ruling breach (the re-point landed at 7aeabaeb just before the retirement migration), but it does not survive as a carve-out. The owner’s forward definition of coverage: how a client’s Q&A pairs and knowledge-base corpus cover what is required to complete a form_instance (formerly a “template” form) — i.e. the template-completion coverage this ruling already retains, re-keyed form-first. Removal and any replacement surface are tracked in tasks/id-373.md.