Repository navigation
Date the two runtime history codes to 1.11.0 - #793
Conversation
runtime_history_budget_exhausted and runtime_storage_observation_incomplete were catalogued with since 1.10.1, a release that was never cut. The release workflow's catalog stamp refuses an added entry whose since names another release than the one being cut, so the 1.11.0 release stopped at "Stamp the run-failure catalog diff". Set since to 1.11.0 in docker/run_failure_codes.json, regenerate docker/run_failure_codes_diff.json (8 added since v1.10.0) and the registry (include/pineforge/run_failure_codes.hpp, src/run_failure_registry.inc), and update the ownership manifest and the catalog test that pin the value. With both codes in the 1.11.0 group, the generator numbers that group by name: the three unreleased codes 80-82 change places (pine_map_capacity_exceeded 80, runtime_history_budget_exhausted 81, runtime_storage_observation_incomplete 82). The selected-capacity codes keep 83-87 and every released number is unchanged. The numbers are on no wire: the C getters answer with names. tests/test_run_failure_code_numbers.py pins one 1.11.0 group instead of a 1.10.1 group that was never released. docs/pages/run-failure-codes.md replaces the "1.10.1 additions" sentence that ba14721 introduced: both codes are now counted and described with the other 1.11.0 additions (8 added in 1.11.0). Co-Authored-By: Claude Opus 5.5 <[email protected]>
![graphify-labs[bot]](https://avatars.githubusercontent.com/in/4356270?s=60&v=4){kind=small}
There was a problem hiding this comment.
Graphify reviewed this change.
No issues found by static checks — no coupling regressions or blocking issues in the code graph. That is not the same as safe to merge: see what was not checked.
Not checked: tests were not run; no formal proof of the changed code.
Graphify review — findings
Retags runtime_history_budget_exhausted and runtime_storage_observation_incomplete as first released in 1.11.0, since no 1.10.1 shipped, and regenerates the catalog so the 1.11.0 group is ordered by name. That renumbers the unreleased codes: pine_map_capacity_exceeded becomes 80, the history-budget code 81, and the storage-observation code 82, with the selected-capacity suffix still starting at 83. The generated catalog, diff JSON (with its new SHA), registry table, enum, ownership manifest, and the run-failure-codes docs page all change to match. The number-pinning tests now use a single 1.11.0 group instead of separate 1.10.1 and 1.11.0 groups.
No blocking issues surfaced.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 2098 functions depend on the 147 functions this change touches.
Health — grade B; 10 existing hotspot(s) in the area this change touches (pre-existing, not introduced here):
commit_input— 32 callers, 14 callees (high)verify_report— 18 callers, 10 callees (high)make_run_failure()— 12 callers, 10 callees (high)strategy_native_submit_v1()— 19 callers, 6 callees (high)put_ok()— 22 callers, 4 callees (high)consume_matched_request— 2 callers, 43 callees (high)begin_ready— 4 callers, 21 callees (high)run()— 1 callers, 74 callees (high)- …and 2 more
Verification — 2098 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 2059 function(s) in the blast radius were not formally verified this run
Summary
The 1.11.0 release dry run stopped at "Stamp the run-failure catalog diff":
Both codes were catalogued with
since1.10.1, a release that was never cut. They first ship in 1.11.0.This is one commit with the same tree as #792 (two commits), which it supersedes: #792's first commit replaced a docs sentence without naming it in its own message, so the doc-reverts check refused it.
Changes
docker/run_failure_codes.json:since1.10.1 -> 1.11.0 for the two codes.docker/run_failure_codes_diff.json: regenerated withscripts/gen_run_failure_catalog_diff.py --write(v1.10.0 -> unreleased: 8 added, 2 changed, 0 removed).include/pineforge/run_failure_codes.hpp,src/run_failure_registry.inc: regenerated withscripts/check_run_failure_codes.py --write-registry. The three unreleased codes 80-82 change places (pine_map_capacity_exceeded80,runtime_history_budget_exhausted81,runtime_storage_observation_incomplete82). The selected-capacity codes keep 83-87, and every released number is unchanged. The numbers are on no wire: the C getters answer with names.tests/test_run_failure_code_numbers.py: pins one 1.11.0 group instead of a 1.10.1 group that was never released.tests/ownership/manifest.v1.json,tests/test_run_failure_codes.cpp: the pinnedsincevalue follows.docs/pages/run-failure-codes.md: replaces the "1.10.1 additions" sentence that ba14721 introduced; both codes are counted and described with the other 1.11.0 additions (8 added in 1.11.0).No class, retryability or argument changes.
Verification
check_run_failure_codes.py: 87 codes, registry in sync.gen_run_failure_catalog_diff.py --checkwith release tags required: OK.check_doc_reverts.py(walk mode and--base 33503b88 --head): 0 unnamed deletions.--stamp --to-version 1.11.0 --previous-tag v1.10.0, now writes the stamped diff instead of refusing.🤖 Generated with Claude Code