[kyle-sexton]

Closes #13290
Refs: #13286

Summary

Moves the Claude Code changelog read marker in docs/upstream/claude-code.md from 2.1.296 to
2.1.318, the newest published release (published 2026-11-04). Releases 2.1.297 to 2.1.318 were
past the replay cap of /harness-ops:changelog, so they were not read one by one. Instead the
components were rechecked against the current docs, within the bounds set by the
scope comment
and the correction posted under it.

Fix

• Marker line: changelog through 2.1.318. The text after it says 2.1.257 to 2.1.296 were read
  release by release, and 2.1.297 to 2.1.318 were rechecked against the current docs instead. It
  links the scope comment and fix(harness-ops): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker #13286.
• Pointer, as-of date (2026-11-04) and recheck trigger in the upstream-drift "Required parts" shape.
  No upstream text is copied.
• The rows paragraph now names the 2.1.257 to 2.1.296 read and says the recheck added no rows. Its
  fixes are in the pull requests listed below.

Verification

• bash plugins/harness-ops/skills/changelog/scripts/changelog-status.sh --ledger docs/upstream/claude-code.md
  run on this branch prints last-applied: 2.1.318, latest: 2.1.318 and range: up to date.
  Before the edit it printed last-applied: 2.1.296, range: 2.1.299..2.1.318 (18 releases, 1048 core items)
  and cap: exceeded. --ledger is there because the script finds the ledger from the current
  directory's repository root.
• changelog-status.test.sh: 86 of 86 assertions pass.
• Release record: no plugin file changes, so no .changes/ fragment.
  check-changelog-fragments.sh --check-required origin/main passes, and so do
  check-changelog-parity.sh --check, --check-bump origin/main, --check-preserved origin/main
  and --check-order.
• markdownlint-cli2 and scripts/check-vocabulary.py report nothing on the edited file.

What the recheck covered

1. Mechanical, whole repository. Every tracked link into code.claude.com/docs/en was checked
   against the page fetched at max-age 0, plus the changelog skill's native-drift pass at 2.1.318.
2. Model read. The 10 pages with over 100 repository links were read raw against the records
   that cite them: permissions, plugins/manifest-reference, skills, sub-agents,
   plugins/cli-reference, hooks, memory, settings, model-config, settings-reference.

Link-only pages: 118. These got step 1 and nothing more. The count is the distinct slugs linked
from tracked files on this branch, minus the 10 read pages (128 distinct). Command:

git grep -ohIE "https://code\.claude\.com/docs/en/[A-Za-z0-9/_.-]+" -- . ":!*/vendor/*" ":!**/CHANGELOG.md" ":!docs/upstream/*" ":!**/*.test.*" ":!**/evals/**" | sed -E 's#^https://code\.claude\.com/docs/en/##; s#[/.]+$##; s#\.md$##; s#[/.]+$##' | sort -u | grep -vxE "permissions|plugins/manifest-reference|skills|sub-agents|plugins/cli-reference|hooks|memory|settings|model-config|settings-reference" | wc -l

The scope comment's count was 109 link-only pages (119 distinct). It was taken on an earlier main,
before the fix pull requests repointed links, and with a different extraction. One of the 118 slugs,
slash-commands, is not in the current docs index. The other 117 are current pages.

The 118 link-only slugs

advisor, agent-sdk/agent-loop, agent-sdk/observability, agent-sdk/permissions, agent-sdk/plugins,
agent-sdk/python, agent-sdk/tool-search, agent-sdk/typescript, agent-sdk/user-input, agent-teams,
agent-view, agents, artifacts, authentication, auto-mode-config, best-practices, changelog,
channels, channels-reference, checkpointing, chrome, claude-code-on-the-web, claude-directory,
claude-security, cli-reference, cloud-environments, code-review, code-review-customize,
code-review-local, code-review-pull-requests, code-review-setup, commands, common-workflows,
computer-use, context-window, costs, cross-session-messaging, data-usage, debug-your-config,
deep-links, desktop, desktop-scheduled-tasks, desktop-wsl, env-vars, errors, fast-mode,
feature-availability, features-overview, fullscreen, github-actions, github-enterprise-server,
glossary, goal, headless, hooks-guide, how-claude-code-works, interactive-mode, keybindings,
large-codebases, legal-and-compliance, llm-gateway, managed-mcp, managed-settings, mcp,
mcp-quickstart, monitoring-usage, output-styles, permission-modes, platforms, plugin-evals,
plugins/anthropic-marketplaces, plugins/cli-hints, plugins/components, plugins/create,
plugins/create-marketplace, plugins/dependencies, plugins/host-marketplace, plugins/install,
plugins/loading, plugins/marketplace-reference, plugins/mods/admin, plugins/mods/api,
plugins/mods/create, plugins/mods/events, plugins/mods/gallery, plugins/mods/interface,
plugins/mods/overview, plugins/mods/reference, plugins/mods/test, plugins/mods/troubleshoot,
plugins/org, plugins/overview, plugins/relevance, plugins/troubleshooting, prompt-caching,
remote-control, routines, sandbox-environments, sandboxing, scheduled-tasks, security,
security-guidance, self-hosted-environments, server-managed-settings, sessions, setup, slack,
slash-commands (not in the current docs index), statusline, terminal-config, tools-reference,
troubleshoot-install, ultrareview, web-quickstart, whats-new/2026-w32, workflows, worktrees,
zero-data-retention

Ledger rows not fixed (4 of 85)

• Handoff skill: whether a subagent stays addressable across /clear (plugins/session-flow/skills/handoff/SKILL.md:339).
  Unsettled. The sub-agents page scopes the name check to the conversation and resets it on
  /clear, and lets names survive a restart only since the last compaction. Neither line says
  whether a live agent stays addressable across /clear. An eval case also pins the claim.
• scripts/check-killswitch-hoist.sh:193: not fixed. It is a check script, so the fence
  forbade editing it. It scans too much, which errs in the safe direction.
• Disk-hygiene and repo-hygiene clean skills: placeholders in skill-frontmatter hooks
  (plugins/disk-hygiene/skills/clean/SKILL.md:14, plugins/repo-hygiene/skills/clean/SKILL.md:44).
  Unsettled. The hooks page says nothing about which placeholders a skill-frontmatter hook
  substitutes. The lines record a probe observation, so they stay as written.
• harness-memory line-count gate: what counts as an external import
  (plugins/harness-memory/skills/audit/reference/criteria.md:63). Unsettled. The page defines
  external against the working directory, which can give a different count. Changing what the
  gate expands is a design choice.

The fallbackModel chain cap row was listed here as not fixed; #13288 fixed it after the ledger
was written, so the engine now reads the cap from model-config's "Fallback model chains" section.

Not covered by the recheck

• Pages other than the 10 got the link check only and are unaudited past it.
• The sub-agents page read cut long lines at 300 to 420 characters. A claim past a cut was not
  read.
• The settings findings had no second review.
• ADOPT items (adopt a new upstream feature) and REPROBE items (rerun a behavior probe) were out of
  scope: the on-demand per-file size limit (memory) and the missing-file Read surface probe.

Fix pull requests

All merged: #13269, #13271, #13278, #13282, #13283, #13288.

Remaining

This pull request delivers #13290 only: the marker and its wording. The fix rows of #13286
(its first four done-when items, tracked as #13289) are not in this diff; they landed in the six
fix pull requests above, and #13289 is closed on that record. #13286 and #10456 close once this
merges, by hand, since the marker is the last item either one names.

Related

• Claude Code changelog: unread releases beyond the replay cap #10456, the bot-filed recheck issue (no keyword: its body is not trusted spec text)
• fix(harness-ops): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker #13286: the spec, split into fix\(harness-ops\): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker - part 1 of 2 #13289 (fixes) and fix\(harness-ops\): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker - part 2 of 2 #13290 (this marker)
• Scope: Claude Code changelog: unread releases beyond the replay cap #10456 (comment)

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-04T17:30:05.466378Z	6ebb00e	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[kyle-sexton]

Held with do-not-merge by Lane 7 until #13283 and #13288 merge, since this PR closes #13289, whose done-when needs every fix on main. Lane 7 removes the label when both have merged.

[github-actions]

claude-security-review reviewed 6ebb00e56df5b11253a1c3a829d14da8c71a3fcf: read 1 of 1 changed file(s); 0 finding(s), 0 as inline comments.

Security review: PR #13314 (head 6ebb00e)

I found no security issues.

Scope: I read the whole change to its one file, docs/upstream/claude-code.md. It matches no glob in the trusted-paths list.

What changed: the documentation-only diff moves the "Last audited upstream state" marker from 2.1.296 to 2.1.318. It also rewrites the paragraphs around the marker:

• They now say that releases 2.1.297 through 2.1.318 were rechecked against the current docs, not read release by release.
• They add a pointer, an as-of date and a recheck trigger.

Controls checked: /harness-ops:changelog reads this marker to choose its default diff/apply range. Moving the marker forward means that lane will not replay those releases. That affects how much of the docs drift gets covered. It is not a security control. The change does not:

• widen who is trusted,
• grow a token's scope,
• weaken the kill switch, or
• weaken a merge hold.

Instruction surfaces and manifests: the change does not touch a standing instruction (CLAUDE.md, a rule, a skill or agent body, or a hook), so the instruction-surface lens does not apply. It touches no plugin manifest.

PR context: the description and closing issues contain no embedded directives aimed at this lane.

Spend and cost: none. No hold.

critical-findings: 0

[github-actions]

claude-review reviewed 6ebb00e56df5b11253a1c3a829d14da8c71a3fcf: read 1 of 1 changed file(s); 1 finding(s), 0 as inline comments.

Code review: PR #13314, moving the Claude Code changelog marker to 2.1.318

Scope: I read the 1 changed file, docs/upstream/claude-code.md, in full (one hunk). This was a complete first review, not blocking only. There were no prior findings and no settled threads.

Checks

• Marker parse. changelog-status.sh finds the marker with grep -oE 'Last audited upstream state:\*\* changelog through X.Y.Z' on a single line (changelog-status.sh#L196). At head, the marker phrase and the version 2.1.318 are both on claude-code.md#L10, so the regex still matches. I didn't run the script. The last-applied: 2.1.318 / range: up to date output is the author's claim and is unverified.
• fix\(harness-ops\): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker - part 2 of 2 #13290 criteria. The marker is at 2.1.318. The text says 2.1.297 through 2.1.318 were "rechecked against the current docs" and not read release by release. The PR body lists the 118 pages that got only the link check. Met.
• fix(harness-ops): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker #13286 / fix\(harness-ops\): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker - part 1 of 2 #13289 "No pull request here loosens a permission, a guard…". Met, since this is a docs-only change.
• Pointer, as-of date and recheck trigger are in the required shape. No upstream changelog text is copied.
• Path-scoped rules. .claude/rules/cost-claims.md matches docs/**/*.md. The edit makes no cost claim, so nothing applies.
• Spend. None. The change only edits docs.

Finding (whole PR, no changed line carries it)

1. Closing fix\(harness-ops\): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker - part 1 of 2 #13289 and fix(harness-ops): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker #13286 depends on merge order. Both issues have the criterion: "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." The PR body says fix: recheck the remaining docs-conformance rows for 2.1.297..2.1.318 #13283 (remaining groups) and fix(harness-config): align audit references, the permission reader and the effort pin check with the docs #13288 (harness-config) were "Still open when this was written", and that "this pull request should merge after those two." Nothing in this PR enforces that order. If it merges first, Closes #13289 and Closes #13286 close both issues while those rows are still off main. The 5 rows it marks as not fixed have reasons, so they meet the criterion's other branch. I can't see the current state of fix: recheck the remaining docs-conformance rows for 2.1.297..2.1.318 #13283 and fix(harness-config): align audit references, the permission reader and the effort pin check with the docs #13288 from this lane. Fix: before merging, confirm both are merged. Otherwise, drop Closes #13289 / Closes #13286 and let the last fix PR close them.

No embedded instructions were found in the PR context.

[kyle-sexton]

Hold lifted: #13283 and #13288 have merged, so every fix PR (#13269, #13271, #13278, #13282, #13283, #13288) is on main.

[github-actions]

The pr-verify verifier failed head 6ebb00e56df5b11253a1c3a829d14da8c71a3fcf. What it wrote, as data:

Summary: The diff does what #13290 asks. It moves the marker in docs/upstream/claude-code.md to
  2.1.318, and the new wording says 2.1.297 through 2.1.318 were rechecked against the current docs
  rather than read one by one. It keeps the marker line in the form changelog-status.sh parses. It
  adds the pointer, as-of date and recheck trigger. The pull request body lists the 118 pages that
  got only the link check, and the PR closes #10456. #10456 itself has no trusted spec text because
  a bot opened it; its trusted comments set the recheck scope this diff follows. The verdict is
  still fail. The PR also closes #13286 and #13289, and their first four done-when items are not in
  this diff: the FIX and CODE rows, the volatile-value pointers, the no-loosening check, and the
  `/bugs:scan` effort behavior change with its test. The body names the fix PRs only in prose. With
  no `Siblings:` line, credited_siblings is empty for both issues, so nothing excuses those items.
  select-tests was skipped, so the CI list is no evidence either way. The only file changed is docs
  prose, with no binaries, nothing secret and nothing in the takeover set. I found no text trying to
  steer the reviewer.
- PR body: it says `Closes #13289` and `Closes #13286`, but this diff delivers none of their
  done-when items 1-4 (FIX/CODE rows, volatile-value pointers, the no-loosening check, the
  `/bugs:scan` effort change and its test), and with no `Siblings:` line no sibling PR is credited
  for them. Either drop `Closes #13289` and `Closes #13286` and keep `Closes #13290` and `Closes
  #10456`, or add a `Siblings: #13269, #13271, #13278, #13282, #13283, #13288` line. Each PR listed
  there must have merged with a `Refs:` line naming the issue it is credited against: `Refs: #13289`
  for #13289 and `Refs: #13286` for #13286.

This pull request leaves the merge queue, and ci-status holds it out while it carries pr-verify-failed. A pr-verify pass removes the label, at a new commit or at this same head: once a trusted person edits the body, and only trusted people have edited it since the fail, this head is judged again, so a fail on the body or the issues it links needs only the body fixed, no new commit.