sync: refresh MCP resource snapshots for the accessibility suite (A1–A9)#2
Merged
Merged
Conversation
The scheduled resource-drift check now fails against agent-ready.dev: the live checks/llms.txt/specs resources gained the accessibility suite (PR #178–#182 on the main repo) but the embedded snapshots were stale. - resource-content.ts: re-render CHECKS_MD (adds the Accessibility checks A1–A9 section), LLMS_TXT (accessibility sub-score line), and SPECS_MD (adds the Accessibility spec family + the newer payments/ACP specs that had also drifted). Rendered from the main repo's buildChecksMarkdown()/LLMS_TXT/buildSpecsMarkdown(). - resources.ts: the `checks` resource description now names the accessibility category + an A-series id example (was "site, page, llms.txt, protocol" only). - README: note the separate accessibility sub-score. check-resource-drift.mjs now passes (all 4 snapshots match live); tsc + 29 tests green. Methodology resource unchanged (it reports only the readability + llms.txt sub-scores both live and here — no drift). Co-Authored-By: Claude Opus 4.8 (1M context) <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.
The scheduled resource-drift check now fails against
agent-ready.dev: the livechecks,llms.txt, andspecsMCP resources gained the accessibility suite (main-repo PRs #178–#182), but the embedded snapshots here were stale.What
src/resource-content.ts— re-rendered the 3 drifted constants from the main repo'sbuildChecksMarkdown()/LLMS_TXT/buildSpecsMarkdown():CHECKS_MD— adds the Accessibility checks (A1–A9) sectionLLMS_TXT— adds the accessibility sub-score lineSPECS_MD— adds the Accessibility spec family (+ the newer payments/ACP specs that had also drifted — the old snapshot stopped at C17)src/resources.ts— thechecksresource description now names the accessibility category and an A-series id example (wassite, page, llms.txt, protocolonly).README.md— notes the separate accessibility sub-score.Not changed
The methodology resource (
METHODOLOGY_MD) — it reports only the readability + llms.txt sub-scores, both live and here, so it didn't drift. (Whether the main-repo MCP methodology resource should mention the accessibility sub-score is a separate upstream question; touching only the description here would create a body/description mismatch.)Verification
check-resource-drift.mjs→ all 4 snapshots match live ✓tsc --noEmitclean · 29 tests passRelease
No version bump in this PR. After merge, cut a release from
mainthe usual way (npm version patch+ push the tag → the release workflow publishes to npm). Flagging separately so the publish stays a deliberate step.🤖 Generated with Claude Code