docs(knowledge): 沉淀 R-00259 两条 lesson - #4
Merged
Merged
Conversation
- 上游裁决点名更正某条事实时，同节其余「现状实测」陈述必须一并复跑。 同批陈述出自同一次快照，一句过期则其余大概率同样过期；本卡上该类 漏检出现三次、分属交付方/QA/TD 三个角色。TD 已同步落架构仓 lessons。 - 「一直没出过问题」有两种原因——守护有效，或根本没机会触发。环境变化 会让原本由环境免费执行的约束第一次真正需要被执行（S3③ 架构测试即例）。 准入说明：第一条按「同类第二次出现」准入成立（三次、三角色）；第二条属 首现，按用户 2026-08-29 明确要求破例收录，条目内已自标并附清出条件。 Co-Authored-By: Claude Opus 5 <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
1 participant
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.
内容
R-00259 更正交付收口后的知识沉淀，两条 lesson 落
.spec/knowledge/lessons.md（该文件此前「条目」节为空）。1. 上游裁决点名更正某条事实时，同节其余「现状实测」陈述必须一并复跑
同批写下的陈述出自同一次快照——一句过期，其余大概率同样过期。「某处被发现失真」是关于该段落维护状态的信号，不只是关于那一句。
本卡上该类漏检出现三次、分属三个角色：交付方写入时未标注快照批次；QA 核销只核被点名项；TD 复核表把「generated 面 6 包」判为 ✅ 属实（只核了包数，放过同节 catalog-only 口径，而后者才影响设计结论）。
规避是可验证行为：以段落为单位复跑，不以被点名的句子为单位，并把段落日期戳与上游锚点 SHA 一并更新——只改被点名句而保留旧日期戳等于给过期内容盖新章。
TD 已同步把本条落进架构仓
.spec/knowledge/lessons.md。2. 「一直没出过问题」有两种原因——守护有效，或根本没机会触发
S3 验收项③「不引用
Lumio.Gen.*有架构测试」的原始理由（netstandard2.1引用不到）在架构仓改双 TFM 后消失。默认直觉是「前提没了 → 约束多余」，实际相反：此前该约束一直由编译期屏障免费执行，双 TFM 后两个目标都能引用，这条分层纪律的唯一兜底才第一次真正落到该测试上——不是变多余，是变更必要。准入说明（本文件自带的门槛）
lessons.md的收录准入写明「同类问题第二次出现才收录——单次偶发不收，防噪音」。逐条对照：验证
node .spec/tools/spec-lint.mjs→spec-lint: OKnode --test .spec/tools/spec-lint.test.mjs→ tests 13 / pass 13 / fail 0repository-policy.yml逐条复跑通过；sha256sum -c docs/architecture/.baseline.sha256→ OK（exit=0，仓根执行）knowledge/README.md导航已含lessons.md一行，无需改动（spec-lint 的导航覆盖校验通过即为证）。纯文档改动，走
AGENTS.md快速模式收口白名单，未派 reviewer。🤖 Generated with Claude Code