@gobing-ai/spur 0.3.47 → 0.3.49

package/plugins/sp/commands/dev-dogfood.md

@@ -1,5 +1,6 @@
 ---
 description: Dogfood an agent skill/command/CLI — drive it end-to-end with bounded auto-fix, self-monitor, and emit a comprehensive report
+role: reviewer
 argument-hint: "<testee> [--agent <inline|auto|name>] [--max-retry <n>] [--save] [--task] [--chain-follow] [--full]"
 allowed-tools: ["Bash", "Read", "Write", "Edit", "Grep", "Glob", "Skill"]
 ---
@@ -13,7 +14,7 @@ Wraps the **sp:dogfood-testing** skill.
 | Flag | Description | Default |
 | --- | --- | --- |
 | `<testee>` | Skill / command / CLI to exercise end-to-end. | required |
-| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing dogfood work. | inline |
+| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing dogfood work. | omit |
 | `--max-retry` `<n>` | Max auto-fix retries per stage. | 3 |
 | `--save` | Compatibility no-op; saving is now default. Retained until evidenced retirement. | off |
 | `--task` | Record outcomes against a task. | omitted |

package/plugins/sp/commands/{dev-featurechange.md → dev-feature-change.md}

@@ -1,13 +1,11 @@
 ---
-description: >-
-  Restructure the feature tree from a mapping file — dry-run then apply via
-  spur feature move / task feature_id edges / root docs/*.md reference rewrites
-  (CLI-gated; no raw Write on docs/features or docs/tasks)
+description: "Restructure the feature tree from a mapping file — dry-run then apply via spur feature move / task feature_id edges / root docs/*.md reference rewrites (CLI-gated; no raw Write on docs/features or docs/tasks). Triggers: feature restructure, feature tree move, reparent features, apply mapping file"
+role: planner
 argument-hint: "[--map <path>] [--dry-run] [--apply] [--limit <old-id>] [--wave <1|2|3|all>] [--yes]"
 allowed-tools: ["Bash", "Read", "AskUserQuestion", "Skill"]
 ---
 
-# Dev Featurechange
+# Dev Feature Change
 
 CLI-gated feature-tree restructure orchestrator. Executes dispositions from a mapping file; does not invent hierarchy.
 
@@ -27,7 +25,7 @@ For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag
 ## Usage
 
 ```
-/sp:dev-featurechange [--map <path>] [--dry-run] [--apply] [--limit <old-id>] [--wave <1|2|3|all>] [--yes]
+/sp:dev-feature-change [--map <path>] [--dry-run] [--apply] [--limit <old-id>] [--wave <1|2|3|all>] [--yes]
 ```
 
 ## Implementation
@@ -42,7 +40,7 @@ For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag
 
 - Read `--map`. Collect rows where disposition is not `keep` (typically `reparent-under:<parent>`).
 - Filter by `--limit` / `--wave` if set.
-- Wave defaults from map: **1** = K→J, L→J · **2** = N→H, O→H · **3** = P→D, Q→F, R→F8.
+- Wave membership comes from the map itself (its wave column/section is the SSOT). Never hard-code letter sets here — the tree moves under the command and literals go stale.
 
 **Free-digit preflight (mandatory before dry-run report)**
 
@@ -52,7 +50,7 @@ Group selected reparent rows by `new_parent`. For each parent:
 spur feature list --json
 ```
 
-Count current children (ids where `id` starts with parent and length = parent.length+1, digit 1–9).  
+Count current children (ids where `id` starts with parent and length = parent.length+1, digit 1–9).
 `free = 9 - childCount`. If `rowsUnderParent.length > free`, **abort the plan** with a clear error naming the parent, free slots, and competing old_ids. Do not apply a partial wave.
 
 **Dry-run plan (always) — sequential prediction**
@@ -101,10 +99,10 @@ spur feature refresh --json
 spur feature check --json
 ```
 
-Task edges: `feature move` rewrites `feature_id` across **all** configured task folders (via `foldersConfig`). Safety check:
+Task edges: `feature move` rewrites `feature_id` across **all** configured task folders (via `foldersConfig`). Safety check (the glob covers every tasks folder, present and future):
 
 ```bash
-rg -n '^feature_id: <old_id>$' docs/tasks docs/tasks2 docs/tasks3
+rg -n '^feature_id: <old_id>$' docs/tasks*/
 ```
 
 If any stale edges remain, fix with:

package/plugins/sp/commands/dev-find-conflict.md

@@ -1,5 +1,6 @@
 ---
 description: "Authority-aware semantic audit across source, task files, feature files, and project authority files — discover conflicts, resolve claim-specific authority, collect reproducible evidence, and route confirmed repairs through owner surfaces. Triggers: find conflict, conflict audit, semantic conflict, authority mismatch, stale projection."
+role: reviewer
 argument-hint: "[<scope>] [--pillar <source|tasks|features|authority|all>] [--mode <adaptive|full>] [--resolve] [--agent <inline|auto|name>] [--json]"
 allowed-tools: ["Bash", "Read", "Write", "Grep", "Glob", "Skill"]
 ---
@@ -18,7 +19,7 @@ owner-routed remediation.
 | `--pillar` `<source\|tasks\|features\|authority\|all>` | Limit the internal audit to one pillar; the minimum authorities needed to judge it still load.                                           | all             |
 | `--mode` `<adaptive\|full>`                            | Scan protocol — adaptive reuses fresh indexed context and discloses skipped areas; full forces a cold comprehensive scan.                | adaptive        |
 | `--resolve`                                            | Enable the proposal, confirmation, and owner-routed remediation workflow. Its absence guarantees no source/corpus/numbered-doc mutation. | off             |
-| `--agent` `<inline\|auto\|name>`                       | Who runs the model-bearing analysis.                                                                                                     | inline          |
+| `--agent` `<inline\|auto\|name>`                       | Who runs the model-bearing analysis.                                                                                                     | omit           |
 | `--json`                                               | Emit the same result envelope as Markdown as JSON.                                                                                       | off             |
 
 For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag-glossary.md).

package/plugins/sp/commands/dev-find-issue.md

@@ -1,36 +1,37 @@
 ---
-description: "Review agent session logs, identify performance bottlenecks and behavioral anti-patterns, and generate a structured task file with proposed fixes. Triggers: post-mortem, performance analysis, session review, find issues, identify bottlenecks"
-argument-hint: "[<topic>] [--sessions <glob>] [--source <auto|omp|claude|codex|gemini|opencode|antigravity|openclaw|pi>] [--feature <id>] [--template <meta|issue|standard>] [--priority <P0|P1|P2|P3>] [--severity <S0|S1|S2>] [--category <list>] [--since <iso>] [--until <iso>] [--top <n>] [--min-cost <duration>] [--strict-topic] [--use-history] [--no-task] [--agent <inline|auto|name>] [--json]"
+description: "Render the session-forensics report from imported history data (8 CLI-derivable sections plus 6 model-authored), identify bottlenecks and behavioral anti-patterns, and optionally create a structured fix task behind --create-task. Triggers: post-mortem, performance analysis, session review, find issues, identify bottlenecks"
+role: reviewer
+argument-hint: "[<topic>] [--sessions <glob>] [--source <auto|pi|claude|codex|gemini|opencode|antigravity|openclaw|omp|grok|agy|all>] [--feature <id>] [--template <meta|issue|standard>] [--priority <P0|P1|P2|P3>] [--severity <S0|S1|S2>] [--category <list>] [--since <iso>] [--until <iso>] [--top <n>] [--min-cost <duration>] [--strict-topic] [--create-task] [--agent <inline|auto|name>] [--json]"
 allowed-tools: ["Bash", "Read", "Write", "Grep", "Glob", "Skill"]
 ---
 
 # Dev Find Issue
 
-Wraps the **sp:issue-finding** skill — forensic session log analysis that identifies performance
-bottlenecks, ranks root causes by time cost, proposes targeted fixes, and generates a structured
+Wraps the **sp:issue-finding** skill — report-first session forensics over the history data plane.
+The CLI renders the 8 derivable report sections (`spur history report --mode forensics`); the skill
+identifies bottlenecks, proposes fixes, and — only with `--create-task` — generates a structured
 task file via `spur task create`.
 
 ## Argument Flags
 
-| Flag                                                                                 | Description                          | Default    |
-| ------------------------------------------------------------------------------------ | ------------------------------------ | ---------- |
-| `[<topic>]`                                                                          | Narrow the analysis to a topic.      | omitted    |
-| `--sessions` `<glob>`                                                                | Session log glob to scan.            | recent     |
-| `--source` `<auto\|omp\|claude\|codex\|gemini\|opencode\|antigravity\|openclaw\|pi>` | Agent source to scan.                | auto       |
-| `--feature` `<id>`                                                                   | Attach findings to a feature.        | omitted    |
-| `--template` `<meta\|issue\|standard>`                                               | Output template shape.               | standard   |
-| `--priority` `<P0\|P1\|P2\|P3>`                                                      | Filter / assign priority.            | omitted    |
-| `--severity` `<S0\|S1\|S2>`                                                          | Filter / assign severity.            | omitted    |
-| `--category` `<list>`                                                                | Comma list of categories to keep.    | all        |
-| `--since` `<iso>`                                                                    | Start of the scan window.            | configured |
-| `--until` `<iso>`                                                                    | End of the scan window.              | now        |
-| `--top` `<n>`                                                                        | Limit to top N findings.             | omitted    |
-| `--min-cost` `<duration>`                                                            | Minimum wasted duration to report.   | omitted    |
-| `--strict-topic`                                                                     | Drop findings off-topic.             | off        |
-| `--use-history`                                                                      | Incorporate indexed history.         | off        |
-| `--no-task`                                                                          | Do not create a task for findings.   | off        |
-| `--agent` `<inline\|auto\|name>`                                                     | Who runs the model-bearing analysis. | inline     |
-| `--json`                                                                             | Emit structured JSON.                | off        |
+| Flag                                                                                                 | Description                                                                                                                   | Default    |
+| ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| `[<topic>]`                                                                                          | Narrow the analysis to a topic.                                                                                               | omitted    |
+| `--sessions` `<glob>`                                                                                | Session log glob (fallback input).                                                                                            | recent     |
+| `--source` `<auto\|pi\|claude\|codex\|gemini\|opencode\|antigravity\|openclaw\|omp\|grok\|agy\|all>` | Agent source to scan (CLI vocabulary; `all` fans out, `auto` resolves at runtime).                                            | auto       |
+| `--feature` `<id>`                                                                                   | Attach the generated task to a feature.                                                                                       | omitted    |
+| `--template` `<meta\|issue\|standard>`                                                               | Task template shape (`--create-task` only); `issue` is the explicit single-finding override, `standard` the generic override. | meta       |
+| `--priority` `<P0\|P1\|P2\|P3>`                                                                      | Filter / assign task priority.                                                                                                | P2         |
+| `--severity` `<S0\|S1\|S2>`                                                                          | Filter / assign severity.                                                                                                     | all        |
+| `--category` `<list>`                                                                                | Comma list of categories to keep.                                                                                             | all        |
+| `--since` `<iso>`                                                                                    | Start of the scan window.                                                                                                     | configured |
+| `--until` `<iso>`                                                                                    | End of the scan window.                                                                                                       | now        |
+| `--top` `<n>`                                                                                        | Limit to top N findings.                                                                                                      | omitted    |
+| `--min-cost` `<duration>`                                                                            | Minimum wasted duration to report.                                                                                            | omitted    |
+| `--strict-topic`                                                                                     | Drop findings off-topic.                                                                                                      | off        |
+| `--create-task`                                                                                      | Generate a fix task for findings.                                                                                             | off        |
+| `--agent` `<inline\|auto\|name>`                                                                     | Who runs the model-bearing analysis.                                                                                          | omit       |
+| `--json`                                                                                             | Emit structured JSON.                                                                                                         | off        |
 
 For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag-glossary.md).
 
@@ -41,28 +42,20 @@ For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag
 /sp:dev-find-issue "test-loop spinning"
 /sp:dev-find-issue --sessions "~/.omp/agent/sessions/-xprojects-spur-new/2026-07-29T*"
 /sp:dev-find-issue "L3 guard format discovery" --feature H51 --priority P1 --severity S1
-/sp:dev-find-issue --category test-loop,guard --min-cost 30m --no-task
-/sp:dev-find-issue --source claude --since 2026-07-28 --json
-/sp:dev-find-issue --sessions plugins/sp/skills/issue-finding/examples/session-test-loop.jsonl --no-task
+/sp:dev-find-issue --category test-loop,guard --min-cost 30m
+/sp:dev-find-issue --source claude --since 2026-07-28 --create-task --json
 ```
 
-| Argument                      | Description                                                                              | Default                         |
-| ----------------------------- | ---------------------------------------------------------------------------------------- | ------------------------------- |
-| `[topic]`                     | Optional focus text or smart positional (path/glob → sessions; category phrase → filter) | (full taxonomy)                 |
-| `--sessions <glob>`           | Session JSONL file(s) or directory                                                       | most recent for resolved source |
-| `--source <name>`             | `auto`, `omp`, `claude`, `codex`, `gemini`, `opencode`, `antigravity`, `openclaw`, `pi`  | `auto`                          |
-| `--feature <id>`              | Feature ID to link the generated task to                                                 | (none)                          |
-| `--template <name>`           | `meta` (umbrella), `issue` (single), or `standard`                                       | `meta`                          |
-| `--priority <P0\|P1\|P2\|P3>` | Task frontmatter priority (not bottleneck severity)                                      | `P2`                            |
-| `--severity <S0\|S1\|S2>`     | Minimum bottleneck severity to keep                                                      | (all)                           |
-| `--category <list>`           | Comma-separated category ids (`test-loop`, `guard`, …)                                   | `all`                           |
-| `--since` / `--until`         | Session start time bounds                                                                | (none)                          |
-| `--top <n>`                   | Cap number of fixes/requirements                                                         | (no cap)                        |
-| `--min-cost <duration>`       | Drop findings under this waste floor (`30m`, `2h`)                                       | (none)                          |
-| `--strict-topic`              | Drop off-topic findings even if severe                                                   | off                             |
-| `--use-history`               | Optional `spur history` import/analyze for cost aggregates                               | off                             |
-| `--no-task`                   | Markdown report only                                                                     | off                             |
-| `--json`                      | JSON findings only (no task)                                                             | off                             |
+**Report-first (task 0556).** Default output is the markdown report to stdout; no task file is
+written. Task creation moved behind `--create-task`. `--use-history` and `--no-task` are removed:
+the history data plane is now the primary source (no flag needed), and the old report-only behavior
+is the new default. Raw JSONL remains a fallback under the three conditions documented in
+`sp:issue-finding`.
+
+**Data-plane preflight.** Forensics read the imported history plane as-is. If findings come back
+empty or stale, run `/sp:dev-history-load` (on-demand cumulative `spur history import` + analyze,
+checkpoint resume — task 0567) before re-running forensics; it owns the interactive preflight, while
+`spur history daily` owns the periodic cadence.
 
 **See also:** skill `sp:issue-finding` (SSOT), `/sp:dev-runall`, `/sp:dev-dogfood`,
 `sp:daily-summary`, `sp:reverse-engineering`.

package/plugins/sp/commands/dev-find-next.md

@@ -1,5 +1,6 @@
 ---
-description: "Prompt-first feature frontier prioritizer — answers 'which feature should we work on now?' with a ranked, evidence-carrying frontier, and emits rank-distorting tree defects as proposals /sp:dev-featurechange consumes. Triggers: find next, which feature, feature ranking, frontier priority, what should I work on."
+description: "Prompt-first feature frontier prioritizer — answers 'which feature should we work on now?' with a ranked, evidence-carrying frontier, and emits rank-distorting tree defects as proposals /sp:dev-feature-change consumes. Triggers: find next, which feature, feature ranking, frontier priority, what should I work on."
+role: planner
 argument-hint: "[--task [<feature-id>]] [--agent <inline|auto|name>] [--auto] [--json]"
 allowed-tools: ["Bash", "Read", "Write", "Grep", "Glob", "Skill"]
 ---
@@ -12,14 +13,14 @@ instead of ranking them, and emits tree structure defects as proposals only.
 
 Answers *"which X"* — the question `/sp:dev-next` deliberately does not (next-router routing-table
 §0 step 1c). Advancing a chosen target remains `/sp:dev-next`'s job; applying tree changes remains
-`/sp:dev-featurechange`'s job.
+`/sp:dev-feature-change`'s job.
 
 ## Argument Flags
 
 | Flag | Description | Default |
 | --- | --- | --- |
 | `--task` `[<feature-id>]` | After the report, confirm one target and dispatch the planning half to produce implement-ready tasks. | omitted |
-| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing analysis. | inline |
+| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing analysis. | omit |
 | `--auto` | Skip the `--task` confirm (accept the offered target) and forward into dispatched children. | off |
 | `--json` | Emit the ranked frontier, gated list, and proposals as a JSON envelope. | off |
 
@@ -54,7 +55,7 @@ Without `--task` the command is read-only with respect to the corpus and docs. U
 only mutation is the one the dispatched commands perform on `docs/tasks*/` after confirm (or
 auto-accept) — the command still performs no `spur feature move`, no sync apply, and no write under
 `docs/features/**`. Defect proposals conform to the `docs/plans/feature-tree-restructure-map.md`
-schema and are applied only through `/sp:dev-featurechange` (dry-run → confirm → apply).
+schema and are applied only through `/sp:dev-feature-change` (dry-run → confirm → apply).
 
 **See also:** skill `sp:next-feature` (SSOT), `sp:next-router` (`/sp:dev-next`),
 `sp:conflict-finding` (the prompt-first template), `sp:spur-cli`.

package/plugins/sp/commands/dev-fixall.md

@@ -1,5 +1,6 @@
 ---
 description: Fix all lint, type, and test errors systematically across the working tree
+role: coder
 argument-hint: "[<validation-command>] [--max-retry <n>] [--scope <path>] [--gate-log <path>] [--findings <anchors>]"
 allowed-tools: ["Bash", "Read", "Write", "Edit", "Grep", "Glob"]
 ---

package/plugins/sp/commands/dev-gitmsg.md

@@ -1,5 +1,6 @@
 ---
 description: Generate conventional commit message(s) from staged changes via per-file summarization, optionally commit
+role: scribe
 argument-hint: "[--commit] [--squash] [--scope <path>]"
 allowed-tools: ["Bash", "Read"]
 ---

package/plugins/sp/commands/dev-gtd.md

@@ -1,14 +1,15 @@
 ---
-description: Get things done — quality gate → fix → act CI simulation → commit → push → gh verify in one flow
-argument-hint: "[<quality-gate-command>] [--dry-run] [--skip-act] [--no-push] [--no-verify] [--scope <path>] [--max-retry <n>]"
+description: Get things done — quality gate → fix → commit → push → gh verify in one flow (optional act CI simulation via --act)
+role: coder
+argument-hint: "[<quality-gate-command>] [--dry-run] [--act] [--no-push] [--no-verify] [--scope <path>] [--max-retry <n>]"
 allowed-tools: ["Bash", "Read", "Write", "Edit", "Grep", "Glob"]
 ---
 
 # Dev GTD
 
 Self-contained end-to-end delivery command: local quality gate (auto-fix via `/sp:dev-fixall`),
-local CI/CD simulation via `act`, conventional commit message generation, commit, push, and
-GitHub push-success verification via `gh`. Designed to stand alone (no backing skill); once mature
+optional local CI/CD simulation via `act` (`--act` only), conventional commit message generation,
+commit, push, and GitHub push-success verification via `gh`. Designed to stand alone (no backing skill); once mature
 it supersedes `/sp:dev-gitmsg` and is absorbed into the shared command structure.
 
 ## Argument Flags
@@ -17,7 +18,7 @@ it supersedes `/sp:dev-gitmsg` and is absorbed into the shared command structure
 | --- | --- | --- |
 | `<quality-gate-command>` | Local quality gate to run first; on failure, invoke `/sp:dev-fixall "<cmd>"` to fix all issues automatically. | `bun run check` |
 | `--dry-run` | Generate the git message and plan only — no commit, push, or gh verify. | off |
-| `--skip-act` | Skip the local `act` CI/CD simulation step. | off |
+| `--act` | Run local `act` CI/CD simulation before commit (heavy: launches Docker). Default off — stage 6 `gh` verify covers real CI post-push. Reach for it on workflow edits, dependency bumps, infra changes. Independent of `--dry-run`: `--dry-run --act` still runs the simulation. | off |
 | `--no-push` | Commit but do not git push or gh-verify. | off |
 | `--no-verify` | Push but skip the `gh` push-success verification. | off |
 | `--scope <path>` | Scope the commit-message diff analysis to a path. | all staged changes |
@@ -27,7 +28,7 @@ For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag
 
 ## Usage
 
-/sp:dev-gtd [<quality-gate-command>] [--dry-run] [--skip-act] [--no-push] [--no-verify] [--scope <path>] [--max-retry <n>]
+/sp:dev-gtd [<quality-gate-command>] [--dry-run] [--act] [--no-push] [--no-verify] [--scope <path>] [--max-retry <n>]
 
 ## Implementation
 
@@ -40,8 +41,9 @@ default `bun run check`. Run it. If it exits non-zero, invoke `/sp:dev-fixall "<
 re-run the gate. Loop until the gate is clean or `--max-retry` is exhausted. Report what was fixed
 per file.
 
-**2 — Local CI/CD simulation via `act`.** Confirm Docker is running (`docker info`). On macOS the
-repo uses OrbStack — if the default context is not ready, use
+**2 — Local CI/CD simulation via `act` (opt-in).** Skip this stage entirely unless `--act` is
+given. When `--act` is given: confirm Docker is running (`docker info`). On macOS the repo uses
+OrbStack — if the default context is not ready, use
 `DOCKER_HOST=unix://$HOME/.orbstack/run/docker.sock`. Run
 `act -W .github/workflows/ci.yml -j verify` (or the repo's `bun run verify-gha-ci`); prefer
 `--container-architecture` matching your host when the runner pulls a foreign platform. If a step
@@ -56,10 +58,8 @@ If the build failure includes `TS2307: Cannot find module` on a workspace packag
 resolve Bun workspace packages because Bun does not create `node_modules/@scope/` symlinks.
 The real GitHub CI runner passes. **Do not** modify the build infrastructure to work around this
 `act`-specific issue. Instead, emit a clear message:
-`⚠ act CI simulation failed on workspace resolution — this is a container-environment artifact. Re-run with --skip-act to skip this step.`
-Then stop the run (this stage failed). The operator can use `--skip-act` to proceed.
-
-Skip this stage entirely when `--skip-act` is given.
+`⚠ act CI simulation failed on workspace resolution — this is a container-environment artifact. Re-run without --act to skip this step (it is opt-in).`
+Then stop the run (this stage failed). The operator can proceed by re-running without `--act`.
 
 **3 — Generate a conventional commit message.** Follow the gitmsg procedure (the same one
 `/sp:dev-gitmsg` runs). Run `git diff --cached --stat` (add `-- <path>` when `--scope` is given) for

package/plugins/sp/commands/dev-handover.md

@@ -1,5 +1,6 @@
 ---
 description: Generate a structured handover document when blocked — captures goal, progress, blocker, rejected approaches, and next steps
+role: scribe
 argument-hint: "\"<blocker description>\""
 allowed-tools: ["Bash", "Read", "Write"]
 ---

package/plugins/sp/commands/dev-history-load.md

@@ -0,0 +1,63 @@
+---
+description: "On-demand cumulative history load + narrowed analyze: run spur history import (checkpoint-resume, additive) then spur history analyze, optionally narrowed to a session/task/window, with optional forensics render. Triggers: load history, import agent conversations, analyze my history, history for this conversation"
+role: scribe
+argument-hint: "[--source <name>] [--session <id>] [--task <wbs>] [--since <iso>] [--until <iso>] [--report] [--dry-run] [--json]"
+allowed-tools: ["Bash", "Read"]
+---
+
+# Dev History Load
+
+Runs the on-demand history load+analyze sequence: `spur history import` (all sources, checkpoint
+resume — additive and self-healing) then `spur history analyze`, with narrowing flags routed to the
+verb that accepts them. Wraps the shipped CLI sequence in one discoverable surface; owns no import
+logic, no state, and no cadence.
+
+## Argument Flags
+
+| Flag                 | Description                                                    | Default  |
+| -------------------- | -------------------------------------------------------------- | -------- |
+| `--source` `<name>`  | Agent source to import and analyze (both verbs).               | all      |
+| `--session` `<id>`   | Narrow the analyze to a single session id.                     | omitted  |
+| `--task` `<wbs>`     | Narrow the analyze to a single task WBS.                       | omitted  |
+| `--since` `<iso>`    | Inclusive lower bound on the analyze window.                   | omitted  |
+| `--until` `<iso>`    | Inclusive upper bound on the analyze window.                   | omitted  |
+| `--report`           | Render `spur history report --mode forensics` after analyze.   | off      |
+| `--dry-run`          | Preview the sequence; import scans without persisting.         | off      |
+| `--json`             | Emit one JSON result object; no banner text interleaved.       | off      |
+
+For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag-glossary.md).
+
+## Usage
+
+```
+/sp:dev-history-load
+/sp:dev-history-load --source omp --session <session-id>
+/sp:dev-history-load --task <wbs> --since 2026-08-01 --until 2026-08-15
+/sp:dev-history-load --report
+/sp:dev-history-load --dry-run
+/sp:dev-history-load --json
+```
+
+**Cumulative by checkpoint, not by this command.** Re-running imports only newly appended
+conversation data — the shipped import checkpoint resume (task 0470 R6) makes repeat runs additive
+and never double-counts. This command never prunes reports and never re-implements the daily
+pipeline; for the periodic cadence (import-all → analyze → artifact → 90-day prune, self-healing),
+run `spur history daily` instead.
+
+**Degraded sources proceed with a warning; fully-failed imports abort (0569).** `spur history
+import` distinguishes fatal from degraded fan-outs by exit code: **exit 1** (every source
+failed) aborts the sequence before analyze and propagates the exit code; **exit 2** (mixed —
+at least one source imported, some skipped malformed rows) proceeds to analyze with a loud
+per-source warning: stderr names each degraded source with its parse/validation error counts
+(human mode), and the `--json` payload carries a `warnings` array with the source, counts, and
+the import step's warning detail. A steady-state degraded source therefore no longer blocks a
+bare run; to scope around one deliberately, use `--source <name>` per source.
+
+## Implementation
+
+Run the load-then-analyze sequence per `plugins/sp/scripts/history-load.ts` — import first, analyze
+only after import exits 0, narrowing forwarded to `analyze` only:
+
+```
+bun plugins/sp/scripts/history-load.ts $ARGUMENTS
+```

package/plugins/sp/commands/dev-idea.md

@@ -1,5 +1,6 @@
 ---
 description: Turn a vague idea into a feature with AC and a decomposed task batch — discovery, idea-eval, feature-create, AC, feature-check, system-design, decompose, batch-create (Design by default), handoff
+role: planner
 argument-hint: "\"<idea>\" [--auto] [--skip-design] [--approve-taste]"
 allowed-tools: ["Bash", "Read", "AskUserQuestion"]
 ---

package/plugins/sp/commands/dev-next.md

@@ -1,5 +1,6 @@
 ---
 description: Status-aware router — pick and run the next best /sp:dev-* step for a task or feature frontier
+role: planner
 argument-hint: "[<wbs|feature-id>] [--dry-run] [--once] [--auto] [--agent <inline|auto|name>] [--full]"
 allowed-tools: ["Bash", "Read", "Skill", "AskUserQuestion"]
 ---
@@ -16,7 +17,7 @@ Wraps the **sp:next-router** skill.
 | `--dry-run` | Resolve and print the next step without executing. | off |
 | `--once` | Resolve exactly one step and stop. | off |
 | `--auto` | Skip objective HITL gates in the dispatched step. | off |
-| `--agent` `<inline\|auto\|name>` | Who runs the dispatched model-bearing step. | inline |
+| `--agent` `<inline\|auto\|name>` | Who runs the dispatched model-bearing step. | omit |
 | `--full` | When the primary route is `dev-run … --next`, substitute `dev-run <wbs> --mode full` (no `--next`). No effect on other routes (warning W-FULL). | off |
 
 For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag-glossary.md).

package/plugins/sp/commands/dev-parallel.md

@@ -1,5 +1,6 @@
 ---
 description: Fan out independent tasks or investigations in parallel via subagents — choose the right pattern and synthesize results
+role: planner
 argument-hint: "--tasks <selector> [--feature <id>] [--mode <fan-out|review-panel|investigation>] [--agent <inline|auto|name>] [--json]"
 allowed-tools: ["Bash", "Read", "Skill"]
 ---
@@ -15,7 +16,7 @@ Wraps the **sp:parallel-execution** skill.
 | `--tasks` `<selector>` | Task selector to fan out. | required |
 | `--feature` `<id>` | Restrict the selector to a feature. | omitted |
 | `--mode` `<fan-out\|review-panel\|investigation>` | Fan-out pattern. | fan-out |
-| `--agent` `<inline\|auto\|name>` | Who runs each dispatched slice. | inline |
+| `--agent` `<inline\|auto\|name>` | Who runs each dispatched slice. Parallel fan-out is dispatch, so explicit `--agent inline` runs the batch **sequentially in the host session** with a printed notice (zero dispatch); omit keeps the default fan-out semantics; `auto` tier-resolves an executor; a name pins that executor. | omit |
 | `--json` | Emit structured JSON. | off |
 
 For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag-glossary.md).

package/plugins/sp/commands/dev-plan.md

@@ -1,5 +1,6 @@
 ---
 description: Plan a feature from a description — intake → feature create → AC generation → feature check gate → decomposition → batch-create (Design by default)
+role: planner
 argument-hint: "\"<description>\" [--feature <id>] [--parent <feature-id>] [--agent <inline|auto|name>] [--skip-design] [--auto] [--approve-taste]"
 allowed-tools: ["Bash", "Read", "Skill", "AskUserQuestion"]
 ---
@@ -15,7 +16,7 @@ Wraps the **sp:spur-dev** skill.
 | `"<description>"` | Feature description to plan. | required |
 | `--feature` `<id>` | Attach to an existing feature. | omitted |
 | `--parent` `<feature-id>` | Create under a parent feature. | omitted |
-| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing planning. The planning pipeline's `agent.run` stages always dispatch a subprocess; `inline` is accepted there as a synonym for omit, resolving to `agent.default` (ADR-047). `auto` tier-resolves an executor; a name pins that executor. | agent.default |
+| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing planning. The planning pipeline's `agent.run` stages are headless — they always dispatch a subprocess. Explicit `--agent inline` is rejected there with the stable special error (exit 2): a headless surface cannot host a session — no dispatch, no `agent.default` fallback. Use `omit` (resolves to `agent.default`), `auto` (tier-resolves an executor), or a name (pins that executor). | agent.default |
 | `--skip-design` | Omit the system-design hop. | off |
 | `--auto` | Skip objective HITL gates. | off |
 | `--approve-taste` | With --auto: skip design-approval pause. | off |

package/plugins/sp/commands/dev-pr-review.md

@@ -0,0 +1,39 @@
+---
+description: "Review GitHub PRs with Codex; collect and fix findings."
+role: reviewer
+argument-hint: "[full|submit|collect|fix|rerun|status|rules] [--base <branch>] [--no-wait] [--agent <inline|auto|name>] [<focus>]"
+allowed-tools: ["Bash", "Read", "Skill"]
+---
+
+# Dev PR Review
+
+Wraps the **sp:pr-reviewing** skill. The review itself runs on the GitHub PR through Codex
+(`@codex review`) — never through a local Codex review mechanism; the invoking agent orchestrates
+and (in `fix` mode) implements.
+
+## Argument Flags
+
+| Flag | Description | Default |
+| --- | --- | --- |
+| `<mode>` | `full\|submit\|collect\|fix\|rerun\|status\|rules` — full: request (deduped) + wait + report; submit: request and stop at pending; collect: report the latest review; fix: validate findings, fix legitimate ones, re-review; rerun: force a fresh review of the pushed HEAD; status: read-only composite; rules: author the repo's `AGENTS.md` `## Code Review Rules`. | full |
+| `--base` `<branch>` | Base branch when a new PR must be created. | existing PR base, else repo default |
+| `--no-wait` | Return pending right after the review request instead of polling. | off |
+| `--agent` `<inline\|auto\|name>` | Who performs model-bearing triage/fix. Omit uses the current agent, `inline` forbids dispatch, `auto` resolves the declared role, and a name pins that executor. This does not change the deterministic workflow/direct route. | omit |
+| `<focus>` | Remaining free text — extra review focus appended to the Codex request (e.g. `security boundaries and transaction idempotency`). | none |
+
+For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag-glossary.md).
+
+## Usage
+
+/sp:dev-pr-review [full|submit|collect|fix|rerun|status|rules] [--base <branch>] [--no-wait] [--agent <inline|auto|name>] [review focus]
+
+## Implementation
+
+- Apply the [inline-default execution-surface contract](../skills/spur-dev/references/cross-cutting.md#inline-default-execution-surface).
+- Delegate everything: `Skill(skill="sp:pr-reviewing", args="$ARGUMENTS")`. The skill owns mode
+  routing, finding triage, fix, and rules authoring; `.spur/workflows/pr-review.yaml` is the SSOT
+  for the review spine's state order and guards; the staged `pr-reviewing.ts` is the
+  deterministic git/gh core every spine step shells out to.
+- The external review goes through the GitHub PR and an `@codex review` comment only — never local
+  Codex review commands. Never force-push, rewrite history, merge the PR, or discard unrelated
+  changes; outside `fix` mode, ask before creating any commit.

package/plugins/sp/commands/dev-refine.md

@@ -1,5 +1,6 @@
 ---
 description: Refine task requirements via structured Q&A — clarify scope, elicit missing details, tighten acceptance criteria; optional implement-ready depth
+role: planner
 argument-hint: "<wbs> [--focus <mode>] [--description <text>] [--depth <standard|ready>] [--agent <inline|auto|name>] [--auto] [--next]"
 allowed-tools: ["Bash", "Read", "Skill", "AskUserQuestion"]
 ---
@@ -18,7 +19,7 @@ agent will implement and L3-clean is not enough (frozen APIs, anti-patterns, fil
 | `--focus` `<mode>` | Refinement focus mode. | omitted |
 | `--description` `<text>` | Override the task description. | omitted |
 | `--depth` `<standard\|ready>` | Spec depth bar (see flag glossary). | `standard` |
-| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing refinement. | inline |
+| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing refinement. | omit |
 | `--auto` | Skip objective HITL gates. | off |
 | `--next` | Hand off to the next-router on success. | off |
 
@@ -34,8 +35,9 @@ Under `--auto` with **`--depth standard`** (default), SKIP only when target sect
 findings: Background, Requirements, Acceptance Criteria, Design, Plan. Solution is not a refine
 target. Under **`--depth ready`**, do **not** SKIP on L3-clean alone — run the implement-ready
 checklist (dev-operations § refine) and rewrite Design/Requirements/Plan until another agent can
-implement without inventing design. Stage floor: `standard` (fallback `capable-2`); ready synthesis
-may use a higher tier when the task spans packages/seams.
+implement without inventing design. Stage floor: the `planner` role per
+[`roles.md`](../references/roles.md) — this command names roles, never tiers (0538 R4);
+ready synthesis may use a higher tier when the task spans packages/seams.
 
 ## Implementation
 

package/plugins/sp/commands/dev-refineall.md

@@ -1,5 +1,6 @@
 ---
 description: Refine a batch of tasks via structured Q&A — resolve a set (feature or selector), refine each in dependency-correct order, emit a batch report; optional implement-ready depth
+role: planner
 argument-hint: "--feature <id> | --tasks <selector> [--focus <mode>] [--description <text>] [--depth <standard|ready>] [--agent <inline|auto|name>] [--auto] [--keep-going] [--status <s>] [--json] [--worktree [<name>]]"
 allowed-tools: ["Bash", "Read", "Skill", "AskUserQuestion"]
 ---
@@ -19,7 +20,7 @@ operation, applied to a resolved set (typically every task under a feature). Pas
 | `--focus` `<mode>` | Refinement focus mode. | omitted |
 | `--description` `<text>` | Override description for each task. | omitted |
 | `--depth` `<standard\|ready>` | Spec depth bar (see flag glossary). | `standard` |
-| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing refinement. | inline |
+| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing refinement. | omit |
 | `--auto` | Skip objective HITL gates. | off |
 | `--keep-going` | Continue past per-task failures. | off |
 | `--status` `<s>` | Only refine tasks in a status. | backlog,todo |

package/plugins/sp/commands/dev-refresh.md

@@ -1,5 +1,6 @@
 ---
 description: Refresh feature status by feature ID, task WBS, or batch sweep via spur feature sync
+role: scribe
 argument-hint: "[<feature-id|wbs>] [--all] [--auto] [--agent <inline|auto|name>]"
 allowed-tools: ["Bash", "Read", "Skill"]
 ---
@@ -15,7 +16,7 @@ Wraps the **sp:spur-dev** skill.
 | `[<feature-id\|wbs>]` | Feature id or task WBS to refresh. | active |
 | `--all` | Refresh every feature. | off |
 | `--auto` | Skip objective HITL gates. | off |
-| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing refresh. | inline |
+| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing refresh. | omit |
 
 For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag-glossary.md).
 

package/plugins/sp/commands/dev-reverse.md

@@ -1,5 +1,6 @@
 ---
 description: Reverse engineer a codebase with selectable depth, focus, and output format
+role: coder
 argument-hint: "[<path>] [--mode <briefing|structure|architecture|design|full>] [--focus <all|stack|dependencies|data|flows|api|security|quality|performance>] [--format <markdown|json|both>] [--output <file>] [--agent <inline|auto|name>]"
 allowed-tools: ["Read", "Write", "Edit", "Grep", "Glob", "Bash", "Skill"]
 ---
@@ -17,7 +18,7 @@ Wraps the **sp:reverse-engineering** skill.
 | `--focus` `<all\|stack\|dependencies\|data\|flows\|api\|security\|quality\|performance>` | Analysis lens. | all |
 | `--format` `<markdown\|json\|both>` | Output format. | markdown |
 | `--output` `<file>` | Write to a file instead of stdout. | stdout |
-| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing analysis. | inline |
+| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing analysis. | omit |
 
 For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag-glossary.md).
 

package/plugins/sp/commands/dev-review.md

@@ -1,5 +1,6 @@
 ---
 description: "Review code for a task or path — multi-dimensional review across functional traceability, SECUA quality, and architectural depth. Triggers: \"review this\", \"check the code\", \"SECUA review\", \"dev review\", \"audit this\"."
+role: reviewer
 argument-hint: "[<wbs|path>] [--agent <inline|auto|name>] [--focus <dims>] [--fix (deprecated)]"
 allowed-tools: ["Bash", "Read", "Skill"]
 ---
@@ -13,7 +14,7 @@ Wraps the **sp:functional-review**, **sp:code-verification**, and **sp:code-impr
 | Flag | Description | Default |
 | --- | --- | --- |
 | `[<wbs\|path>]` | Task WBS or source path to review. | cwd |
-| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing review. | inline |
+| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing review. | omit |
 | `--focus` `<dims>` | Review dimensions (functional / SECUA / architecture). | all |
 | `--fix` | Deprecated no-op + warning; route remediation to /sp:dev-verify --fix. | off |