docs: reconcile narrative docs with v1.9.5 reality#60
Merged
Conversation
- Update standards-doc count to 18 in .cursorrules, AGENTS.md, CLAUDE.md, and CONTRIBUTING.md (was 9 or 17 depending on file) - docs/index.html: standards grid expanded from 8 to 18 cards matching standards/README.md order; footer version updated from v1.5.0 to v1.9.5; standards count badge corrected to 18 - ROADMAP.md: Current Status updated to v1.9.5 with accurate prior-milestone list; Release Plan table updated with six Released range rows for v1.7.x through v1.9.x; speculative v1.7.0, v1.8.0, v1.9.0 narrative sections replaced with accurate content derived from git history and release notes; new sections added for v1.7.1-v1.7.5, v1.8.1-v1.8.5, and v1.9.1-v1.9.5 Patch range rows in the Release Plan table are deliberate: they group closely related patch series by theme rather than listing each patch individually. This is not a per-patch policy but a readability choice for series that shipped in rapid succession. standards/drift-checker.config.json intentionally left unstaged (Windows CRLF phantom, no content change). Signed-off-by: fOuttaMyPaint <154358121+TMHSDigital@users.noreply.github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
github-actions
Bot
added
the
documentation
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
.cursorrules(was 9),CONTRIBUTING.md(was 9),AGENTS.md(was 17), andCLAUDE.md(was 17).README.mdandstandards/README.mdwere already correct.docs/index.html: standards grid expanded from 8 to 18 cards instandards/README.mdQuick Reference order; count badge updated from 8 to 18; footer version updated from v1.5.0 to v1.9.5.ROADMAP.md: Current Status updated to v1.9.5 with accurate prior-milestone list; Release Plan table updated with six Released range rows for v1.7.x through v1.9.x (replacing three Planned rows); speculative placeholder sections for v1.7.0, v1.8.0, and v1.9.0 replaced with content derived from git history and release notes; new range sections added for v1.7.1-v1.7.5, v1.8.1-v1.8.5, and v1.9.1-v1.9.5.The patch-range rows in the Release Plan table group closely related patch series by theme rather than listing each patch individually. This is a readability choice for series that shipped in rapid succession and is not intended as a per-patch row policy.
standards/drift-checker.config.jsonis intentionally not staged (Windows CRLF phantom, no content change).Verification
python scripts/sync_from_registry.py --checkexits 0 (registry not changed)docs:commit prefix, no VERSION bump requiredTest plan
docs/index.htmlstandards grid has 18 cards in the correct orderdocs/index.htmlfooter shows v1.9.5