Repository navigation
Description
Refs: #7292
Outcome
28 passages in 10 files state a fact an external source owns. Rewrite each as a pointer to the live upstream section, or remove it, so the next upstream change cannot leave a stale copy here. Plugins: work-items, context-budget.
Done when
- Every row below is fixed: the restated value is deleted, the local decision stays in this repository's own words, and the pointer goes to the exact upstream section with an as-of date and a recheck trigger, per
.claude/rules/skill-bodies-state-current-rules.md. A record beside a restated value does not fix it. A row marked Remove has no local dependency on the fact. - The PR passes
check-stamps.sh --trigger-less(plugins/attribution/skills/audit/scripts/check-stamps.sh) on the files it touches. - Each touched plugin has a changelog fragment.
check-stamps.sh also flags a trigger-less stamp at plugins/context-budget/skills/audit/reference/report.md:37 on the same commit; write its recheck trigger if the PR touches that file.
Rows
work-items
plugins/work-items/reference/permission-preflight.md:101-108(r475). Pointer: https://code.claude.com/docs/en/permissions#wildcard-patterns Drop the explanation of what a bare-exact rule permits; keep the decision that only an open-glob grant counts as coverage, pointing at the rule-syntax section.plugins/work-items/reference/permission-preflight.md:171-173,214-222(r476). Pointer: https://git-scm.com/docs/git-config#Documentation/git-config.txt-coreworktree (confirm the section) Drop the claims about when git writes or leaves unset core.worktree; keep the three-candidate resolution order and the Unresolved-reports-INCOMPLETE decision, pointing at git's core.worktree entry.plugins/work-items/reference/tracker-seam.md:35-37(r477). Pointer: https://jqlang.org/download/ (confirm the section) Drop the Windows and Git Bash install parenthetical; keep that jq is required, a missing jq stops the action, and the install link stays as the pointer.plugins/work-items/skills/attend-queue/SKILL.md:162-164(r479). Pointer: https://cli.github.com/manual/gh_issue_edit#options Drop the literal flag spelling; keep the decision to clear @me through the bound adapter's assignee edit, pointing at the adapter README and gh issue edit options. Same text also at:plugins/work-items/tools/work-item-tracker/adapters/github/README.md:278,plugins/work-items/skills/triage/SKILL.md:145; a row of its own covers it only if listed.plugins/work-items/skills/attend-queue/SKILL.md:318-333(r478). Pointer: none found; No Claude Code page documents the account fields of .claude.json; the PR must search code.claude.com docs for oauthAccount, and if none, record the field as unverified rather than state its update timing. Drop the claim about when the account field in the Claude config file updates; keep the rule to read the account directly at each re-evaluation and treat unreadable as cannot attribute.plugins/work-items/skills/setup/SKILL.md:425-427(r481). Pointer: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-resolutions/#api-rest-api-3-resolution-search-get (confirm the section) Drop the endpoint path and pagination claim; keep the step to discover resolutions, show name and description and mark the default, pointing at the Jira section.plugins/work-items/skills/work-loop/reference/telemetry-upsert.md:66-68(r484). Pointer: https://cli.github.com/manual/gh_api (confirm the section) Drop the explanation of what -f body=@file transmits; keep the decision to use -F body=@ for create and update and point at the gh api page.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:62-63,124-129,169-174,217-220(r485). Pointer: https://code.claude.com/docs/en/cloud-environments#github-proxy Drop the claims about which GitHub APIs sandboxed or cloud sessions refuse; keep the decision to read via the REST recipes there and point at the section.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:84-87,321-322(r486). Pointer: https://cli.github.com/manual/gh_issue_list (confirm the section) Drop the default truncation count and maximum page size; keep the rule that --limit is always passed for larger sets and point at the gh manual pages.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:109-122(r487). Pointer: https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests (confirm the section) Delete the qualifier table and its meanings; keep the qualifiers the recipes actually use inline in their commands and point at GitHub's search syntax page.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:189-194,210-215(r488). Pointer: https://cli.github.com/manual/gh_api (confirm the section) Drop the descriptions of the REST comments field and gh api placeholder expansion; keep the instruction to run from the target clone or set GH_REPO and point at the page.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:231-233(r489). Pointer: https://docs.github.com/en/rest/using-the-rest-api/using-pagination-in-the-rest-api#about-pagination Drop the page size, ordering and silent-truncation description; keep the decision that --paginate is required and the local note on long-running telemetry items.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:247-248(r490). Pointer: https://cli.github.com/manual/gh_issue_close (confirm the section) Drop the claim about accepted close reasons and quoting; keep the mapping of done and --not-planned to the reason flags and point at the gh issue close page.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:277-280(r491). Pointer: https://cli.github.com/manual/gh_issue_edit (confirm the section) Drop the statement of which flags edit versus create; keep that this adapter edits labels and assignees through gh issue edit and point at the page.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:295-301(r492). Pointer: https://docs.github.com/en/rest/issues/assignees#add-assignees-to-an-issue (confirm the section) Drop the REST literal-login and silent-drop 201 claims; keep the decision that claim resolves the login explicitly, re-reads assignees and fails 4, pointing at the section.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:354-356(r493). Pointer: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword Delete the enumerated closing-keyword list; keep that matching follows GitHub's keyword set plus the repo's opt-out markers and point at the section.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:363-367,515-520(r494). Pointer: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#about-linked-issues-and-pull-requests Drop the description of what GitHub's computed linkage connection returns and where it surfaces; keep the decision to use it as the authoritative signal and point at the section.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:429-432(r495). Pointer: https://docs.github.com/en/graphql/reference/objects#issue (confirm the section) Drop the account of what includeClosedPrs suppresses; keep the decision to filter to OPEN in the query output and point at the Issue object reference.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:448-453,458-462(r496). Pointer: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword Drop the claims about code blocks, comments and base-branch linking; keep the adapter's reliance on GitHub's linkage and the behavior-change note, pointing at the section.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:624-637(r497). Pointer: https://cli.github.com/manual/gh_issue_view (confirm the section) Drop the list of projected sub-issue fields and what gh drops on export; keep the decision not to filter on repository for sub-issues and point at the gh manual.plugins/work-items/tools/work-item-tracker/adapters/github/README.md:660-661(r499). Pointer: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms (confirm the section) Drop the claim about when Issue Forms labeling fires; keep the instruction to apply labels explicitly on programmatic creation and point at the issue forms page.
context-budget
plugins/context-budget/README.md:6-9(r067). Pointer: https://code.claude.com/docs/en/commands#all-commands Drop what /context attributes or reports only as totals; keep that this plugin attributes the built-in tool pools per tool, and point at the /context entry. Same text also at:plugins/context-budget/skills/audit/SKILL.md:38-42; a row of its own covers it only if listed.plugins/context-budget/README.md:194-197(r069). Pointer: https://code.claude.com/docs/en/commands#all-commands (confirm the section) Drop the parenthetical on skill-frontmatter subtraction from System tools; keep that the engine fingerprints the listing and marks mismatches incomparable, and point at the /context entry. Same text also at:plugins/context-budget/skills/audit/SKILL.md:325-326,plugins/context-budget/skills/audit/SKILL.md:337-340,plugins/context-budget/skills/audit/reference/engine.md:68-70; a row of its own covers it only if listed.plugins/context-budget/skills/audit/SKILL.md:78-80(r075). Pointer: none found; Upstream page documenting the bundled explain-usage skill; it is absent from the fetched commands and skills pages. Search the docs index (llms.txt) and release notes for explain-usage. Drop the description of what explain-usage does and who can invoke it; keep the routing between it and this skill, and point at an owner source once found. Same text also at:plugins/context-budget/skills/audit/reference/native-explain-usage.md:9-10; a row of its own covers it only if listed.plugins/context-budget/skills/audit/SKILL.md:337-340(r077). Pointer: https://code.claude.com/docs/en/commands#all-commands (confirm the section) Drop the explanation of skill-frontmatter subtraction and the safe-mode example; keep the rule never to hand-compare snapshots the engine marked incomparable, and point at the /context entry. Same text also at:plugins/context-budget/skills/audit/SKILL.md:325-326,plugins/context-budget/README.md:194-197,plugins/context-budget/skills/audit/reference/engine.md:68-70; a row of its own covers it only if listed.plugins/context-budget/skills/audit/reference/engine.md:68-75(r078). Pointer: https://code.claude.com/docs/en/commands#all-commands (confirm the section) Drop the claim that the System tools bucket has skill-frontmatter tokens subtracted; keep the signature hash, systemToolsComparable rule and per-bucket gating, and point at the /context entry. Same text also at:plugins/context-budget/README.md:194-197,plugins/context-budget/skills/audit/SKILL.md:325-326,plugins/context-budget/skills/audit/SKILL.md:337-340; a row of its own covers it only if listed.plugins/context-budget/skills/audit/reference/report.md:51-52(r079). Pointer: https://code.claude.com/docs/en/skills#skill-descriptions-are-cut-short Drop the sentence that the listing cap is characters, not tokens; keep printing the measured resolution including an explained zero, and point at the listing-budget section.plugins/context-budget/skills/audit/reference/report.md:57-58(r080). Pointer: https://code.claude.com/docs/en/commands#all-commands Drop what /skill-doctor and /doctor cover (unused skills, MCP servers, plugins); keep the routing and that the operator runs them, and point at their command entries. Same text also at:plugins/context-budget/README.md:233-239,plugins/context-budget/skills/audit/SKILL.md:62-68; a row of its own covers it only if listed.
Notes
Lines are as of 3bd42cabfe (https://github.com/melodic-software/claude-code-plugins/blob/3bd42cabfe6bdef37a05778d396869af0381bb51); locate each passage by its text if main has moved. Each rNNN is that row's number in the order of #7292's "Findings by plugin". Every row was upheld by three blind judges and survived a refutation pass, run report-only for #12072. Pointers are candidates: fetch each before writing it, and confirm the section still documents the fact.
Parent: #7292
Metadata
Metadata
Assignees
Labels
Type
Fields
Work status
Activity
github-actions commentedon Nov 3, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: 27 of the 28 rows were fixed by #12810. Row r478 is the only one left. It is the "Account switch" block, which has to be edited in the reader contract and in every registered copy.
#12689 (comment)
This decision settles the open questions, so I'm asking nothing further. The eval-evidence branch is routed to a host run, not to a person.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 3, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41578865652, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-03T04:45:28Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.24 remaining items
github-actions commentedon Nov 4, 2026
github-actions commentedon Nov 4, 2026
github-actions commentedon Nov 4, 2026
melodic-automation-lanes commentedon Nov 4, 2026
The work-resolve-issue lane stopped on this issue (
host-only): the run reports the work needs a host run the lane cannot make.It added
host-runand removedagent-ready: an agent run on a host builds it, and it waits on no decision from a person.In the run's words:
What the run says it did not do:
Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41765760223
To hand it back to the lane, remove
host-runand addagent-readyagain.kyle-sexton commentedon Nov 4, 2026
Delivered: closing as completed.
Agent choice, not an owner answer.
The 2026-11-04T03:11Z record left row r478 open. It is met on
origin/main(55f8a62), so no further PR is needed:oauthAccountandemailAddresshave no hits in the code.claude.com docs (llms-full.txt, read 2026-11-04), so the no-page branch applies.plugins/rate-limit-guard/reference/reader-contract.md:25-35calls.oauthAccount.emailAddressinternal CLI state, gives the date and Claude Code version it was observed with, and names the recheck trigger, added by 4338584 (docs: replace restated upstream facts with pointers in fleet, harness-memory, repo-hygiene #12871).plugins/work-items/skills/attend-queue/SKILL.md:358-361points at that record..claude.jsonupdates is left to drop. The floor's timing sentence (attend-queue/SKILL.md:319-322, identical in every registered copy) is about the guard's snapshot file: "it names an account only as of a session's last API response".plugins/rate-limit-guard/CHANGELOG.md:294gives the same subject ("the file names an account only as of ..."), andrecordResponse(plugins/rate-limit-guard/hooks/register.tsx:515-520) reads the account at each API response, which the snapshot write carries only when a second read at the write agrees (reader-contract.md:128-130). No skill text is cut, sodocs/review/skills-and-agents.md:6-8asks for no eval.attend-queue/SKILL.md:323-333).scripts/check-loop-lane-floor-drift.sh --checkpasses on main.check-stamps.sh --trigger-lesson the reader contract and its 7 registered copies finds 0 findings on main; docs: replace restated upstream facts with pointers in fleet, harness-memory, repo-hygiene #12871 carried the changelog fragments for the files it touched.The other 27 rows were delivered by #12810 (d06270f), as the 03:11Z record shows.
kyle-sexton commentedon Nov 4, 2026
Closing as completed on the delivery record above: row r478 is met on main, and #12810 delivered the other 27 rows.