Repository navigation
docs(plan): record r26 - the merges before v0.7.0 and the v0.7.0 release - #56
Merged
Merged
Conversation
Execution log: new section 10.29 (PRs 45-48 and 55, the web PRs 50-54 as facts only, the v0.7.0 release and its checks, what stays unverified); contents list, section 10 title, intro and revision log updated. Plan: header and current state at r26, new section 'Release milestone V0.7', the next steps and the unverified list (download-artifact@v7 is verified now; three new entries), index row, revision summary, link definitions. Docs only. This record was r24 / section 10.27 before the stack. PR 58 and PR 59 hold r24 / 10.27 and r25 / 10.28 and merge first, so this record takes the next numbers.
This was referenced Oct 31, 2026
zy1233
added a commit
that referenced
this pull request
Oct 31, 2026
…ne on main (#67) Ten PRs (#56 to #65) were merged into main with one `gh stack merge` (stack #66, squash). main went from 7cb9e23 to 032ddbb. - Execution log: new section 10.31 (stack order, the eight rebuilt heads, conflicts, checks before the merge, CI on main), contents list, section 10 title and intro, revision log. - Plan: header and "current state" at r28; phase D started; D.5 and D.8 ticked; the sentences that said "not merged" now say "merged"; the section 10 index; the revision summary; link definitions. - docs/baselines/tui.md: numbers from the TUI CI run on main (8,558 passed, residue ceilings 239 and 282, test and job times). Documents only.
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
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.
Summary
Records r26 (the number was r24 before the stack): what was merged after r23, and how v0.7.0 was released. Documents only.
Round numbers
This PR was written as r24 / section 10.27. PR #58 and PR #59 (from the other session) also hold r24 / 10.27 and r25 / 10.28, and they are at the bottom of the stack (#58, #59, #56, #57, #60 to #63, #64, #65). So this PR is now r26 / 10.29 and its base is the branch of #59. The text is the same; only the numbers, the anchors and the lists of rounds changed (section 10 title and intro, the "not in V0.6" paragraph, the index rows, the revision log).
Evidence
download-artifact@v7as never run.After: the plan says "r26". The
Releaserun 41049069065 (six jobs, all green) is the first run ofdownload-artifact@v7, so the entry is gone.ghand the PyPI JSON API: PR sizes and merge times, run ids and durations, the 16 release assets, the seven package versions. The numbers of ci(tui): run only python_agent_e2e for agent-only changes; keep the rust-cache key across image updates #48 are from its PR body.[text][ref]of the plan has a definition; every](#anchor)of both files has a heading; the new anchors follow the GitHub rules.gh api markdown(gfm) shows no stray**.ruff checkandruff format --checkpass. No code changed, so no test ran.Merge Danger
Door: two-way.
Blast Radius: documentation (two files under
docs/PLAN/).