11 docs/features pages are absent from the wiki publish map, including stage-e-operations.md

[WilfordGrimley]

Found 2026-07-30 while landing PR #650. docs/features/stage-e-operations.md is not in .github/wiki-publish-map.json, so it publishes to neither the wiki nor the site.

That matters because it is the living operational doc for Stage E, and three changes were deliberately routed into it this week under the owner rule "if we are documenting changes to the way something actually works, we should be editing existing docs that are wiki/site facing" — the throttle-not-halt section (#644), the channel_report section (#646/#650), and the global rate ceiling (#649). All correct content, in the correct file, reaching no reader outside the repo.

10 of 21 docs/features/*.md are mapped. The 11 that are not:

artist-support-links.md      homepage-panel.md
bleed-measurement.md         saved-decks.md
catalog-stats.md             search-operator-syntax.md
consent-toast.md             stage-e-operations.md
display-left-rail.md         theming.md
foreign-order-resilience.md

The systemic part

Nothing lints for this. PR #591 added a MANIFEST coverage rule enforced in both directions — but it checks docs/MANIFEST.md, not the publish map. A doc can be fully indexed, authoritative and CI-enforced while publishing nowhere. docs_lint.py's check_wiki_publish_map validates the map's internal consistency (sources exist, targets valid, no duplicates) but never asks the reverse question: which docs are missing from it.

Same shape as #623 (docs/reference/skip-reasons.md is a CI-enforced roster, also unmapped — and NO docs/reference/ file appears in the map at all).

What would close this

1. Decide which of the 11 should publish. Not obviously all — some may be genuinely internal, and that is a legitimate answer per page.
2. Add the ones that should.
3. Extend check_wiki_publish_map with the reverse direction: a doc under a publishing directory with no map entry is a finding, with a per-entry-justified allowlist for deliberate omissions. Same pattern docs_lint rule 5: MANIFEST.md coverage, both directions #591 used for MANIFEST.

Related: #623, #642 (the living-doc-vs-report rule).