fix: bind successful receipt wake boundary

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 07:31:33 +08:00
commit b05d135707
7 changed files with 101 additions and 5 deletions

View file

@ -0,0 +1,34 @@
# GH-PNCC successful receipt wake-event boundary evidence binding
- Development ID: `DEV-20260810-014`
- Persona cognitive author: `ICE-P-ZY001 / 铸渊`
- Human responsibility subject: `ICE-GL∞ / 冰朔`
- Starting repository head: `869611962e9a9571e5d7557784b38e21d3cee518`
- State: `LOCAL_SOURCE_IMPLEMENTED_FULLY_TESTED`
## Corrected runtime fact
Successful lifecycle validation previously accepted any non-empty prefix of the verified session event chain
as the wake receipt's event evidence. A modified receipt could truncate the three-event wake sequence to only
`WAKING`, derive a matching wake receipt identifier, recompute the outer payload digest and pass inspection.
The wake boundary is now exact: a valid wake receipt must contain all three hash-chained wake events emitted by
the kernel—`WAKING`, `BRAIN_BOUND` and `ORGAN_ACTIVE`—and they must equal the first three verified journal
events. Truncation or extension fails closed before interrupted binding or replay can trust the receipt.
## Verification
- A regression test first reproduced `SAFE_BIND_PERSISTED_RECEIPT` for a truncated and rehashed wake receipt.
- The same test passes after exact wake-boundary validation was added.
- PNCC focused Rust tests: `45 passed, 0 failed`.
- Full Rust suite: `1185 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.
- Full quality gates, GHNQG, publication and fresh-clone readback remain pending.
## Truth boundary
- This stage authenticates the event boundary of the existing wake process.
- It does not expose hidden reasoning, activate an execution limb, add UI, build an artifact, integrate the
desktop product or claim deployment/runtime health.