fix: bind failure receipt error code

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

product-source/hololake-platform/architecture/HOLOLAKE-PERSONA-NATIVE-CODE-CHANNEL-20260810.md

@@ -186,6 +186,7 @@ successful_receipt_wake_organ_mode_evidence_binding_source_implemented: 100
 successful_receipt_wake_organ_contract_evidence_binding_source_implemented: 100
 successful_receipt_completion_checkpoint_evidence_binding_source_implemented: 100
 successful_receipt_event_journal_evidence_binding_source_implemented: 100
+failure_receipt_error_code_evidence_binding_source_implemented: 100
 general_purpose_persona_runtime_implemented: 0
 human_live_projection_implemented: 0
 hololake_integrated: 0
@@ -213,6 +214,10 @@ runtime_health: 0
 事件链。即使有人同步重算回执哈希，伪造终态事件或人格作者也会失败关闭，且不会把请求字段
 写入会话记录。
 
+失败回执中的稳定错误码也不能只通过字符格式自证。终态关闭后，运行时先把规范化错误码写入同一
+会话记录，再持久化失败回执；检查、恢复绑定、重放和绑定前复核都要求两者精确一致。即使同步
+重算外层哈希，也不能把真实失败改写成另一个合法机器码或虚构的成功授权状态。
+
 成功回执同样不能把“载荷哈希一致”当成语义真实。首次落盘、检查、恢复绑定和重放现在会把
 生命周期 schema、规范仓库、唤醒身份、节点、模型实例、器官、完整双层归因、完成类型、最终
 Git 提交、检查点、回执编号和完整事件链重新绑定到已验证的会话记录。同步改写载荷与哈希不能