Repository navigation
fix: enforce documented repository safety contracts - #95
Conversation
Cross-Review 检视意见(已核实)并行独立评审(DeepSeek / GLM / Kimi,3/3 quorum)后,我对所有候选意见逐一对照 PR 源码与基准差异进行了验证。以下 3 项为可复现/可证实的发现,按严重度排序。其余候选(LFS CI 内容校验、release tag base 退化、双失败未覆盖、性能权衡、Windows 矩阵缺失、 1. [medium] 导入回滚 fallback 存在符号链接竞态,可能覆盖任意文件
2. [low] 新建 focus/config 文件时短暂清空进程级 umask
3. [low] 无参
|
|
Thanks for the cross-review — all three findings reproduced and are addressed in the latest push ( 1. Import rollback symlink race (medium) — fixedConfirmed reproducible. Root cause: 2. Umask transient (low) — fixedConfirmed reproducible in a concurrent thread. Replaced the 3.
|
Description
Related Issue
Fixes #94
Testing
PYTHONPATH=src pytestruff check .black --check .actionlintgit diff --checkChecklist
Snapshot Runtime Provenance
Snapshot provenance decision: no-update
Snapshot provenance no-update reason: Changes under the snapshot runtime scope only update agent guidance; runtime origin and copied-code history are unchanged.
Additional Notes
Committed pickle fixtures are now verified against reviewed provenance, SHA-256 digests, and expected sizes before pytest collection.