@gobing-ai/spur 0.4.25 → 0.4.27

package/plugins/sp/skills/spur-dev/references/execution-batch-report.md

@@ -20,21 +20,29 @@ results). A `paused` task is non-terminal — the report marks it `paused` (neve
 the resume command. Unless `--no-summary`, follow it with the measured
 [execution summary](dev-operations.md#execution-summary), one `--progress <wbs>=<file>` per attempted run.
 
+Under `--auto` the report's mode field reads `Mode: --auto (keep-going)`, and `--auto` implies `--keep-going`:
+an unattended batch never stops for a human (1318 R1). For an `--agent auto` or
+`--agent <name>` batch, print the header `Executor pin: <name> (from <wbs>|--agent)` and fill the
+per-task `Executor` column with the pinned executor, or `A → B (failed-agent)` for a run that was
+re-dispatched once on a new executor (1318 R2–R4). Leave that line and column out for host-inline
+runs, which have no executor to pin.
+
 ```
 ## Batch Report — <selector>
 
 **Selector:** <value>
 **Plan:** <n> tasks (ordered: <wbs-list>) · <m> blocked · <p> not-attempted
-**Mode:** stop-the-batch | --keep-going | --auto
+**Mode:** stop-the-batch | --keep-going | --auto (keep-going)
+**Executor pin:** <name> (from <wbs>|--agent)   ← `--agent auto`/`--agent <name>` runs only
 **Verdict:** clean | halted | aborted
 
-| WBS | Status | Reason |
-|-----|--------|--------|
-| 0040 | done | — |
-| 0042 | failed | verify verdict PARTIAL (see .spur/run/0042-verdict.json) |
-| 0050 | not-attempted | batch halted after 0042 (stop-the-batch) |
-| 0051 | skipped | dependency 0040 failed (--keep-going) |
-| 0060 | blocked | unmet out-of-set dep: 0099 is wip |
+| WBS | Status | Executor | Reason |
+|-----|--------|----------|--------|
+| 0040 | done | claude | — |
+| 0042 | failed | codex-a → codex-b (failed-agent) | verify verdict PARTIAL (see .spur/run/0042-verdict.json) |
+| 0050 | not-attempted | — | batch halted after 0042 (stop-the-batch) |
+| 0051 | skipped | — | dependency 0040 failed (--keep-going) |
+| 0060 | blocked | — | unmet out-of-set dep: 0099 is wip |
 
 **Next:** <one-line action — pick up halted run / resolve 0099 / all green, feature H1 complete>
 

package/plugins/sp/skills/spur-dev/references/execution-batch.md

@@ -23,6 +23,9 @@ see_also:
   [execution-batch-continuation.md](execution-batch-continuation.md) for `--continue`.
 - **Never re-derive the plan** — the frozen plan is the persisted report; a new selector match is
   `not-admitted`, not a plan change.
+- **Fresh session per segment** — when host context nears its limit, stop after a task terminal and
+  resume in a new session with `--continue`; the persisted report and markers carry the state. A
+  near-full context slows every later turn and degrades judgment.
 
 ## What this file owns
 
@@ -146,6 +149,13 @@ recorded in the batch report, and independent tasks keep running. The batch does
 - **without `--auto`:** unchanged halt behavior — the batch stops on the failing task (`--keep-going`
 still skips only its in-batch dependents).
 
+**`--auto` implies `--keep-going` (1318 R1).** An unattended batch never stops for a human: under
+`--auto` every per-task failure follows §4.2 whether or not the flag is passed — a failed,
+cancelled, `stale-evidence` or worker-lost (1317) task is recorded `failed`, its in-batch
+dependents are `skipped` with `dependency <wbs> failed`, and independent tasks keep running. The
+refine pass above is only the extra step before that, not an exception. Without `--auto` the §4.1
+stop-the-batch default is unchanged. No new flag.
+
 `--tasks <value>` (or the effective value after normalization) resolves to a frozen set of task WBS numbers. Resolution happens **once, at
 kickoff** — the driver never re-queries `spur task list` to recompute membership mid-batch (R2.1).
 
@@ -408,6 +418,18 @@ The host session remains the orchestrator for interactive sequential omit/inline
 owns explicit-executor and parallel paths; there the flag pins the per-task step executor, not the
 orchestrator.
 
+**Executor pin (1318 R2/R3).** `--agent auto` is resolved **once per batch**, not once per task:
+after the first task run, read the resolved implement executor from that run's implement `agent.run`
+trace event — `spur workflow trace <run> --json` → `.events[] | select(.node=="implement" and
+.actionKind=="agent.run") | .result.executor` — and dispatch every later task with
+`--agent <that executor>`. The report's header records `Executor pin: <name> (from <wbs>)`; an
+explicit `--agent <name>` records `(from --agent)` and needs no resolution. A task whose run ends
+with `terminalReason == "failed-agent"` is re-dispatched **exactly once** with `--agent auto`; a
+different resolved executor then becomes the pin for the remaining tasks, and a second
+`failed-agent` records the task `failed` under the failure policy with the pin kept. No other terminal reason
+is ever retried on a new executor. `--agent inline` (host driver) has no executor
+to pin, so R2/R3 do not apply.
+
 ### 3.3 Terminal-state inspection
 
 Each pipeline run ends in one of two terminal states:
@@ -525,10 +547,11 @@ belongs to a subagent or the operator, not to the batch controller's report loop
 
 ## Step 4 — Failure policy (R3)
 
-### 4.1 Stop-the-batch (default) (R3.1)
+### 4.1 Stop-the-batch (default unless `--auto`) (R3.1)
 
-By default, the **first** pipeline failure halts the batch. Remaining tasks in the plan are reported
-as `not-attempted`. The report lists succeeded, failed, and not-attempted tasks.
+By default — i.e. without `--auto` (1318 R1) — the **first** pipeline failure halts the batch.
+Remaining tasks in the plan are reported as `not-attempted`. The report lists succeeded, failed,
+and not-attempted tasks.
 
 **Run-failed / task-done (observed 2026-10-19, feature P1).** A run can fail *after* the task is
 already finished: the `done` state's close commands run last, and a lint or anchor rule can refuse
@@ -540,9 +563,10 @@ contract, not to a run whose last recorded state was superseded. Surface it in t
 way (never silently continue), and never re-run the pipeline just to flip a run row from `failed` to
 `done` — a second run re-executes model stages for a task that is already closed.
 
-### 4.2 `--keep-going` (R3.2)
+### 4.2 `--keep-going` (R3.2), or implied by `--auto`
 
-With `--keep-going`, a failed task does **not** halt the batch. Instead:
+With `--keep-going` — passed explicitly, or implied by `--auto` (1318 R1) — a failed task does
+**not** halt the batch. Instead:
 
 - The failed task's **in-batch dependents** (tasks in the plan that transitively depend on it) are
   marked `skipped` with the failed dependency as the reason — they cannot run because their dep did

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

@@ -138,6 +138,11 @@ Only declared where the command already has at least one HITL gate the flag can
 taste gates (idea-eval, design-approval) — every gate there is reversible corpus writes. A gate
 without an actionable recommendation (missing eval recommendation, FAIL design check) still pauses.
 
+**Batch policy** (`dev-runall`): `--auto` implies `--keep-going` — an unattended batch never stops
+for a human. With `--agent auto` the driver also pins ONE executor for the batch — `Executor pin:
+<name>`, read from the first run's implement `result.executor` — and only a `failed-agent` ending
+re-resolves it, exactly once (1318 R1–R3).
+
 ### `--keep-going` — batch failure policy: skip dependents, continue independents
 
 **Anchor:** `#flag-keep-going`.
@@ -146,6 +151,10 @@ Batch operation only (`dev-refineall`, `dev-runall`). When a task in the batch
 fails, skip its in-batch dependents and continue the independent ones, instead of the default
 halt-on-first-failure. Never silently retried; the failure is still reported.
 
+**Default:** off, except under `--auto` — `--auto` implies `--keep-going` (1318 R1), because an
+unattended batch that stops to wait for a human is the defect it was supposed to avoid. To stop at
+the first failure, run without `--auto`.
+
 ### `--defer-gate` — opt-in parallel-batch gate policy (task 1111 / H15)
 
 **Applies to:** `/sp-dev-runall --mode parallel`, and `--mode auto` when it resolves to parallel.