Repository navigation
docs(plan): set the V0.5 release milestone from the stripping status (plan r12) - #16
Merged
Merged
Conversation
…(plan r12) Define what V0.5 is from the state of the Rust agent runtime removal on main (4fc028a; CI and TUI CI are green on it): the untagged 0.5.0 plus the TUI side of r3-r11. The scope follows the status table. The plan now holds the six exit conditions, the known issues that ship with the release and the items that do not ship. The evidence is in section 10.15 of the archived execution log. Found while checking the release path: - release.yml had no manual trigger, and its macOS arm64 job had never run in a release (PR #14 adds the trigger); - the CHANGELOG had no entry for the removal itself (PR #15 adds it); - zypi --version and "is this a release build" share GROK_VERSION, so the obvious fix for the version string would turn folder trust on (new plan decision 16). The follow-ups that were chosen are recorded here, not done here: - release size (condition 2): 420,767,096 B, 10.6 % below v0.4.0, from the release_baseline run 38221952524; docs/baselines/tui.md has the numbers; - dry run (condition 3): run 38223353755, started from the PR branch, built Linux x86_64 and macOS arm64 and published nothing; - release notes (condition 5): PR #15; - decision 16: option (a) chosen, not implemented. The comparison with v0.4.0 (condition 4) is not done. WSL does not start on this machine, so no release binary was run. A GitHub milestone v0.5.0 was created next to this change. Nothing is attached to it. Nothing under tui/, packages/ or .github/ changes.
…entry in #15, condition 4 skipped) After the first push of this PR the owner answered three questions: - Decision 16 is done now, in its own PR (#17, stacked on #15): the plan item moves from "decided, not done" to "done", the known issue about the version numbers leaves the list (it comes back only if #17 is not merged before the tag), and the "not verified" text now says what the CI of #17 proved and what nobody has seen (the output of `zypi --version`). - The macOS arm64 binary entry went into #15 (CHANGELOG, README and docs/TUI-AND-CODE-AGENT.md, "built by CI, nobody has started it"): condition 5 says so, with the new entry counts (20 new entries; the release body is 45,076 B, and 45,855 B after #17). - Condition 4 (compare with v0.4.0) is skipped. V0.5 does not wait for it. The execution log gets a "续 2" part in section 10.15 with the answers, what changed, the tests (6 new, 8 mutations caught), the Windows and Linux numbers and the CI runs of #17. The index, the revision log and the link definitions follow. Only documents change.
…L2 (plan r12, part 3) #15, #17 and #14 are squash-merged (59545c1, d57fd9b, 0efd400). The plan and the execution log say so, and main is now 0efd400 in the current-state text. WSL2 works again. On 0efd400: Linux pytest 2,539 passed / 16 skipped / 31 deselected; `zypi --version` prints `zypi 0.5.0 (0efd400)` (a debug build on ext4, not the CI release-dist artifact); the PTY scripts pass, except one check of smoke.py, which is out of date since #12 (22/23). Section 10.15 gets a part 3 with these results and the leftovers; the "not verified" lines that said "WSL does not start" are brought up to date. Only documents change.
zy1233
force-pushed
the
docs/v0.5-milestone
branch
from
October 12, 2026 10:25
712d47d to
6f21478
Compare
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
This PR records the V0.5 release in the plan: what the release is, what must be true before the tag, and what is known to be wrong. It is revision r12 of the plan for the removal of the Rust agent runtime. Only documents change.
The milestone is on GitHub: v0.5.0. Nothing is attached to it, because the conditions are written in one place (the plan).
The three PRs that do the work of the conditions are merged before this one: #15 (
59545c1), #17 (d57fd9b) and #14 (0efd400), in that order, each as one squash commit. This branch is rebased onto0efd400.docs/PLAN/PLAN-RUST-AGENT-RUNTIME-REMOVAL.md: a new section "发布里程碑 V0.5" (what the release is, six exit conditions, known issues, what is not in it). The status, the next steps and the "not verified" list start frommainat0efd400. Decision 16 is new, and fix(release): zypi --version and ACP agentInfo show the release version (plan decision 16) #17 did it.docs/PLAN/archive/PLAN-RUST-AGENT-RUNTIME-REMOVAL-EXECUTION-LOG.md: section 10.15, with the reasons, the figures, the follow-up work, your three answers (part "续 2"), and the merges and the WSL2 checks (part "续 3").docs/baselines/tui.md: the numbers of the new release measurement.The six exit conditions
CIon0efd400,TUI CIond57fd9b(0efd400differs from it only inrelease.yml). Look again on the commit that gets the tag.v0.5.0After the merges, with WSL2 working again
You fixed WSL. These runs are on
0efd400(details: section 10.15, part "续 3").pytest: 2,539 passed / 16 skipped / 31 deselected.zypi --versionprintszypi 0.5.0 (0efd40071ca0), exit 0. That is a debug build on ext4. It is not therelease-distfile that CI builds.agentInfo.versionis0.5.0in a venv installed from the merged tree. An older editable install keeps the version it had when it was installed (the old/tmp/wsl-venv: 0.2.0).exit_matrix.py12/12,print_exit.py4/4,resume_matrix.py10 PASS / 3 GAP (the known gaps),mode_probe.pyas in feat(tui): offer only the permission modes the agent honours (plan 1.P3 (a), plan r10) #12,status_line_probe.py4/4,net_audit.py --mock13/13 and with--no-network13/13.smoke.pyis 22/23. The failing check, "status line follows the switch", waits for the textSecond modelfollowed by a·. The screen shows the right label,Second model, the session file has themodel_change, and the next turn answers. The check is out of date since feat(tui): offer only the permission modes the agent honours (plan 1.P3 (a), plan r10) #12. My inference, not tested on an old build: the·came from theautoflag, which feat(tui): offer only the permission modes the agent honours (plan 1.P3 (a), plan r10) #12 no longer shows in the normal mode. It is a script problem, not a TUI problem. It is not fixed here. The fix is one regular expression.Decisions for you
[0.5.0]in the changelog is 2026-10-12. Change it on the day of the tag. The known issues become public release text.Not verified
release-distbinary that CI builds; only a debug build ofmainran. Nobody ran the macOS binary. The changelog, the README and the TUI guide say so.iflines ofrelease.ymlhave run only on their false side. A tag push runs the true side.smoke.py --sandbox, or the whole Rust test manifest on WSL2. CI ran the manifest ond57fd9b: 8,665 passed / 0 failed / 22 ignored.pi-configcould stop working for a user config that needs a version above0.5.0. I found no default config that does, and I cannot see user configs.Verification
ruff check .andruff format --check .: clean (nothing in Python changes).gh run view) and from the output of the runs on WSL2.--match-head-commit. docs(release): fold [Unreleased] into [0.5.0], add the missing entries and the macOS binary #15 and fix(release): zypi --version and ACP agentInfo show the release version (plan decision 16) #17 merged with the tree that CI had tested (fix(release): zypi --version and ACP agentInfo show the release version (plan decision 16) #17 was rebased ontomainafter docs(release): fold [Unreleased] into [0.5.0], add the missing entries and the macOS binary #15, andgit diffagainst its tested tip was empty). ci(release): add a manual dry run that builds everything and publishes nothing #14 merged onto a newermain, soCIran again on the result,0efd400, and passed.