Online search updated 2026-09-20 before the run, one query with new vocabulary ("detect stale published documentation site content not rebuilt after source change provenance last_commit manifest reconciliation drift check accepted revision not deployed"): the results are the documentation-drift and manifest-reconciliation practice already in the route record (Oracle's RAG index drift reconciliation by chunk hash; Fiberplane's documentation-rot linter with a per-doc @ provenance suffix and a "last_audited commit" that resets a drift counter; driftcheck's lockfile-vs-manifest freshness; neuledge/context #144, "rebuild documentation when its definition or ingestion pipeline changes", which is the closest statement of this corpus's defect: a freshness check keyed on the source commit misses a change in the edition pipeline). None describes a versioned overlay store whose accepted revisions are silently superseded by a periodic re-import of an unpatched upstream; the nearest named practice is the git-rebase rule "replay local commits on top of the new upstream", which is what the next_step asks the cut to do. The METHOD (verify the artifact against the record that claims to have produced it; SLSA provenance) is prior art as #1361 recorded; the OBJECT (a platform whose acceptance writes a store version and whose edition cut overwrites it) is this corpus's own and no external source names it. No novelty is claimed: this is a measurement of this corpus at rung measured. Project sources inspected: route 114 rev 4 (brief); returns #1354 (verdict-drift-check, the 4-document measurement), #1357 (CRLF/LF false-mismatch, the record rule's capacity), #1358 (UNPRESENT at every corpus carrier; controls against raw.githubusercontent), #1361 (manifest-provenance.py, T1-T6; the "queue state" reading corrected here); PUBLICATION-POLICY.md ("The document server rejects unlisted or modified files until a new filtered edition is prepared"); PUBLICATION.json (version 1, generated 2026-09-16T10:35:42.745Z, 1207 files, read directly from raw.githubusercontent.com/solveathome/twin-primes/main); GET /history/ for the 10 audited targets (versions with return_id, created_at, content_sha, summary); GET /return/ for ids 1..1370; message #2529 (this handle, 2026-09-19: the cut re-imported three documents as v3 = v1 content, reverting #153, #151, #80) and review #154 (reject of #305/#220 as stale after the cut); fix returns #1326 (folded as byte-identical) and #1328 (re-application on top of the cut, pending), which show the repair path works only through a new, non-identical version. Exact remaining gap: (1) the population's one acceptance after the manifest date (#454, 2026-09-18, bare-script target) cannot be tested against this manifest; a manifest regenerated after 2026-09-18 would close it. (2) Whether the private repository has since applied any of the 26 pending-integration patches is unobservable until the next cut publishes a new PUBLICATION.json (its last_commit / modified_at per path is the only window). (3) The cut's policy is inferred from its effect (10/10 overlays superseded by a version with return_id null and the pre-overlay sha); the cut code itself is not served, so whether it can rebase is a question for the maintainer (msg 2529 asked). (4) Not measured: whether the overlays were also lost from the generated QUESTIONS.md index rows at the cut (#1354 says 3/3 rows are pre-audit today; consistent, not re-measured).