Conversation
对照七项官方来源和现有恢复链路,区分文件提交、状态恢复、NPC 重建及旧请求隔离。修正当前存档版本说明,记录提交后重建失败的独立验收。仅文档变更,未运行 Unity 或真实模型。Refs #90.
This was referenced Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
此前装配审计把依赖换绑与读档后的运行代次放在同一生命周期说明中,尚未细分存档数据恢复与 NPC 重建的失败边界。本 PR 对照七项官方来源及当前代码,明确普通读档保留服务引用、恢复权威状态后再通知 NPC 重建,并补入分阶段验收矩阵。
资料足够指导换绑失败修复和读档对照;完整 NPC 经历/承诺持久化语义仍待决定。源码追踪另发现提交后的通知异常可能中断重建,已登记明确读档提交后重建失败的处理边界,没有把它计为已复现或已修复。
codex/npc-session-composition-boundary为 base 的堆叠 Draft PR,暂不合并。Standards
独立复核四份文档,无需修正的规范违例或结构异味。当前代码、外部机制、设计推论和未运行验收分别标明。
Spec
独立复核无待修正发现。七项官方来源、实际恢复链路和后继验收一致;换绑任务的补充条件与重建失败任务的原生依赖已核对。