docs\(playbooks\): fix the 53 drift findings from the held-files sweep - part 2 of 2

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

Done when

The three behavior-changing rows go through docs(skills): ship the five eval-gated #6916 drift fixes after a no-loss measurement #11823's eval-gated route.

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

Size: Small
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: #11823

This is part 2 of 2 of #12106, split at intake. It asks for the three behavior-changing playbook drift fixes to go through the eval-gated route tracked in #11823. That route has to land first, so I've listed #11823 as a blocker. Part 1 is a sibling split, not a duplicate. The parent #12106 is still open, so I haven't marked this as a duplicate of it either.

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

Not admitted to the issue lane yet: blocker #11823 is not closed by a listed human or a merge.

No description provided.

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.

No description provided.

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

Matched security word: token. A match holds the stop whether or not the text names a risk, so read the word in context below.

Why, in the run's own words:

already-done: the three behavior-changing rows already went through ＃11823's eval-gated route. PR ＃12926 (merged 2026-11-03, merge commit ae73d0b) shipped the opus-4-8 change. ＃11823 records the per-message effort carve-out as needing no edit. PR ＃12906 (closing ＃12879) shipped the bytes-per-token re-pin. All three are on the default branch at 50fb4e0.

What the run says it did not do:

The merge of PR ＃12906 was not read from its own PR page. The default branch content (SKILL.md:252 at 2.7 bytes per token, CHANGELOG 3.0.2) shows the change is on main.
Tidy, review and verify steps were skipped because nothing was changed.

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

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

Delivered: closing as completed.
Agent choice, not an owner answer.

The done-when "The three behavior-changing rows go through #11823's eval-gated route" holds on main:

#12106 row	Route outcome	Evidence
`criteria.md:467`, `opus-4-8` out of the inert set	Shipped with before/after evals and a negative control	#12926, commit `ae73d0b` (Refs: #11823)
`criteria.md:1337`, per-message effort carve-out	Re-read under the route, no edit needed: the proposed anchor does not exist and `criteria.md` already cites `effort#change-effort-mid-conversation-beta` (lines 1248, 1354, 1363 on `main`)	#11823 record: #11823 (comment)
`audit-instructions/SKILL.md:251`, bytes-per-token re-pin	Shipped at 2.7 with a sound negative control, through the route's follow-up #12879	#12906, commit `ed2611b` (`SKILL.md:275` on `main`)

The lane's stop on this issue was the security keyword token in "bytes-per-token", not a security finding.

This is the last open part of #12106. The parent's other done-when items, carried by #12107, also hold: #12128 (daea6b9) covered the other 50 rows, and the decision on #12107 records 49 of them done, each new pointer with an as-of date and a recheck trigger. That count includes calibration.md:68: #12128 re-pinned it to #rejected-configurations, and the size and MD5 recorded there (from b0da2bb, #12055) matched the live page on 2026-11-02. The last row, calibration.md:72, was reworded as dated history in #12314 (a7e3a0e), which closed #12107 as completed.

Closing as completed on the delivery record above (issuecomment-6620624787).

Navigation Menu

Repository navigation

docs\(playbooks\): fix the 53 drift findings from the held-files sweep - part 2 of 2 #12108

Done when

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

docs\(playbooks\): fix the 53 drift findings from the held-files sweep - part 2 of 2 #12108

Description

Done when

Activity

github-actions commented on Nov 1, 2026

melodic-automation-lanes commented on Nov 1, 2026

github-actions commented on Nov 3, 2026

github-actions commented on Nov 3, 2026

melodic-automation-lanes commented on Nov 3, 2026

github-actions commented on Nov 3, 2026

melodic-automation-lanes commented on Nov 3, 2026

github-actions commented on Nov 4, 2026

github-actions commented on Nov 4, 2026

melodic-automation-lanes commented on Nov 4, 2026

kyle-sexton commented on Nov 4, 2026

kyle-sexton commented on Nov 4, 2026

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions