@gobing-ai/spur 0.3.81 → 0.3.83

package/plugins/sp/skills/spur-cli/references/agent.md

@@ -1,6 +1,6 @@
 ---
 name: spur-cli-agent
-description: "spur-cli noun reference: operate `spur agent` as the coding-agent execution surface - run prompts, wait on pinned occupants, manage team agent specs, run the persistent self-draining loop, and check readiness."
+description: "spur-cli noun reference: operate `spur agent` as the coding-agent execution surface - run prompts, wait on pinned occupants, list agent specs, start/stop supervised processes, and check readiness."
 see_also:
   - spur-cli
 ---
@@ -9,7 +9,7 @@ see_also:
 
 `spur agent` is the CLI for **running and inspecting coding agents**. It wraps the agents the
 operator already has installed (Claude Code, Codex, omp, OpenCode, Antigravity, etc.) behind a
-uniform run, wait, loop, and spec-management surface, so the rest of the harness can dispatch work without
+uniform run, wait, and supervision surface, so the rest of the harness can dispatch work without
 hard-coding a specific agent.
 
 This is a **companion reference**, not an orchestrator. It documents *what each verb is and how to
@@ -22,18 +22,14 @@ that before using `run` for fan-out dispatch.
 | Verb | Purpose | Key flags |
 | ---- | ------- | --------- |
 | `run <prompt>` | Execute a prompt or slash command via a coding agent | `--agent <name>` `--spec <id>` `--model <name>` `--mode <mode>` `--continue` `--cwd <path>` `--drain` `--json` |
-| `loop` | Persistent self-draining inbox loop for a team member (supervisor-managed) | `--spec <id>` `--agent <id>` `--poll <ms>` |
 | `wait [<specId>]` | Identity-pinned wait for an occupant run to reach a lifecycle state (G4 wave 2; `--role` selector per 0685) | `--role <name>` `--run <runId>` `--until <state>...` `--timeout <ms>` `--json` |
-| `list` | List detected coding agents, or team agent specs with `--specs` (live run status merged from `spur serve`) | `--specs` `--server <url>` `--json` |
+| `list` | List detected coding agents, or agent specs with `--specs` (live run status merged from `spur serve`) | `--specs` `--server <url>` `--json` |
 | `doctor [agent]` | Check agent readiness | `--json` `--probe-health` `--force-refresh` |
-| `create <id>` | Write a team agent spec to `.spur/agents/<id>.yaml` | `--type` `--tags` `--model` `--autonomy` `--system-prompt` `--name` `--workspace` `--purpose` `--auto-start` `--no-identity-preamble` `--json` |
-| `edit <id>` | Open an agent spec in `$EDITOR`, or print its path | - |
-| `delete <id>` | Remove an agent spec | `--force` |
-| `start <spec-id>` | Start a supervised agent process (requires `spur serve`; 0848 moved home of `spur team start`) | `--server <url>` `--json` |
-| `stop <spec-id>` | Stop a supervised agent process (requires `spur serve`; 0848 moved home of `spur team stop`) | `--server <url>` `--json` |
-
-`list`, `doctor`, `run`, `wait`, and `create` accept `--json` plus `--json-envelope`. `loop`, `edit`,
-and `delete` are human/process-control surfaces. **Exit codes:** `0` success, `1` failure, and `2`
+| `start <spec-id>` | Start a supervised agent process (requires `spur serve`) | `--server <url>` `--json` |
+| `stop <spec-id>` | Stop a supervised agent process (requires `spur serve`) | `--server <url>` `--json` |
+
+`list`, `doctor`, `run`, `wait`, `start`, and `stop` accept `--json` plus `--json-envelope`. The hidden
+`loop` is a supervisor-internal process surface. **Exit codes:** `0` success, `1` failure, and `2`
 invalid usage; `run` can also propagate the invoked agent's non-zero result.
 
 ## `run` - execute a prompt via a coding agent
@@ -56,7 +52,7 @@ through a coding agent as an external process, producing a persisted run record
 | `--mode <mode>` | Agent output mode: `text` or `json`. |
 | `--continue` | Resume the previous agent session instead of starting fresh. |
 | `--cwd <path>` | Working directory for agent execution (default: current directory). |
-| `--spec <id>` | Team agent spec id (occupant addressing, 0542 R1). Pairs with `--drain`; with `--spec` alone the run is addressed to the occupant without touching the inbox. A legacy `--agent <spec-id>` is still accepted as fallback addressing (task 0849 retired the `agent-flag-spec-id` deprecation warning). |
+| `--spec <id>` | Agent spec id (occupant addressing, 0542 R1). Pairs with `--drain`; with `--spec` alone the run is addressed to the occupant without touching the inbox. A legacy `--agent <spec-id>` is still accepted as fallback addressing (task 0849 retired the `agent-flag-spec-id` deprecation warning). |
 | `--drain` | Prepend pending inbox messages addressed to `--spec <id>` before the prompt. |
 | `--json` | Output machine-readable JSON where supported. |
 | `--json-envelope` | Wrap JSON using the facade's standard output contract. |
@@ -85,30 +81,15 @@ can fail when the external agent writes its own storage outside the sandbox's al
 `AgentStorage` SQLite DB). This is not a reason to abandon `spur agent run` - triggers 1-4 still
 justify it - but ensure the run executes in a context that can write the target agent's storage.
 
-## `loop` - persistent self-draining wrapper
-
-```bash
-spur agent loop --agent worker-1 --poll 2000
-```
-
-`loop` is the **persistent self-draining wrapper** used by the team supervisor. It waits for a
-wake on the `system_events` ledger — a human request (`message.sent`), a strategy change
-(`strategy.changed`), a capacity change (`fleet.capacity.changed`), or a completion receipt
-(`agent.invoke.exit`) — then drains the inbox into an `agent run` invocation. An idle wake
-records the hold reason instead of dispatching; with no wake event at all it still drains every
-`--poll` ms (backstop). It
-between drains. It is not typically invoked directly by the operator - `spur agent start` launches it
-under supervision.
-
-### Flags
-
-| Flag | Purpose |
-|------|---------|
-| `--spec <id>` | **Required.** Team agent spec id / message recipient (0542 R1; legacy `--agent <spec-id>` still read with a one-time warning). |
-| `--poll <ms>` | Wakeup backstop timeout in milliseconds — drains at least this often (default: `2000`). |
+## `loop` - supervisor-internal self-draining wrapper (hidden)
 
-The loop runs until `SIGINT` / `SIGTERM`. Each iteration: check inbox -> if messages, drain each
-into `run` with `--drain` -> else record the idle hold (an empty drain dispatches nothing).
+`spur agent loop --spec <id> [--poll <ms>]` is spawned by the `spur serve` supervisor for each
+materialized agent spec; it is hidden from `--help` and not an operator verb (use `spur agent start`).
+It waits for a wake on the `system_events` ledger — a human request (`message.sent`), a strategy
+change (`strategy.changed`), a capacity change (`fleet.capacity.changed`), or a completion receipt
+(`agent.invoke.exit`) — then drains the inbox into an `agent run` invocation. An idle wake records
+the hold reason instead of dispatching; with no wake event it still drains every `--poll` ms
+(default `2000`). It runs until `SIGINT` / `SIGTERM`.
 
 ## `wait` - identity-pinned occupant wait (G4 wave 2)
 
@@ -149,17 +130,17 @@ exits 2 naming the accepted vocabulary. Resolution collapses onto the same ident
 | `timeout` | 1 | Caller `--timeout` elapsed (or aborted via SIGINT). |
 | `usage` | 2 | Invalid flags, or `--until blocked` as the sole target (no first-class signal in wave 2). |
 
-## `list` - detected agents and team specs
+## `list` - detected agents and agent specs
 
 ```bash
 spur agent list              # detected coding agents on this machine
-spur agent list --specs      # team agent specs under .spur/agents/
+spur agent list --specs      # agent specs under .spur/agents/
 spur agent list --json       # machine-readable
 ```
 
 Without `--specs`, lists coding agents detected on the host (by binary on `PATH`). With `--specs`,
-lists team agent specs (`.spur/agents/*.yaml`) **with live run status merged from the server's
-supervisor** (0848, the moved home of `spur team status`): each row carries a trailing status column
+lists agent specs (`.spur/agents/*.yaml`) **with live run status merged from the server's
+supervisor**: each row carries a trailing status column
 (`running` / `stopped` / `errored` / `unknown`) and `pid=<n>` where a process exists. When `spur serve`
 is unreachable, the listing falls back to all `stopped` with a stderr warning. `--server <url>`
 (default `http://localhost:3000/api`) targets the supervisor API.
@@ -184,89 +165,41 @@ Checks whether each agent is installed and ready to run. Text mode renders a cap
 (`cheap|standard|capable-*`), MODEL the pinned config model (`—` when undeclared), and ROLES lists
 candidate pipeline roles with `*` on the elected one. Exit `1` if any checked agent is not ready.
 
-## `create` - author a team agent spec
-
-```bash
-spur agent create worker-1 --type claude --tags team:alpha --model sonnet
-spur agent create reviewer --type codex --autonomy review --auto-start
-```
-
-Writes a team agent spec to `.spur/agents/<id>.yaml`. The spec captures the agent's identity
-(type, model, autonomy, system prompt, tags) so the fleet declaration (`.spur/fleet.json`, converted
-by `spur projects migrate`) can materialize a roster and `spur
-agent loop` can self-drain its inbox.
-
-### Flags
-
-| Flag | Purpose |
-| ------ | --------- |
-| `--type <agent-type>` | Agent spec type (e.g. `claude`, `codex`, `omp`). |
-| `--tags <a,b>` | Comma-separated team identity tags (e.g. `team:alpha,role:worker`). |
-| `--model <name>` | Agent model argument. |
-| `--autonomy <level>` | Autonomy level (e.g. `full`, `review`). |
-| `--system-prompt <text>` | Team identity system prompt. |
-| `--name <name>` | Agent display name. |
-| `--workspace <path>` | Workspace path for this agent. |
-| `--purpose <text>` | Team identity purpose. |
-| `--auto-start` | Auto-start flag (started by the supervisor when serve materializes the fleet; without it, start manually with `spur agent start`). |
-| `--no-identity-preamble` | Disable the identity preamble prepended to prompts. |
-| `--json` | Output machine-readable JSON. |
-
-## `edit` - open a spec in `$EDITOR`
-
-```bash
-spur agent edit worker-1
-```
-
-Opens `.spur/agents/<id>.yaml` in `$EDITOR`. If `$EDITOR` is unset, prints the spec path instead.
-
-## `delete` - remove a spec
-
-```bash
-spur agent delete worker-1 --force
-```
-
-`--force` is required (guards against accidental deletion). Removes `.spur/agents/<id>.yaml`.
-
-## `start` - start a supervised process (0848)
+## `start` - start a supervised process
 
 ```bash
 spur agent start worker-1
 spur agent start worker-1 --json
 ```
 
-The moved home of `spur team start`. Posts to the `spur serve` supervisor API
-(`POST /api/team/agents/:id/start`) and prints `started <id> (pid=<n>, status=<s>)`. Requires a
+Posts to the `spur serve` supervisor API
+(`POST /api/agents/:id/start`) and prints `started <id> (pid=<n>, status=<s>)`. Requires a
 reachable `spur serve`; `--server <url>` (default `http://localhost:3000/api`) targets it. Exit `1`
 when the server is unreachable or the start fails.
 
-## `stop` - stop a supervised process (0848)
+## `stop` - stop a supervised process
 
 ```bash
 spur agent stop worker-1
 spur agent stop worker-1 --json
 ```
 
-The moved home of `spur team stop`. Posts to the supervisor API
-(`POST /api/team/agents/:id/stop`) and prints `stopped <id>`. Same server requirement and flags as
-`start`. `spur agent delete` (with `--force`) remains the spec-removal counterpart of the old
-`team down --purge`.
+Posts to the supervisor API
+(`POST /api/agents/:id/stop`) and prints `stopped <id>`. Same server requirement and flags as
+`start`.
 
 ## What this skill is NOT
 
 - **Not the dispatch decision.** *When* to use `spur agent run` vs a native subagent is the
   **[dispatch-surface rule](../../parallel-execution/references/dispatch-surface.md)**, not this
   reference. This reference documents the verbs; that rule decides which surface carries a dispatch.
-- **Not the team orchestrator.** The `spur serve` supervisor drives the lifecycle: `spur agent
-  start` / `stop` manage supervised processes and `agent list --specs` reports live state (0848
-  moved these homes off the deprecated `spur team` noun).
+- **Not the fleet orchestrator.** The `spur serve` supervisor drives the lifecycle: `spur agent
+  start` / `stop` manage supervised processes and `agent list --specs` reports live state.
 
 ## See also
 
 - **[dispatch-surface.md](../../parallel-execution/references/dispatch-surface.md)** - native
   subagent vs `spur agent run` decision rule. `--model` and `--agent` are its escalation levers.
-- **`spur team` (see [team.md](team.md))** - deprecated team noun (0848); its verbs moved to this
-  noun (`start`/`stop`/`list --specs`) and to `spur task update --assignee`.
 - **`spur message` (see [message.md](message.md))** - the inbox `--drain` reads from.
 - **`sp:spur-cli`** SKILL.md - the facade that routes to this reference.
 

package/plugins/sp/skills/spur-cli/references/message.md

@@ -134,7 +134,7 @@ lines.
 
 - **`spur agent` (see [agent.md](agent.md))** - `run --drain` and `loop` consume the inbox.
 - **`spur task` (see [tasks.md](tasks.md))** - `task update --assignee` wires an agent spec to a
-  task (0848 moved home of `spur team assign`).
+  task.
 - **`sp:spur-cli`** SKILL.md - the facade that routes to this reference.
 
 > **Shared option declarations (0618):** options shared across command modules resolve from

package/plugins/sp/skills/spur-cli/references/projects.md

@@ -22,7 +22,6 @@ shapes live in `apps/cli/src/commands/projects.ts`.
 | `list` | List entries with live running status | `--json` `--fleet` |
 | `start <target>` | Start or reuse a detached project server | `--port <n>` `--json` |
 | `stop <target>` | Best-effort stop the listener and clear its recorded port | `--json` |
-| `migrate [path]` | Preview (default) or apply the legacy `agent.team` → `fleet.json` conversion (0847) | `--dry-run` `--apply` `--json` |
 
 Every verb also advertises `--json-envelope`; use the facade's machine-output contract. Success is
 exit `0`; validation, registry, spawn, health, or lookup failure is exit `1`.
@@ -37,14 +36,15 @@ exit `0`; validation, registry, spawn, health, or lookup failure is exit `1`.
   defaults the display name to its basename. It upserts; it does not start a server. The current
   source does not enforce a `.spur/` marker or directory type.
 - `list` probes recorded ports and heals stale entries to `port: 0` before reporting `running`.
-- `list --fleet` (0835) additionally resolves each project's fleet declaration at
-  `<project>/.spur/fleet.json` under the existing verb (no new noun). Per project it prints one line
+- `list --fleet` (0835/0858) additionally resolves each project's `agent.fleet` section from that
+  project's `.spur/config.yaml` under the existing verb (no new noun). Per project it prints one line
   per member: instance id (the spec id / mailbox identity), `role`, resolved `executor`,
   `fsWrite` capability state, and derived `write` flag. A project with no declaration reports
-  `no declaration (.spur/fleet.json)`; an all-disabled roster reports `no enabled members`; a project
-  whose executors fail resolution reports the error without failing the listing. Under `--json` each
-  project gains `fleet` (the resolved fleet, `null` on resolution failure) and, on failure,
-  `fleetError`.
+  `no declaration (agent.fleet)`; a declared but switched-off fleet reports
+  `disabled (agent.fleet.enabled: false)` and still lists its roster; an all-disabled roster reports
+  `no enabled members`; a project whose config fails to load (a retired source, an invalid section)
+  reports the loader's message without failing the listing. Under `--json` each project gains `fleet`
+  (the resolved fleet, `null` on resolution failure) and, on failure, `fleetError`.
 - `list --fleet` (0836) also reports the project's orchestrator binding: one
   `orchestrator:` line per project with state `bound-online <id> (holder <spec-id>)`,
   `bound-offline <id> (no live claim)`, `missing (no-orchestrator-declared)`, or
@@ -60,26 +60,6 @@ exit `0`; validation, registry, spawn, health, or lookup failure is exit `1`.
   persisted row, or `unavailable (<error>)` on a db failure. Under `--json` each
   project gains `strategy` (`{ strategy, strategyVersion }`, `null` when
   unpersisted) and, on failure, `strategyError`.
-- `migrate [path]` (0847) converts the single legacy `agent.team.<id>` roster whose
-  `work_dir` resolves to the project into `<project>/.spur/fleet.json`, preserving
-  every spec id verbatim (explicit member ids freeze the `<role>-<n>` derivation).
-  Dry-run is the default: it emits the 0846 plan (steps + conflicts + warnings) and
-  writes nothing — an existing project db is opened read-only without migrations;
-  an absent db or table contributes no addressed identities.
-  `--apply` validates first, deep-equals an existing declaration (`unchanged`, no
-  rewrite), backs up a differing prior file to `.bak`, then atomically writes the
-  declaration (`converted`). It is purely additive — specs, `config.yaml`, and the
-  database are never touched — and it refuses to write while any conflict exists
-  (`addressed-id-without-spec`, `two-teams-one-project`, …). A registry name that
-  differs from the legacy team ID is `project-name-mismatch`: align that name
-  explicitly before conversion so fleet resolution preserves the spec-id prefix.
-  Exit codes: `0` for a
-  clean preview or `converted`/`unchanged`/`nothing-to-convert`; `2` when blocked
-  (the JSON payload still carries the full plan/result); `1` on error. Under
-  `--json` the payload is the raw `MigrationPlan` (preview) or `ConversionResult`
-  (apply). `rollback` is a service-level API (no CLI verb): restore the `.bak` a
-  previous apply created, remove a file that apply created when no `.bak` exists,
-  or report `nothing-to-roll-back`.
 
 ## Server lifecycle
 

package/plugins/sp/skills/spur-cli/references/self.md

@@ -77,7 +77,7 @@ spur self serve --json                # dry probe: print { port, url, pid, runni
 ```
 
 Starts the Hono/Cloudflare-Worker server that serves the web Task Kanban and exposes the team
-supervisor API (`/api/team/*`). It is the local fallback when no remote server is configured.
+supervisor API (`/api/processes/*` + `/api/agents/*`). It is the local fallback when no remote server is configured.
 Flags: `--port <n>`, `--host <addr>`, `--no-open`, `--cwd <path>`, `--json` (a dry probe — reports
 the resolved port/url without starting the server). Full flag semantics: **[serve.md](serve.md)**.
 
@@ -95,7 +95,7 @@ directory. Only flag is `--json`.
 
 ## What this skill is NOT
 
-- **Not the team supervisor.** `self serve` hosts the supervisor API; `spur agent start` / `stop` /
+- **Not the agent supervisor.** `self serve` hosts the supervisor API; `spur agent start` / `stop` /
   `agent list --specs` are the verbs that drive and inspect it (0848). See
   **[agent.md](agent.md)**.
 - **Not a production server.** This is the local fallback. Production deployment uses the Cloudflare

package/plugins/sp/skills/spur-cli/references/serve.md

@@ -1,6 +1,6 @@
 ---
 name: spur-cli-serve
-description: "spur-cli noun reference: operate `spur serve` as the local web-server fallback - start the Hono/Cloudflare-Worker server that backs the web Task Kanban and the team supervisor API. Single verb, five flags."
+description: "spur-cli noun reference: operate `spur serve` as the local web-server fallback - start the Hono/Cloudflare-Worker server that backs the web Task Kanban and the supervisor API. Single verb, five flags."
 see_also:
   - spur-cli
 ---
@@ -8,7 +8,7 @@ see_also:
 # spur serve - local web server
 
 `spur serve` starts the **Spur web server** - a local Hono / Cloudflare-Worker server that serves
-the web Task Kanban and exposes the team supervisor API (`/api/team/*`). It is the local fallback
+the web Task Kanban and exposes the supervisor API (`/api/processes/*` + `/api/agents/*`). It is the local fallback
 when no remote server is configured.
 
 ## Verb map
@@ -29,7 +29,7 @@ spur serve --json                   # dry probe: print { port, url, pid, running
 ```
 
 Starts the server with the Hono app backed by the local SQLite database. The web Task Kanban and
-the team supervisor API become available at `http://<host>:<port>`.
+the supervisor API become available at `http://<host>:<port>`.
 
 ### Flags
 
@@ -46,7 +46,7 @@ the team supervisor API become available at `http://<host>:<port>`.
 
 ## What this skill is NOT
 
-- **Not the team supervisor.** `spur serve` hosts the supervisor API; `spur agent start` / `stop` /
+- **Not the agent supervisor.** `spur serve` hosts the supervisor API; `spur agent start` / `stop` /
   `agent list --specs` are the verbs that drive and inspect it (0848). See
   **[agent.md](agent.md)**.
 - **Not a production server.** This is the local fallback. Production deployment uses the Cloudflare

package/plugins/sp/skills/spur-cli/references/tasks.md

@@ -40,7 +40,7 @@ re-reading or re-tokenizing the task.
 | ---- | ------- | --------- |
 | `create <title>` | Allocate a new task (race-safe WBS) | `--feature <id>` `--parent <wbs>` `--template <variant>` `--dedupe-within <s>` `--allow-duplicate-name` `--folder` `--json` |
 | `show <wbs>` | Print one task's frontmatter + body | `--folder` `--json` |
-| `update <wbs> [status]` | Lifecycle transition, section replace, **or** frontmatter set | `--section <name> --from-file <path>` `--assignee <spec-id>` (moved home of `spur team assign`; exclusive with `--section`) `--feature <id>` `--priority <p>` `--no-lifecycle` `--force-done` `--reason <text>` `--verdict-dir <path>` `--folder` `--json` |
+| `update <wbs> [status]` | Lifecycle transition, section replace, **or** frontmatter set | `--section <name> --from-file <path>` `--assignee <spec-id>` (exclusive with `--section`) `--feature <id>` `--priority <p>` `--no-lifecycle` `--force-done` `--reason <text>` `--verdict-dir <path>` `--folder` `--json` |
 | `deps <wbs> <op> [values...]` | Mutate `dependencies[]` frontmatter array (ops: `set`, `add`, `remove`, `clear`) | `--folder` `--json` |
 | `sections <wbs> <op> [name]` | Initialize, add, or list canonical task sections (ops: `init`, `add`, `list`) | `--folder` `--json` |
 | `list` | List tasks, filtered | `--status <s>` `--phase <p>` `--parent <wbs>` `--feature <id>` `--folder` `--json` |

package/plugins/sp/skills/spur-composer/SKILL.md

@@ -36,8 +36,8 @@ its own output and never runs a recurring loop — evaluation is the doctor's jo
   or flag catalog: [../spur-cli/SKILL.md](../spur-cli/SKILL.md).
 - **Recurring loops and coordination go to `sp:super-planner`** or a workflow — not here. This skill
   runs one bounded composition or tuning pass per invocation.
-- **Forbidden surfaces: `spur team` and `spur agent loop`.** Agent specs are reached only through
-  `spur agent create|edit|delete|list --specs`.
+- **Forbidden surface: `spur agent loop`** (supervisor-internal). Agent specs are read through
+  `spur agent list --specs`; they are declared in the fleet config, not authored by a CLI verb.
 - **Writes land only through `spur` verbs** and the ladder's gated file steps (§ below). The shared
   step additionally needs recorded operator consent plus `build:bundle` parity.
 
@@ -49,7 +49,7 @@ its own output and never runs a recurring loop — evaluation is the doctor's jo
 | feature | Apply accepted rows through `spur feature update --section --from-file`; keep acceptance criteria in Gherkin | [../spur-cli/references/features.md](../spur-cli/references/features.md) |
 | rule | The trace-driven tuning loop (§ Rule tuning loop) | [../spur-cli/references/rules.md](../spur-cli/references/rules.md) · [fine-tuning](../spur-cli/references/rules/fine-tuning.md) |
 | workflow | Catalog selection, the composition ladder, and the ADR-115 budgets (§ below) | [../spur-cli/references/workflows.md](../spur-cli/references/workflows.md) · [operations](../spur-cli/references/workflows/operations.md) |
-| agent spec | Compose and edit `.spur/agents/<id>.yaml` only through `spur agent create|edit|delete|list --specs` | [../spur-cli/references/agent.md](../spur-cli/references/agent.md) |
+| agent spec | Read through `spur agent list --specs`; specs are materialized from the fleet declaration at serve start | [../spur-cli/references/agent.md](../spur-cli/references/agent.md) |
 
 Do not drive the planning→execution lifecycle from here — that is `sp:spur-dev`.
 

package/plugins/sp/skills/spur-dev/references/ac-style-guide.md

@@ -127,6 +127,16 @@ unmatchable):
 | AC-0817-HERM-SKIP | MET | test | `tests/loader.test.ts:962` |        ← declared
 ```
 
+### A bullet's bold head is its id
+
+`verify-answer-lint` declares the bold span of a single-line criterion bullet
+(`- **AC2 — The roster runtime is gone (R3).** Given …, when …, then …`) and its head before the
+first ` — ` or `:` — so answer rows may key `AC2` or `AC2 — The roster runtime is gone (R3).`. Keep
+at least one answer row keyed to the verbatim feature scenario title the task graduates, and keep
+requirement ids in the corpus form they are checked against (`- **R1** — …`): `L3.requirements-format`
+matches `R\d+` followed by a space, so a colon after the bold span silently drops the whole section
+to a warning.
+
 ### The id is exactly the scenario title — no Gherkin body appended
 
 An AC row id must be **exactly** the scenario title (plus any of the four forms above), with the

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

@@ -885,7 +885,7 @@ command doc so it does not read as a bug.
 ## Still out of scope
 
 - **Interactive within-step Q&A** — a headless subprocess `agent.run` agent asking the operator a
-  real question. This waits for the workspace module + inbox module + `spur agent` team mode.
+  real question. This waits for the workspace module + inbox module + the agent fleet.
   `sp:super-planner` surfaces blockers/HITL only at the **batch boundary** (between task runs), not
   from inside a pipeline step.
 

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

@@ -327,12 +327,10 @@ task.** A `cheap`/`standard`-tier model handed a task that big does not fail fas
 entire `implementTimeoutMs` and exits 3 with a partial tree (run `ca130182` — 7 reqs / 9 plan
 items / 12+ files → 30 minutes, 6 of 12 files, no tests, no docs, no `## Solution`).
 
-The precheck size gate enforces this: it resolves `$implementAgent`'s capability tier
-(`spur agent doctor <exec> --json` → `capabilityTier`) and writes FAIL for a large task on an
-executor below the `reviewer` role's floor, naming the executor and its tier. An unknown or
-undeclared tier reads as the `coder` floor, so the block is the default. Clear it deliberately —
-`--agent <capable>` / `--vars '{"implementAgent":"<capable>"}'`, or split — never by raising
-`maxImplementReqs`: the caps accept a big task, they do not make a flash model able to finish one.
+The precheck size gate is count-only: it writes FAIL above 10 requirements or 16 Plan items and
+never consults the executor's capability tier. Clear a FAIL deliberately — split the task, or raise
+the cap with `--vars '{"maxImplementReqs":<n>}'` — but the caps only accept a big task, they do not
+make a flash model able to finish one.
 
 The empty-implement guard (`requireDiff` on the task-pipeline `implement` step, R3) fails the
 run fast when an implement exits 0 with zero non-corpus changes — a no-op never drifts into

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

@@ -55,7 +55,7 @@ Avoid: *result* (too generic — a verdict has a fixed three-value contract), *r
 for narrative output like the dogfood report or batch report).
 
 **noun/verb** — the two-part CLI grammar: a noun names the domain object (`task`, `feature`,
-`rule`, `workflow`, `agent`, `message`, `team`), a verb names the operation on it (`create`,
+`rule`, `workflow`, `agent`, `message`), a verb names the operation on it (`create`,
 `update`, `check`, `run`, `list`). The `sp:spur-cli` facade organizes its references one file
 per noun.
 Avoid: *command* alone (ambiguous with a `/sp:dev-*` slash command, which is a different

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

@@ -206,7 +206,12 @@ Action semantics come from the YAML and the workflow action contract:
   state mutates the task, the host validates the same refusal conditions inline — the declared
   artifact exists at the resolved path and is canonical-valid for the run's wbs (for
   `verify-verdict`: verdict `PASS`), `proofBinding: current` is honored against a freshly captured
-  proof digest, and the run-scoped review-completion marker exists — then appends one provenance
+  proof digest — capture it with `bun "$SETUP_SCRIPT" --fingerprint --task-file <task path>
+  [--feature-file <feature path>]`, the same entry point used at Run setup, which prints the engine
+  `sha256:<hex>` digest. Run it from the worktree root (cwd feeds the git-tree half of the digest)
+  and pass the same `--feature-file` the run folded in — omitting it, or running from elsewhere,
+  yields a different digest and the mismatch surfaces later as a refused `run.artifact`
+  registration — and the run-scoped review-completion marker exists — then appends one provenance
   line to `.spur/run/<run-id>.log` naming the equivalence (artifact kind, path, verdict, digest) and
   proceeds to `spur task record`. A failed validation stops at the state and follows the failure
   contract; the step is never silently skipped. Artifact-provenance consumers read that run-log
@@ -267,6 +272,11 @@ boundary, and a delegate left to re-derive them re-derives them against its own
 Nothing else: no task/session transcripts, no machine-specific session paths. The WBS/path already
 carried by the slash command remains the task handoff.
 
+**Delegate hygiene.** A dispatched stage cleans up after itself: temporary artifacts stay inside the
+execution tree, and an ad-hoc git worktree created for a comparison is removed before the stage
+reports. The G65 batch's implement dispatches left an 867 MB worktree plus a trail of `/tmp` scratch
+files that outlived the run (2026-09-15).
+
 **Verify-stage artifact contract.** A verify handoff names
 [`code-verification/references/verdict-schema.md`](../../code-verification/references/verdict-schema.md)
 as the canonical answer schema and carries this compact form verbatim:

package/plugins/sp/skills/spur-doctor/SKILL.md

@@ -42,7 +42,7 @@ record saves the returned table under `docs/reports/`; the doctor creates no art
   of scope and are never re-interpreted here; history-anatomy is the only history interpreter.
 - **Recurring reflection loops and coordination go to `sp:super-planner`** or a workflow — one
   bounded evaluation pass per invocation.
-- **Forbidden surfaces: `spur team` and `spur agent loop`.** Agent specs are read only through
+- **Forbidden surface: `spur agent loop`** (supervisor-internal). Agent specs are read only through
   `spur agent list --specs --json`.
 
 ## Evidence per noun
@@ -53,7 +53,7 @@ record saves the returned table under `docs/reports/`; the doctor creates no art
 | feature | `spur feature check <id> --json` |
 | rule | `spur rule trace --json`, `spur rule validate` |
 | workflow | `spur workflow validate --json` (findings by `level`), `node "$(superskill script path sp workflow-step-profile.mjs)" <workflow> --json` |
-| agent spec | `spur agent list --specs --json`, read and written through `spur agent` with `--specs`, never `spur team` |
+| agent spec | `spur agent list --specs --json` |
 | history | A `sp:history-anatomy` report ([../history-anatomy/SKILL.md](../history-anatomy/SKILL.md)), never raw history records |
 
 Every row of a proposal cites the evidence it rests on. No anchor, no proposal.