Repository navigation
Claude Code changelog: unread releases beyond the replay cap #10456
Description
Agent-written spec section, added on the hub's order to give pr-verify a done-when to judge. It is not an owner answer. The scope choice is the agent's comment; the original bot text follows unedited.
Scope
A docs-conformance recheck of the repository against the Claude Code docs at 2.1.318, in place of a release-by-release replay: a mechanical check of every tracked link into code.claude.com/docs/en, and a model read of the 10 pages with over 100 links. Delivered as one pull request per group, each naming its share, and a last one that moves the marker.
Done when
- Every FIX and CODE row the recheck recorded is fixed on
main, or its pull request records it as holding or not fixed, with the reason. - A line that restated a wrong volatile value states our decision with a pointer, as-of date and recheck trigger, per
.claude/rules/skill-bodies-state-current-rules.md, rather than a new restated value. - No pull request here loosens a permission, a guard or what an agent may do unattended.
- A behavior change carries a test that fails on the old code.
- The marker in
docs/upstream/claude-code.mdis at the newest release checked, its wording says those releases were rechecked rather than read one by one, and the closing pull request says which pages got only the link check.bash plugins/harness-ops/skills/changelog/scripts/changelog-status.shreads that marker.
Original report
Run: 2026-10-27, https://github.com/melodic-software/claude-code-plugins/actions/runs/40475462340
The unread Claude Code releases 2.1.299..2.1.311 exceed the replay cap of /harness-ops:changelog, read from marker 2.1.296 in docs/upstream/claude-code.md. Its status script recommends:
recommend: replay cost scales with items and the current docs carry the cumulative state. Run a docs-conformance recheck of the components, then set the marker in docs/upstream/claude-code.md to 2.1.311 and diff only from there
Do that instead of a release-by-release replay. Moving the marker makes the next run file per-release issues again.
Activity
kyle-sexton commentedon Nov 4, 2026
kyle-sexton commentedon Nov 4, 2026
Agent choice, not an owner answer. Nothing defines the scope of a "docs-conformance recheck of the components", and
discover-surfaces.shlists about 2,300 files, so this run bounds it:code.claude.com/docs/enagainst the page fetched at--max-age 0, plus the changelog skill's native-drift pass at 2.1.318. Measured: 5,129 links, 3 retired pages, about 40 dead anchors after excluding the changelog's version anchors, which the rendered page still serves.Basis: judgment on the split; link counts from
git grepthis session. The issue's own alternative, a release-by-release replay, is what the cap rejects.Found on the way: #13233 (the release lane spends its cap on credit stops), and the inventory reads 2.1.318 with four broken lanes, which will be filed through the native-drift key.
kyle-sexton commentedon Nov 4, 2026
Correction to the scope comment above: "about 40 dead anchors" was wrong. A check of the rendered pages found none dead: the docs renamed headings but kept the old ids, so my slug comparison against raw markdown over-reported them. The retired slugs
plugins-referenceanddiscover-pluginsstill serve 200 and are only gone from the docs index; a PR repoints them.Page results so far, from read-only agents, each quoted line to be re-read before any edit:
permissionsandplugins/manifest-referenceare done; both found wrong restated specifics or mis-aimed pointers. The rest are running.fix(discipline,session-flow,bugs): correct preflight parameter reason…
fix(harness-ops): quote the page's marketplace cache wording without …
fix(skill-quality): accept every documented boolean spelling for disa…
fix(harness-config): find the effort defaults item by content and reb…
fix(harness-config): read the root's shared file too when below the r…
docs(harness-config): stamp the checked claims and point at where app…
fix(harness-config): lint both project files and keep the over-report…
kyle-sexton commentedon Nov 4, 2026
The fix PRs now link #13286, which holds the same done-when: this issue was opened by github-actions, so pr-verify never reads its body as trusted text, edited or not. #10456 closes with the marker PR.
kyle-sexton commentedon Nov 4, 2026
Done. The docs-conformance recheck landed in #13269, #13271, #13278, #13282, #13283 and #13288, and #13314 moved the marker in docs/upstream/claude-code.md to 2.1.318, saying those releases were rechecked rather than read one by one. Spec and record: #13286.