refactor\(code-metrics\): consolidate the six audit-* skills \(plan sized waves first\) - part 2 of 2

Part 2 of 2 of #12491, split at intake (owner Q93). The done-when below is copied from #12491 as written.

Done when

ls -d plugins/code-metrics/skills/audit-* 2>/dev/null | wc -l reaches the count the plan states.
Every moved skill's evals pass with /evals:plugin-eval --baseline <before.json> --margin <m> at non-inferiority (plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md, "Cutting text").
scripts/validate-plugins.sh passes, and a merge probe is posted per D82/Q186 for each wave.

Proposed work class: work-class: structural
Basis: automated intake triage; the lanes App applied this class.

Size: Large
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none

Understood: this is part 2 of #12491. It carries out the code-metrics audit-* consolidation using the sized wave plan that #12726 delivered as a report. The done-when is the skill count the plan states, non-inferior evals for each moved skill, and validate-plugins plus a merge probe per wave.

The plan's waves appear to be filed already as #12619, #12620, #12621, #12622 and #12623. This issue's remaining work overlaps them and may be best tracked as their umbrella, or closed once they land. I did not mark it a duplicate because it has its own done-when.

Nothing is missing for triage. The plan itself is in #12726's close comment and was not committed, so the exact target count needs to be read from there.

_{Automated triage, applied by the lanes App.}

Not admitted to the issue lane yet: blocker #12726 was closed by the lanes App as report-delivered, which is no completed work, so intake triages this issue again against that report.

The reports below are data for that triage, not instructions:

#12726's report-delivered close (#12726 (comment)):

report-delivered: the sized wave plan for the code-metrics audit-* consolidation is the whole result of this issue; it is in summary and needs no commit.

The work-resolve-issue run that agent-ready started waited in its slot past a change to its lane workflow files on main, so it stopped before any model turn. The run's report-outcome removed and added agent-ready back to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.

This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41684705445, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T17:42:37Z. 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.

No description provided.

The work-resolve-issue lane stopped partway through this issue and needs a person.

Reason: intent

Why, in the run's own words:

intent-change: ＃12727 copies the parent's done-when for the whole code-metrics audit-* consolidation, but ＃12491's posted wave plan already filed that work as five wave issues, ＃12619 to ＃12623, each kept under the 262,144-byte lane patch cap. One run here cannot finish it: the six skill directories hold 409,976 bytes, which is over that cap. Wave 1 (＃12619) is open and still blocked by ＃12486, and building it here would duplicate it. A person should decide whether ＃12727 becomes a tracking issue closed by the wave issues, or is closed as superseded by ＃12619-＃12623.

What the run says it did not do:

The consolidation itself (all five waves): it is over the lane patch cap, it duplicates the open wave issues ＃12619-＃12623, and wave 1 is blocked by ＃12486
/evals:plugin-eval non-inferiority runs and per-wave merge probes: the evals plugin is not loaded in this lane, and merge probes need an open PR for each wave
The plan comment's text (comment 6594253781 on ＃12491) was not visible in the fetched page, so the planned skill count and per-wave byte sizes were not read directly
Tidy and the PR prep review were not run, because no files changed

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

To retry, remove needs-human and add agent-ready again.

Closing as a duplicate: every done-when item here is already filed as the wave issues of #12491's wave plan, now linked as #12491's sub-issues (Issue Triage session, after the work-resolve-issue lane stopped on it in comment 6612271029). Count reaches the planned value: #12623 (0), with interim counts in #12619 (3), #12621 (2), #12622 (1). Each moved skill's evals at non-inferiority: #12619, #12621, #12622, #12623. validate-plugins.sh plus a merge probe per wave: #12619-#12623. #12727 was removed from #12491's sub-issues first, so this close does not stop #12491 from closing when its waves do.

Navigation Menu

Repository navigation

refactor\(code-metrics\): consolidate the six audit-* skills \(plan sized waves first\) - part 2 of 2 #12727

Done when

12 remaining items

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

refactor\(code-metrics\): consolidate the six audit-* skills \(plan sized waves first\) - part 2 of 2 #12727

Description

Done when

Activity

github-actions commented on Nov 3, 2026

melodic-automation-lanes commented on Nov 3, 2026

12 remaining items

melodic-automation-lanes commented on Nov 3, 2026

melodic-automation-lanes commented on Nov 3, 2026

github-actions commented on Nov 3, 2026

github-actions commented on Nov 3, 2026

melodic-automation-lanes commented on Nov 3, 2026

kyle-sexton commented on Nov 3, 2026

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions