Skip to content

docs(plugin-options): remove restated Claude Code behavior from the generated README block #12700

Description

@kyle-sexton

Refs: #7292, #7291

Outcome

13 rows of #7292 sit inside the generated plugin-options README block and still state a fact Claude Code owns after #7291 made the template pointer-only. The owner's 2026-10-18 decision keeps a generator's class in its own item, not in the per-plugin slices. Fix the source (the template in scripts/sync-plugin-options-docs.py, or the plugin manifest for an option's own row) and regenerate; do not hand-edit the block.

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

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: 13 rows in the generated plugin-options README block still restate facts Claude Code owns. The fix is to edit the template in scripts/sync-plugin-options-docs.py (or a plugin manifest for an option's own row), swap each restated value for a dated pointer with a recheck trigger, regenerate, and add changelog fragments. It must also pass check-stamps.sh --trigger-less.

    Nothing is missing: every row names its pointer and the edit. The issue is a docs-only change.

    No duplicate found. #12685 to #12699 cover the per-plugin README slices, and this issue covers the generator class.

    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. 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 41596259533, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T08:37: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.

  8. 37 remaining items

  9. removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 4, 2026
  10. melodic-automation-lanes commented on Nov 4, 2026

    @melodic-automation-lanes
    Contributor

    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-run and removed agent-ready: an agent run on a host builds it, and it waits on no decision from a person.

    In the run's words:

    host-only: the issue asks for a template change in scripts/sync-plugin-options-docs.py followed by a regeneration of the generated block ("Fix the source ... and regenerate; do not hand-edit the block"). That regeneration is python3 scripts/sync-plugin-options-docs.py, and this lane cannot run it: it allows no interpreter, and no verification wrapper runs the generator (check-affected runs only the merge-base copy in --check mode, and skips it when the branch changes the generator). The template feeds 55 plugin READMEs, about 300 option-table rows in all; dropping the environment-variable column alone rewrites every row. Hand-writing that output byte-exact, with no local --check, is the hand edit the issue forbids, and with a changelog fragment for each of the 55 plugins it does not fit this run's turn budget. A host run that can execute the generator (and check-stamps.sh --trigger-less) is needed.

    What the run says it did not do:

    • All 13 rows (r016, r033, r036, r070, r073, r086, r087, r163, r165, r322, r401, r408, r442): no template edit and no regeneration, because the generator cannot run in this lane
    • Fetching each candidate upstream pointer to confirm it still documents the fact: not done, since no edit was made
    • check-stamps.sh --trigger-less on touched files: not run, since no files were touched and the lane cannot run it
    • Changelog fragments for the touched plugins: none written, since no plugin changed
    • tidy, review and verify: skipped, since there is no change

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41743082380

    To hand it back to the lane, remove host-run and add agent-ready again.

  11. kyle-sexton commented on Nov 4, 2026

    @kyle-sexton
    MemberAuthor

    Claim. Host-run lane 1 (melo-lap-001) is taking this now, on the hub's H19 order.

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

    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.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