docs: the install instructions pinned v1.2.1 on a 2.0.0b4 package - #125
Merged
Conversation
The canonical getting-started page told every new user to install v1, and nothing gates it: test_docs_site.py only parses python fences and docs-check.yml only asserts the build produced a page. The release skill now greps docs-site for a pinned version at preflight. Also drops the ssh URL — the repository is public, so credentials were never needed.
sagi5060
added a commit
that referenced
this pull request
Aug 6, 2026
Three real conflicts, all resolved as a union rather than by taking a side: - Runtime._bind: #116 binds a Reporter and its per-run report buffer; this slice binds the Gate with the poll interval #85 added. Both now happen in the one binder, and _with_gate — which the auto-merge replaced with #116's _bind — is gone, with its two remaining call sites (resume, resume_run) moved over. - Runtime._play: this slice folded run/resume's two inlined bodies into one; #116 had added its report drain to both copies. The drain now lives once in _play, so all three openings (start, resumed interrupt, lifted pause) drain identically — and resume_run gets #116's reporting for free rather than silently missing it. - CHANGELOG: both sides added an Added entry. Both kept. Also removed a duplicated ### Removed block (#118's entries appeared twice) left by an earlier merge. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 6, 2026
Closed
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
1 participant
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.
Found by the #71 audit.
docs-site/content/getting-started.mdx— the canonical getting-started page — told every new user touv pip install …@v1.2.1, on a package that is at2.0.0b4. So the documented path installed v1.Nothing gates it, which is why it rotted:
test_docs_site.pyonly parsespythonfences, anddocs-check.ymlonly asserts the build producedout/index.html.docs/delivery/docs-site-plan.mdpredicted exactly this and asked for a release-checklist item that was never added — so the release skill's preflight now grepsdocs-site/content/for a pinned version.Also drops
ssh://git@forhttps: the repository is public, so the credentials the old instructions implied were never needed.Docs and a skill file only — no package change, no test change.
Judgment ledger
pyproject.tomlwould fail ondevfor the whole window between a release and the next docs edit, and pinning "latest" in the docs is not what we want either — the install line should name a released tag. A preflight step puts the check where the version actually changes.v1.2.1reference alone. The remaining ones (docs/agentdeck-prd.md,docs/project-brief.md,docs/delivery/docs-site-plan.md) are historical or normative statements about the frozen baseline — "v1.2.1 projects load unchanged" is a requirement, not a stale pin.