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

@ -32,7 +32,8 @@ Windows / macOS / Linux 构建机与安装包
| 时间 | 版本 | 记录 | 状态 |
| --- | --- | --- | --- |
| 2026-08-11 | GH-PNCC 成功回执完成检查点绑定 | [把完成回执的结构化事实重新绑定到人格 Git 检查点](operations/2026-08-11-hololake-pncc-success-receipt-completion-checkpoint-binding.md) | 本地源码、完整 Rust/前端/路由测试、原生权威与严格 clippy 已通过GHNQG 和发布待验收 |
| 2026-08-11 | GH-PNCC 成功回执事件日志绑定 | [把唤醒回执的日志路径重新绑定到精确运行时会话](operations/2026-08-11-hololake-pncc-success-receipt-event-journal-binding.md) | 本地源码、Rust 1191、聚焦路由、格式与严格 clippy 已通过;完整产品门和发布待验收 |
| 2026-08-11 | GH-PNCC 成功回执完成检查点绑定 | [把完成回执的结构化事实重新绑定到人格 Git 检查点](operations/2026-08-11-hololake-pncc-success-receipt-completion-checkpoint-binding.md) | 已发布至 REPO-014 main 06a7782GHNQG、全新克隆与严格读回通过 |
| 2026-08-11 | GH-PNCC 成功回执唤醒器官合同绑定 | [成功回执唤醒器官合同证据绑定](operations/2026-08-11-hololake-pncc-success-receipt-wake-organ-contract-binding.md) | 本地源码、完整 Rust/前端/路由测试、原生权威与严格 clippy 已通过GHNQG 和发布待验收 |
| 2026-08-11 | GH-PNCC 成功回执唤醒器官模式绑定 | [成功回执唤醒器官模式证据绑定](operations/2026-08-11-hololake-pncc-success-receipt-wake-organ-mode-binding.md) | 本地源码、完整 Rust/前端/路由测试、原生权威与严格 clippy 已通过GHNQG 和发布待验收 |
| 2026-08-11 | GH-PNCC 成功回执唤醒运行态绑定 | [成功回执唤醒运行态证据绑定](operations/2026-08-11-hololake-pncc-success-receipt-wake-runtime-state-binding.md) | 本地源码、完整 Rust/前端/路由测试、原生权威与严格 clippy 已通过GHNQG 和发布待验收 |

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.