📦 deps(thirdparty): update snapshots

brooks-lint/.claude/agents/release-manager.md

@@ -29,7 +29,9 @@ the Skill tool with the target version, or follow these steps directly):
 3. **Write the changelog.** Add a `## <version>` section at the top of CHANGELOG.md
    with Added / Fixed / Changed notes summarizing `git log <last-tag>..HEAD --oneline`.
 4. **Re-validate.** `npm run validate` then `npm test`. Fix and re-run until clean.
-5. **Commit & push.** Stage the changed manifests, README, CHANGELOG; commit
+5. **Commit & push.** Stage everything `npm run bump` rewrote plus CHANGELOG — read
+   `git status` rather than naming files, since the version-bearing set is discovered
+   from disk and is more than one README; commit
    `chore(release): bump version to <version>`; push to `main` (direct-to-main repo,
    no PR).
 6. **Tag & publish.** `gh release create v<version> --title "v<version>"

brooks-lint/.claude/skills/release/SKILL.md

@@ -20,7 +20,8 @@ for the semver bump before doing anything.
 
 Execute these steps in order. `bump-version.mjs` reads the version FROM
 `package.json` and does NOT touch the changelog — so the version edit and the
-CHANGELOG entry are manual; the script only fans the version out to manifests + badge.
+CHANGELOG entry are manual; the script only fans the version out to the manifests
+and every version-bearing text file.
 
 1. **Set the source of truth.** `npm version <version> --no-git-tag-version`
    (the `--no-git-tag-version` flag is required — plain `npm version` would create
@@ -36,9 +37,12 @@ CHANGELOG entry are manual; the script only fans the version out to manifests +
    last release tag (`git log <last-tag>..HEAD --oneline`). The heading MUST be
    `## [<version>] - YYYY-MM-DD` — `npm run validate` parses that exact shape and
    fails on a bare `## <version>`.
-4. **Validate.** `npm run validate` — fails if any manifest, the README badge, or
-   the CHANGELOG entry is out of sync. Fix and re-run until clean. Then `npm test`.
-5. **Commit & push.** Stage the changed manifests, README, and CHANGELOG; commit
+4. **Validate.** `npm run validate` — fails if any manifest, any version-bearing
+   text file, or the CHANGELOG entry is out of sync. Fix and re-run until clean.
+   Then `npm test`.
+5. **Commit & push.** Stage everything `npm run bump` rewrote plus `CHANGELOG.md` —
+   read `git status` rather than naming files, because the version-bearing set is
+   discovered from disk and is more than one README; commit
    with a conventional message (`chore(release): bump version to <version>`); push
    to `main` (direct-to-main repo — no PR).
 6. **Tag & publish.** Create the GitHub release:

brooks-lint/CLAUDE.md

@@ -72,8 +72,8 @@ To add a scenario: append to the `evals` array with the next sequential `id` and
 ## Development Commands
 
 ```bash
-npm run bump              # Propagate the package.json version to all manifests + README badge (NOT changelog)
-npm run validate          # Repo consistency: manifests, README badge, changelog, source inventory, skills structure
+npm run bump              # Propagate the package.json version to all manifests + every version-bearing text file (NOT changelog)
+npm run validate          # Repo consistency: manifests, version refs, changelog, source inventory, skills structure
 npm test                  # Unit tests for validate-repo helpers
 npm run evals             # Eval structural validation (IDs, fields, risk-code refs)
 npm run evals:live        # Live evals against the AI (requires ANTHROPIC_API_KEY)
@@ -87,4 +87,4 @@ CLAUDE_PLUGIN_ROOT=1 bash hooks/session-start   # plugin platform branch
 
 ## Release Process
 
-Set the new version in `package.json` (e.g. `npm version <v> --no-git-tag-version`), then `npm run bump` (propagates the version to all manifests + README badge) → add the new `CHANGELOG.md` section by hand → `npm run validate` → commit, push, tag GitHub release.
+Set the new version in `package.json` (e.g. `npm version <v> --no-git-tag-version`), then `npm run bump` (propagates the version to all manifests plus every version-bearing text file listed by `scripts/version-refs.mjs` — all six README badges and the docs landing-page JSON-LD) → add the new `CHANGELOG.md` section by hand → `npm run validate` → commit, push, tag GitHub release.

brooks-lint/SOURCE.md

@@ -1,8 +1,8 @@
 # Source
 
 - Repo: https://github.com/hyhmrright/brooks-lint
-- Ref: f62481960b5b9d48816d2258277961a4005640b0
+- Ref: 40d437e5af2919d28f87c9f39b9c02d0b9d5be2d
 - Remove-Paths: 
-- Snapshot: 2026-08-24
+- Snapshot: 2026-08-30
 - Sync-Mode: copy_skill_dirs
 - Notes: vendored into playbook branch thirdparty/skill