Siblings of #4725: readiness report inputs

已关闭
#5,229 5 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
18/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
devtools

调研方向

The work touches the per-estate readiness report, which reads from cics_census.blockers() and proof_blockers.py; the issue asks for a new proof-level ranking section and for narrowing the oracle-caveat list to reached entries. It depends on the evidence report described in definition_of_done.md section 3, which the payload does not show, and on the sibling issue #4725. Done means both sections render in the report and the caveat list reflects reached entries only, which likely needs a test on a burned estate.

由索引模型根据 Issue 内容生成。

描述

enhancement legacy-modernization priority: high scope:infra

Siblings of #4725 (class: readiness report inputs — what the per-estate readiness report reads from committed tool outputs). Found in the review of PR #5228.

  • Proof-level ranking: the report ranks the rules that stop programs translating whole (cics_census.blockers()), but not what stops a whole program from being proven (proof_blockers.py). Add that ranking as its own section. (#6251)
  • Reached caveats: the oracle-caveat list is an upper bound (every register entry a program's commands name). Narrow it to the entries a program actually reaches once the evidence report measures that (definition_of_done.md section 3).

Not a gap (policy): non-burned estates get no per-program report.

Siblings: #4725

🤖 Generated with Claude Code

主要语言
Python
星标
57
派生
11
平均合并
1 小时 26 分钟
30 天内合并 PR
974

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

squid-protocol/gitgalaxy 的其他 Issue

查看 squid-protocol/gitgalaxy 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。