Repository navigation
feat(prototype): keep explore-directions and build-generator evidence on a throwaway branch after the repository's secrets check #12030
Description
Parent #7591 records the decision "prototype evidence on a throwaway branch after the secrets check" (Q167, Q168), and the recommendation the owner accepted for Q168 speaks of "a prototype's evidence" in general (.work/poteto-review/deepdive/ROUND.md:301). The poteto-review ledger records the owner's answer to Q168 as "accepted as recommended audit A7" (.work/poteto-review/interview-checklist.md:213), and decision row 99 records Q160 and Q165-Q169 as "APPROVED as recommended" (.work/poteto-review/GUIDE.md:209, owner 2026-10-15). Slice S4 adds the evidence step to /prototype:pressure-test; this slice applies the same step to /prototype:explore-directions and /prototype:build-generator.
Done when
-
plugins/prototype/skills/explore-directions/SKILL.mdruns the evidence step S4 defines, after its durable capture and before the variants are deleted. It points at the evidence step inplugins/prototype/context/discipline.md"When done" and does not restate it. For the defaultfile://mockup, which lives outside the repository, the step either copies the page onto the evidence branch or records its local path withnot pushed: <reason>, and says which. -
plugins/prototype/skills/build-generator/SKILL.mdruns the same step before the generating tool is deleted, again by pointing at thatdiscipline.mdsection. It names the generating tool's files as the evidence pushed. -
plugins/prototype/evals/gains one case for each of the two skills. Each case's scaffold has no secrets check, and eachexpected_outcomestates that nothing is pushed and that the note records the local path andnot pushed: <reason>. - A
.changes/prototype/*.mdfragment withbump: minordescribes the change. - The PR's CI is green.
Out of scope
- The canvas and shared-session exceptions in
plugins/prototype/context/discipline.md: those variants live outside the repository.
Related
- Concise skills rollout: prototype (2 skills, 2 model-invoked) #6589 rewrites both skills.
Parent: #7591
Activity
github-actions commentedon Nov 1, 2026
The triage sweep dispatched intake triage for this issue (attempt 1 of 2).
github-actions commentedon Nov 1, 2026
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
I read this as a bounded change. It adds the throwaway-branch evidence step to
/prototype:explore-directionsand/prototype:build-generator. Both skills would point at thediscipline.md"When done" section instead of restating it. It also adds one eval case per skill and a minor.changesfragment. The done-when list is exact and the parent decision is cited, so I'm not asking anything. The slice relies on the evidence step that S4 (/prototype:pressure-test) defines. I couldn't match S4 to an open issue number, so I listed no blocker. No duplicates found among the open issues.Automated triage, applied by the lanes App.
github-actions commentedon Nov 1, 2026
melodic-automation-lanes commentedon Nov 2, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41356922840, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-01T22:35:07Z. work-unblock has now removed and addedagent-readyback 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 addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.melodic-automation-lanes commentedon Nov 2, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41369761125, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-02T01:18:26Z. work-unblock has now removed and addedagent-readyback 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 addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.github-actions commentedon Nov 2, 2026