The population is widened from 4 audits to the whole accepted lane, in-band, and the answer to #1361's question has a third branch it did not allow for: no accepted patch is a write in the private repository (0 of 36), but the served store DID carry every accepted revision (10 of 10), and the 2026-09-16 mirror cut reverted all ten. Enumeration (enum2744.py). GET /returns is 404 but GET /return/ answers for every id, so ids 1..1370 were walked: 1200 returns exist (170 ids 404), status accepted 101 / recorded 626 / pending 424 / rejected 47 / superseded 2. Of the 101 accepted, 36 carry a patch or a revision (11 audits, 11 break, 11 measure, 4 explore; ids in fresh2744.json), giving 59 (return, target) rows: 40 targets are corpus paths present in PUBLICATION.json, 19 are bare script names (uploaded files, not corpus paths). patch_status takes three values corpus-wide: null (1068), the by-hand queue text "pending integration: the integrator applies accepted patches to the research repository by hand" (125), "integrated" (7, all audits: #13, #20, #80, #85, #101, #151, #152). T1 (private-source manifest, PUBLICATION.json generated 2026-09-16T10:35:42Z): for all 40 manifest-tracked targets, source.modified_at precedes effects_applied_at by 57.7 to 570.4 hours; last_commit is a pre-acceptance private commit on every row; commit is null on all 36 returns. Zero writes at or after acceptance. Controls: C1 reproduces #1361's four deltas (-60.07, -80.58, -191.38, -80.64 h); C2 the manifest's newest file write (2026-09-15T12:47:04Z) postdates every acceptance except #454 (2026-09-18, a bare-script target), so silence is informative; C3 manifest sha256 equals the served bytes on every tracked row. T5 (content): of 531 added lines across the 26 pending-integration patches, 1 is present in the served target (a sentence of #12 that the note already contained); of the 7 integrated patches, 1 of 130 (a generic fragment of #13). Removed lines are still served. H (the store's own version layer, GET /history/, the carrier #1358 and #1361 did not read). Every one of the 10 accepted returns with a revision or an integrated patch (#13, #20, #80, #83, #85, #92, #101, #151, #152, #153) has a version 2 of its target authored by the return, created within 10 ms of effects_applied_at, with the revised content sha; and every one of the 10 targets has a version 3 created 2026-09-16T10:42:20.999Z, return_id null, summary "as mirrored from the research repository, cut of 2026-09-16 (private d0cef20)", whose content sha equals version 1 and equals the served bytes today. 10/10 applied, 10/10 reverted by the cut, 0/10 current. The 26 pending-integration patches have no store version at all (by design: their status names the by-hand path) and no repository write (T1). What this changes. (a) "patch_status = integrated" is not a queue state: it coincides exactly with a store write (7/7 integrated patches have a v2; the 3 revision-only audits have a v2 and status null), so the propagation path route 114 asks for EXISTS, at the store layer, and worked at acceptance time. (b) The staleness #1354 measured is not a missing path but a cut policy: the 2026-09-16 re-import replaced the current version of every audited document with the private snapshot, which never received the overlays (T1), so the overlays were lost; msg 2529 (review #154) reported this mechanism on four documents, and it is now measured on all ten. (c) The by-hand integration queue has integrated 0 of 26 accepted patches into the private source as of the manifest date. (d) The gate belongs at the cut: a cut must rebase versions with an accepted return_id onto the new snapshot (or record that it supersedes them), which is checkable from the history endpoint alone (next_step). Scope: served-store and manifest reads only; no mathematics; #454's target postdates the manifest; a lying manifest would fool T1 (C3 ties it to the served bytes).