@gobing-ai/spur 0.3.72 → 0.3.74

package/config/workflows/task-pipeline.yaml

@@ -27,6 +27,9 @@
 "$schema": "@gobing-ai/spur/schemas/state-machine-workflow.schema.json"
 kind: state-machine
 name: task-pipeline
+# 0772 R2: explicit identity tag. Set only after the proof failure-path tests
+# passed; the engine treats unversioned external definitions as supported.
+version: "1"
 description: "Standard task pipeline: precheck → implement → quality-gate (test/fix/recheck) → review → approve → verify → record → done"
 # Task entity lifecycle (owned by task-lifecycle.yaml):
 #   normal: backlog → todo → wip → testing → done
@@ -40,867 +43,949 @@ description: "Standard task pipeline: precheck → implement → quality-gate (t
 iterationBound: 20
 initialState: precheck
 terminalStates:
-  - done
-  - failed
-  - cancelled
+    - done
+    - failed
+    - cancelled
 failureStates:
-  - failed
-  - cancelled
+    - failed
+    - cancelled
 vars:
-  wbs: "0000"
-  profile: "standard"
-  # PATH-independent spur invocation for shell guards/actions. The CLI overrides this
-  # at run start (resolveSpurBin); the literal default is a safe fallback so direct/dry
-  # runs and `workflow validate` resolve the template. (See AGENTS.md / ADR-026.)
-  spurBin: "spur"
-  # Agent the pipeline's agent.run steps invoke. Override per run with
-  # `--vars '{"agent":"claude"}'`. `auto` is the reserved config-resolving selector:
-  # `agent.default` role -> tier -> cheapest USABLE executor. A named literal here would
-  # pin a box-specific binary into tracked SSOT and escape that usability ladder.
-  agent: "auto"
-  # Implement-only executor override (R1, task 0454). Resolves like `agent` unless
-  # overridden. The `--agent` flag (execution-batch.md §3.2) forwards into BOTH
-  # `agent` and `implementAgent`, so a pinned `--agent X` reaches implement too. To
-  # pin ONLY implement while other hops keep the default, pass
-  # `--vars '{"implementAgent":"omp-zai"}'`.
-  implementAgent: "auto"
-  # Step-level timeout for agentic hops (review / verify / test-fix) in ms.
-  # Soft quality-gate shells are unbounded by this var (host shell only).
-  # Raised 600s → 1800s (task 0398 R4 / H6 dogfood). Override:
-  # `--vars '{"stepTimeoutMs":"120000"}'`. 30 min is headroom, not a licence to
-  # run unbounded — if a hop still hits this wall, STOP and record it.
-  stepTimeoutMs: "1800000"
-  # Timeout for the `implement` step specifically (R2a). Implementation is the
-  # heaviest agent.run step (full read/write/test-probe loop) and has timed out
-  # at the 600s default in five consecutive dogfood runs (bugs 742/744/746/748),
-  # a 100% failure rate at that budget. 30 min gives real headroom; STOP and
-  # record honestly rather than raising it further without operator sign-off.
-  implementTimeoutMs: "1800000"
-  # Answer captured by the approve gate's hitl.confirm (R1): "yes" | "no" | "cancel".
-  # Empty by default; only meaningful once the approve state has been entered.
-  __hitlAnswer: ""
-  # Proof-state bracket (task 0612, ADR-071; restructured by task 0703). `proofDigest` is the
-  # canonical capture taken at quality-gate ENTRY — immediately before the evidence-producing
-  # final chain (quality → review → verify) — and re-captured at `test-recheck` when bounded
-  # remediation mutated the tree, so every evidence stage names one fresh digest (R2/R4).
-  # `proofDigestNow` is the live re-capture compared against `proofDigest` at verify entry and
-  # immediately before `record`; a mismatch means a proof input changed after evidence was
-  # established, so the run routes to `failed` instead of crossing the completion boundary (R5).
-  # `taskSpecPath` carries the task file path because `docs/tasks*` is excluded from the digest's
-  # git-tree half — spec content is folded in explicitly or a task-file edit would go undetected.
-  # The fingerprint scopes task content to the proof-input sections only (Background, Requirements,
-  # Acceptance Criteria, Design, Plan), so record-time Solution/Testing/Review evidence writes do
-  # not retroactively invalidate the certified input set (R6).
-  proofDigest: ""
-  proofDigestNow: ""
-  taskSpecPath: ""
-  # 0710 R4: task priority tier (P0..P4) extracted from the task frontmatter at the
-  # quality-gate stage. P0/P1 make the review/verify distinct-executor policy apply;
-  # unknown/empty priority means fresh-context-only (executor reuse allowed).
-  taskPriority: ""
-  # Project quality gate for the `test` hop (probe + fixall + recheck). Override per project
-  # with the same package-manager surface (this monorepo is Bun-only):
-  # `--vars '{"qualityGateCmd":"bun run lint && bun run test"}'`. Soft probe, hard recheck,
-  # and the fixall slash input all use this same var so the command stays single-sourced.
-  # TRUSTED CONFIG ONLY — this string is executed via `sh -c` (see test/test-recheck). Never
-  # interpolate untrusted operator/LLM input into qualityGateCmd (task 0436 SECUA residual).
-  # NO `format` PREFIX: `implement` already ran `$formatCmd` on its way out, and `test`
-  # captures `proofDigest` (onEnter[3]) BEFORE this command runs (onEnter[4]) — a formatter
-  # inside the gate rewrites the very tree the digest just fingerprinted (ADR-071 proof
-  # window). It was a no-op only because the implement-stage format got there first; that is
-  # an accident, not an invariant. The gate observes, it does not mutate.
-  qualityGateCmd: "bun run spur-check"
-  # Cheap red-detector run before the full gate on **recheck only**; empty ⇒ no probe
-  # (full gate every recheck — the pre-0587 behavior). A project overriding qualityGateCmd
-  # should override this too. TRUSTED CONFIG ONLY — executed via `sh -c` (same surface as
-  # qualityGateCmd). Invariant: `review` is only ever entered through a full green
-  # qualityGateCmd — only the full gate writes PASS to <wbs>-test-gate.status.
-  gateProbeCmd: "bun run lint"
-  # Max /sp:dev-fixall attempts after a red quality-gate probe/recheck (bounded; no thrash).
-  # Attempt counter: .spur/run/<wbs>-test-fix-attempt. Default 2 = two fixall hops before failed.
-  qualityGateMaxFixAttempts: "2"
-  # Post-implement auto-format. Overridable like qualityGateCmd so a non-Bun seeded
-  # project can point it at its own formatter; invoked best-effort (a missing or
-  # failing formatter must never abort a run — the quality gate is the real gate).
-  formatCmd: "bun run format"
-  # Bounded `file:line` anchors extracted from the failing quality-gate log by the
-  # `test` / `test-recheck` hops (deduped, max 20, space-separated on one line).
-  # `test-fix` reads `.spur/run/<wbs>-test-gate.findings` into this var and names the
-  # anchors directly in the /sp:dev-fixall input, so the fix agent starts AT the failing
-  # file:line instead of re-deriving it from a fresh gate run (0482 R3).
-  gateFindings: ""
-  # Max R-items in ## Requirements before size precheck fails (R2, task 0454).
-  # Override with `--vars '{"maxImplementReqs":"20"}'`.
-  maxImplementReqs: "10"
-  # Max checklist items under ## Plan before size precheck fails (R2, task 0454).
-  # Override with `--vars '{"maxImplementPlanItems":"32"}'`.
-  maxImplementPlanItems: "16"
-  # Diff-scope guard on the implement hop (R1, task 0487). When the target task
-  # body backticks at least one path, non-corpus changes outside those paths
-  # fail the step by name. New files beside a declared file are allowed. Empty
-  # (default) = on; set to "off" to bypass:
-  # `--vars '{"implementScopeGuard":"off"}'`.
-  implementScopeGuard: ""
+    wbs: "0000"
+    profile: "standard"
+    mode: ""
+    __runId: ""
+    __definitionDigest: ""
+    # PATH-independent spur invocation for shell guards/actions. The CLI overrides this
+    # at run start (resolveSpurBin); the literal default is a safe fallback so direct/dry
+    # runs and `workflow validate` resolve the template. (See AGENTS.md / ADR-026.)
+    spurBin: "spur"
+    # Agent the pipeline's agent.run steps invoke. Override per run with
+    # `--vars '{"agent":"claude"}'`. `auto` is the reserved config-resolving selector:
+    # `agent.default` role -> tier -> cheapest USABLE executor. A named literal here would
+    # pin a box-specific binary into tracked SSOT and escape that usability ladder.
+    # It does not inherit the host session's interactive model; required capability
+    # attestation still gates the chosen executor before dispatch (0706).
+    agent: "auto"
+    # Implement-only executor override (R1, task 0454). Resolves like `agent` unless
+    # overridden. The `--agent` flag (execution-batch.md §3.2) forwards into BOTH
+    # `agent` and `implementAgent`, so a pinned `--agent X` reaches implement too. To
+    # pin ONLY implement while other hops keep the default, pass
+    # `--vars '{"implementAgent":"pi-zai"}'`.
+    implementAgent: "auto"
+    # Remediation can mutate code only when BOTH this cap and the task's declared
+    # mutationPolicy permit code. none/tests require scoped manual repair, not fixall.
+    mutationPolicy: "code"
+    # Step-level timeout for agentic hops (review / verify / test-fix) in ms.
+    # Soft quality-gate shells are unbounded by this var (host shell only).
+    # Raised 600s → 1800s (task 0398 R4 / H6 dogfood). Override:
+    # `--vars '{"stepTimeoutMs":"120000"}'`. 30 min is headroom, not a licence to
+    # run unbounded — if a hop still hits this wall, STOP and record it.
+    stepTimeoutMs: "1800000"
+    # Timeout for the `implement` step specifically (R2a). Implementation is the
+    # heaviest agent.run step (full read/write/test-probe loop) and has timed out
+    # at the 600s default in five consecutive dogfood runs (bugs 742/744/746/748),
+    # a 100% failure rate at that budget. 30 min gives real headroom; STOP and
+    # record honestly rather than raising it further without operator sign-off.
+    implementTimeoutMs: "1800000"
+    # Answer captured by the approve gate's hitl.confirm (R1): "yes" | "no" | "cancel".
+    # Empty by default; only meaningful once the approve state has been entered.
+    __hitlAnswer: ""
+    # Proof-state bracket (task 0612, ADR-071; restructured by task 0703). `proofDigest` is the
+    # canonical capture taken at quality-gate ENTRY — immediately before the evidence-producing
+    # final chain (quality → review → verify) — and re-captured at `test-recheck` when bounded
+    # remediation mutated the tree, so every evidence stage names one fresh digest (R2/R4).
+    # `proofDigestNow` is the live re-capture compared against `proofDigest` at verify entry and
+    # immediately before `record`; a mismatch means a proof input changed after evidence was
+    # established, so the run routes to `failed` instead of crossing the completion boundary (R5).
+    # `taskSpecPath` carries the task file path because `docs/tasks*` is excluded from the digest's
+    # git-tree half — spec content is folded in explicitly or a task-file edit would go undetected.
+    # The fingerprint scopes task content to the proof-input sections only (Background, Requirements,
+    # Acceptance Criteria, Design, Plan), so record-time Solution/Testing/Review evidence writes do
+    # not retroactively invalidate the certified input set (R6).
+    proofDigest: ""
+    proofDigestNow: ""
+    taskSpecPath: ""
+    # 0710 R4: task priority tier (P0..P4) extracted from the task frontmatter at the
+    # quality-gate stage. P0/P1 make the review/verify distinct-executor policy apply;
+    # unknown/empty priority means fresh-context-only (executor reuse allowed).
+    taskPriority: ""
+    # Project quality gate for the `test` hop (probe + fixall + recheck). Override per project
+    # with the same package-manager surface (this monorepo is Bun-only):
+    # `--vars '{"qualityGateCmd":"bun run lint && bun run test"}'`. Soft probe, hard recheck,
+    # and the fixall slash input all use this same var so the command stays single-sourced.
+    # TRUSTED CONFIG ONLY — this string is executed via `sh -c` (see test/test-recheck). Never
+    # interpolate untrusted operator/LLM input into qualityGateCmd (task 0436 SECUA residual).
+    # NO `format` PREFIX: `implement` already ran `$formatCmd` on its way out, and `test`
+    # captures `proofDigest` (onEnter[3]) BEFORE this command runs (onEnter[4]) — a formatter
+    # inside the gate rewrites the very tree the digest just fingerprinted (ADR-071 proof
+    # window). It was a no-op only because the implement-stage format got there first; that is
+    # an accident, not an invariant. The gate observes, it does not mutate.
+    qualityGateCmd: "bun run spur-check"
+    # Cheap red-detector run before the full gate on **recheck only**; empty ⇒ no probe
+    # (full gate every recheck — the pre-0587 behavior). A project overriding qualityGateCmd
+    # should override this too. TRUSTED CONFIG ONLY — executed via `sh -c` (same surface as
+    # qualityGateCmd). Invariant: `review` is only ever entered through a full green
+    # qualityGateCmd — only the full gate writes PASS to <wbs>-test-gate.status.
+    gateProbeCmd: "bun run lint"
+    # Max /sp:dev-fixall attempts after a red quality-gate probe/recheck (bounded; no thrash).
+    # Attempt counter: .spur/run/<wbs>-test-fix-attempt. Default 2 = two fixall hops before failed.
+    qualityGateMaxFixAttempts: "2"
+    # Post-implement auto-format. Overridable like qualityGateCmd so a non-Bun seeded
+    # project can point it at its own formatter; invoked best-effort (a missing or
+    # failing formatter must never abort a run — the quality gate is the real gate).
+    formatCmd: "bun run format"
+    # Bounded `file:line` anchors extracted from the failing quality-gate log by the
+    # `test` / `test-recheck` hops (deduped, max 20, space-separated on one line).
+    # `test-fix` reads `.spur/run/<wbs>-test-gate.findings` into this var and names the
+    # anchors directly in the /sp:dev-fixall input, so the fix agent starts AT the failing
+    # file:line instead of re-deriving it from a fresh gate run (0482 R3).
+    gateFindings: ""
+    # Max R-items in ## Requirements before size precheck fails (R2, task 0454).
+    # Override with `--vars '{"maxImplementReqs":"20"}'`.
+    maxImplementReqs: "10"
+    # Max checklist items under ## Plan before size precheck fails (R2, task 0454).
+    # Override with `--vars '{"maxImplementPlanItems":"32"}'`.
+    maxImplementPlanItems: "16"
+    # Diff-scope guard on the implement hop (R1, task 0487). When the target task
+    # body backticks at least one path, non-corpus changes outside those paths
+    # fail the step by name. New files beside a declared file are allowed. Empty
+    # (default) = on; set to "off" to bypass:
+    # `--vars '{"implementScopeGuard":"off"}'`.
+    implementScopeGuard: ""
 
 states:
-  - id: precheck
-    description: >
-      Fast deterministic task readiness and size checks. Failures route to the
-      `failed` terminal state (not a raw lifecycle abort mid-enter).
-    onEnter:
-      # R6 (0487): pre-launch hygiene WARNING (never a block) — starting a task on
-      # a tree already dirty with another task's implementation is how 0485's diff
-      # got swept into 0486's run. Corpus dirs are excluded: the pipeline writes
-      # those itself.
-      # R1 (0511): task-corpus dirt gets its own advisory NOTE — docs/tasks* is
-      # excluded from the non-corpus warning, so pre-existing task-corpus edits are
-      # invisible at launch yet can be accidentally staged with the current task
-      # later. Advisory only (never a block): the pipeline legitimately updates
-      # task files, so corpus dirt is launch-time visibility, not a lifecycle guard.
-      - kind: shell
-        options:
-          command: >-
-            DIRTY=$(git status --porcelain -- . ':(exclude)docs/tasks*' ':(exclude)docs/features' 2>/dev/null);
-            if [ -n "$DIRTY" ]; then
-              echo "precheck: WARNING - working tree has uncommitted non-corpus changes; commit or stash before starting a new task:";
-              echo "$DIRTY";
-            fi;
-            CORPUS_DIRTY=$(git status --porcelain -- ':(glob)docs/tasks*/**' 2>/dev/null);
-            if [ -n "$CORPUS_DIRTY" ]; then
-              echo "precheck: NOTE - task corpus has uncommitted changes; review before staging with this task:";
-              echo "$CORPUS_DIRTY";
-            fi;
-            exit 0
-      - kind: note
-        options:
-          # R4 task_run_links linkage (kind=pipeline) is written by a WorkflowService
-          # hook at run start — see the 0062 follow-up note; there is no link-writing
-          # CLI verb to call from a shell step, so it cannot live in pure YAML.
-          message: "Pipeline start for task ${vars.wbs}."
-      # R1 (0453): auto-profile precheck reopens a done feature before task check.
-      # Under profile=auto, resolve feature_id, sync (preferred) or update to active.
-      # Under non-auto, leave R4 message to guide the operator.
-      # R3 (0723): a real reactivation failure is surfaced, not swallowed —
-      # the default 'fail' onEnter policy halts the sequence and routes the
-      # run to `failed` before implementation. Verbs stay single-shot:
-      # one sync, then one update fallback, never retried in a loop.
-      - kind: shell
-        options:
-          command: >-
-            if [ "$profile" = auto ]; then
-              FID=$($spurBin task show $wbs --json 2>/dev/null |
-              jq -r '.feature_id // .frontmatter.feature_id // empty' 2>/dev/null);
-              if [ -n "$FID" ]; then
-                if ! $spurBin feature sync "$FID" --force 2>/dev/null; then
-                if ! $spurBin feature update "$FID" active 2>/dev/null; then
-                echo "precheck: FAIL - feature reactivation $FID failed;" >&2;
-                echo "precheck: feature sync + feature update both errored" >&2;
-                exit 1;
-                fi;
-                fi;
-              fi;
-            fi;
-            exit 0
-      # R2 (0454, 0723): task size precheck — deterministic count-only
-      # evaluation of R-item and Plan-item counts. No executor-tier policy:
-      # dispatch-time requiresCapabilities at `agent.run` is the
-      # authoritative capability check. Writes PASS/FAIL to
-      # .spur/run/<wbs>-precheck-size.status. Always exit 0 (soft action);
-      # the precheck→implement guard reads the file, so a missing checker
-      # fails closed (writes FAIL, never PASS).
-      - kind: shell
-        options:
-          command: >-
-            SIZE_FILE=".spur/run/$wbs-precheck-size.status" &&
-            mkdir -p .spur/run &&
-            SIZE_SCRIPT="plugins/sp/scripts/task-size-precheck.ts";
-            [ -f "$SIZE_SCRIPT" ] ||
-            SIZE_SCRIPT="$(superskill script path sp task-size-precheck.ts 2>/dev/null)";
-            if [ -n "$SIZE_SCRIPT" ] && [ -f "$SIZE_SCRIPT" ]; then
-            bun "$SIZE_SCRIPT" "$wbs"
-            --spur-bin "$spurBin" --max-reqs "$maxImplementReqs"
-            --max-plan-items "$maxImplementPlanItems";
-            else
-              echo "task-size-precheck failed closed — checker not found in" >&2 &&
-              echo "plugins/sp/scripts/ nor staged; run 'superskill install sp'." >&2 &&
-              echo "FAIL" > "$SIZE_FILE";
-            fi &&
-            exit 0
-      # 0726 R2: task evidence precheck — deterministic live-data
-      # evidence-channel proof before implement dispatch. Writes PASS/FAIL to
-      # .spur/run/<wbs>-precheck-evidence.status. Always exit 0 (soft action);
-      # the precheck→implement guard reads the file, so a missing checker
-      # fails closed (writes FAIL, never PASS).
-      - kind: shell
-        options:
-          command: >-
-            EVID_FILE=".spur/run/$wbs-precheck-evidence.status" &&
-            mkdir -p .spur/run &&
-            EVID_SCRIPT="plugins/sp/scripts/task-evidence-precheck.ts";
-            [ -f "$EVID_SCRIPT" ] ||
-            EVID_SCRIPT="$(superskill script path sp task-evidence-precheck.ts 2>/dev/null)";
-            if [ -n "$EVID_SCRIPT" ] && [ -f "$EVID_SCRIPT" ]; then
-            bun "$EVID_SCRIPT" "$wbs"
-            --spur-bin "$spurBin";
-            else
-              echo "task-evidence-precheck failed closed — checker not found" >&2 &&
-              echo "in plugins/sp/scripts/ nor staged; run 'superskill install sp'." >&2 &&
-              echo "FAIL" > "$EVID_FILE";
-            fi &&
-            exit 0
+    - id: precheck
+      description: >
+          Fast deterministic task readiness and size checks. Failures route to the
+          `failed` terminal state (not a raw lifecycle abort mid-enter).
+      onEnter:
+          # R6 (0487): pre-launch hygiene WARNING (never a block) — starting a task on
+          # a tree already dirty with another task's implementation is how 0485's diff
+          # got swept into 0486's run. Corpus dirs are excluded: the pipeline writes
+          # those itself.
+          # R1 (0511): task-corpus dirt gets its own advisory NOTE — docs/tasks* is
+          # excluded from the non-corpus warning, so pre-existing task-corpus edits are
+          # invisible at launch yet can be accidentally staged with the current task
+          # later. Advisory only (never a block): the pipeline legitimately updates
+          # task files, so corpus dirt is launch-time visibility, not a lifecycle guard.
+          - kind: shell
+            options:
+                command: >-
+                    DIRTY=$(git status --porcelain -- . ':(exclude)docs/tasks*' ':(exclude)docs/features' 2>/dev/null);
+                    if [ -n "$DIRTY" ]; then
+                      echo "precheck: WARNING - working tree has uncommitted non-corpus changes; commit or stash before starting a new task:";
+                      echo "$DIRTY";
+                    fi;
+                    CORPUS_DIRTY=$(git status --porcelain -- ':(glob)docs/tasks*/**' 2>/dev/null);
+                    if [ -n "$CORPUS_DIRTY" ]; then
+                      echo "precheck: NOTE - task corpus has uncommitted changes; review before staging with this task:";
+                      echo "$CORPUS_DIRTY";
+                    fi;
+                    exit 0
+          - kind: note
+            options:
+                # R4 task_run_links linkage (kind=pipeline) is written by a WorkflowService
+                # hook at run start — see the 0062 follow-up note; there is no link-writing
+                # CLI verb to call from a shell step, so it cannot live in pure YAML.
+                message: "Pipeline start for task ${vars.wbs}."
+          # R1 (0453): auto-profile precheck reopens a done feature before task check.
+          # Under profile=auto, resolve feature_id, sync (preferred) or update to active.
+          # Under non-auto, leave R4 message to guide the operator.
+          # R3 (0723): a real reactivation failure is surfaced, not swallowed —
+          # the default 'fail' onEnter policy halts the sequence and routes the
+          # run to `failed` before implementation. Verbs stay single-shot:
+          # one sync, then one update fallback, never retried in a loop.
+          - kind: shell
+            options:
+                command: >-
+                    if [ "$profile" = auto ]; then
+                      FID=$($spurBin task show $wbs --json 2>/dev/null |
+                      jq -r '.feature_id // .frontmatter.feature_id // empty' 2>/dev/null);
+                      if [ -n "$FID" ]; then
+                        if ! $spurBin feature sync "$FID" --force 2>/dev/null; then
+                        if ! $spurBin feature update "$FID" active 2>/dev/null; then
+                        echo "precheck: FAIL - feature reactivation $FID failed;" >&2;
+                        echo "precheck: feature sync + feature update both errored" >&2;
+                        exit 1;
+                        fi;
+                        fi;
+                      fi;
+                    fi;
+                    exit 0
+          # R2 (0454, 0723): task size precheck — deterministic count-only
+          # evaluation of R-item and Plan-item counts. No executor-tier policy:
+          # dispatch-time requiresCapabilities at `agent.run` is the
+          # authoritative capability check. Writes PASS/FAIL to
+          # .spur/run/<wbs>-precheck-size.status. Always exit 0 (soft action);
+          # the precheck→implement guard reads the file, so a missing checker
+          # fails closed (writes FAIL, never PASS).
+          - kind: shell
+            options:
+                command: >-
+                    SIZE_FILE=".spur/run/$wbs-precheck-size.status" &&
+                    mkdir -p .spur/run &&
+                    SIZE_SCRIPT="plugins/sp/scripts/task-size-precheck.ts";
+                    [ -f "$SIZE_SCRIPT" ] ||
+                    SIZE_SCRIPT="$(superskill script path sp task-size-precheck.ts 2>/dev/null)";
+                    if [ -n "$SIZE_SCRIPT" ] && [ -f "$SIZE_SCRIPT" ]; then
+                    bun "$SIZE_SCRIPT" "$wbs"
+                    --spur-bin "$spurBin" --max-reqs "$maxImplementReqs"
+                    --max-plan-items "$maxImplementPlanItems";
+                    else
+                      echo "task-size-precheck failed closed — checker not found in" >&2 &&
+                      echo "plugins/sp/scripts/ nor staged; run 'superskill install sp'." >&2 &&
+                      echo "FAIL" > "$SIZE_FILE";
+                    fi &&
+                    exit 0
+          # 0726 R2: task evidence precheck — deterministic live-data
+          # evidence-channel proof before implement dispatch. Writes PASS/FAIL to
+          # .spur/run/<wbs>-precheck-evidence.status. Always exit 0 (soft action);
+          # the precheck→implement guard reads the file, so a missing checker
+          # fails closed (writes FAIL, never PASS).
+          - kind: shell
+            options:
+                command: >-
+                    EVID_FILE=".spur/run/$wbs-precheck-evidence.status" &&
+                    mkdir -p .spur/run &&
+                    EVID_SCRIPT="plugins/sp/scripts/task-evidence-precheck.ts";
+                    [ -f "$EVID_SCRIPT" ] ||
+                    EVID_SCRIPT="$(superskill script path sp task-evidence-precheck.ts 2>/dev/null)";
+                    if [ -n "$EVID_SCRIPT" ] && [ -f "$EVID_SCRIPT" ]; then
+                    bun "$EVID_SCRIPT" "$wbs"
+                    --spur-bin "$spurBin";
+                    else
+                      echo "task-evidence-precheck failed closed — checker not found" >&2 &&
+                      echo "in plugins/sp/scripts/ nor staged; run 'superskill install sp'." >&2 &&
+                      echo "FAIL" > "$EVID_FILE";
+                    fi &&
+                    exit 0
+          # Proportional route table evaluation (0759 R1/R4). The reason artifact is RUN-scoped, not
+          # wbs-scoped: ADR-107 names `.spur/run/<runId>-route-reason.txt`, and a wbs-scoped path lets
+          # a re-run of the same task overwrite the earlier run's route claim, so the artifact could
+          # not attribute a route to the run that took it (0759 R5). `__runId` is injected by
+          # WorkflowAppService.run(); the wbs fallback keeps a driver-less invocation from writing to
+          # a bare "-route-reason.txt". The log line carries the run id for the same reason — an
+          # unattributed append is log scraping, which R5 explicitly rejects as evidence.
+          - kind: shell
+            options:
+                command: >-
+                    mkdir -p .spur/run .spur/memory &&
+                    RUN_ID="$__runId" &&
+                    if [ -z "$RUN_ID" ]; then RUN_ID="pipeline-$wbs"; fi &&
+                    REASON_FILE=".spur/run/$RUN_ID-route-reason.txt" &&
+                    if [ "$mode" = "fast" ]; then
+                      echo "fast:evidence complete+consistent" > "$REASON_FILE";
+                    elif [ -z "$mode" ]; then
+                      echo "safety:standard verification" > "$REASON_FILE";
+                    elif [ "$mode" = "unknown" ]; then
+                      echo "safety:unknown evidence quality" > "$REASON_FILE";
+                    elif [ "$mode" = "conflict" ]; then
+                      echo "safety:conflicting evidence" > "$REASON_FILE";
+                    else
+                      echo "safety:unrecognized evidence (mode=$mode)" > "$REASON_FILE";
+                    fi &&
+                    printf '%s %s %s\n' "$RUN_ID" "$wbs" "$(cat "$REASON_FILE")"
+                    >> .spur/memory/task-pipeline-routes.log &&
+                    exit 0
 
-  - id: implement
-    description: >
-      Run agent-driven implementation via /sp:dev-run --mode implement, THEN move the
-      task to `wip` via the normal verb. The lifecycle transition fires AFTER the
-      implement agent.run succeeds — onEnter runs in declaration order and the default
-      'fail' policy halts the sequence (routing the run to `failed`) if the agent.run
-      fails or times out, so a halted implement never leaves the task at `wip` with an
-      empty Solution (the F3 half-state). The `--no-lifecycle` flag is correct here: the
-      pipeline owns this transition; the FSM guard would otherwise re-run `spur task
-      check`, which is precheck's job.
-      NOTE: this step must NOT call /sp:dev-run in full mode (the default) —
-      that command DRIVES this pipeline, so calling it here recurses.
-      --mode implement is the single-step implement entry.
-    onEnter:
-      - kind: agent.run
-        options:
-          agent: ${vars.implementAgent}
-          # Pure slash command only (ADR-043). Anti-recursion / implement discipline
-          # Declared Layer-1 role (0538 R2/0710 R7): routing reason; no executor pin — role routing feeds the distinctness gate.
-          role: coder
-          # lives in /sp:dev-run --mode implement → sp:code-implementation, not YAML prose.
-          input: /sp:dev-run --mode implement ${vars.wbs} --auto
-          timeoutMs: ${vars.implementTimeoutMs}
-          # R3 (task 0424): empty-implement no-op guard — the agent.run action
-          # fails the step when exit 0 produced zero non-corpus file changes, so
-          # a silent no-op routes the run to `failed` here instead of drifting
-          # into test/review and being caught a full pass later.
-          requireDiff: true
-          # 0706 R6: this stage mutates the working tree unattended under the
-          # auto profile, so it declares minimum execution-capability
-          # requirements. Dispatch fails closed (before spawn) when the
-          # resolved executor's attestation cannot satisfy them — attest the
-          # executor in agent config.
-          requiresCapabilities:
-            fsWrite: available
-            processSpawn: available
-      - kind: shell
-        options:
-          command: >-
-            retry_transient() {
-              RETRY_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
-              printf '%s\n' "$RETRY_OUTPUT";
-              if [ "$RETRY_RC" -eq 0 ]; then return 0; fi;
-              if ! printf '%s' "$RETRY_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY|database is locked'; then return "$RETRY_RC"; fi;
-              sleep 2;
-              RETRY_SECOND_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
-              printf '%s\n' "$RETRY_SECOND_OUTPUT";
-              if [ "$RETRY_RC" -ne 0 ] && printf '%s\n%s' "$RETRY_OUTPUT" "$RETRY_SECOND_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY'; then
-                echo "node_modules link/dependency broken — run bun install and retry";
-              fi;
-              return "$RETRY_RC";
-            };
-            retry_transient $spurBin task update "$wbs" wip --no-lifecycle
-      # Post-implement cleanup: auto-format any unformatted output the agent produced.
-      # The agent may leave files that don't pass `biome check`, which then fails
-      # `bun run lint` downstream. Running format here is cheap (< 1 s) and prevents
-      # the test stage from tripping on a purely mechanical formatting defect (dogfood
-      # bug-733 — omp left agent-run.test.ts unformatted, causing a spurious lint gate
-      # failure that the ## Testing section mis-attributed to "pre-existing gaps").
-      # Best-effort: `; exit 0` (not `&&`) so a missing/failing formatter in a seeded
-      # non-Bun project cannot abort a run mid-implement. Formatting is a convenience;
-      # `${vars.qualityGateCmd}` at `test` is the gate that actually decides.
-      - kind: shell
-        options:
-          command: "$formatCmd ; exit 0"
+    - id: implement
+      description: >
+          Run agent-driven implementation via /sp:dev-run --mode implement, THEN move the
+          task to `wip` via the normal verb. The lifecycle transition fires AFTER the
+          implement agent.run succeeds — onEnter runs in declaration order and the default
+          'fail' policy halts the sequence (routing the run to `failed`) if the agent.run
+          fails or times out, so a halted implement never leaves the task at `wip` with an
+          empty Solution (the F3 half-state). The `--no-lifecycle` flag is correct here: the
+          pipeline owns this transition; the FSM guard would otherwise re-run `spur task
+          check`, which is precheck's job.
+          NOTE: this step must NOT call /sp:dev-run in full mode (the default) —
+          that command DRIVES this pipeline, so calling it here recurses.
+          --mode implement is the single-step implement entry.
+      onEnter:
+          - kind: agent.run
+            options:
+                agent: ${vars.implementAgent}
+                # Pure slash command only (ADR-043). Anti-recursion / implement discipline
+                # Declared Layer-1 role (0538 R2/0710 R7): routing reason; no executor pin — role routing feeds the distinctness gate.
+                role: coder
+                # lives in /sp:dev-run --mode implement → sp:code-implementation, not YAML prose.
+                input: /sp:dev-run --mode implement ${vars.wbs} --auto
+                timeoutMs: ${vars.implementTimeoutMs}
+                # R3 (task 0424): empty-implement no-op guard — the agent.run action
+                # fails the step when exit 0 produced zero non-corpus file changes, so
+                # a silent no-op routes the run to `failed` here instead of drifting
+                # into test/review and being caught a full pass later.
+                requireDiff: true
+                # 0706 R6: this stage mutates the working tree unattended under the
+                # auto profile, so it declares minimum execution-capability
+                # requirements. Dispatch fails closed (before spawn) when the
+                # resolved executor's attestation cannot satisfy them — attest the
+                # executor in agent config.
+                requiresCapabilities:
+                    fsWrite: available
+                    processSpawn: available
+          - kind: shell
+            options:
+                command: >-
+                    retry_transient() {
+                      RETRY_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
+                      printf '%s\n' "$RETRY_OUTPUT";
+                      if [ "$RETRY_RC" -eq 0 ]; then return 0; fi;
+                      if ! printf '%s' "$RETRY_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY|database is locked'; then return "$RETRY_RC"; fi;
+                      sleep 2;
+                      RETRY_SECOND_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
+                      printf '%s\n' "$RETRY_SECOND_OUTPUT";
+                      if [ "$RETRY_RC" -ne 0 ] && printf '%s\n%s' "$RETRY_OUTPUT" "$RETRY_SECOND_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY'; then
+                        echo "node_modules link/dependency broken — run bun install and retry";
+                      fi;
+                      return "$RETRY_RC";
+                    };
+                    retry_transient $spurBin task update "$wbs" wip --no-lifecycle
+          # Post-implement cleanup: auto-format any unformatted output the agent produced.
+          # The agent may leave files that don't pass `biome check`, which then fails
+          # `bun run lint` downstream. Running format here is cheap (< 1 s) and prevents
+          # the test stage from tripping on a purely mechanical formatting defect (dogfood
+          # bug-733 — omp left agent-run.test.ts unformatted, causing a spurious lint gate
+          # failure that the ## Testing section mis-attributed to "pre-existing gaps").
+          # Best-effort: `; exit 0` (not `&&`) so a missing/failing formatter in a seeded
+          # non-Bun project cannot abort a run mid-implement. Formatting is a convenience;
+          # `${vars.qualityGateCmd}` at `test` is the gate that actually decides.
+          - kind: shell
+            options:
+                command: "$formatCmd ; exit 0"
 
-  # ── test hop (quality gate + bounded auto-fix) ─────────────────────────────
-  # NOT /sp:dev-unit. That command (sp:code-testing) *extends/generates* tests toward
-  # a coverage target; it is not the project quality gate. Coverage gap-fill remains
-  # available via router C3/C5 (`/sp:dev-unit`) or inside implement — not this hop.
-  #
-  # Shape (engine has no per-action "run next only if previous failed" without
-  # `onError`, and Spur's action schema does not expose `onError`):
-  #   test         — soft probe: qualityGateCmd → PASS|FAIL status; always exit 0
-  #                  (green path: one gate run → review; no fixall/recheck tax)
-  #   test-fix     — increment attempt + pure slash /sp:dev-fixall (≤ max attempts)
-  #   test-recheck — soft recheck → review | test-fix | failed (never silent lifecycle abort)
-  - id: test
-    description: >
-      Proof-chain entry + soft quality-gate probe (single logical gate on the green path; bounded retries only
-      for SQLite lock contention). Capture of the canonical proof-input digest happens HERE — before any
-      evidence-producing final check (task 0703, ADR-071) — so the gate, review, and verification evidence
-      all name one digest. Then runs
-      `${vars.qualityGateCmd}`, records PASS|FAIL under
-      `.spur/run/<wbs>-test-gate.status`, resets the fix attempt counter, always exit 0.
-    onEnter:
-      # R6/R2 (0703): resolve the task-spec path BEFORE the digest capture. `docs/tasks*` is excluded
-      # from the digest's git-tree half, so the spec is folded in explicitly via `taskSpecPath`.
-      - kind: shell
-        options:
-          # 0710 R4: resolve the spec path, then extract `priority:` from the TASK FILE itself (not the
-          # path listing); normalize to upper so requiresDistinctExecutor's exact 'P0'/'P1' match hits.
-          # Missing spec/line -> empty var -> back-compat (no distinctness requirement).
-          command: '$spurBin task path $wbs --json 2>/dev/null | jq -r ".path // .filePath // empty" > ".spur/run/$wbs-taskpath.txt" || true; sed -n "s/^priority:[[:space:]]*//p" "$(cat ".spur/run/$wbs-taskpath.txt" 2>/dev/null)" 2>/dev/null | head -1 | tr -d "[:space:]" | tr "[:lower:]" "[:upper:]" > ".spur/run/$wbs-priority.txt"; exit 0'
-      - kind: file.read.into-var
-        options:
-          path: .spur/run/${vars.wbs}-taskpath.txt
-          var: taskSpecPath
-      # 0710 R4: carry the task's priority tier into the review/verify risk policy.
-      - kind: file.read.into-var
-        options:
-          path: .spur/run/${vars.wbs}-priority.txt
-          var: taskPriority
-      # R2 (0703, ADR-071): THE canonical proof capture. Placement is load-bearing: immediately before
-      # the final evidence chain, after every implement mutation (including the post-implement format).
-      # Capture-only here; `record` compares. A remediation pass re-captures at `test-recheck` (R4).
-      - kind: proof.fingerprint
-        options:
-          var: proofDigest
-          taskFile: ${vars.taskSpecPath}
-      - kind: shell
-        options:
-          command: >-
-            mkdir -p .spur/run &&
-            STATUS_FILE=".spur/run/$wbs-test-gate.status" &&
-            LOG_FILE=".spur/run/$wbs-test-gate.log" &&
-            ATTEMPT_FILE=".spur/run/$wbs-test-fix-attempt" &&
-            echo 0 > "$ATTEMPT_FILE" &&
-            : > "$LOG_FILE" &&
-            gate_attempt=1;
-            while [ "$gate_attempt" -le 5 ]; do
-              ATTEMPT_LOG="$LOG_FILE.attempt-$gate_attempt";
-              sh -c "$qualityGateCmd" > "$ATTEMPT_LOG" 2>&1; gate_rc=$?;
-              gate_locked=0;
-              grep -q 'SQLiteError: database is locked' "$ATTEMPT_LOG" && gate_locked=1;
-              cat "$ATTEMPT_LOG" >> "$LOG_FILE";
-              rm -f "$ATTEMPT_LOG";
-              if [ "$gate_rc" -eq 0 ] || [ "$gate_locked" -ne 1 ] || [ "$gate_attempt" -ge 5 ]; then break; fi;
-              printf 'quality gate: database is locked; retrying (%s/5) in 10s\n' "$gate_attempt" | tee -a "$LOG_FILE";
-              sleep 10;
-              gate_attempt=$((gate_attempt + 1));
-            done &&
-            cat "$LOG_FILE" &&
-            FINDINGS_FILE=".spur/run/$wbs-test-gate.findings" &&
-            set +e; grep -oE '[A-Za-z0-9_./-]+\.[A-Za-z]+:[0-9]+' "$LOG_FILE" | sort -u | head -20 | tr '\n' ' ' > "$FINDINGS_FILE"; set -e &&
-            if [ "$gate_rc" -eq 0 ]; then
-              printf 'PASS\n' > "$STATUS_FILE";
-            else
-              printf 'FAIL\n' > "$STATUS_FILE";
-            fi &&
-            printf 'proof-digest: %s\n' "$proofDigest" >> "$LOG_FILE" &&
-            exit 0
+    # ── test hop (quality gate + bounded auto-fix) ─────────────────────────────
+    # NOT /sp:dev-unit. That command (sp:code-testing) *extends/generates* tests toward
+    # a coverage target; it is not the project quality gate. Coverage gap-fill remains
+    # available via router C3/C5 (`/sp:dev-unit`) or inside implement — not this hop.
+    #
+    # Shape (engine has no per-action "run next only if previous failed" without
+    # `onError`, and Spur's action schema does not expose `onError`):
+    #   test         — soft probe: qualityGateCmd → PASS|FAIL status; always exit 0
+    #                  (green path: one gate run → review; no fixall/recheck tax)
+    #   test-fix     — increment attempt + pure slash /sp:dev-fixall (≤ max attempts)
+    #   test-recheck — soft recheck → review | test-fix | failed (never silent lifecycle abort)
+    - id: test
+      description: >
+          Proof-chain entry + soft quality-gate probe (single logical gate on the green path; bounded retries only
+          for SQLite lock contention). Capture of the canonical proof-input digest happens HERE — before any
+          evidence-producing final check (task 0703, ADR-071) — so the gate, review, and verification evidence
+          all name one digest. Then runs
+          `${vars.qualityGateCmd}`, records PASS|FAIL under
+          `.spur/run/<wbs>-test-gate.status`, resets the fix attempt counter, always exit 0.
+      onEnter:
+          # R6/R2 (0703): resolve the task-spec path BEFORE the digest capture. `docs/tasks*` is excluded
+          # from the digest's git-tree half, so the spec is folded in explicitly via `taskSpecPath`.
+          - kind: shell
+            options:
+                # 0710 R4: resolve the spec path, then extract `priority:` from the TASK FILE itself (not the
+                # path listing); normalize to upper so requiresDistinctExecutor's exact 'P0'/'P1' match hits.
+                # 0751 R2: the task path is NOT optional - an unresolved lookup fails
+                # the step (no `|| true`, no forced `exit 0`, no stderr suppression)
+                # instead of degrading the proof to whole-tree-only. The priority read
+                # stays tolerant: a missing line is genuinely optional.
+                command: 'mkdir -p .spur/run; $spurBin task path $wbs --json | jq -r ".path // .filePath // empty" > ".spur/run/$wbs-taskpath.txt"; task_path="$(cat ".spur/run/$wbs-taskpath.txt")"; if [ -z "$task_path" ]; then echo "fail-closed proof chain (0751 R2): task path for $wbs did not resolve - the task spec cannot be folded into the proof digest" >&2; exit 1; fi; sed -n "s/^priority:[[:space:]]*//p" "$task_path" | head -1 | tr -d "[:space:]" | tr "[:lower:]" "[:upper:]" > ".spur/run/$wbs-priority.txt"'
+          - kind: file.read.into-var
+            options:
+                path: .spur/run/${vars.wbs}-taskpath.txt
+                var: taskSpecPath
+          # 0710 R4: carry the task's priority tier into the review/verify risk policy.
+          - kind: file.read.into-var
+            options:
+                path: .spur/run/${vars.wbs}-priority.txt
+                var: taskPriority
+          # R2 (0703, ADR-071): THE canonical proof capture. Placement is load-bearing: immediately before
+          # the final evidence chain, after every implement mutation (including the post-implement format).
+          # Capture-only here; `record` compares. A remediation pass re-captures at `test-recheck` (R4).
+          - kind: proof.fingerprint
+            options:
+                var: proofDigest
+                taskFile: ${vars.taskSpecPath}
+          - kind: shell
+            options:
+                command: >-
+                    mkdir -p .spur/run &&
+                    STATUS_FILE=".spur/run/$wbs-test-gate.status" &&
+                    LOG_FILE=".spur/run/$wbs-test-gate.log" &&
+                    ATTEMPT_FILE=".spur/run/$wbs-test-fix-attempt" &&
+                    echo 0 > "$ATTEMPT_FILE" &&
+                    : > "$LOG_FILE" &&
+                    gate_attempt=1;
+                    while [ "$gate_attempt" -le 5 ]; do
+                      ATTEMPT_LOG="$LOG_FILE.attempt-$gate_attempt";
+                      sh -c "$qualityGateCmd" > "$ATTEMPT_LOG" 2>&1; gate_rc=$?;
+                      gate_locked=0;
+                      grep -q 'SQLiteError: database is locked' "$ATTEMPT_LOG" && gate_locked=1;
+                      cat "$ATTEMPT_LOG" >> "$LOG_FILE";
+                      rm -f "$ATTEMPT_LOG";
+                      if [ "$gate_rc" -eq 0 ] || [ "$gate_locked" -ne 1 ] || [ "$gate_attempt" -ge 5 ]; then break; fi;
+                      printf 'quality gate: database is locked; retrying (%s/5) in 10s\n' "$gate_attempt" | tee -a "$LOG_FILE";
+                      sleep 10;
+                      gate_attempt=$((gate_attempt + 1));
+                    done &&
+                    if [ "$gate_rc" -eq 0 ]; then
+                      printf 'quality gate PASS (attempts: %s; log: %s; bytes: %s)\n' "$gate_attempt" "$LOG_FILE" "$(wc -c < "$LOG_FILE" | tr -d "[:space:]")";
+                    else
+                      printf 'quality gate FAIL — last 40 lines follow (full log: %s)\n' "$LOG_FILE";
+                      tail -n 40 "$LOG_FILE";
+                    fi &&
+                    FINDINGS_FILE=".spur/run/$wbs-test-gate.findings" &&
+                    set +e; grep -oE '[A-Za-z0-9_./-]+\.[A-Za-z]+:[0-9]+' "$LOG_FILE" | sort -u | head -20 | tr '\n' ' ' > "$FINDINGS_FILE"; set -e &&
+                    if [ "$gate_rc" -eq 0 ]; then
+                      printf 'PASS\n' > "$STATUS_FILE";
+                    else
+                      printf 'FAIL\n' > "$STATUS_FILE";
+                    fi &&
+                    printf 'proof-digest: %s\n' "$proofDigest" >> "$LOG_FILE" &&
+                    exit 0
 
-  - id: test-fix
-    description: >
-      Bounded auto-fix hop when the quality gate is red OR final verification returned a
-      repairable non-PASS (task 0703 R4: remediation never happens inside verify — it loops
-      through here, then re-enters quality → review → verify on a fresh digest). Increments
-      `.spur/run/<wbs>-test-fix-attempt` (the shared bound with the quality path), projects the
-      verify verdict into the gate log when one exists so the repair hop sees it, then pure
-      slash (ADR-043) `/sp:dev-fixall` against `${vars.qualityGateCmd}`.
-    onEnter:
-      - kind: shell
-        options:
-          command: >-
-            mkdir -p .spur/run &&
-            ATTEMPT_FILE=".spur/run/$wbs-test-fix-attempt" &&
-            n=$(cat "$ATTEMPT_FILE" 2>/dev/null || echo 0) &&
-            printf '%s\n' "$((n + 1))" > "$ATTEMPT_FILE" &&
-            if [ -f ".spur/run/$wbs-verdict.json" ]; then
-              { echo '--- verify verdict (remediation input, task 0703 R4) ---';
-                cat ".spur/run/$wbs-verdict.json";
-              } >> ".spur/run/$wbs-test-gate.log";
-            fi;
-            exit 0
-      # R3 (0482): project the extracted gate anchors into a var so the dispatch input
-      # can NAME the failing file:line, not merely point at a log. A vars template cannot
-      # run a shell, so the read is an action, not an inline `$(cat ...)` substitution.
-      - kind: file.read.into-var
-        options:
-          path: .spur/run/${vars.wbs}-test-gate.findings
-          var: gateFindings
-      - kind: agent.run
-        options:
-          agent: ${vars.agent}
-          # R3 (0482): `--findings` names the failing anchors inline; `--gate-log` remains
-          # Declared Layer-1 role (0538 R2/0710 R7): routing reason; no executor pin — role routing feeds the distinctness gate.
-          role: coder
-          # the full-context escape hatch when the digest is not enough.
-          input: /sp:dev-fixall "${vars.qualityGateCmd}" --gate-log .spur/run/${vars.wbs}-test-gate.log --findings "${vars.gateFindings}"
-          timeoutMs: ${vars.stepTimeoutMs}
-          # 0706 R6: bounded remediation hop — unattended and tree-mutating,
-          # so it declares the same minimum requirements as `implement`.
-          requiresCapabilities:
-            fsWrite: available
-            processSpawn: available
+    - id: test-fix
+      description: >
+          Bounded auto-fix hop when the quality gate is red OR final verification returned a
+          repairable non-PASS (task 0703 R4: remediation never happens inside verify — it loops
+          through here, then re-enters quality → review → verify on a fresh digest). Increments
+          `.spur/run/<wbs>-test-fix-attempt` (the shared bound with the quality path), projects the
+          verify verdict into the gate log when one exists so the repair hop sees it, then pure
+          slash (ADR-043) `/sp:dev-fixall` against `${vars.qualityGateCmd}`.
+      onEnter:
+          - kind: shell
+            options:
+                command: >-
+                    TASK_POLICY=$($spurBin task show "$wbs" --json |
+                      jq -er '.frontmatter.mutationPolicy // ([.content | scan("(?m)^mutationPolicy:[ \t]*([^ \r\n]+)[ \t]*$") | .[0]] | if length == 0 then "code" elif length == 1 then .[0] else "ambiguous" end)') || exit 1;
+                    if [ "$mutationPolicy:$TASK_POLICY" != "code:code" ]; then
+                      echo "test-fix: mutation policy forbids automatic code repair (run=$mutationPolicy, task=$TASK_POLICY); gate failure preserved, no agent dispatched" >&2;
+                      exit 1;
+                    fi;
+                    mkdir -p .spur/run &&
+                    ATTEMPT_FILE=".spur/run/$wbs-test-fix-attempt" &&
+                    n=$(cat "$ATTEMPT_FILE" 2>/dev/null || echo 0) &&
+                    printf '%s\n' "$((n + 1))" > "$ATTEMPT_FILE" &&
+                    if [ -f ".spur/run/$wbs-verdict.json" ]; then
+                      { echo '--- verify verdict (remediation input, task 0703 R4) ---';
+                        cat ".spur/run/$wbs-verdict.json";
+                      } >> ".spur/run/$wbs-test-gate.log";
+                    fi;
+                    exit 0
+          # R3 (0482): project the extracted gate anchors into a var so the dispatch input
+          # can NAME the failing file:line, not merely point at a log. A vars template cannot
+          # run a shell, so the read is an action, not an inline `$(cat ...)` substitution.
+          - kind: file.read.into-var
+            options:
+                path: .spur/run/${vars.wbs}-test-gate.findings
+                var: gateFindings
+          - kind: agent.run
+            options:
+                agent: ${vars.agent}
+                # R3 (0482): `--findings` names the failing anchors inline; `--gate-log` remains
+                # Declared Layer-1 role (0538 R2/0710 R7): routing reason; no executor pin — role routing feeds the distinctness gate.
+                role: coder
+                # the full-context escape hatch when the digest is not enough.
+                input: /sp:dev-fixall "${vars.qualityGateCmd}" --gate-log .spur/run/${vars.wbs}-test-gate.log --findings "${vars.gateFindings}"
+                timeoutMs: ${vars.stepTimeoutMs}
+                # 0706 R6: bounded remediation hop — unattended and tree-mutating,
+                # so it declares the same minimum requirements as `implement`.
+                requiresCapabilities:
+                    fsWrite: available
+                    processSpawn: available
 
-  - id: test-recheck
-    description: >
-      Soft recheck after fixall with bounded SQLite-lock retry. Writes PASS|FAIL (always exit 0). Transitions
-      branch to review (PASS), another test-fix (FAIL and under max attempts),
-      or the pipeline `failed` state (FAIL and attempts exhausted) — never a
-      raw lifecycle abort that skips the terminal `failed` state.
-    onEnter:
-      # R4 (0703, ADR-071): bounded remediation mutated the tree by design, so the fresh evidence
-      # chain (recheck gate → review → verify) must start from a NEWLY captured digest. Capture-only;
-      # the guards and `record` compare against this value.
-      - kind: proof.fingerprint
-        options:
-          var: proofDigest
-          taskFile: ${vars.taskSpecPath}
-      # 0587 R3: probe-then-full recheck. A red gateProbeCmd records FAIL and skips the full
-      # gate (the measured waste is re-running a 110–140s gate to learn the tree is still red);
-      # a green probe (or empty gateProbeCmd) falls through to the full-gate loop unchanged.
-      # Only the full gate writes PASS, so the `test-recheck → review` guard (reads PASS)
-      # still means a full green qualityGateCmd ran — invariant preserved by construction.
-      - kind: shell
-        options:
-          command: >-
-            mkdir -p .spur/run &&
-            STATUS_FILE=".spur/run/$wbs-test-gate.status" &&
-            LOG_FILE=".spur/run/$wbs-test-gate.log" &&
-            FINDINGS_FILE=".spur/run/$wbs-test-gate.findings" &&
-            : > "$LOG_FILE" &&
-            probe_rc=0;
-            if [ -n "$gateProbeCmd" ]; then
-              sh -c "$gateProbeCmd" > "$LOG_FILE.probe" 2>&1; probe_rc=$?;
-              cat "$LOG_FILE.probe" >> "$LOG_FILE";
-              rm -f "$LOG_FILE.probe";
-            fi;
-            if [ "$probe_rc" -ne 0 ]; then
-              gate_rc=$probe_rc;
-            else
-              gate_attempt=1;
-              while [ "$gate_attempt" -le 5 ]; do
-                ATTEMPT_LOG="$LOG_FILE.attempt-$gate_attempt";
-                sh -c "$qualityGateCmd" > "$ATTEMPT_LOG" 2>&1; gate_rc=$?;
-                gate_locked=0;
-                grep -q 'SQLiteError: database is locked' "$ATTEMPT_LOG" && gate_locked=1;
-                cat "$ATTEMPT_LOG" >> "$LOG_FILE";
-                rm -f "$ATTEMPT_LOG";
-                if [ "$gate_rc" -eq 0 ] || [ "$gate_locked" -ne 1 ] || [ "$gate_attempt" -ge 5 ]; then break; fi;
-                printf 'quality gate: database is locked; retrying (%s/5) in 10s\n' "$gate_attempt" | tee -a "$LOG_FILE";
-                sleep 10;
-                gate_attempt=$((gate_attempt + 1));
-              done;
-            fi &&
-            cat "$LOG_FILE" &&
-            set +e; grep -oE '[A-Za-z0-9_./-]+\.[A-Za-z]+:[0-9]+' "$LOG_FILE" | sort -u | head -20 | tr '\n' ' ' > "$FINDINGS_FILE"; set -e &&
-            if [ "$gate_rc" -eq 0 ]; then
-              printf 'PASS\n' > "$STATUS_FILE";
-            else
-              printf 'FAIL\n' > "$STATUS_FILE";
-            fi &&
-            printf 'proof-digest: %s\n' "$proofDigest" >> "$LOG_FILE" &&
-            exit 0
+    - id: test-recheck
+      description: >
+          Soft recheck after fixall with bounded SQLite-lock retry. Writes PASS|FAIL (always exit 0). Transitions
+          branch to review (PASS), another test-fix (FAIL and under max attempts),
+          or the pipeline `failed` state (FAIL and attempts exhausted) — never a
+          raw lifecycle abort that skips the terminal `failed` state.
+      onEnter:
+          # R4 (0703, ADR-071): bounded remediation mutated the tree by design, so the fresh evidence
+          # chain (recheck gate → review → verify) must start from a NEWLY captured digest. Capture-only;
+          # the guards and `record` compare against this value.
+          - kind: proof.fingerprint
+            options:
+                var: proofDigest
+                taskFile: ${vars.taskSpecPath}
+          # 0587 R3: probe-then-full recheck. A red gateProbeCmd records FAIL and skips the full
+          # gate (the measured waste is re-running a 110–140s gate to learn the tree is still red);
+          # a green probe (or empty gateProbeCmd) falls through to the full-gate loop unchanged.
+          # Only the full gate writes PASS, so the `test-recheck → review` guard (reads PASS)
+          # still means a full green qualityGateCmd ran — invariant preserved by construction.
+          - kind: shell
+            options:
+                command: >-
+                    mkdir -p .spur/run &&
+                    STATUS_FILE=".spur/run/$wbs-test-gate.status" &&
+                    LOG_FILE=".spur/run/$wbs-test-gate.log" &&
+                    FINDINGS_FILE=".spur/run/$wbs-test-gate.findings" &&
+                    : > "$LOG_FILE" &&
+                    probe_rc=0;
+                    if [ -n "$gateProbeCmd" ]; then
+                      sh -c "$gateProbeCmd" > "$LOG_FILE.probe" 2>&1; probe_rc=$?;
+                      cat "$LOG_FILE.probe" >> "$LOG_FILE";
+                      rm -f "$LOG_FILE.probe";
+                    fi;
+                    if [ "$probe_rc" -ne 0 ]; then
+                      gate_rc=$probe_rc;
+                    else
+                      gate_attempt=1;
+                      while [ "$gate_attempt" -le 5 ]; do
+                        ATTEMPT_LOG="$LOG_FILE.attempt-$gate_attempt";
+                        sh -c "$qualityGateCmd" > "$ATTEMPT_LOG" 2>&1; gate_rc=$?;
+                        gate_locked=0;
+                        grep -q 'SQLiteError: database is locked' "$ATTEMPT_LOG" && gate_locked=1;
+                        cat "$ATTEMPT_LOG" >> "$LOG_FILE";
+                        rm -f "$ATTEMPT_LOG";
+                        if [ "$gate_rc" -eq 0 ] || [ "$gate_locked" -ne 1 ] || [ "$gate_attempt" -ge 5 ]; then break; fi;
+                        printf 'quality gate: database is locked; retrying (%s/5) in 10s\n' "$gate_attempt" | tee -a "$LOG_FILE";
+                        sleep 10;
+                        gate_attempt=$((gate_attempt + 1));
+                      done;
+                    fi &&
+                    if [ "$gate_rc" -eq 0 ]; then
+                      printf 'quality gate PASS (attempts: %s; log: %s; bytes: %s)\n' "$gate_attempt" "$LOG_FILE" "$(wc -c < "$LOG_FILE" | tr -d "[:space:]")";
+                    else
+                      printf 'quality gate FAIL — last 40 lines follow (full log: %s)\n' "$LOG_FILE";
+                      tail -n 40 "$LOG_FILE";
+                    fi &&
+                    set +e; grep -oE '[A-Za-z0-9_./-]+\.[A-Za-z]+:[0-9]+' "$LOG_FILE" | sort -u | head -20 | tr '\n' ' ' > "$FINDINGS_FILE"; set -e &&
+                    if [ "$gate_rc" -eq 0 ]; then
+                      printf 'PASS\n' > "$STATUS_FILE";
+                    else
+                      printf 'FAIL\n' > "$STATUS_FILE";
+                    fi &&
+                    printf 'proof-digest: %s\n' "$proofDigest" >> "$LOG_FILE" &&
+                    exit 0
 
-  - id: review
-    description: Three-dimensional code review via /sp:dev-review (functional requirements traceability + SECUA framework (Security, Efficiency, Correctness, Usability, Architecture) + architecture depth), findings written to `## Review`.
-    onEnter:
-      - kind: agent.run
-        options:
-          # 0710 R2: review always runs on a fresh session — no implementation-session
-          # inheritance, no latch resume; implementation context reaches the reviewer
-          # only via the persisted task spec, the recorded diff, and run artifacts.
-          # 0710 R4/R5: the agent pin is deliberately gone — role: reviewer routes
-          # through the executor registry, and the runner enforces (pre-dispatch,
-          # fail-closed) that a P0/P1 task's review resolves a DIFFERENT executor
-          # spec than the implement stage recorded in __agentRouting_implement.
-          input: /sp:dev-review ${vars.wbs} --auto
-          # Declared Layer-1 role (0538 R2/0710 R7): routing reason; no executor pin — role routing feeds the distinctness gate.
-          role: reviewer
-          freshSession: true
-          priority: ${vars.taskPriority}
-          compareExecutorWith: implement
-          timeoutMs: ${vars.stepTimeoutMs}
+    - id: review
+      description: Three-dimensional code review via /sp:dev-review (functional requirements traceability + SECUA framework (Security, Efficiency, Correctness, Usability, Architecture) + architecture depth), findings written to `## Review`.
+      onEnter:
+          - kind: agent.run
+            options:
+                # 0710 R2: review always runs on a fresh session — no implementation-session
+                # inheritance, no latch resume; implementation context reaches the reviewer
+                # only via the persisted task spec, the recorded diff, and run artifacts.
+                # 0710 R4/R5: the agent pin is deliberately gone — role: reviewer routes
+                # through the executor registry, and the runner enforces (pre-dispatch,
+                # fail-closed) that a P0/P1 task's review resolves a DIFFERENT executor
+                # spec than the implement stage recorded in __agentRouting_implement.
+                input: /sp:dev-review ${vars.wbs} --auto
+                # Declared Layer-1 role (0538 R2/0710 R7): routing reason; no executor pin — role routing feeds the distinctness gate.
+                role: reviewer
+                freshSession: true
+                priority: ${vars.taskPriority}
+                compareExecutorWith: implement
+                timeoutMs: ${vars.stepTimeoutMs}
 
-  - id: approve
-    description: >
-      Human-in-the-loop approval gate. Under `profile=auto` this state is never entered
-      (review routes around it straight to verify). In interactive mode this state pauses
-      the run for `spur workflow continue` (E3), making approval an explicit operator action.
-      The operator's answer is routed (R1, bug-750): yes -> verify; no -> failed (rejection
-      recorded, not silently approved); cancel -> cancelled (a distinct terminal state).
-    pause: true
-    onEnter:
-      - kind: hitl.confirm
-        options:
-          prompt: "Approve task ${vars.wbs} to proceed to verification?"
+    - id: approve
+      description: >
+          Human-in-the-loop approval gate. Under `profile=auto` this state is never entered
+          (review routes around it straight to verify). In interactive mode this state pauses
+          the run for `spur workflow continue` (E3), making approval an explicit operator action.
+          The operator's answer is routed (R1, bug-750): yes -> verify; no -> failed (rejection
+          recorded, not silently approved); cancel -> cancelled (a distinct terminal state).
+      pause: true
+      onEnter:
+          - kind: hitl.confirm
+            options:
+                prompt: "Approve task ${vars.wbs} to proceed to verification?"
 
-  - id: verify
-    description: >
-      Observe-only functional verification (BDD + traceability) via /sp:dev-verify --fix none
-      (task 0703 R1, ADR-071): the verifier certifies the state, it never repairs its own subject.
-      A live digest compare BEFORE the agent refuses to certify a state that drifted after the
-      quality/review evidence was produced (R2). The agent's
-      captured answer is written to `.spur/run/<wbs>-verify-answer.txt` and MUST follow
-      the answer-file schema contract (explicit `Verdict: PASS|PARTIAL|FAIL` line plus
-      `| Req | Status | Evidence |` and `| AC | Status | Evidence Type | Evidence |` tables);
-      a deterministic shell step then derives the verdict and writes the gate artifact
-      `.spur/run/<wbs>-verdict.json` (so the completion gate reads a real verdict, not
-      agent discretion — R9) with a proof block naming the digest and the per-stage results (R3).
-      Repairable non-PASS routes once through the bounded remediation hop (verify → test-fix,
-      R4); the chain reruns on a fresh digest.
-    onEnter:
-      # R2 (0703): midpoint bracket compare — refuse to spend verification on a state that no
-      # longer matches the digest the quality/review evidence names. Reuses `proofDigestNow`:
-      # set here and re-set by the final compare at `record` entry.
-      - kind: proof.fingerprint
-        options:
-          var: proofDigestNow
-          taskFile: ${vars.taskSpecPath}
-          expect: ${vars.proofDigest}
-      - kind: agent.run
-        options:
-          # 0710 R2: verify is a separate fresh-session execution — never the review
-          # session, never the implement session (R6).
-          # 0710 R4/R5: role-routed like review; P0/P1 demands a distinct executor.
-          # R1 (0703, ADR-071): `--fix none` — final verification is observe-only. Remediation
-          # belongs to the bounded test-fix hop, never to the certifying pass.
-          input: /sp:dev-verify ${vars.wbs} --auto --fix none --focus all
-          # Declared Layer-1 role (0538 R2/0710 R7): routing reason; no executor pin — role routing feeds the distinctness gate.
-          role: reviewer
-          freshSession: true
-          priority: ${vars.taskPriority}
-          compareExecutorWith: implement
-          timeoutMs: ${vars.stepTimeoutMs}
-          expectFile: .spur/run/${vars.wbs}-verify-answer.txt
-      # 0726 R3: hard lint gate over the verifier-owned answer — shape and
-      # evidence-row identity, before the verdict derivation reads it.
-      # Hard action: a malformed answer halts the sequence here instead of
-      # poisoning the verdict parse downstream.
-      - kind: shell
-        options:
-          command: >-
-            LINT_SCRIPT="plugins/sp/scripts/verify-answer-lint.ts";
-            [ -f "$LINT_SCRIPT" ] ||
-            LINT_SCRIPT="$(superskill script path sp verify-answer-lint.ts 2>/dev/null)";
-            if [ -z "$LINT_SCRIPT" ] || [ ! -f "$LINT_SCRIPT" ]; then
-              echo "verify-answer-lint: checker not found in plugins/sp/scripts/ nor staged — run 'superskill install sp'" >&2;
-              exit 1;
-            fi;
-            bun "$LINT_SCRIPT" "$wbs"
-            --answer ".spur/run/$wbs-verify-answer.txt"
-            --spur-bin "$spurBin"
-      - kind: shell
-        options:
-          command: "$spurBin task verdict $wbs --from-answer .spur/run/$wbs-verify-answer.txt"
-      # R3 (0703): write the required proof block into the verdict artifact — the digest, the
-      # capture point, and the named per-stage results, each stage carrying the SAME digest
-      # value (prose asserting proof validity is insufficient). Also keeps the flat
-      # `proof-input-digest` check row for consumers that read `checks[]`. Soft action + hard
-      # guard: a missing/malformed stamp fails the `verify → record` guard below, not this step.
-      - kind: shell
-        options:
-          command: >-
-            V=".spur/run/$wbs-verdict.json";
-            if [ -f "$V" ] && [ -n "$proofDigest" ]; then
-              jq --arg d "$proofDigest" --arg g "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null || echo UNKNOWN)"
-              '. + {proof: {digest: $d, capturePoint: "quality-gate-entry", stages: {
-                qualityGate: {status: $g, digest: $d},
-                review: {status: "completed", digest: $d},
-                verification: {status: .verdict, digest: $d}}}}
-                | .checks += [{name: "proof-input-digest", status: "pass", evidence: $d}]'
-              "$V" > "$V.tmp" && mv "$V.tmp" "$V";
-            fi;
-            exit 0
+    - id: verify
+      description: >
+          Observe-only functional verification (BDD + traceability) via /sp:dev-verify --fix none
+          (task 0703 R1, ADR-071): the verifier certifies the state, it never repairs its own subject.
+          A live digest compare BEFORE the agent refuses to certify a state that drifted after the
+          quality/review evidence was produced (R2). The agent's
+          captured answer is written to `.spur/run/<wbs>-verify-answer.txt` and MUST follow
+          the answer-file schema contract (explicit `Verdict: PASS|PARTIAL|FAIL` line plus
+          `| Req | Status | Evidence |` and `| AC | Status | Evidence Type | Evidence |` tables);
+          a deterministic shell step then derives the verdict and writes the gate artifact
+          `.spur/run/<wbs>-verdict.json` (so the completion gate reads a real verdict, not
+          agent discretion — R9) with a proof block naming the digest and the per-stage results (R3).
+          Repairable non-PASS routes once through the bounded remediation hop (verify → test-fix,
+          R4); the chain reruns on a fresh digest.
+      onEnter:
+          # R2 (0703): midpoint bracket compare — refuse to spend verification on a state that no
+          # longer matches the digest the quality/review evidence names. Reuses `proofDigestNow`:
+          # set here and re-set by the final compare at `record` entry.
+          - kind: proof.fingerprint
+            options:
+                var: proofDigestNow
+                taskFile: ${vars.taskSpecPath}
+                expect: ${vars.proofDigest}
+          - kind: agent.run
+            options:
+                # 0710 R2: verify is a separate fresh-session execution — never the review
+                # session, never the implement session (R6).
+                # 0710 R4/R5: role-routed like review; P0/P1 demands a distinct executor.
+                # R1 (0703, ADR-071): `--fix none` — final verification is observe-only. Remediation
+                # belongs to the bounded test-fix hop, never to the certifying pass.
+                input: /sp:dev-verify ${vars.wbs} --auto --fix none --focus all
+                # Declared Layer-1 role (0538 R2/0710 R7): routing reason; no executor pin — role routing feeds the distinctness gate.
+                role: reviewer
+                freshSession: true
+                priority: ${vars.taskPriority}
+                compareExecutorWith: implement
+                timeoutMs: ${vars.stepTimeoutMs}
+                expectFile: .spur/run/${vars.wbs}-verify-answer.txt
+          # 0726 R3: hard lint gate over the verifier-owned answer — shape and
+          # evidence-row identity, before the verdict derivation reads it.
+          # Hard action: a malformed answer halts the sequence here instead of
+          # poisoning the verdict parse downstream.
+          - kind: shell
+            options:
+                command: >-
+                    LINT_SCRIPT="plugins/sp/scripts/verify-answer-lint.ts";
+                    [ -f "$LINT_SCRIPT" ] ||
+                    LINT_SCRIPT="$(superskill script path sp verify-answer-lint.ts 2>/dev/null)";
+                    if [ -z "$LINT_SCRIPT" ] || [ ! -f "$LINT_SCRIPT" ]; then
+                      echo "verify-answer-lint: checker not found in plugins/sp/scripts/ nor staged — run 'superskill install sp'" >&2;
+                      exit 1;
+                    fi;
+                    bun "$LINT_SCRIPT" "$wbs"
+                    --answer ".spur/run/$wbs-verify-answer.txt"
+                    --spur-bin "$spurBin"
+          - kind: shell
+            options:
+                command: "$spurBin task verdict $wbs --from-answer .spur/run/$wbs-verify-answer.txt"
+          # R3 (0703): write the required proof block into the verdict artifact — the digest, the
+          # certifying run id, the capture point, and the named per-stage results, each stage carrying
+          # the SAME digest value (prose asserting proof validity is insufficient). `runId` closes
+          # 0730 §B.2 (task 0757 R4): without it the verified-outcome fold has to accept ANY linked
+          # run as certifying, so a dry-run probe linked to the same wbs reads as proof of completion.
+          # `definitionDigest` closes 0759 R5: the record binds to the certifying run AND the exact
+          # workflow definition it executed — a stale-definition resume or a definition edited
+          # between run and record cannot certify silently. `__definitionDigest` is injected at run
+          # start (workflow-service.ts) and equals the digest stamped on the run row (task 0603).
+          # Also keeps the flat
+          # `proof-input-digest` check row for consumers that read `checks[]`. Soft action + hard
+          # guard: a missing/malformed stamp fails the `verify → record` guard below, not this step.
+          - kind: shell
+            options:
+                command: >-
+                    V=".spur/run/$wbs-verdict.json";
+                    if [ -f "$V" ] && [ -n "$proofDigest" ]; then
+                      jq --arg d "$proofDigest" --arg r "$__runId" --arg dd "$__definitionDigest" --arg g "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null || echo UNKNOWN)"
+                      '. + {proof: {digest: $d, runId: $r, definitionDigest: $dd, capturePoint: "quality-gate-entry", stages: {
+                        qualityGate: {status: $g, digest: $d},
+                        review: {status: "completed", digest: $d},
+                        verification: {status: .verdict, digest: $d}}}}
+                        | .checks += [{name: "proof-input-digest", status: "pass", evidence: $d}]'
+                      "$V" > "$V.tmp" && mv "$V.tmp" "$V";
+                    fi;
+                    exit 0
 
-  - id: record
-    description: >
-      Record pipeline results into the task file via `spur task record` —
-      Testing/Review from the verdict, Solution backfilled from git diff as a
-      safety net, optional transition to testing. Post-record step conditionally syncs
-      feature status via the bounded `feature-sync-bounded` wrapper (task 0411
-      retry-suppression) if `feature_id` is present, or appends an orphan link proposal
-      to the run report if absent (task 0328 / ADR-0322).
-    onEnter:
-      # Proof-state compare (task 0612, ADR-071; bracket closed against the pre-chain
-      # capture per task 0703) — FIRST action in the state, before any record write.
-      # Re-captures the digest and asserts it equals the value the evidence chain started
-      # from. A mismatch means a proof input changed after evidence was established; the
-      # default `fail` policy halts the sequence and routes the run to `failed` rather
-      # than crossing into `record`. Task-spec evidence writes (Testing/Review/Solution,
-      # R6) happen only in the actions AFTER this comparison, and the fingerprint scopes
-      # task content to the proof-input sections, so they cannot invalidate the certified
-      # input set.
-      - kind: proof.fingerprint
-        options:
-          var: proofDigestNow
-          taskFile: ${vars.taskSpecPath}
-          expect: ${vars.proofDigest}
-      - kind: shell
-        options:
-          command: >-
-            retry_transient() {
-              RETRY_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
-              printf '%s\n' "$RETRY_OUTPUT";
-              if [ "$RETRY_RC" -eq 0 ]; then return 0; fi;
-              if ! printf '%s' "$RETRY_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY|database is locked'; then return "$RETRY_RC"; fi;
-              sleep 2;
-              RETRY_SECOND_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
-              printf '%s\n' "$RETRY_SECOND_OUTPUT";
-              if [ "$RETRY_RC" -ne 0 ] && printf '%s\n%s' "$RETRY_OUTPUT" "$RETRY_SECOND_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY'; then
-                echo "node_modules link/dependency broken — run bun install and retry";
-              fi;
-              return "$RETRY_RC";
-            };
-            retry_transient $spurBin task record "$wbs" --solution-from-diff --transition testing
-      # Best-effort, and portable across layouts. `feature-sync-bounded.ts` is a
-      # Spur-monorepo path — `spur init` never scaffolds `plugins/sp/`, so a seeded
-      # project must fall back to the plain `spur feature sync` verb rather than
-      # abort a run that already produced a PASS verdict. Trailing `exit 0` keeps the
-      # whole step advisory for the same reason (feature status sync is a follow-up,
-      # not a completion gate — `record → done` runs `spur task check`).
-      - kind: shell
-        options:
-          command: >-
-            FID=$($spurBin task show $wbs --json 2>/dev/null |
-            jq -r ".feature_id // .frontmatter.feature_id // empty" 2>/dev/null);
-            if [ -n "$FID" ]; then
-              if [ -f plugins/sp/scripts/feature-sync-bounded.ts ]; then
-                bun plugins/sp/scripts/feature-sync-bounded.ts "$FID" --spur-bin "$spurBin" --json;
-              elif SYNC_MJS="$(superskill script path sp feature-sync-bounded.mjs 2>/dev/null)" && [ -f "$SYNC_MJS" ]; then
-                node "$SYNC_MJS" "$FID" --spur-bin "$spurBin" --json;
-              else
-                $spurBin feature sync "$FID" --json;
-              fi;
-            else
-              echo "Orphan task $wbs — no feature_id linked; proposal: consider linking to a parent feature." >> ".spur/run/$wbs-report.txt";
-            fi;
-            exit 0
+    - id: record
+      description: >
+          Record pipeline results into the task file via `spur task record` —
+          Testing/Review from the verdict, Solution backfilled from git diff as a
+          safety net, optional transition to testing. Post-record step conditionally syncs
+          feature status via the bounded `feature-sync-bounded` wrapper (task 0411
+          retry-suppression) if `feature_id` is present, or appends an orphan link proposal
+          to the run report if absent (task 0328 / ADR-0322).
+      onEnter:
+          # Proof-state compare (task 0612, ADR-071; bracket closed against the pre-chain
+          # capture per task 0703) — FIRST action in the state, before any record write.
+          # Re-captures the digest and asserts it equals the value the evidence chain started
+          # from. A mismatch means a proof input changed after evidence was established; the
+          # default `fail` policy halts the sequence and routes the run to `failed` rather
+          # than crossing into `record`. Task-spec evidence writes (Testing/Review/Solution,
+          # R6) happen only in the actions AFTER this comparison, and the fingerprint scopes
+          # task content to the proof-input sections, so they cannot invalidate the certified
+          # input set.
+          - kind: proof.fingerprint
+            options:
+                var: proofDigestNow
+                taskFile: ${vars.taskSpecPath}
+                expect: ${vars.proofDigest}
+          - kind: shell
+            options:
+                command: >-
+                    retry_transient() {
+                      RETRY_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
+                      printf '%s\n' "$RETRY_OUTPUT";
+                      if [ "$RETRY_RC" -eq 0 ]; then return 0; fi;
+                      if ! printf '%s' "$RETRY_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY|database is locked'; then return "$RETRY_RC"; fi;
+                      sleep 2;
+                      RETRY_SECOND_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
+                      printf '%s\n' "$RETRY_SECOND_OUTPUT";
+                      if [ "$RETRY_RC" -ne 0 ] && printf '%s\n%s' "$RETRY_OUTPUT" "$RETRY_SECOND_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY'; then
+                        echo "node_modules link/dependency broken — run bun install and retry";
+                      fi;
+                      return "$RETRY_RC";
+                    };
+                    retry_transient $spurBin task record "$wbs" --solution-from-diff --transition testing
+          # Best-effort, and portable across layouts. `feature-sync-bounded.ts` is a
+          # Spur-monorepo path — `spur init` never scaffolds `plugins/sp/`, so a seeded
+          # project must fall back to the plain `spur feature sync` verb rather than
+          # abort a run that already produced a PASS verdict. Trailing `exit 0` keeps the
+          # whole step advisory for the same reason (feature status sync is a follow-up,
+          # not a completion gate — `record → done` runs `spur task check`).
+          - kind: shell
+            options:
+                command: >-
+                    FID=$($spurBin task show $wbs --json 2>/dev/null |
+                    jq -r ".feature_id // .frontmatter.feature_id // empty" 2>/dev/null);
+                    if [ -n "$FID" ]; then
+                      if [ -f plugins/sp/scripts/feature-sync-bounded.ts ]; then
+                        bun plugins/sp/scripts/feature-sync-bounded.ts "$FID" --spur-bin "$spurBin" --json;
+                      elif SYNC_MJS="$(superskill script path sp feature-sync-bounded.mjs 2>/dev/null)" && [ -f "$SYNC_MJS" ]; then
+                        node "$SYNC_MJS" "$FID" --spur-bin "$spurBin" --json;
+                      else
+                        $spurBin feature sync "$FID" --json;
+                      fi;
+                    else
+                      echo "Orphan task $wbs — no feature_id linked; proposal: consider linking to a parent feature." >> ".spur/run/$wbs-report.txt";
+                    fi;
+                    exit 0
 
-  - id: done
-    description: >
-      Terminal — task executed, verified, and recorded. The `record → done`
-      guard runs `spur task check` before certifying; a genuinely non-compliant
-      task routes to `failed` instead of a silent bad `done`.
-    onEnter:
-      - kind: shell
-        options:
-          command: >-
-            retry_transient() {
-              RETRY_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
-              printf '%s\n' "$RETRY_OUTPUT";
-              if [ "$RETRY_RC" -eq 0 ]; then return 0; fi;
-              if ! printf '%s' "$RETRY_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY|database is locked'; then return "$RETRY_RC"; fi;
-              sleep 2;
-              RETRY_SECOND_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
-              printf '%s\n' "$RETRY_SECOND_OUTPUT";
-              if [ "$RETRY_RC" -ne 0 ] && printf '%s\n%s' "$RETRY_OUTPUT" "$RETRY_SECOND_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY'; then
-                echo "node_modules link/dependency broken — run bun install and retry";
-              fi;
-              return "$RETRY_RC";
-            };
-            retry_transient $spurBin task update "$wbs" done --no-lifecycle
-      # D5-L: the verify verdict is this pipeline's proof of completion, so its ownership
-      # belongs to a deterministic primitive rather than an untracked file on disk.
-      # `run.artifact` records path + kind + runId only — never the body (ADR-069).
-      - kind: run.artifact
-        options:
-          path: .spur/run/${vars.wbs}-verdict.json
-          artifactKind: verify-verdict
-      - kind: note
-        options:
-          message: "Pipeline complete for task ${vars.wbs} (done gate cleared)."
-      # Checkpoint write: record session state for resume (0711 R1–R3) —
-      # canonical frontmatter contract; mirrors the Session Checkpoint
-      # Convention in plugins/sp/skills/spur-dev/references/cross-cutting.md.
-      # Advisory only: the task file and the persisted run row stay authoritative.
-      - kind: shell
-        options:
-          # Single logical line: the composition-baseline argument-split lint flags any
-          # command whose continuation lines look like argument lists (heredocs with
-          # `- item` entries trip it), so the checkpoint body is one printf with \n escapes.
-          command: >-
-            mkdir -p .spur/memory/sessions; CP_TS="$(date -u +%Y-%m-%dT%H:%M:%SZ)"; CP_COMMIT="$(git rev-parse HEAD 2>/dev/null || echo unknown)"; CP_DIGEST="$(cut -d= -f2 .spur/run/$wbs-proofdigest.txt 2>/dev/null || echo '')"; CP_RUN="$SPUR_RUN_ID"; [ -z "$CP_RUN" ] && CP_RUN="$RUN_ID"; printf '%s\n' '---' 'schema_version: 1' "session_id: $(date -u +%Y-%m-%d)-$wbs" 'workflow: task-pipeline' "run_id: $CP_RUN" "task_wbs: $wbs" 'feature_id: ""' 'phase: done' 'status: done' 'last_gate: record' "source_commit: $CP_COMMIT" "digest: $CP_DIGEST" "generated_at: $CP_TS" "updated_at: $CP_TS" "next_action: none - task $wbs complete (terminal; advisory only)" 'artifacts:' '  - .spur/run/$wbs-verdict.json' '  - .spur/run/$wbs-test-gate.log' '---' '' '## Session Notes' '' "Terminal checkpoint for task $wbs (task-pipeline done)." 'Advisory only; the task file is authoritative.' > .spur/memory/sessions/$wbs-checkpoint.md; exit 0
+    - id: done
+      description: >
+          Terminal — task executed, verified, and recorded. The `record → done`
+          guard runs `spur task check` before certifying; a genuinely non-compliant
+          task routes to `failed` instead of a silent bad `done`.
+      onEnter:
+          - kind: shell
+            options:
+                command: >-
+                    retry_transient() {
+                      RETRY_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
+                      printf '%s\n' "$RETRY_OUTPUT";
+                      if [ "$RETRY_RC" -eq 0 ]; then return 0; fi;
+                      if ! printf '%s' "$RETRY_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY|database is locked'; then return "$RETRY_RC"; fi;
+                      sleep 2;
+                      RETRY_SECOND_OUTPUT=$("$@" 2>&1); RETRY_RC=$?;
+                      printf '%s\n' "$RETRY_SECOND_OUTPUT";
+                      if [ "$RETRY_RC" -ne 0 ] && printf '%s\n%s' "$RETRY_OUTPUT" "$RETRY_SECOND_OUTPUT" | grep -Eq 'ENOENT|EBUSY|ENOTEMPTY'; then
+                        echo "node_modules link/dependency broken — run bun install and retry";
+                      fi;
+                      return "$RETRY_RC";
+                    };
+                    retry_transient $spurBin task update "$wbs" done --no-lifecycle
+          # D5-L: the verify verdict is this pipeline's proof of completion, so its ownership
+          # belongs to a deterministic primitive rather than an untracked file on disk.
+          # `run.artifact` records path + kind + runId only — never the body (ADR-069).
+          - kind: run.artifact
+            options:
+                path: .spur/run/${vars.wbs}-verdict.json
+                artifactKind: verify-verdict
+                # 0751 R4: bind the verdict to the run's captured proof digest. `record`
+                # re-captures `proofDigestNow` with expect=proofDigest, so the binding
+                # holds by construction here — making the option non-decorative.
+                proofBinding: current
+          - kind: note
+            options:
+                message: "Pipeline complete for task ${vars.wbs} (done gate cleared)."
+          # Checkpoint write: record session state for resume (0711 R1–R3) —
+          # canonical frontmatter contract; mirrors the Session Checkpoint
+          # Convention in plugins/sp/skills/spur-dev/references/cross-cutting.md.
+          # Advisory only: the task file and the persisted run row stay authoritative.
+          - kind: shell
+            options:
+                # Single logical line: the composition-baseline argument-split lint flags any
+                # command whose continuation lines look like argument lists (heredocs with
+                # `- item` entries trip it), so the checkpoint body is one printf with \n escapes.
+                command: >-
+                    mkdir -p .spur/memory/sessions; CP_TS="$(date -u +%Y-%m-%dT%H:%M:%SZ)"; CP_COMMIT="$(git rev-parse HEAD 2>/dev/null || echo unknown)"; CP_DIGEST="$(cut -d= -f2 .spur/run/$wbs-proofdigest.txt 2>/dev/null || echo '')"; CP_RUN="$SPUR_RUN_ID"; [ -z "$CP_RUN" ] && CP_RUN="$RUN_ID"; printf '%s\n' '---' 'schema_version: 1' "session_id: $(date -u +%Y-%m-%d)-$wbs" 'workflow: task-pipeline' "run_id: $CP_RUN" "task_wbs: $wbs" 'feature_id: ""' 'phase: done' 'status: done' 'last_gate: record' "source_commit: $CP_COMMIT" "digest: $CP_DIGEST" "generated_at: $CP_TS" "updated_at: $CP_TS" "next_action: none - task $wbs complete (terminal; advisory only)" 'artifacts:' '  - .spur/run/$wbs-verdict.json' '  - .spur/run/$wbs-test-gate.log' '---' '' '## Session Notes' '' "Terminal checkpoint for task $wbs (task-pipeline done)." 'Advisory only; the task file is authoritative.' > .spur/memory/sessions/$wbs-checkpoint.md; exit 0
 
-  - id: failed
-    description: >
-      Terminal — precheck, quality-gate exhaustion, verify non-PASS, record check
-      failure, or operator rejection; reported, not advanced.
+    - id: failed
+      description: >
+          Terminal — precheck, quality-gate exhaustion, verify non-PASS, record check
+          failure, or operator rejection; reported, not advanced.
 
-  - id: cancelled
-    description: Terminal — pipeline cancelled by operator at the approval gate (R1).
+    - id: cancelled
+      description: Terminal — pipeline cancelled by operator at the approval gate (R1).
 
 transitions:
-  # ── precheck: size PASS + task check → implement; else → failed ──
-  - from: precheck
-    to: implement
-    description: Deterministic size, evidence, and task checks are green — begin implementation.
-    guard:
-      kind: shell
-      options:
-        command: 'test "$(cat .spur/run/$wbs-precheck-size.status 2>/dev/null)" = PASS && test "$(cat .spur/run/$wbs-precheck-evidence.status 2>/dev/null)" = PASS && $spurBin task check $wbs'
-  - from: precheck
-    to: failed
-    description: Size and/or task check failed — stop before implement.
-    guard:
-      kind: always
+    # ── precheck: size PASS + task check → implement; else → failed ──
+    - from: precheck
+      to: implement
+      description: Deterministic size, evidence, and task checks are green — begin implementation.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$(cat .spur/run/$wbs-precheck-size.status 2>/dev/null)" = PASS && test "$(cat .spur/run/$wbs-precheck-evidence.status 2>/dev/null)" = PASS && $spurBin task check $wbs'
+    - from: precheck
+      to: failed
+      description: Size and/or task check failed — stop before implement.
+      guard:
+          kind: always
 
-  # ── linear body ──
-  - from: implement
-    to: test
-    description: Implementation done — quality-gate probe.
-    guard:
-      kind: always
-  # Soft probe branching (declaration order: PASS first, then FAIL, then defense).
-  - from: test
-    to: review
-    description: Quality gate already green — one gate run only; skip fixall/recheck.
-    guard:
-      kind: shell
-      options:
-        command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = PASS'
-  - from: test
-    to: test-fix
-    description: Quality gate red — start bounded fixall loop.
-    guard:
-      kind: shell
-      options:
-        command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = FAIL'
-  # Defense: missing/corrupt status — treat as FAIL path, not silent PASS.
-  - from: test
-    to: test-fix
-    description: Probe status missing/corrupt — attempt fixall then recheck.
-    guard:
-      kind: always
-  - from: test-fix
-    to: test-recheck
-    description: Fixall finished — soft recheck the same quality gate.
-    guard:
-      kind: always
-  # Recheck branching (PASS first; under-max FAIL → fixall again; exhausted → failed).
-  - from: test-recheck
-    to: review
-    description: Quality gate green after fixall — proceed to review.
-    guard:
-      kind: shell
-      options:
-        command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = PASS'
-  - from: test-recheck
-    to: test-fix
-    description: Still red and under qualityGateMaxFixAttempts — another fixall hop.
-    guard:
-      kind: shell
-      options:
-        command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = FAIL && test "$(cat .spur/run/$wbs-test-fix-attempt 2>/dev/null || echo 0)" -lt "$qualityGateMaxFixAttempts"'
-  - from: test-recheck
-    to: failed
-    description: Still red after max fixall attempts — stop at failed (not silent abort).
-    guard:
-      kind: shell
-      options:
-        command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = FAIL && test "$(cat .spur/run/$wbs-test-fix-attempt 2>/dev/null || echo 0)" -ge "$qualityGateMaxFixAttempts"'
-  # Defense: corrupt recheck status — failed, not review.
-  - from: test-recheck
-    to: failed
-    description: Recheck status missing/corrupt — stop at failed.
-    guard:
-      kind: always
-  # ── review → approve, OR skip the HITL gate entirely when profile=auto (R4) ──
-  # Declaration order matters: the auto-skip guard is tried FIRST, so under
-  # profile=auto the run routes straight to verify and never ENTERS approve
-  # (whose onEnter hitl.confirm would otherwise block). Otherwise fall through
-  # to approve for the human gate.
-  - from: review
-    to: verify
-    description: profile=auto — skip the human approval gate, go straight to verify.
-    guard:
-      kind: shell
-      options:
-        command: 'test "$profile" = auto'
-  - from: review
-    to: approve
-    description: Review done — gate on human approval.
-    guard:
-      kind: always
+    # ── linear body ──
+    - from: implement
+      to: test
+      description: Implementation done — quality-gate probe.
+      guard:
+          kind: always
+    # Soft probe branching (declaration order: PASS first, then FAIL, then defense).
+    - from: test
+      to: verify
+      description: Quality gate already green and mode is fast — proportional fast path bypasses review.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = PASS && test "$mode" = fast'
+    - from: test
+      to: review
+      description: Quality gate already green and safety mode — proceed to review.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = PASS && test "$mode" != fast'
+    - from: test
+      to: test-fix
+      description: Quality gate red — start bounded fixall loop.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = FAIL'
+    # Defense: missing/corrupt status — treat as FAIL path, not silent PASS.
+    - from: test
+      to: test-fix
+      description: Probe status missing/corrupt — attempt fixall then recheck.
+      guard:
+          kind: always
+    - from: test-fix
+      to: test-recheck
+      description: Fixall finished — soft recheck the same quality gate.
+      guard:
+          kind: always
+    # Recheck branching (PASS first; under-max FAIL → fixall again; exhausted → failed).
+    - from: test-recheck
+      to: verify
+      description: Quality gate green after fixall and mode is fast — proportional fast path bypasses review.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = PASS && test "$mode" = fast'
+    - from: test-recheck
+      to: review
+      description: Quality gate green after fixall and safety mode — proceed to review.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = PASS && test "$mode" != fast'
+    - from: test-recheck
+      to: test-fix
+      description: Still red and under qualityGateMaxFixAttempts — another fixall hop.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = FAIL && test "$(cat .spur/run/$wbs-test-fix-attempt 2>/dev/null || echo 0)" -lt "$qualityGateMaxFixAttempts"'
+    - from: test-recheck
+      to: failed
+      description: Still red after max fixall attempts — stop at failed (not silent abort).
+      guard:
+          kind: shell
+          options:
+              command: 'test "$(cat .spur/run/$wbs-test-gate.status 2>/dev/null)" = FAIL && test "$(cat .spur/run/$wbs-test-fix-attempt 2>/dev/null || echo 0)" -ge "$qualityGateMaxFixAttempts"'
+    # Defense: corrupt recheck status — failed, not review.
+    - from: test-recheck
+      to: failed
+      description: Recheck status missing/corrupt — stop at failed.
+      guard:
+          kind: always
+    # ── review → approve, OR skip the HITL gate entirely when profile=auto (R4) ──
+    # Declaration order matters: the auto-skip guard is tried FIRST, so under
+    # profile=auto the run routes straight to verify and never ENTERS approve
+    # (whose onEnter hitl.confirm would otherwise block). Otherwise fall through
+    # to approve for the human gate.
+    - from: review
+      to: verify
+      description: profile=auto — skip the human approval gate, go straight to verify.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$profile" = auto'
+    - from: review
+      to: approve
+      description: Review done — gate on human approval.
+      guard:
+          kind: always
 
-  # ── approve: HITL gate (reached only when profile != auto). Routed by the
-  # operator's captured answer (R1, bug-750) — three ordered guards, declaration
-  # order matters (yes first, then no, then cancel), mirroring idea-pipeline's
-  # design-approval gate (.spur/workflows/idea-pipeline.yaml:352-366). No
-  # `always` edge remains out of `approve`. ──
-  - from: approve
-    to: verify
-    description: Approved — proceed to verification.
-    guard:
-      kind: shell
-      options:
-        command: 'test "$__hitlAnswer" = yes'
-  - from: approve
-    to: failed
-    description: Operator rejected at the approval gate — report and stop.
-    guard:
-      kind: shell
-      options:
-        command: 'test "$__hitlAnswer" = no'
-  - from: approve
-    to: cancelled
-    description: Operator cancelled at the approval gate.
-    guard:
-      kind: shell
-      options:
-        command: 'test "$__hitlAnswer" = cancel'
+    # ── approve: HITL gate (reached only when profile != auto). Routed by the
+    # operator's captured answer (R1, bug-750) — three ordered guards, declaration
+    # order matters (yes first, then no, then cancel), mirroring idea-pipeline's
+    # design-approval gate (.spur/workflows/idea-pipeline.yaml:352-366). No
+    # `always` edge remains out of `approve`. ──
+    - from: approve
+      to: verify
+      description: Approved — proceed to verification.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$__hitlAnswer" = yes'
+    - from: approve
+      to: failed
+      description: Operator rejected at the approval gate — report and stop.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$__hitlAnswer" = no'
+    - from: approve
+      to: cancelled
+      description: Operator cancelled at the approval gate.
+      guard:
+          kind: shell
+          options:
+              command: 'test "$__hitlAnswer" = cancel'
 
-  # ── completion gate (the YAML-native replacement for rd3's default-on --postflight-verify) ──
-  # The verify step emits .spur/run/<wbs>-verdict.json with a required proof block (task 0703 R3/R5).
-  # Only `verdict: PASS` PLUS a proof block whose digest — top level and every named stage — equals
-  # the captured `proofDigest` clears the gate to `record`; any non-PASS, a missing file, malformed
-  # JSON, or missing/mismatched proof evidence does not. Declaration order: PASS+proof guard FIRST,
-  # then the bounded remediation route (R4), then the always catch-all so a PASS verdict with a
-  # missing/malformed proof block still terminates at `failed` instead of hanging the state.
-  - from: verify
-    to: record
-    description: Verification verdict is PASS and its proof block names the captured digest on every stage — record results and proceed to done.
-    guard:
-      kind: shell
-      options:
-        command: >-
-          V=".spur/run/$wbs-verdict.json";
-          test "$(jq -r .verdict "$V" 2>/dev/null)" = PASS &&
-          test "$(jq -r '.proof.digest // ""' "$V" 2>/dev/null)" = "$proofDigest" &&
-          test "$(jq -r '.proof.stages.qualityGate.digest // ""' "$V" 2>/dev/null)" = "$proofDigest" &&
-          test "$(jq -r '.proof.stages.review.digest // ""' "$V" 2>/dev/null)" = "$proofDigest" &&
-          test "$(jq -r '.proof.stages.verification.digest // ""' "$V" 2>/dev/null)" = "$proofDigest"
-  - from: verify
-    to: test-fix
-    description: >-
-      Verification returned a repairable non-PASS and the shared fix budget is not exhausted —
-      bounded remediation hop (task 0703 R4); the chain re-enters quality → review → verify on a
-      freshly captured digest. Never reached on PASS: remediation cannot follow certification.
-    guard:
-      kind: shell
-      options:
-        command: >-
-          V="$(jq -r .verdict .spur/run/$wbs-verdict.json 2>/dev/null)";
-          test -n "$V" && test "$V" != PASS &&
-          test "$(cat .spur/run/$wbs-test-fix-attempt 2>/dev/null || echo 0)" -lt "$qualityGateMaxFixAttempts"
-  - from: verify
-    to: failed
-    description: >-
-      Non-PASS with the fix budget exhausted, or a PASS/missing/malformed verdict whose proof
-      block is absent or mismatched (task 0703 R5) — block before done; defense catch-all so the
-      state always has a viable outgoing edge.
-    guard:
-      kind: always
-  # ── done gate: record → done/failed gated on `spur task check` (ADR-026 amendment 2026-06-23)
-  # PLUS the proof-block re-assertion (task 0703 R5): the verdict artifact must still be PASS and
-  # still name the captured digest — a forged or mutated completion artifact fails closed here.
-  # Declaration order: pass guard first.
-  - from: record
-    to: done
-    description: Task check passed and the verdict proof block still names the captured digest — certify done.
-    guard:
-      kind: shell
-      options:
-        command: >-
-          $spurBin task check $wbs &&
-          test "$(jq -r .verdict .spur/run/$wbs-verdict.json 2>/dev/null)" = PASS &&
-          test "$(jq -r '.proof.digest // ""' .spur/run/$wbs-verdict.json 2>/dev/null)" = "$proofDigest"
-  - from: record
-    to: failed
-    description: Task check failed or proof evidence missing/malformed/mismatched — block before done.
-    guard:
-      kind: always
+    # ── completion gate (the YAML-native replacement for rd3's default-on --postflight-verify) ──
+    # The verify step emits .spur/run/<wbs>-verdict.json with a required proof block (task 0703 R3/R5).
+    # Only `verdict: PASS` PLUS a proof block whose digest — top level and every named stage — equals
+    # the captured `proofDigest` clears the gate to `record`; any non-PASS, a missing file, malformed
+    # JSON, or missing/mismatched proof evidence does not. Declaration order: PASS+proof guard FIRST,
+    # then the bounded remediation route (R4), then the always catch-all so a PASS verdict with a
+    # missing/malformed proof block still terminates at `failed` instead of hanging the state.
+    - from: verify
+      to: record
+      description: Verification verdict is PASS and its proof block names the captured digest on every stage — record results and proceed to done.
+      guard:
+          kind: shell
+          options:
+              command: >-
+                  V=".spur/run/$wbs-verdict.json";
+                  test "$(jq -r .verdict "$V" 2>/dev/null)" = PASS &&
+                  test "$(jq -r '.proof.digest // ""' "$V" 2>/dev/null)" = "$proofDigest" &&
+                  test "$(jq -r '.proof.stages.qualityGate.digest // ""' "$V" 2>/dev/null)" = "$proofDigest" &&
+                  test "$(jq -r '.proof.stages.review.digest // ""' "$V" 2>/dev/null)" = "$proofDigest" &&
+                  test "$(jq -r '.proof.stages.verification.digest // ""' "$V" 2>/dev/null)" = "$proofDigest" &&
+                  test "$(jq -r '.proof.runId // ""' "$V" 2>/dev/null)" = "$__runId" &&
+                  test "$(jq -r '.proof.definitionDigest // ""' "$V" 2>/dev/null)" = "$__definitionDigest"
+    - from: verify
+      to: test-fix
+      description: >-
+          Verification returned a repairable non-PASS and the shared fix budget is not exhausted —
+          bounded remediation hop (task 0703 R4); the chain re-enters quality → review → verify on a
+          freshly captured digest. Never reached on PASS: remediation cannot follow certification.
+      guard:
+          kind: shell
+          options:
+              command: >-
+                  V="$(jq -r .verdict .spur/run/$wbs-verdict.json 2>/dev/null)";
+                  test -n "$V" && test "$V" != PASS &&
+                  test "$(cat .spur/run/$wbs-test-fix-attempt 2>/dev/null || echo 0)" -lt "$qualityGateMaxFixAttempts"
+    - from: verify
+      to: failed
+      description: >-
+          Non-PASS with the fix budget exhausted, or a PASS/missing/malformed verdict whose proof
+          block is absent or mismatched (task 0703 R5) — block before done; defense catch-all so the
+          state always has a viable outgoing edge.
+      guard:
+          kind: always
+    # ── done gate: record → done/failed gated on `spur task check` (ADR-026 amendment 2026-06-23)
+    # PLUS the proof-block re-assertion (task 0703 R5): the verdict artifact must still be PASS and
+    # still name the captured digest — a forged or mutated completion artifact fails closed here.
+    # Declaration order: pass guard first.
+    - from: record
+      to: done
+      description: Task check passed and the verdict proof block still names the captured digest — certify done.
+      guard:
+          kind: shell
+          options:
+              command: >-
+                  $spurBin task check $wbs &&
+                  test "$(jq -r .verdict .spur/run/$wbs-verdict.json 2>/dev/null)" = PASS &&
+                  test "$(jq -r '.proof.digest // ""' .spur/run/$wbs-verdict.json 2>/dev/null)" = "$proofDigest"
+    - from: record
+      to: failed
+      description: Task check failed or proof evidence missing/malformed/mismatched — block before done.
+      guard:
+          kind: always