v1.0.0 docs: post-v1.0 staleness sweep (3 stragglers)#335
Merged
Conversation
…count, spec/31 era) Three quick copy flips the post-v1.0 documentation staleness scan surfaced that didn't make it into the PR #334 /ship + /document-release sweep. All doc-only; no code, no tests, no version bump. - ROADMAP.md lines 8-17: section header reframed from "remaining backend protocols" to "backend protocols shipped"; "Eleven of twelve" flipped to "Twelve of twelve"; MCPServerRegistryBackend added to the list; table Status flipped from "Planned" to "Shipped (v1.0.0)"; footer reframed from future-tense to PyPI-install present-tense. - docs/deployment/programmatic.md lines 727-735: backend count flipped Eleven to Twelve; MCPServerRegistryBackend added to the parenthetical list; "one remains for v1.0" clause removed; numbered spec list extended to include spec/36. - docs/spec/31-llm-backend.md line 3: status line "as of v0.13 era" updated to "as of v1.0". CHANGELOG [Unreleased] gets a brief Documentation note pointing back to this sweep. These are the only stale references the audit found across 90+ markdown + 5 HTML/SVG explainer artifacts. All other v1.0-relevant docs were already updated in PR #334 (the v1.0 release PR) or by the document-release subagent during the v1.0 ship. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
Three quick copy flips a post-v1.0 documentation staleness scan surfaced that didn't make it into the PR #334 v1.0 release sweep. All doc-only; no code, no tests, no version bump (stays at v1.0.0).
ROADMAP.mdlines 8-17: section header reframed from "remaining backend protocols" to "backend protocols shipped"; "Eleven of twelve" flipped to "Twelve of twelve"; MCPServerRegistryBackend added to the list; table Status flipped from "Planned" to "Shipped (v1.0.0)"; footer reframed from future-tense to PyPI-install present-tense.docs/deployment/programmatic.mdlines 727-735: backend count flipped Eleven to Twelve; MCPServerRegistryBackend added to the parenthetical list; "one remains for v1.0" clause removed; numbered spec list extended to include spec/36.docs/spec/31-llm-backend.mdline 3: status line "as of v0.13 era" updated to "as of v1.0".CHANGELOG.md[Unreleased] gets a brief Documentation note pointing back to this sweep.How this slipped through
PR #334 ran the document-release subagent in Step 18 which caught and updated
docs/methodology.md,CONTRIBUTING.md, anddocs/getting-started.md. The subagent was diff-scoped (only looked at files the v1.0 release diff touched) and didn't crawl the rest of the doc surface. A fresh post-v1.0 audit caught these 3 outliers.Pre-Landing Review
Doc-only diff (10 lines insertions, 10 deletions, 4 files). Manually reviewed inline; no behavior change. No specialist dispatch needed.
Test Coverage
No code paths touched. Test suite re-run after edits: 3,270 passed + 56 skipped + 0 failures (unchanged from main HEAD).
Audit context
The full doc staleness audit (90+ markdown + 5 HTML/SVG explainer artifacts scanned) found exactly these 3 stale files. Notably the visual explainer pages (
docs/explainer/leader-brief.html,docs/explainer/index.html, hero SVGs) were already current — no version text embedded, no stale architectural claims, leader-brief.html was updated Jun 4 (within the v1.0 release window).Test plan
🤖 Generated with Claude Code