Skip to content

docs: replace restated upstream facts with pointers in multi-agent, playbooks, playwright, powershell-format and 6 more #12698

Description

@kyle-sexton

Refs: #7292

Outcome

15 passages in 11 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: multi-agent, playbooks, playwright, powershell-format, ruff-format, biome-format, code-metrics, desktop-notification, eol-normalizer, mutation-testing.

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

multi-agent

playbooks

playwright

powershell-format

ruff-format

  • plugins/ruff-format/README.md:24-34 (r422). Pointer: https://docs.astral.sh/ruff/configuration/#config-file-discovery Drop the description of Ruff's discovery rules and how it treats pyproject.toml without [tool.ruff]; keep the opt-in decision and the known matcher limitation, pointing at the section.
  • plugins/ruff-format/README.md:37-40 (r424). Pointer: https://docs.astral.sh/ruff/settings/#lint_unfixable (confirm the section) Drop the statement of how --unfixable relates to the config's own unfixable list; keep the decision to pass F401 protection in the batch row only, pointing at the setting.

biome-format

  • plugins/biome-format/README.md:4-6,39-40 (r030). Pointer: https://biomejs.dev/reference/cli/#--write---fix Drop the description of what --write applies and the never-unsafe claim; keep the decision to run biome check --write on the listed extensions and point at the flag section.

code-metrics

  • plugins/code-metrics/skills/principles/SKILL.md:132-133 (r045). Pointer: https://www.omg.org/spec/ASCQM/#formal-versions Drop the 'OMG's current release' version claim; keep citing ISO/IEC 5055 and 25023 by clause and version, and point at the ASCQM formal versions.

desktop-notification

  • plugins/desktop-notification/README.md:40 (r095). Pointer: https://man.archlinux.org/man/notify-send.1.en (confirm the section) Drop the distro package names; keep that Linux needs notify-send and that os_toast is a no-op without it, and point at the notify-send manual page.

eol-normalizer

  • plugins/eol-normalizer/README.md:21-25 (r159). Pointer: https://git-scm.com/docs/gitattributes#text Drop the per-attribute semantics and the NUL-scan window figure; keep the decision that the hook mirrors gitattributes and never rewrites binary files, and point at the section.

mutation-testing

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: Medium
    Complexity: Low
    Uncertainty: Known
    Flags: none
    Blocked by: none

    Understood: a docs-only cleanup. 15 passages in 11 files across 10 plugins restate facts that upstream sources own. Each should become a pointer with an as-of date and a recheck trigger, keeping the local decision. Done-when is exact: every row fixed, check-stamps.sh --trigger-less passes on touched files, and each touched plugin has a changelog fragment. Several pointer URLs are marked "confirm the section", so they need checking before use. Similar sibling issues cover other plugins, so I found no 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 2 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. added
    admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.
    on Nov 3, 2026
  7. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  8. 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 41596273911, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T08:41:55Z. 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.

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

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

    @github-actions
    Contributor
    No description provided.
  12. 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