chore(process): 变异判死证明(RED-PROOF)随修复入库——含已引用未入库的存量回收
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- git, python
- Domain
- documentation, testing
Research direction
Start with docs/landing-and-acceptance.md sections 3 and 5, then inspect tests/unit/test_issue165_masker_complexity_bound.py, STORE-CONSOLIDATION.md, and the existing stores under scripts/mutation_replay/. Recover the referenced proof records for #165, #68, #79, #85, and #133 into docs/proofs/ with machine-readable evidence in docs/proofs/data/. Done means the documentation references resolve to tracked proof files and replay.py --store … --check-anchors can replay the stored evidence.
Written by the indexing model from the issue text.
Description
优先级 P2 · 依赖：无
基线 HEAD = e92d2f5
Summary
测试 docstring 引用的变异证明文件不在版本控制内。例证（命令可复跑）：
tests/unit/test_issue165_masker_complexity_bound.pydocstring：「变异（还原二次写法）由普通 FAILED 行杀死，见 RED-PROOF.md 的变异记录」——但git ls-files | grep -i 'red-proof'零命中，该文件不存在于任何已跟踪路径。STORE-CONSOLIDATION.md记录了 #68 / #79+#85 / #133 各单位的 store 与 kill 判定，但各单落地时的 RED-PROOF 正文同样未随修复入库（gist 编号只存在于 commit message）。
gist 是传输通道，不是台账：证明链的终点落在仓外，验收侧要靠 commit message 里的 gist 号去外部找回，gist 的可见性/存续变化即断链。
影响
- 分级验收 B 级 =「验证明」（docs/landing-and-acceptance.md §5）执行时，验收者需要仓内可核对的 kill 记录，目前这一步无法在仓内完成。
- 变异定义已入库（scripts/mutation_replay/），但「这些变异在某基线上确实被杀死」的运行证据不在——定义与证据分离。
建议
- 约定（已写入 docs/landing-and-acceptance.md §3，本单为执行）：证明文件随修复提交进
docs/proofs/<issue>-<slug>.md，机读 JSON 旁证放docs/proofs/data/。 - 存量回收按引用优先级：#165（docstring 已引用且当前 open）→ #68 / #79+#85 / #133（store 定义已在库，补运行证据）。
- 验收条件：
git grep -il 'red-proof' -- docs/能命中每个 docstring 引用对应的证明文件；replay.py --store … --check-anchors对入库证据可复跑。
边界
- 不重跑历史全量变异（只回收已有证明文本/记录）；不改 store 格式。
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 3h
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
[Device Support Request] HOBEIAN ZG-204ZL (Tuya PIR motion sensor with illuminance)Possibly taken @lenucksi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zigpy/zha-device-handlers#5493 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
drevendev/BeautifulRepo#42 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
writerslogic/holographic-memory#93 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
antoine-tena/kiln#47 ·
Maintainers usually reply within 1 day