runcastle 1.2.12 → 1.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "runcastle",
-  "version": "1.2.12",
+  "version": "1.3.1",
   "description": "Burn tickets into shipped features with Claude Code.",
   "license": "FSL-1.1-ALv2",
   "type": "module",

package/skills/burner/review-ticket.md

@@ -156,7 +156,7 @@ Findings from **either** mode go through it — a cited Standards or Spec findin
 
 **Severity is `high` when an acceptance criterion is unmet or data/flow is broken**, `medium` for a real defect that is not that, `low` for the rest. It orders and labels; it never gates.
 
-**Report defects highest severity first.** Each defect mints a fix ticket that burns in this same run, and only the first 8 do — everything after the cap is stored for the human to decide on, so the order you report in decides what gets fixed.
+**Report defects highest severity first.** Each defect mints a fix ticket that burns in this same run, and only the first {{AUTO_FIX_CAP}} do — everything after the cap is stored for the human to decide on, so the order you report in decides what gets fixed.
 
 Report as you find things, never in a batch at the end: a finding you have sent survives an iteration that ends early, and one you were saving up does not. There is no closing wrap-up call — the digest (step 5) is the summary, and your observations render beneath it.
 

package/skills/burner/verify-fixes.md

@@ -0,0 +1,39 @@
+# Verification pass — tour and verify
+
+You are running a bounded verification pass on `{{FEATURE_BRANCH}}` against `{{BASE_BRANCH}}`. The pass you verify is {{VERIFIES_PASS}}. The mode is inherited and never chosen:
+
+{{DRIVE_AVAILABILITY}}
+
+## What landed
+
+{{LANDED_FIXES}}
+
+## Context
+
+Ticket:
+
+{{TICKET_JSON}}
+
+Feature:
+
+{{FEATURE_BRIEF}}
+
+Project docs digest:
+
+{{DOCS_DIGEST}}
+
+Run digests:
+
+{{LAP_DIGESTS}}
+
+## Tour and verify
+
+In **Drive mode**, call `mcp__runcastle__review_drive({ action: "start" })`, start the recorder at `{{WALKTHROUGH_PATH}}`, and walk every acceptance criterion's user-facing surface once at pace. Keep the recorder running for the whole tour. Scrutinise only the landed fixes: check whether each listed repro step still reproduces and inspect the surfaces those fixes touched. Report anything plainly broken during the tour, but do not hunt for unrelated defects. Stop the recorder and drive when finished.
+
+In **Gates mode**, read each fix diff against its finding and run the configured gates exactly once. Do not perform a second two-axis review of the whole branch.
+
+{{GATE_NOTES}}
+
+Report findings through `mcp__runcastle__report_finding` as usual. Verification findings remain open for the human and never mint fix tickets. The ordinary review auto-fix cap is {{AUTO_FIX_CAP}}.
+
+Write `{{DIGEST_PATH}}`. Its first line must name the inherited mode and say "verification pass" (for example, `Drive verification pass`). Summarise which fixes held, which did not, and anything plainly broken on the tour. If the pass cannot run at all, write `{{BLOCKED_PATH}}` with the precise reason instead. End with `<promise>COMPLETE</promise>`.