fix: bind successful receipt brain entry

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 06:38:59 +08:00
commit 5630338285
7 changed files with 95 additions and 4 deletions

View file

@ -0,0 +1,32 @@
# GH-PNCC successful receipt brain-entry evidence binding
- Development ID: `DEV-20260810-014`
- Persona cognitive author: `ICE-P-ZY001 / 铸渊`
- Human responsibility subject: `ICE-GL∞ / 冰朔`
- Starting repository head: `a6504ca74971998d679da13c467022a8e04bbeae`
- State: `LOCAL_SOURCE_IMPLEMENTED_FULLY_TESTED`
## Corrected runtime fact
The successful lifecycle receipt previously rebound identity, repository, events, attribution and completion
evidence to the verified session, but did not rebind the wake receipt's `brainEntry`. A modified receipt could
therefore claim that another brain file had been started if its payload digest was recomputed.
Inspection, interrupted receipt binding and replay now resolve the canonical brain path from the verified
session repository plus its recorded relative brain entry. The successful receipt must name that exact file or
fail closed with `PERSONA_LIFECYCLE_COMPLETION_EVIDENCE_MISMATCH`.
## Verification
- A regression test first reproduced acceptance of a forged `brainEntry` after recomputing the payload digest.
- The same test passes after canonical brain-entry evidence binding was added.
- PNCC focused Rust tests: `42 passed, 0 failed`.
- Full Rust suite: `1182 passed, 2 ignored`; integration test: `1 passed`.
- Routing suite: `29 passed, 0 failed`; `cargo fmt`, strict clippy and diff checks passed.
- Frontend lint, TypeScript check and full Vitest suite passed; Guanghu native authority: `PASS_100`.
- GHNQG, publication and fresh-clone readback remain pending.
## Truth boundary
- This stage authenticates which existing brain file the successful wake receipt says was bound.
- It does not add model inference, activate an execution limb, add UI, build an artifact or claim deployment.