Skip to content

docs: replace restated upstream facts with pointers in knowledge, context-guard, disk-hygiene, computer-use #12694

Closed
2 of 2 issues completed

Description

@kyle-sexton

Refs: #7292

Outcome

28 passages in 14 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: knowledge, context-guard, disk-hygiene, computer-use.

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.

Rows

knowledge

context-guard

disk-hygiene

computer-use

  • plugins/computer-use/README.md:32-34 (r060). Pointer: https://code.claude.com/docs/en/computer-use#screenshots-are-downscaled-automatically Drop the pixel-budget explanation and the claim that smaller monitors do not help; keep the decision that zoom is the lever, and point at the downscaling section. Same text also at: plugins/computer-use/skills/diagnose/SKILL.md:75-77, plugins/computer-use/skills/diagnose/SKILL.md:37-38; a row of its own covers it only if listed.
  • plugins/computer-use/skills/diagnose/SKILL.md:75-77 (r061). Pointer: https://code.claude.com/docs/en/computer-use#screenshots-are-downscaled-automatically Drop the megapixel-count explanation; keep the instruction to read the reference file before advising on resolution, and point at the downscaling section. Same text also at: plugins/computer-use/README.md:32-34, plugins/computer-use/skills/diagnose/SKILL.md:37-38; a row of its own covers it only if listed.
  • plugins/computer-use/skills/setup/SKILL.md:44-46,117-119 (r062). Pointer: none found; Upstream owner of the computer-use MCP tool descriptions (list_granted_applications, request_access); the fetched computer-use page does not name them. Search the docs for a tool reference or confirm via the /mcp tool listing. Drop what list_granted_applications returns and its read-only/no-side-effect description, in both places; keep the decision to use it as the check's probe, with a pointer.
  • plugins/computer-use/skills/setup/SKILL.md:60-61,117-118 (r063). Pointer: https://code.claude.com/docs/en/computer-use#approve-apps-per-session Drop the statement that request_access raises a consent dialog, in both places; keep the rule never to call it during a check, and point at the approval section.
  • plugins/computer-use/skills/setup/SKILL.md:65-66 (r064). Pointer: none found; Upstream doc on whether synthesized input resets the OS idle timer (Windows/macOS input injection or idle-detection docs); the computer-use page does not cover it. If none exists, reclassify as local measurement. Drop the claim that synthesized input does not reset the idle timer; keep the decision to probe and report the three timeouts, and point at an owner source once found. Same text also at: plugins/computer-use/README.md:29-31, plugins/computer-use/skills/diagnose/SKILL.md:42, plugins/computer-use/skills/setup/SKILL.md:79-81; a row of its own covers it only if listed.
  • plugins/computer-use/skills/setup/SKILL.md:104-107 (r065). Pointer: https://code.claude.com/docs/en/computer-use#approve-apps-per-session (confirm the section) Drop the description of the allowlist gate's refusal and its error text; keep reporting focus-stealing utilities as INFO with the retry pattern, and point at the approval section. Same text also at: plugins/computer-use/skills/diagnose/SKILL.md:41, plugins/computer-use/skills/diagnose/SKILL.md:80-81; 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

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 3, 2026
  2. github-actions commented on Nov 3, 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

    Understood: 28 passages in 14 files across knowledge, context-guard, disk-hygiene and computer-use restate facts that upstream sources own. Each should become a pointer to the live upstream section, with an as-of date and recheck trigger. The local decision stays, and each touched plugin gets a changelog fragment. The work is docs-only and the rows are specific. Several pointers are marked "confirm the section" or "none found", so each needs a fetch to check it before it is written. The change spans four plugins and may need splitting. This looks related to the sibling "replace restated upstream facts" issues under #7292, but each covers different plugins, so I don't see a duplicate.

    Automated triage, applied by the lanes App.

  3. added
    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 3, 2026
  4. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor

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

  5. 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 3, 2026
  6. melodic-automation-lanes commented on Nov 3, 2026

    @melodic-automation-lanes
    Contributor

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

  7. melodic-automation-lanes commented on Nov 3, 2026

    @melodic-automation-lanes
    Contributor

    Not split at intake (owner Q93). This Size Large issue stays parked at status: ready: no split into whole changes was found, either by task-list line or by the targets the lines name. No person is asked to act and no hold label is added. The split settings are size-split in .github/actions/resolve-config/admission-rules.json.

    Automated by the lanes App, once per reason and body version.

  8. added
    host-runNeeds an agent run or builder session on a host; not a person or the issue lane.
    on Nov 4, 2026
  9. kyle-sexton commented on Nov 4, 2026

    @kyle-sexton
    MemberAuthor

    Decision recorded. 27 of the 28 rows are delivered on main; this issue stays open for row r318 alone, as host work.
    Agent choice, not an owner answer.

    Delivered, checked row by row on origin/main: the knowledge and computer-use rows by #12913 (e5389b6), r311 by #12818 (019146e), and the context-guard and disk-hygiene rows by #12812 (a4c9a26). check-stamps.sh --trigger-less on the 13 touched files: 93 stamps, 0 findings. Changelog fragments exist for all four plugins.

    Not delivered: r318. plugins/knowledge/skills/docpage-digest/context/anthropic-docs-profile.md:38-40 still lists the channel artifacts (theme={null} fence attributes, tab expansion, \&-escaped URLs). #12913 left it out because removing it cuts skill behaviour, which needs before-and-after eval evidence first (docs/review/skills-and-agents.md:6-8), and said #12775 would stay open for it; #12775 has since closed, so the row is tracked here.

    • On a fleet host, run the docpage-digest evals before and after removing the r318 sentences (or replacing them with a pointer to an upstream page that documents the raw markdown channel, if one is found), and post both results here.
    • If the after run shows no loss, the same PR removes or points the r318 sentences, keeps that source.* stays the unaltered fetch, and adds a knowledge changelog fragment.
  10. kyle-sexton commented on Nov 4, 2026

    @kyle-sexton
    MemberAuthor

    Row r318 is settled by the owner, so nothing is left here. The 13:19Z record above is an agent's, and it does not reflect the owner's answer on #12775: owner, verbatim, 2026-11-04: "Go w/ recommendations", on option (a), keep the r318 sentences and close with the row recorded as unmeasurable (record).

    The before and after evals this record asks for already ran on #12775: before 1.00, after 1.00, degraded 0.858, a mean drop of 0.142 against the 0.15 bar, so under rewrite-a-plugin.md step 7 the before text ships. The sentences stay. Re-opening the cut would be option (c), which the owner did not pick. The other 27 rows are delivered, per the record above.

  11. removed
    host-runNeeds an agent run or builder session on a host; not a person or the issue lane.
    on Nov 4, 2026
  12. kyle-sexton commented on Nov 4, 2026

    @kyle-sexton
    MemberAuthor

    Correction: withdraw the record above; this issue is done as closed.
    Agent choice, not an owner answer.

    The record above missed the owner's answer on #12775 (2026-11-04T13:10:54Z, verbatim: "Go w/ recommendations", option (a)): r318's sentences stay, recorded as unmeasurable because the negative control's mean drop was 0.142 against the 0.15 bar. No r318 work remains, so host-run is removed and nothing is routed.

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.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