Skip to content

docs: remove beta labels and make CLI release guidance durable - #51

Merged
fakayser merged 1 commit into
mainfrom
feature/release-independent-docs
Nov 4, 2026
Merged

fakayser merged 1 commit into
mainfrom
feature/release-independent-docs

Conversation

@fakayser

@fakayser fakayser commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

CLI documentation still labels the current API as beta and links to the old documentation feature branches. Default installation to the current stable wheel release, use main for maintained references, and explain how readers select the matching version tag for an installed runtime. Rename the API route heading and update its internal link.

Preserve the historical beta.3 test-fixture pin and dated evidence. No API, schema, generated model, dependency or submodule changes are included.

Validation: Node 24.22.1; all 7 documentation-check tests pass; 20 Markdown files checked with no problems; git diff --check passes.

An existing link in docs/cli-agent-contract.md to the not-yet-published central cli-sample-workflow.md remains outside this documentation cleanup.

Companion PRs: Handbook #5 and Frontend #66. Feature branches are intended for manual maintainer merge.

@fakayser
fakayser merged commit b8d062e into main Nov 4, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant