Skip to content

fix(harness-ops): land the 2.1.297..2.1.318 docs-conformance fixes and move the changelog marker #13286

Closed
2 of 2 issues completed

Description

@kyle-sexton

Agent-written spec, filed so pr-verify has a trusted done-when for the #10456 fix PRs: #10456 was opened by github-actions, so its body is never trusted text, edited or not (.github/actions/select-trusted-text/README.md, the author check). The recheck's scope is an agent choice, not an owner answer (scope comment).

Problem

The changelog read marker in docs/upstream/claude-code.md sits at 2.1.296, and releases 2.1.297 to 2.1.318 are past the replay cap. The status script recommends a docs-conformance recheck instead of a release-by-release replay. The recheck read the 10 Claude Code docs pages with over 100 repository links and found lines that no longer match those pages, some of them code defects.

Fix

One pull request per group, each naming its share of the recheck, then 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, or, for skill text, says what covers it. Named behavior changes: /bugs:scan gates always pass an effort (their variant's, or the session's level when that is higher, or the session's level with no role map), and its run metadata labels an omitted effort unset instead of session, because the skill cannot see which model a spawn lands on.
  • The marker in docs/upstream/claude-code.md is 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.sh reads that marker.
  • Claude Code changelog: unread releases beyond the replay cap #10456 is closed with the marker pull request.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 4, 2026
  2. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Large
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: none

    I understood this as the follow-up to #10456. The changelog marker in docs/upstream/claude-code.md sits at 2.1.296, and releases 2.1.297 to 2.1.318 are past the replay cap. The docs-conformance recheck found repository lines that no longer match the Claude Code docs, some of them code defects. The work is one pull request per group of plugins, then a closing pull request that moves the marker and closes #10456.

    The work spans many plugins and several pull requests, so it needs splitting. The recheck's FIX and CODE rows are the source of scope, and reading them would settle the exact list. #10456 is the parent tracker, not a duplicate. #13236 and #13237 also concern Claude Code 2.1.318, but they cover inventory extraction rather than docs conformance.

    Automated triage, applied by the lanes App.

  3. added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 4, 2026
  4. added
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    on Nov 4, 2026
  5. melodic-automation-lanes commented on Nov 4, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane yet: sub-issue #13290 is open.

  6. melodic-automation-lanes commented on Nov 4, 2026

    @melodic-automation-lanes
    Contributor

    Split at intake (owner Q93). This issue is Size Large, so its done-when is split into 2 sub-issues, each holding its task-list lines as written.

    Automated split by the lanes App. Admission waits on this issue while a sub-issue is open; work-unblock closes it as completed once every sub-issue is closed as completed by a merge or a listed human and its done-when is covered.

  7. kyle-sexton commented on Nov 4, 2026

    @kyle-sexton
    MemberAuthor

    Lane 7 holds both parts; no other lane should take #13289 or #13290.

  8. kyle-sexton commented on Nov 4, 2026

    @kyle-sexton
    MemberAuthor

    Done. Fix rows: #13269, #13271, #13278, #13282, #13283, #13288 (closed #13289); rows not fixed, with reasons, are in #13314. Marker: #13314 sets 2.1.318, and changelog-status.sh on main reads it as up to date (closed #13290).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: mediumReal value, no hard deadline; normal backlog flow.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    Work status

    ready

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions