Resume missing newspapers without replaying world waves

This commit is contained in:
Meta Vens 2026-08-29 06:56:37 +02:00
commit 8a971daab8
6 changed files with 414 additions and 29 deletions

View file

@ -1,6 +1,6 @@
# Ghostlight Fresh Workspace Handoff
Updated: 2026-08-28
Updated: 2026-08-29
This is the compact re-entry packet. It records current authority, deployed
truth, proof, and the next decision. Git history owns chronology; the system map
@ -1009,34 +1009,49 @@ wave 15. That materialized-versus-dormant routing fix was pushed in exact source
Run 41 cloned run 40 at committed revision 23, removed only copied wave-15
failure artifacts, and did not replay prior waves. It committed waves 15 through
18 through revision 27 with 363 events and 853 news rows. The unit then failed
only during final newspaper composition: one-pass grounding reconciliation
rejected distinct findings that shared one editable target. The remote root is
18 through revision 27 with 363 events and 853 news rows. Issue 14 is accepted;
Issues 13 and 15 through 18 are absent because their old grounding repair failed
after the corresponding immutable world-wave commit. Final newspaper composition
also failed. The remote root is
`/var/lib/gamecult/ghostlight-dungeon/acceptance/elven-realms-autonomous-46810c3-41`.
`BUILD-WITNESS` binds the run-40 resume root and
`live_service_mutated=false`. Simulation mechanics are complete; no accepted
final digest exists. Runs 38, 39, and 40 remain preserved, and acceptance is
incomplete.
`live_service_mutated=false`. Simulation mechanics are complete; the derived
publication sequence and final digest are incomplete. Runs 38, 39, and 40
remain preserved, and acceptance is incomplete.
The current uncommitted `newspaper.rs` diff groups replacements by editable
target, validates every exact phrase once against the original copy, rejects
overlapping ranges, and atomically applies distinct non-overlapping replacements
in reverse source order before requiring the complete finding set and fresh
whole-page verification. Its defining regression and all newspaper tests pass;
the full 468-test library gate and `git diff --check` also pass. The fix is not
yet committed, pushed, provider-proven, or editorially accepted.
Pushed `19a66a4` groups newspaper grounding replacements by editable target,
validates every exact phrase once against the original copy, rejects overlapping
ranges, and atomically applies distinct non-overlapping replacements in reverse
source order before requiring the complete finding set and fresh whole-page
verification. Its defining regression, all newspaper tests, the full 468-test
library gate, and `git diff --check` pass. Provider and editorial acceptance
remain open.
The current uncommitted strategic-smoke runner diff adds a presentation-only
recovery seam for missing per-wave editions. It derives each absent issue from
that wave's immutable committed campaign snapshot and exact prior committed news
boundary, publishes an immutable recomposition receipt, and skips accepted
issues such as Issue 14. It fails closed when the exact prior boundary is
unavailable, including a missing first-wave issue. Every recomposition receipt
binds source, contract, issue, typed model receipts, rendered content, and file
digests; typed receipt JSON roundtrip is covered. The complete local gate passes
12/12 strategic-smoke binary tests, 468/468 library tests, and
`git diff --check`. It cannot replay or mutate world mechanics and is not yet
committed, pushed, or provider-proven.
Pushed `af749de` routes a provider timeout through the shared model transport's
existing one same-request retry and records attempt telemetry. Run 36 crossed
that boundary; timeout retry is not its active blocker.
1. Commit and push the locally verified atomic same-target grounding edit fix.
2. Resume only final newspaper composition from run 41's committed revision 27.
Do not replay waves 15-18 or any earlier wave. Require the resulting unedited
final digest to pass fresh independent editorial and provenance review before
claiming acceptance. Preserve runs 38/39/40, the run-41 root and committed
world lineage, stopped run 23, exact acceptance conditions, and unchanged
live daemons.
1. Commit and push the locally verified missing-edition recomposition boundary.
2. Launch exact-source run 42 from run 41's committed revision 27 to compose only missing Issues 13
and 15 through 18 plus the final digest. Preserve accepted Issue 14, every
completed wave checkpoint, and canonical world state; do not replay any
mechanics. Require the resulting unedited publications and final digest to
pass fresh independent editorial and provenance review before claiming
acceptance. Preserve runs 38/39/40, the run-41 root and committed world
lineage, stopped run 23, exact acceptance conditions, and unchanged live
daemons.
3. Have the game-side adapter lower its authored hierarchy into the published
generic schemas; keep projection and economy translation consumer-owned.
4. Prove one consumer-owned effect crosses that public API, changes two foreign

View file

@ -1340,6 +1340,57 @@ text before Markdown emission; the provenance renderer applies the same
plain-text boundary to its audit data. Neither editor, copy desk, renderer, nor
receipt persistence can write world state.
#### Acceptance-driver per-wave newspaper recovery
- **Owner:** the strategic acceptance driver owns recovery of a missing
consumer artifact after its world wave has already committed. It owns neither
the wave nor the newspaper's factual or editorial judgment.
- **Inputs:** the missing wave's immutable checkpoint and committed `Campaign`
snapshot, the preceding wave checkpoint's committed news-ledger boundary,
the configured title and voice, and the same campaign receipt store used by
ordinary newspaper composition.
- **Output:** one separately named immutable recomposition checkpoint containing
the accepted issue, grounding verdict, and newspaper model receipts, plus the
rendered reader and audit files. Its receipt binds the narrowed source
campaign, title/voice/article-budget contract, issue, model-receipt collection,
expected filenames, and both rendered byte streams by digest. The driver fills
only the missing newspaper fields in its in-memory result projection. Existing
successful issues and original wave checkpoints remain unchanged.
- **Derived state:** the newsroom receives a clone of the completed wave's
campaign whose news ledger is narrowed to rows appended since the preceding
committed boundary. All events and canonical names remain available only so
those exact news rows can resolve their sources; the clone is a consumer view,
not a campaign mutation.
- **Forbidden writers:** recovery cannot rerun a strategic tick, Nemesis,
simulation cells, outcome resolution, clocks, or `WorldKernel`, and it cannot
alter campaign, event, or news state. A failed recomposition stops consumer
recovery and cannot repair mechanics.
- **Shared paths:** live per-wave composition, recovery composition, and final
combined composition all call `compose_persisted_newspaper`, including the
same grounding/copy-desk path and idempotent model-receipt persistence. A
later resume consumes the successful recomposition checkpoint instead of
paying for the newspaper again, but only after recomputing its source and
contract bindings, deserializing the issue, regenerating reader and audit copy,
and comparing the exact stored files and digests.
- **Verification layer:** the focused boundary regression proves that a second
wave is recomposed from only its newly appended news row while retaining the
committed event ledger needed to resolve that row. It also rejects prior-news
prefix drift and confirms that first-wave recovery fails closed without an
exact pre-run boundary. Immutable checkpoint publication separately rejects
overwrite and publishes by synchronized temporary-file rename. A typed
receipt-digest regression proves that checkpoint JSON is deserialized back to
`Vec<ModelStageReceipt>` before hashing and rejects an invalid receipt shape,
so creation and verification share one representation. The current binary and
library test suites pass.
The first-wave limit is now an explicit closed boundary rather than inferred
recovery: without a preserved pre-run news prefix the driver refuses to compose.
Run 41 already has its first issue, so the bounded recovery set is later missing
issues only. The remaining limitation is verification breadth, not split
authority: no focused test yet executes the complete resume orchestration from
fresh recomposition through later reuse while asserting successful-issue
preservation, exact rendered-file validation, and absence of mechanics calls.
Session Zero compilation, expansion, and fission follow the same projection
rule. Review projections expose topology, pressures, source-use coverage, gaps,
assumptions, public party cards, and only the current viewer's private ledger.