Repository navigation
feat(engine): 事实型交接不再依赖评估启用 - #306
Merged
Merged
Conversation
status 现在只要有确定性异常就发布事实型交接，同意只影响相邻的 attn 块 （enabled、固定 reason、assessment: assessed/pending/unavailable）。attn_path 的含义从“用户已启用”改为“当前有异常”，agent 不必再读设置文件猜测。 同时修正遗漏的提示文案：tip、doctor 行与固定原因提示改为 config/on，而不是 已删除的 enable/preview。 验证：go test -count=1 -timeout=8m ./...；隔离 BERTH_HOME 验证无配置时 status 仍发布 attn_path 且 attn.enabled=false；verify-attention-handoff.py Co-Authored-By: Claude Code <noreply@anthropic.com>
cli 双语对与 architecture 更新为“事实型交接总是发布，attn 块说明能否评估”， 并在 agent 字段表加入 attn 块。 验证：python3 scripts/check_docs.py；check_skill_contract.py（85 个锚点） Co-Authored-By: Claude Code <noreply@anthropic.com>
status 新增 attn 块后，锚点提取测试的期望集合需要包含它；skill 文档已通过 `attn_path` 覆盖该锚点。 验证：python3 scripts/check_skill_contract_test.py；check_skill_contract.py Co-Authored-By: Claude Code <noreply@anthropic.com>
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.
第四步（收尾）:把确定性交接与模型同意解耦，并修正上一步遗漏的提示文案。
改了什么
status只要出现确定性异常就发布事实型交接，与是否启用评估无关；发布本地事实不发送任何数据。status --json新增attn块：enabled、固定reason、assessment（assessed/pending/unavailable）。attn_path的含义从“用户已启用”改为“当前有异常”。attn.enabled再决定是否运行attn assess。attn enable/attn preview，现在改为attn config/attn on/assess --dry-run。attn_test.go改为在新契约下验证：无同意仍发布、有同意显示 pending、关闭后交接仍在。验证（已执行）
cd engine && go test -count=1 -timeout=8m ./...BERTH_HOME实跑：无设置时失败服务仍产生attn_path，输出attn: {enabled: false, reason: no_key, assessment: unavailable}。mage build、scripts/check_docs.py、scripts/check_skill_contract.py（85 个锚点）、verify-attention-handoff.py --choice continue_without_action。未执行
契约变更
读取
status --json的 agent 需要把“有attn_path= 已启用”改为“有attn_path= 有异常；能否评估看attn”。这是本轮最后一个契约变更。🤖 Generated with Claude Code