Ratify Stage E streaming amendments, close wave-1 Bug-A arc, fix rail-delegacy doc drift

[WilfordGrimley]

Description

Three docs-only edits, all in place per this repo's docs convention:

1. docs/proposals/stage-e-streaming.md — added a "Ratified amendments
   (2026-07-24, owner)" section (§10) resolving §9's open items 1/2 and
   sharpening two more: (a) two-mode operation (PASSIVE, load-governed,
   no cards/hour cap, bounded by host-load 7.0 / 512MB RSS / worker /

   1% fetch-failure over a 500-card window / instant lockout pause /
   fresh-owner-action resume; BULK unchanged, today's per-batch poll
   discipline) replaces the single cards/hour ceiling §3 decision (5)
   left open; (b) CardScanLog retention tripwire codified (10M
   rows/5GB, prune keeps latest-per-(card, anonymous_id) + <12mo, via a
   dry-run-gated command); (c) micro-batch size ratified as a measured
   output of the §7 tail-shakedown's instrumentation, not a pre-chosen
   constant; (d) PR Fix three small IO findings from the 2026-07-24 audit #424 (landed IO-audit quick wins) and issue tesserocr A/B spike: eliminate per-call tesseract spawn/model-load floor #423
   (tesserocr spike) cross-referenced into §4's efficiency section. §9
   items 1/2 marked RESOLVED with pointers to §10.

2. docs/pipeline-fidelity-gate.md — added §15 documenting the wave-1
   Bug-A arc's full closure (10,437-card re-scan → reparse retraction →
   full-pool lands write → wave-1-scoped Stage D write → a closing
   consensus_recompute dry-run with zero transitions), every figure
   keyed by run_id. Updated "What remains open" item 1 (wave-1 closed,
   only the ~6,535-card tail stays open, routed to Stage E streaming's
   shakedown per Stage E: streaming assembly + resume contract + kill-test #153/Bug-A re-scan tail: remaining sources after wave-1 measure #418, not a batch) and item 2 (moderation package
   sizing corrected from "data-ready" to DEFERRED by owner ruling,
   pending further passes, with the 167,045/76% raw-union figure at
   ruling time recorded alongside the existing 134,370 dedup'd figure).
   Also folded in the scryfall-cache incident's missing linkage: issue
   scryfall_cache is lost on every container rebuild #402 resolved by merged PR Persist scryfall_cache volume and fail loud on a missing cache #412, live via deploy-3.
3. docs/features/grid-selector.md / docs/features/printing-tags.md
   — fixed rail-delegacy (Rail-delegacy: remove the nine grey /editor rail accordions #413) doc drift PR Rail-delegacy: remove the nine grey /editor rail accordions #413's own open items
   flagged: the funnel's per-axis chips are no longer an always-visible
   top-to-bottom column on the /editor rail caller, they're relocated
   into RD4's shared, tier-conditional Filters panel (phone in-rail
   collapse, desktop/tablet floating portal); AttributeVotingPanel now
   has a third mount (the D14-anchored IdentifyPanel) alongside the
   funnel and the card-detail-modal. Ghost-tile thumbnails (EP1) and the
   five client-side sort orderings (EP7) were already correctly
   documented by Editor-polish round: rail-head enlargement, Sources de-grey, D14 restyle, compare-on-pill, consent gate #421 itself — no change needed there.

Deviations

• D14 compare-on-pill (EP9) and the "More details" relocation
  (amendment 1) are real Rail-delegacy: remove the nine grey /editor rail accordions #413/Editor-polish round: rail-head enlargement, Sources de-grey, D14 restyle, compare-on-pill, consent gate #421-round changes, but neither
  grid-selector.md nor printing-tags.md ever described them — their
  actual (and now stale, pre-Rail-delegacy: remove the nine grey /editor rail accordions #413) home is
  docs/features/display-left-rail.md, which still documents the
  removed AutofillCollapse rail accordions wholesale. That file is
  out of this task's assigned scope (only printing-tags.md/
  grid-selector.md were named) and substantial enough to need its own
  dedicated pass rather than a rushed rewrite here — flagged as an open
  item below rather than fixed speculatively.
• Did not touch docs/troubleshooting.md's scryfall-cache entry (has
  the mechanism detail but not the PR Persist scryfall_cache volume and fail loud on a missing cache #412/deploy-3 citation) — the
  task scoped the linkage fix to pipeline-fidelity-gate.md's own ops
  notes specifically.

Verification

• python3 .github/scripts/docs_lint.py --strict — clean.
• python3 .github/scripts/tests/test_docs_lint.py — 26/26 pass.
• python3 .github/scripts/tests/test_publish_wiki_link_rewrite.py — 4/4 pass.
• python3 .github/scripts/tests/test_publish_readme.py — 8/8 pass; regenerate-and-diff against committed readme.md — no drift (readme.md untouched by this PR anyway).
• python3 .github/scripts/check_protected_core_license.py — clean, 9 files checked.
• pre-commit (prettier) — clean after one auto-reformat of the new §15 table, re-committed.

Open items

1. docs/features/display-left-rail.md is substantially stale against
   both Rail-delegacy: remove the nine grey /editor rail accordions #413 (still describes the removed grey AutofillCollapse rail
   accordions) and Editor-polish round: rail-head enlargement, Sources de-grey, D14 restyle, compare-on-pill, consent gate #421 — worth a dedicated follow-up pass; not
   attempted here (out of this task's scope, and too large to do
   safely alongside the other three edits).
2. Wiki maintenance: none of these three docs are wiki-published pages
   per docs/documentation-process.md, so no wiki update is needed for
   this PR.

Closes context for #153, #418, #154.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com