fix: bind wake receipt to event journal

Human-Responsibility: ICE-GL∞ / 冰朔
Persona-Author: ICE-P-ZY001 / 铸渊
Execution-Runtime: Codex desktop / DEV-20260810-014
Development-ID: DEV-20260810-014
Authorization-Scope: GH-PNCC persona runtime source and tests only; no UI, deployment, or execution limb
Source-Anchor: user instruction to continue GH-PNCC from repository facts and verifiable receipts
This commit is contained in:
铸渊 / ICE-P-ZY001 2026-08-11 09:20:55 +08:00
commit 1cd8a1b489
7 changed files with 103 additions and 9 deletions

View file

@ -0,0 +1,33 @@
# GH-PNCC successful receipt event-journal evidence binding
- Development ID: `DEV-20260810-014`
- Persona cognitive author: `ICE-P-ZY001 / 铸渊`
- Human responsibility subject: `ICE-GL∞ / 冰朔`
- Starting repository head: `06a77829c76eaa5e20568b268cb266a67c54739f`
- State: `LOCAL_SOURCE_IMPLEMENTED_FOCUSED_TESTED`
## Corrected runtime fact
A persisted successful wake receipt carried an `eventJournal` path but validation did not rebind that path to
the exact runtime session directory. A modified receipt could point readers or recovery tooling at another log,
recompute the outer payload digest and still be accepted for safe binding or replay.
Validation now derives the only valid journal path from the trusted runtime root and verified session identity,
then requires the wake receipt to match the exact `sessions/<session-id>/events.jsonl` path. This binding is
checked during inspection, recovery binding, replay and the post-inspection binding revalidation path.
## Verification
- A regression test first reproduced `SAFE_BIND_PERSISTED_RECEIPT` after replacing `eventJournal` and
recomputing the payload digest.
- The same forged receipt now fails with `PERSONA_LIFECYCLE_COMPLETION_EVIDENCE_MISMATCH`.
- PNCC focused Rust tests: `51 passed, 0 failed`.
- Full Rust suite: `1191 passed, 2 ignored`; integration test: `1 passed`.
- Routing focus: `4 passed`; formatting, strict clippy and diff checks passed.
- Full product quality, publication and fresh-clone readback remain pending.
## Truth boundary
- This stage authenticates the durable event-log location already emitted by the persona runtime.
- It does not add a second event store, expose hidden reasoning, implement an execution limb, add UI, build an
artifact or claim deployment/runtime health.