Skip to content

docs: replace restated upstream facts with pointers in context-guard and disk-hygiene #12776

Description

@kyle-sexton

Refs #12694

Outcome

14 passages in 5 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: context-guard, disk-hygiene.

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.

Scope: the context-guard and disk-hygiene rows of #12694 only: plugins/context-guard/README.md, plugins/context-guard/reference/reader-contract.md, plugins/disk-hygiene/README.md, plugins/disk-hygiene/skills/clean/reference/unsupported-platform-handoff.md, plugins/disk-hygiene/skills/setup/SKILL.md. The knowledge and computer-use rows belong to the sibling child.

Rows

context-guard

disk-hygiene

Notes

Drafted by the issue-triage session. Agent choice, not an owner answer. Split from #12694 by whole plugins, so no file is touched by both children; every file above exists on origin/main. Size Medium from the passage count (14 of the parent's 28, which intake sized Large). Five rows carry "(confirm the section)" and need a fetch before the pointer is written.

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". Pointers are candidates: fetch each before writing it, and confirm the section still documents the fact.

Related

Activity

  1. added
    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.
    on Nov 3, 2026
  2. added theissue type on Nov 3, 2026
  3. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  4. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  5. melodic-automation-lanes commented on Nov 3, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41594746558, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T08:41:38Z. work-unblock has now removed and added agent-ready back 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 added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.

  6. added
    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 Nov 3, 2026
  7. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  8. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  9. removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
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

    agent-ready

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions