Skip to content

Light pointer pass: open medium and low pointer findings from the upstream-pointer sweep #7293

Open
5 of 7 issues completed

Description

@kyle-sexton

Description

The upstream-pointer sweep's light pass read 176 live docs pages (160 on code.claude.com, 16 on claude.dev) and checked every repo citation of each page: whether each anchor still exists, and whether repo text that restates the page carries a whole pointer record (anchor, as-of date, recheck trigger). This issue lists the medium and low findings that the sweep's own branches left open. High-severity findings are not in this list.

Kinds:

  • drift: the repo states something the live page now says differently.
  • missing-pointer: the repo restates the page with no link to it.
  • incomplete-record: a link exists but lacks the exact anchor, the as-of date, or the recheck trigger.
  • wrong-host citation: the cited URL redirects off its host; cite the canonical one.

Line numbers come from the sweep's read of 2026-10-11/12. main and the sweep branches have moved since, so confirm each line before editing. Where a sweep PR (#7061-#7274) touches a file listed here, that PR left the finding open.

Open findings

autonomy

context-guard

fleet

harness-config

harness-memory

harness-ops

instruction-placement

machine-health

miro

playbooks

visualization

(repository root)

Recheck on main first

The pass deferred these because another open PR owned the file at the time. Those PRs have since merged, so each finding may already be fixed.

context-budget

disk-hygiene

dometrain-mcp

  • plugins/dometrain-mcp/README.md:183: incomplete-record, medium. Live: https://code.claude.com/docs/en/mcp, anchor #scope-hierarchy-and-precedence, #use-dynamic-headers-for-custom-authentication

harness-config

planning

playbooks

session-flow

source-control

(repository root)

Skipped: files owned by other open PRs

Not listed above because an open PR outside the sweep touches the file. Pick them up after that PR merges.

The pass also found a dead anchor, hooks-guide#debug-techniques, cited in docs/conventions/hook-observability/README.md and owned by #7064. #7064 has since merged, and main no longer cites that anchor, so no action is needed.

Affected area / component

Pointer records to upstream docs across the plugins and repo docs listed above.

Found during the upstream-pointer sweep (PRs #7061-#7274).

Activity

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

    @github-actions
    Contributor

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

    Size: Large
    Complexity: Low
    Uncertainty: Known
    Flags: none
    Blocked by: none

    Understood: this is a docs-only tracking issue for the medium and low upstream-pointer findings that the sweep left open. Each finding needs an anchor, as-of date or recheck trigger added or corrected. The earlier comment shows the work is already split into seven filed sub-issues (#8006-#8012). Two pieces are still unfiled: the AGENTS.md pointer, and the recheck of the files the sweep skipped. Nothing is missing from the issue itself. Maintainers may want to confirm the unfiled pieces once their blockers clear. I found no likely duplicates other than the sub-issues already linked.

    Automated triage, applied by the lanes App.

  4. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Oct 12, 2026
  5. kyle-sexton commented on Oct 13, 2026

    @kyle-sexton
    MemberAuthor

    Owner batch-ratified this admission in an attended session on 2026-10-12: work-class: scoped. Rule: class C1-C3, no trust surface, the independent check confirmed the recorded decision, and no owner step remains.

  6. added
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Oct 13, 2026
  7. kyle-sexton commented on Oct 18, 2026

    @kyle-sexton
    MemberAuthor

    This was generated by AI during backlog shaping.

    This issue is split into 9 pieces, each sized for one lane PR. About 50 findings in about 45 files across 20 plugins and repo docs, over the lane size. Split into seven groups of at most 10 files including one changelog fragment per plugin (every listed plugin is in fragment mode), plus AGENTS.md (protected path) and the skipped-file set, whose blocking PRs have all merged or closed but which carry no recorded finding detail. The boris vendor/upstream-skill.md drift item is dropped: that file is the verbatim upstream baseline kept for drift detection (playbooks boris SKILL.md:21-23).

    Filed pieces are sub-issues of this one, and the paced queue admits them to the lane. Unfiled pieces wait on the blocker shown. The owner approved this split in an attended backlog-shaping session on 2026-10-18.

  8. github-actions commented on Oct 25, 2026

    @github-actions
    Contributor

    The triage sweep dispatched intake triage for this issue (attempt 1 of 2).

  9. melodic-automation-lanes commented on Oct 25, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane yet: Size large: the split into sub-issues at intake is pending (owner Q93).

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: lowNice-to-have, cosmetic, or speculative; opportunistic.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.

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions