@gobing-ai/spur 0.3.58 → 0.3.61

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
     "plugins": [
         {
             "name": "sp",
-            "version": "0.3.58",
+            "version": "0.3.61",
             "source": "./plugins/sp"
         }
     ]

package/config/config.example.yaml

@@ -4,11 +4,11 @@
 # Copy / adapt into a project as `.spur/config.yaml`.
 
 $schema: "@gobing-ai/spur/schemas/spur-config.schema.json"
-# Config schema version (string). Current recommended: "1.1".
+# Config schema version (string). Current recommended: "1.2".
 # "1" remains accepted; there is no hard migrator yet. Prefer "1.1" for
 # new projects so editors and operators know the file targets the ADR-033
 # + planning shape.
-version: "1.1"
+version: "1.2"
 name: my-project
 
 # ── Portable bootstrap (consumed by @gobing-ai/ts-infra

package/config/config.global.yaml

@@ -0,0 +1,137 @@
+# Spur GLOBAL configuration — `~/.config/spur/config.yaml`
+#
+# Seeded here by `spur init` on first run (never overwritten once it exists — you
+# own this file). It is the DEFAULT layer: every project's `.spur/config.yaml` is
+# merged OVER it, so a project config only needs to carry its delta.
+#
+# Merge contract (A4 / config 1.2):
+#   - Both layers are validated by the SAME schema; each legitimately carries a subset.
+#   - The merge is total and automatic: project layer wins over global, key by key.
+#   - Validation runs ONCE, on the merged result — a partial entry here is a legal
+#     merge fragment, never a legal config on its own.
+#   - `agent.executors` merges by `name`: a project restating `- name: omp` with a
+#     different `model` overrides just that field and keeps the rest from here.
+#
+# Only machine-wide keys belong in this file. Project-shaped keys — `name`,
+# `bootstrap`, `rules`, `redaction`, `tasks`, `features`, `agent.team` — resolve
+# against a project's own folder structure and must stay in `.spur/config.yaml`.
+
+$schema: "@gobing-ai/spur/schemas/spur-config.schema.json"
+
+# Inert label (task 0649 R6 ruling): nothing branches on `version` today.
+# Reunified at "1.2" across every shipped artifact (init stamp, JSON Schema).
+version: "1.2"
+
+agent:
+    # `default` is the role used for `--agent auto` when the caller declares
+    # nothing (task 0542 R2 — the value domain moved from executor names to
+    # roles). A role id selects its tier's cheapest eligible executor; a
+    # configured executor name still resolves during the transition with a
+    # one-time warning (shim agent-default-executor); any other value fails
+    # naming both accepted sets.
+    default: coder
+
+    # Role → tier map. Resolution: role → tier → cheapest USABLE executor whose
+    # tier >= the role's tier, climbing the ladder across gaps. Keep at least one
+    # usable executor at or above each rung or that role fails loudly at dispatch.
+    # Stage floors (stage-registry model_policy): changelog=cheap;
+    # implement/test/wrap/review/refine/brainstorm=standard;
+    # verify/dogfood=capable-1; plan=capable-2. A stage's fallback ladder
+    # (auth / resource-exhaustion / gate-fail) only advances when a higher rung
+    # has a usable executor — an empty rung turns a quota failure into a hang.
+    #
+    # The vocabulary is CLOSED (task 0536): re-tier or re-stage these four, never
+    # invent a fifth — a config naming any other key fails at load naming the
+    # accepted four. A project may override per-field in its own `.spur/config.yaml`;
+    # restate only what you change.
+    #
+    # ADR-078: THIS TABLE IS THE SSOT. `DEFAULT_AGENT_ROLES` in
+    # `packages/config/src/index.ts` is a byte-identical fallback that applies only
+    # when no config layer supplies `agent.roles` at all (the CF-safe core must
+    # resolve roles with no filesystem). The two must stay byte-identical — a
+    # fallback that differed would turn a missing config file into a silent
+    # behavior change. `plugins/sp/tests/roles.test.ts` R9 gates all three
+    # projections (this table, the constant, and `plugins/sp/references/roles.md`).
+    roles:
+        scribe:
+            tier: cheap
+            stages: [changelog]
+        coder:
+            tier: standard
+            stages: [implement, test, wrap]
+        reviewer:
+            tier: capable-1
+            stages: [verify, review, dogfood]
+        planner:
+            tier: capable-2
+            stages: [plan, refine, brainstorm]
+
+    # Canonical coding-agent ids (ts-ai-runner DISPLAY_ORDER, 0.4.8+):
+    #   claude, codex, gemini, pi, omp, opencode, antigravity-cli,
+    #   openclaw, hermes, grok
+    # Grok auth: non-empty XAI_API_KEY and/or ~/.grok/auth.json (no CLI
+    # auth-status verb).
+
+    # Named executor profiles (ADR-033 / 0343). Each pairs a canonical agent with
+    # an explicit model override and an explicit capability tier.
+    # `model` is pinned on every entry: omitting it defers to the agent CLI's own
+    # default, which drifts with CLI upgrades and account state — pin what your
+    # CLI would resolve today (`grok models`, omp config.yml modelRoles.default,
+    # ~/.codex/config.toml, ~/.claude.json). The ids below are working examples,
+    # not vendor defaults — re-pin for your accounts.
+    #
+    # Pairing philosophy (operator guidance, 2026-08): a `native` pair — a vendor's
+    # model served by that vendor's own CLI (gpt-5.6-* via codex, claude-*-5 via
+    # claude, grok-4.6 via grok, gemini-3.x via agy) — consistently outperforms the
+    # same model routed through a third-party CLI, and belongs at the capable rungs.
+    # `portable` models (glm-5.x, deepseek-v4-*, …) are provider-agnostic and best
+    # carried by omp or pi at the cheap/standard rungs. The ladder below mixes both
+    # classes on purpose; measure pairings with the history plane before promoting
+    # a portable model into a capable rung.
+    # Live tiers: cheap | standard | capable-1 | capable-2 | capable-3
+    # (1=low quality within capable, 3=high). DECLARE tier — inference never
+    # invents capable-2/3. Stage routing starts on the cheapest executor whose
+    # tier >= min_tier; same exact tier ties break by array order.
+    # Legacy bare `capable` is accepted at runtime as synonym for capable-1.
+    #
+    # Because this is the global layer, a project that wants one different model
+    # writes only `- name: omp` + `model: …` — the agent and tier come from here.
+    executors:
+        # cheap rung is optional: with none declared, scribe-role work starts one
+        # rung up at the cheapest standard executor. Add one when transcript-heavy
+        # mechanical commands (changelog/gitmsg/handover) get noisy on cost.
+        # - name: minimax
+        #   agent: omp
+        #   model: minimax/MiniMax-M3
+        #   tier: cheap
+        - name: omp
+          agent: omp
+          model: opencode/deepseek-v4-flash
+          tier: standard
+        - name: pi
+          agent: pi
+          model: "k3"
+          tier: capable-1
+        - name: grok
+          agent: grok
+          model: grok-4.6
+          tier: capable-2
+        - name: claude
+          agent: claude
+          model: k3
+          tier: capable-3
+        - name: codex
+          agent: codex
+          model: gpt-5.6
+          tier: capable-3
+
+# `workflows.paths` is deliberately NOT set here. Its values are search paths
+# resolved against a project's own root (0639 classifies it project-relative), so
+# a machine-wide value would point every project at a directory that mostly does
+# not exist. The key is present (the A4 goal names it among the shipped global
+# defaults) but empty: `workflow list` falls back to default `.spur/workflows/`
+# discovery, and the lifecycle adapter resolves bundled → project
+# `.spur/workflows/` on its own (make-lifecycle-adapter.ts:24, two tiers since
+# task 0648). Set paths per project when a project keeps workflows somewhere
+# non-standard.
+workflows: {}

package/config/corpus-baseline.json

@@ -447,6 +447,102 @@
             "reason": "Accepted backlog: L4.orphan-scenarios",
             "since": "2026-08-19"
         },
+        {
+            "kind": "feature",
+            "id": "B1",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "B3",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "E5",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "F",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "F31",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "F82",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "G4",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "H11",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "I",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "I4",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "I5",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
+        {
+            "kind": "feature",
+            "id": "J",
+            "code": "L4.dogfood-missing",
+            "severity": "warning",
+            "reason": "Feature remains verifying; direct linked tasks touch self-referential workflow infrastructure, but no dogfood report exists. Accepted as pre-A4 corpus debt only; the strict feature completion gate still requires real dogfood evidence.",
+            "since": "2026-08-24"
+        },
         {
             "kind": "task",
             "id": "0001",
@@ -12213,14 +12309,6 @@
             "reason": "Accumulated anchor drift, surfaced for the first time by task 0583's content-matching rule. The cited lines resolve and are in bounds, but no longer name the requirement row's subject — a later task edited the file and pushed the anchor onto unrelated code. Spot-verified true positives (an import block cited for a component's hooks; a severity-parsing block cited for `runL4Rollup`). Repairing 1,300+ historical citations is its own campaign; the rule ships at warning severity until then (0583 R6).",
             "since": "2026-08-18"
         },
-        {
-            "kind": "task",
-            "id": "0416",
-            "code": "L4.stale-line-anchor",
-            "severity": "warning",
-            "reason": "Anchor written with an incomplete path; qualification migration (task 0583) owns the mechanical repair — see note § L4.stale-line-anchor.",
-            "since": "2026-08-17"
-        },
         {
             "kind": "task",
             "id": "0416",

package/config/workflow-composition-baseline.json

@@ -719,7 +719,7 @@
                 },
                 "collect:onEnter:1": {
                     "kind": "shell",
-                    "invocation": "$spurBin workflow validate .spur/workflows/wayfinder-resolution.yaml > .spur/run/wayfinder/$wbs-workflow-check.txt",
+                    "invocation": "$spurBin workflow validate wayfinder-resolution.yaml > .spur/run/wayfinder/$wbs-workflow-check.txt",
                     "stateEffect": "read",
                     "evidenceEffect": "write",
                     "disposition": "SIMPLE"

package/config/workflows/wayfinder-resolution.yaml

@@ -64,13 +64,11 @@ states:
       - kind: shell
         options:
           command: "mkdir -p .spur/run/wayfinder && $spurBin task show $wbs --json > .spur/run/wayfinder/$wbs-input.json"
-      # `.spur/workflows/` is the runtime read path in every layout — a symlink to
-      # config/workflows/ inside the Spur monorepo, a real directory in a seeded
-      # project. The previous `config/workflows/…` literal only resolved in the
-      # monorepo and hard-failed `collect` anywhere else.
+      # `wayfinder-resolution.yaml` uses the project→bundled resolver (tasks 0648/0650):
+      # a bare name falls back to the bundled tree; an explicit project path wins.
       - kind: shell
         options:
-          command: "$spurBin workflow validate .spur/workflows/wayfinder-resolution.yaml > .spur/run/wayfinder/$wbs-workflow-check.txt"
+          command: "$spurBin workflow validate wayfinder-resolution.yaml > .spur/run/wayfinder/$wbs-workflow-check.txt"
       - kind: shell
         options:
           command: "$spurBin task check $wbs > .spur/run/wayfinder/$wbs-precheck.txt"
@@ -112,7 +110,7 @@ states:
     onEnter:
       - kind: shell
         options:
-          command: 'rm -f .spur/run/wayfinder/$wbs-resolution-verdict.txt'
+          command: "rm -f .spur/run/wayfinder/$wbs-resolution-verdict.txt"
       - kind: agent.run
         options:
           agent: ${vars.agent}

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gobing-ai/spur",
-    "version": "0.3.58",
+    "version": "0.3.61",
     "description": "Spur CLI — local-first harness for mainstream coding agents: constraint checking, workflow orchestration, agent health, and history analytics. Bun-native; exposes the `spur` command.",
     "keywords": [
         "spur",
@@ -53,14 +53,14 @@
     },
     "devDependencies": {
         "@commander-js/extra-typings": "^14.0.0",
-        "@gobing-ai/ts-db": "^0.4.41",
-        "@gobing-ai/ts-ai-runner": "^0.4.41",
-        "@gobing-ai/ts-dual-workflow-engine": "^0.4.41",
-        "@gobing-ai/ts-infra": "^0.4.41",
-        "@gobing-ai/ts-llm-jsonl-importer": "^0.4.41",
-        "@gobing-ai/ts-rule-engine": "^0.4.41",
-        "@gobing-ai/ts-runtime": "^0.4.41",
-        "@gobing-ai/ts-utils": "^0.4.41",
+        "@gobing-ai/ts-db": "^0.4.42",
+        "@gobing-ai/ts-ai-runner": "^0.4.42",
+        "@gobing-ai/ts-dual-workflow-engine": "^0.4.42",
+        "@gobing-ai/ts-infra": "^0.4.42",
+        "@gobing-ai/ts-llm-jsonl-importer": "^0.4.42",
+        "@gobing-ai/ts-rule-engine": "^0.4.42",
+        "@gobing-ai/ts-runtime": "^0.4.42",
+        "@gobing-ai/ts-utils": "^0.4.42",
         "@types/bun": "1.3.14",
         "@types/figlet": "^1.7.0",
         "@types/node-notifier": "8.0.5",

package/plugins/README.md

@@ -228,7 +228,7 @@ graph TB
     subgraph "Corpus Layer"
         CORPUS["docs/tasks/ + docs/features/<br/>Markdown planning corpus"]
         RULES[".spur/rules/<br/>YAML constraint rules"]
-        WFS[".spur/workflows/<br/>YAML workflow definitions"]
+        WFS["bundled workflows tree<br/>YAML workflow definitions"]
     end
 
     %% Command → Skill delegations
@@ -309,7 +309,7 @@ Tier 3 — Execution Layer (spur CLI + Guard Scripts)
 
 1. User types `/sp:dev-run 0090`
 2. **Command** delegates to `sp:spur-dev` skill (execution half)
-3. **Skill** reads the task, loads `.spur/workflows/task-pipeline.yaml`, and runs `spur workflow run` with HITL surfacing
+3. **Skill** reads the task, loads `task-pipeline.yaml`, and runs `spur workflow run` with HITL surfacing
 4. **CLI** executes the workflow engine (`@gobing-ai/ts-dual-workflow-engine`), pauses at HITL gates, persists run state
 5. Result: task driven through implement → check → fix → verify lifecycle
 
@@ -351,8 +351,9 @@ The **workflow** and **rule** engines have their own lifecycles (author → vali
 
 ## Workflow Pipelines
 
-The plugin ships workflow YAMLs under `.spur/workflows/`.
-Each pipeline owns one lifecycle phase:
+The plugin references workflow YAMLs by bare name; the CLI resolves them through the
+bundled tree (two-tier model, task 0648/0650) — a project-local override wins when
+present, otherwise the bundled copy is used. Each pipeline owns one lifecycle phase:
 
 | Workflow                 | Phase                             | Entry command                     | Status        |
 | ------------------------ | --------------------------------- | --------------------------------- | ------------- |

package/plugins/sp/README.md

@@ -509,7 +509,7 @@ graph TB
     subgraph "Corpus layer"
         CORPUS["docs/tasks/ + docs/features/<br/>markdown planning corpus"]
         RULES[".spur/rules/<br/>YAML constraint rules"]
-        WFS[".spur/workflows/<br/>YAML workflow definitions"]
+        WFS["bundled workflows tree<br/>YAML workflow definitions"]
     end
 
     CMD -->|"Skill(sp:spur-dev, ...)"| SKILL_DEV
@@ -557,7 +557,7 @@ graph TB
 
 1. User types `/sp:dev-run 0090`.
 2. **Command** delegates to `sp:spur-dev` skill (execution half).
-3. **Skill** reads the task, loads `.spur/workflows/task-pipeline.yaml`, and runs
+3. **Skill** reads the task, loads `task-pipeline.yaml`, and runs
    `spur workflow run` with HITL surfacing.
 4. **CLI** executes the workflow engine (`@gobing-ai/ts-dual-workflow-engine`), pauses at HITL gates,
    persists run state.
@@ -575,7 +575,7 @@ graph TB
 
 ### Workflow pipelines
 
-The plugin ships workflow YAMLs under `.spur/workflows/`. Each
+The plugin references workflow YAMLs by bare name; the CLI resolves them through the bundled tree (two-tier model, task 0648/0650) — project-local overrides win when present. Each
 pipeline owns one lifecycle phase:
 
 | Workflow                    | Phase                             | Entry command                     |

package/plugins/sp/agents/super-planner.md

@@ -78,7 +78,7 @@ You own the spaces **between** task runs:
 - **Preflight (Step 2.5 / 3.0)** - before each pipeline launch, evaluate TABLE A STOP rows
   (`batch-preflight.ts` or equivalent). Skip A2/A7/A8/A9; still **launch `task-pipeline.yaml`** for
   ready WBS (never substitute a `dev-next` loop for the happy path).
-- **Run each ready task** through `.spur/workflows/task-pipeline.yaml` via `spur workflow run --async`
+- **Run each ready task** through `task-pipeline.yaml` via `spur workflow run --async`
   (Step 3). The command/script layer polls `spur workflow trace` to terminal state - polling is
   transport, not planner reasoning (R3: the poll loop must not live in this agent's body; the planner
   inspects the terminal verdict, not the poll iterations). Follow the

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

@@ -31,7 +31,7 @@ For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag
 
 - 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
+  routing, finding triage, fix, and rules authoring; `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

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

@@ -28,7 +28,7 @@ For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag
 ## Implementation
 
 - Apply the [inline-default execution-surface contract](../skills/spur-dev/references/cross-cutting.md#inline-default-execution-surface).
-- Wrap stays **workflow-backed** — `spur workflow run .spur/workflows/wrapup-pipeline.yaml` is the only implementation; there is no inline wrap driver.
+- Wrap stays **workflow-backed** — `spur workflow run wrapup-pipeline.yaml` is the only implementation; there is no inline wrap driver.
 - Resolve the executor **before** launching the workflow:
   - `--agent <name>` → pass the name unchanged into `vars.agent`.
   - `--agent auto` → tier-resolve a concrete executor first, then merge it into `vars.agent`.
@@ -42,7 +42,7 @@ AGENT=… # resolved above: agent.default for omitted, tier-resolved for auto, u
 echo "execution surface: subprocess; reason: trigger 3 — durable auditable run record required; requested agent: <inline|auto|name>; executor: $AGENT"
 VARS=$(jq -nc --arg tasks "[\"$WBS\"]" --arg agent "$AGENT" --arg profile "$PROFILE" --arg merge "$MERGE" \
   '{tasks:$tasks, agent:$agent, profile:$profile, merge:$merge}')
-spur workflow run .spur/workflows/wrapup-pipeline.yaml --vars "$VARS" [--dry-run]
+spur workflow run wrapup-pipeline.yaml --vars "$VARS" [--dry-run]
 ```
 
 The executor resolution is described in the bullets above; the snippet's `AGENT` variable carries

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

@@ -30,7 +30,7 @@ For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag
 ## Implementation
 
 - Apply the [inline-default execution-surface contract](../skills/spur-dev/references/cross-cutting.md#inline-default-execution-surface).
-- Wrap stays **workflow-backed** — `spur workflow run .spur/workflows/wrapup-pipeline.yaml` is the only implementation; there is no inline wrap driver.
+- Wrap stays **workflow-backed** — `spur workflow run wrapup-pipeline.yaml` is the only implementation; there is no inline wrap driver.
 - Resolve the executor **before** launching the workflow:
   - `--agent <name>` → pass the name unchanged into `vars.agent`.
   - `--agent auto` → tier-resolve a concrete executor first, then merge it into `vars.agent`.
@@ -44,7 +44,7 @@ AGENT=… # resolved above: agent.default for omitted, tier-resolved for auto, u
 echo "execution surface: subprocess; reason: trigger 3 — durable auditable run record required; requested agent: <inline|auto|name>; executor: $AGENT"
 VARS=$(jq -nc --arg tasks "$TASKS" --arg feature "$FEATURE" --arg agent "$AGENT" --arg profile "$PROFILE" --arg merge "$MERGE" \
   '{tasks:$tasks, feature:$feature, agent:$agent, profile:$profile, merge:$merge}')
-spur workflow run .spur/workflows/wrapup-pipeline.yaml --vars "$VARS" [--dry-run]
+spur workflow run wrapup-pipeline.yaml --vars "$VARS" [--dry-run]
 ```
 
 The executor resolution is described in the bullets above; the snippet's `AGENT` variable carries

package/plugins/sp/plugin.json

@@ -1,6 +1,6 @@
 {
     "name": "sp",
-    "version": "0.3.58",
+    "version": "0.3.61",
     "description": "Spur — a local-first harness engineering toolkit that wraps mainstream coding agents with constraint checking, workflow orchestration, and history analytics.",
     "extensions": {
         "pi": ["./hooks/pi/guard-extension.ts"]

package/plugins/sp/references/roles.md

@@ -10,8 +10,9 @@ see_also:
 # Roles — the Layer-1 role-to-tier table
 
 The executor-selection contract is two layers. **Layer 1 (this file)** projects *role → tier*;
-its SSOT is `DEFAULT_AGENT_ROLES` in `packages/config/src/index.ts` (task 0572 / ADR-061) — this
-file is the agent/human-facing view plus the plugin-owned command→role mapping. **Layer 2** maps
+its SSOT is `agent.roles` in `config/config.global.yaml` (task 0647 / ADR-078) — this file is the
+agent/human-facing view plus the plugin-owned command→role mapping. `DEFAULT_AGENT_ROLES` in
+`packages/config/src/index.ts` is the no-filesystem fallback and must remain identical. **Layer 2** maps
 *tier → executor* and is owned by the operator in `.spur/config.yaml`. This file never names an
 executor, a model, or a vendor — it declares only what tier a role's work needs, and the
 operator's config decides which executor serves that tier.
@@ -38,9 +39,10 @@ collapse, named as people so they stay addressable in `--agent`.
 
 ## The table
 
-<!-- PROJECTION (task 0572 / ADR-061): the tier/stages half of the block below is a generated view
-     of DEFAULT_AGENT_ROLES in packages/config/src/index.ts — edit that constant, not this file.
-     plugins/sp/tests/roles.test.ts (R9) fails the suite on any drift between the two. The
+<!-- PROJECTION (task 0647 / ADR-078): the tier/stages half of the block below is a generated view
+     of agent.roles in config/config.global.yaml — edit that SSOT, not this file.
+     plugins/sp/tests/roles.test.ts (R9) fails the suite on any three-way drift with the
+     DEFAULT_AGENT_ROLES no-filesystem fallback. The
      `commands:` half is plugin data (command frontmatter is its SSOT). -->
 
 ```yaml
@@ -98,9 +100,10 @@ driving the external PR review and triaging its findings folds the `review` stag
 
 **Consistency is a test, not a convention.** `plugins/sp/tests/roles.test.ts` parses this YAML and
 asserts the tier-distinctness, command closure, stage-floor, and boundary invariants against the
-real command directory, the real stage registry, and the real operator config — plus parity with
-`DEFAULT_AGENT_ROLES` (R9, 0572): the table above must equal the code SSOT byte-for-byte on
-id/tier/stages. When the table and the registry disagree, fix the table or the registry — never the
-test. When the table and `DEFAULT_AGENT_ROLES` disagree, fix the constant (or regenerate this view).
+real command directory, the real stage registry, and the real operator config — plus three-way parity
+with `config/config.global.yaml` and `DEFAULT_AGENT_ROLES` (R9, 0647): the table above must equal the
+shipped SSOT and no-filesystem fallback on id/tier/stages. When the table and the registry disagree,
+fix the table or the registry — never the test. When the three role tables disagree, fix the shipped
+SSOT first, then regenerate the projections.
 A project may re-tier/re-stage a role at config time via `agent.roles` (closed vocabulary) — that
 override never flows back into this file.