@gobing-ai/spur 0.3.93 → 0.3.94

package/plugins/sp/skills/spur-dev/references/flag-glossary.md

@@ -410,6 +410,17 @@ Full checklist: [dev-operations.md](dev-operations.md) § refine (depth ready).
 Use the task's Gherkin scenarios as the verification lens on verify-family commands (`dev-verify`,
 `dev-verifyall`).
 
+### `--triage` — fix small findings, file the rest as tasks
+
+**Anchor:** `#flag-triage`.
+
+Review commands (`dev-review`, `dev-review-session`): after the report, bucket every finding once
+(direct fix / task / note), apply the direct fixes inline with a targeted check each, and file the
+remainder through `spur task` — never fix straight from the raw findings list. Off by default
+(report-only). Both file one or more implement-ready tasks sized per cohesive unit, under existing
+features ([dev-operations.md § 2. review](dev-operations.md#2-review)); `dev-review-session` keeps
+the stricter direct-fix bar (pure docs / one-to-two-line fixes).
+
 ### `--approve-taste` — pre-clear all taste gates this run
 
 **Anchor:** `#flag-approve-taste`.
@@ -422,9 +433,11 @@ flag sets both.
 
 **Anchor:** `#flag-worktree`.
 
-Batch commands plus single-task `dev-run` (`dev-refineall`, `dev-runall`, `dev-verifyall`,
-`dev-run`): run the entire driver loop inside an isolated git worktree instead of the operator's
-working directory. One flag, two modes:
+Batch commands plus single-task `dev-run` and review triage (`dev-refineall`, `dev-runall`,
+`dev-verifyall`, `dev-run`, `dev-review`): run the entire driver loop inside an isolated git
+worktree instead of the operator's working directory. On `dev-review` the flag requires `--triage`
+and wraps the review-plus-triage pass
+([dev-operations.md § 2. review](dev-operations.md#2-review)). One flag, two modes:
 
 - **Create mode** — bare `--worktree` (no value). Cut a fresh branch from the current HEAD's ref,
   create a sibling worktree with a derived name, run the batch there. On a fully successful batch

package/plugins/sp/skills/spur-dev/references/inline-pipeline-driver.md

@@ -511,7 +511,10 @@ The driver reaches it through the existing run delegate (`$SETUP_SCRIPT`,
   against the project workdir. The decision never pauses and never fails the run for model
   problems: a degraded outcome (feature switch off, no backend, error, timeout, low confidence)
   prints `ok:true` with `degraded:true`, the declared `reason`, and `value = default`, and exits
-  `0` — route on the resultFile's `.value` with the declared file guards. Only an invalid options
+  `0` — route on the resultFile's `.value` with the declared file guards. Every row carries
+  `source: model|default` (0976 R2), and the delegate appends
+  `decide node=<id> value=<v> source=<s> reason=<r>` to the run log, so a declared-default
+  fallback is never read as a model decision. Only an invalid options
   schema exits `1` (fail closed), and usage errors exit `2`. The `action_runs` trace row is
   best-effort exactly like `--action`.
 
@@ -524,7 +527,18 @@ The driver reaches it through the existing run delegate (`$SETUP_SCRIPT`,
   ```
 
   `--status` is the declared terminal state's verdict, not a guess: a run that reached a terminal
-  state is `done`; a run halted by a failing action under its error policy is `failed`.
+  state is `done`; a run halted by a failing action under its error policy is `failed`. On success
+  the close reports the recorded evidence: `{"ok":true,"runId":…,"actionRows":<n>}`.
+
+  **Zero-row done closes are a named failure (task 0975 R2).** A run closed `done` with **zero**
+  `action_runs` rows (`actionRows:0`) finalizes the row but exits `1` with
+  `{"ok":false,"code":"NO_ACTION_ROWS","actionRows":0}` — a run that claims success without a
+  single recorded action is exactly the untraced-runs gap ADR-117 closes, so the driver must
+  surface the code in its final report instead of reporting a clean close. The failure must NOT
+  be repaired by backfilling rows: the run row is already terminal, and hand-written rows are
+  forbidden (ADR-117) — record the finding and let the task's evidence show the gap. A `failed`
+  close with zero rows stays a clean `0` (a halt before the first boundary legitimately records
+  nothing), and any `done` close with `actionRows ≥ 1` exits `0`.
 
 **Best-effort at the action boundary only (ADR-117).** An `--action` persistence failure is
 recorded — the delegate appends a `trace-emission-failed` line to `.spur/run/<run-id>.md` and