Repository navigation
docs(plan): record V0.6 exit conditions 1 to 4, the v0.6.0 release and its checks (plan r21, r22) - #41
Merged
Conversation
…it conditions 1 to 4 (plan r21) Conditions 1 to 5 of the V0.6 milestone now have a result. Condition 6 (the tag) is the only one left, and the owner decides who sets it. - plan: status, current state, scope numbers, the result of each exit condition, next steps, decision 20 (done in #39, with the correction about the harness floor of pi-dynamic-workflows-py), the section index and the revision log - execution log: new section 10.24 (version numbers, the merge, conditions 1 to 4 with method and numbers, what is not verified) - docs/baselines/tui.md: release size 406,911,320 B, build time 895 s, dry-run result No code, no workflow and no manifest change.
…x literal asterisks (plan r22) Record what happened after the tag: the tag v0.6.0 on 5f73e07, the Release run (six jobs, first try), PyPI (seven packages; pi-mcp-py is a new project), the GitHub Release (16 assets), the two binaries, the clean-venv install, the pi-mcp tests against the PyPI wheels, and the PTY scripts against the released zypi. Plan: status, current state, V0.6 status and exit conditions 1, 3, 4 and 6, known issues, next steps, decision 20, section 10 index, revision log. Execution log: new section 10.25. Baseline: the release numbers of v0.6.0. Also fix 12 bold spans in the plan and the execution log (r17 to r21 text): GitHub keeps the asterisks of a span when its closing ** follows a CJK punctuation mark and a letter follows it. The mark now goes outside the span. Docs only. No code, no workflow change.
zy1233
changed the title
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
Plan r21 and r22. The plan, its execution log and the baseline now record the whole V0.6 release: exit conditions 1 to 5 (r21), and condition 6 with the checks after the tag (r22). Docs only: 3 files, +220 / −30 lines.
V0.6 at the tag
v0.6.0(on5f73e07):CI(run) andTUI CI(run) pass on5f73e07CHANGELOG.md, 1 is a race in the probe (#40, merged)v0.6.0on5f73e07; theReleaserun passes (6 jobs, first try, 20 m 22 s); GitHub Release with 16 assetsThe checks after the release (r22) found no defect:
pi-mcp-py0.1.0 is a new project and its first upload worked; the 14 files have the same SHA-256 as the Release assetsuv pip checkpasses; the 4 extension entry points loadpi-mcptests against the PyPI wheelszypiand PyPI agentsmoke23/23;exit_matrix12 cases;resume_matrix --strict16 pass;mode_probe15 rows as expected;status_line_probe4/4Left open, and not changed here (the owner decides):
release.ymlbuilds Linux onubuntu-latest, which GitHub moves to Ubuntu 26; the glibc floor is not in the docs; Node.js 20 warnings; Trusted Publishing on PyPI. Not verified: the macOS binary was never run; the PyPI install was tested on Linux only.The PR also fixes 12 bold spans in the plan and the execution log (text of r17 to r21). GitHub keeps the asterisks of a span when its closing
**follows a CJK punctuation mark and a letter follows it. The mark now goes outside the span.Evidence
Before: GitHub shows the asterisks of 12 spans, for example
**更正 r17：**CI 的.After: the same check finds 0 such spans in the plan, the log, the baseline and
CHANGELOG.md. I rendered each file with GitHub's own markdown API (gh api markdown) and searched the output for a literal*.Releaserun (jobs, times, cache), the PyPI JSON API and the GitHub Release API (sizes, SHA-256, assets), and the files I ran the scripts against.ruff check .andruff format --check .pass.Merge Danger
Door: two-way.
Blast Radius: documentation only. No code, no workflow, no manifest. The tag does not move. This PR merges after
v0.6.0and after #40; neither changestui/orpackages/, somainisv0.6.0plus a 3-line probe fix and these docs.