fix: bind successful receipt wake checkpoint

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

engineering/INDEX.md

@@ -33,6 +33,7 @@ Windows / macOS / Linux 构建机与安装包
 | 时间 | 版本 | 记录 | 状态 |
 | --- | --- | --- | --- |
 | 2026-08-11 | GH-PNCC 成功回执大脑入口证据绑定 | [从已验证会话重建并核对真实大脑入口](operations/2026-08-11-hololake-pncc-success-receipt-brain-entry-evidence-binding.md) | 本地源码、完整 Rust/前端/路由测试、原生权威与严格 clippy 已通过；GHNQG 和发布待验收 |
+| 2026-08-11 | GH-PNCC 成功回执唤醒检查点证据绑定 | [把唤醒时检查点路径绑定到不可变会话证据](operations/2026-08-11-hololake-pncc-success-receipt-wake-checkpoint-evidence-binding.md) | 本地源码、完整 Rust/前端/路由测试、原生权威与严格 clippy 已通过；GHNQG 和发布待验收 |
 | 2026-08-11 | GH-PNCC 安全回执绑定终态复核 | [检查后、绑定前重新验证回执与人格 Git 终态](operations/2026-08-11-hololake-pncc-safe-receipt-binding-terminal-revalidation.md) | 本地源码、完整 Rust/路由测试与严格 clippy 已通过；GHNQG 和发布待验收 |
 | 2026-08-11 | GH-PNCC 成功回执终态复核 | [成功回执持久化前重新验证终态证据](operations/2026-08-11-hololake-pncc-success-receipt-terminal-revalidation.md) | 本地源码、完整 Rust/路由测试与严格 clippy 已通过；GHNQG 和发布待验收 |
 | 2026-08-11 | GH-PNCC 重放仓库复核 | [幂等重放时重新验证人格 Git 状态](operations/2026-08-11-hololake-pncc-replay-repository-state-revalidation.md) | 本地源码、完整 Rust/路由测试与严格 clippy 已通过；GHNQG 和发布待验收 |

engineering/operations/2026-08-11-hololake-pncc-success-receipt-wake-checkpoint-evidence-binding.md

@@ -0,0 +1,38 @@
+# GH-PNCC successful receipt wake-checkpoint evidence binding
+
+- Development ID: `DEV-20260810-014`
+- Persona cognitive author: `ICE-P-ZY001 / 铸渊`
+- Human responsibility subject: `ICE-GL∞ / 冰朔`
+- Starting repository head: `56303382856de025199e75fdffa57be7507bb418`
+- State: `LOCAL_SOURCE_IMPLEMENTED_FULLY_TESTED`
+
+## Corrected runtime fact
+
+The successful lifecycle receipt already rebound the brain entry to the verified session, but the wake
+receipt's `checkpointPath` was not independently rebound. A modified receipt could therefore name another
+checkpoint path after recomputing its payload digest.
+
+New sessions now retain the exact canonical checkpoint path observed at wake as immutable session evidence.
+Inspection, interrupted binding and replay require the persisted wake receipt to name that same path. Legacy
+session records without the new field derive it from the persona manifest at the hash-chained wake Git head;
+if that evidence cannot be reconstructed, validation fails closed.
+
+## Verification
+
+- A regression test first reproduced acceptance of a forged wake `checkpointPath` after recomputing the
+  payload digest.
+- The same test passes after immutable wake-checkpoint evidence binding was added.
+- A compatibility regression proves a legacy session without the new field reconstructs the same evidence from
+  the hash-chained wake Git head.
+- PNCC focused Rust tests: `44 passed, 0 failed`.
+- Full Rust suite: `1184 passed, 2 ignored`; integration test: `1 passed`.
+- Routing suite: `29 passed, 0 failed`; formatting, strict clippy and diff checks passed.
+- Frontend lint and TypeScript checks passed; full Vitest suite: `5008 passed, 0 failed`.
+- Guanghu native authority: `PASS_100`; native core: `15 passed` with 100% lines and functions.
+- GHNQG, publication and fresh-clone readback remain pending.
+
+## Truth boundary
+
+- This stage authenticates which existing checkpoint file was mounted when the persona woke.
+- It does not change the promoted completion checkpoint, expose hidden reasoning, activate an execution limb,
+  add UI, build an artifact or claim deployment.