@gobing-ai/spur 0.3.75 → 0.3.76

package/.claude-plugin/marketplace.json

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

package/config/config.example.yaml

@@ -130,6 +130,12 @@ agent:
     #   agent: omp
     #   model: minimax/MiniMax-M3
     #   tier: cheap
+    # A disabled profile stays visible to `spur agent doctor` but never routes
+    # (no role, team, stage, or explicit selection). Flip back to enabled by
+    # removing the line or setting disabled: false.
+    # - name: retired-profile
+    #   agent: omp
+    #   disabled: true
     - name: pi-dsv4-flash-volc
       agent: pi
     #   tier: standard

package/config/rules/README.md

@@ -9,7 +9,7 @@ install or to ts-libs.
 
 | Category | Dir | Purpose |
 |---|---|---|
-| `typescript` | `typescript/` | TypeScript tooling, output boundaries, biome-suppression ban, no `debugger` |
+| `typescript` | `typescript/` | TypeScript tooling, output boundaries, biome/eslint-suppression ban, no `debugger` |
 | `strict` | `strict/` | Opt-in strict rules (runtime boundaries, HTTP boundaries, structural) |
 | `boundary` | `boundary/` | DB/DAO boundary enforcement |
 | `structure` | `structure/` | File layout, protected files, no focused/skipped tests |

package/config/rules/strict/runtime-boundaries.yaml

@@ -69,6 +69,7 @@ rules:
             # Synchronous bootstrap & path resolution:
             - "packages/config/src/bundled-config.ts" # sync bundledConfigRoot() directory walk
             - "packages/config/src/loader.ts" # sync resolveConfigFile() / schema specifier lookup
+            - "packages/config/src/executor-update.ts" # atomic single-entry config update (task 0797): O_EXCL lock, fsync'd tmp+rename commit, lstat symlink refusal, mode preservation — ts-runtime FileSystem seam has no lstat/fsync/chmod/O_EXCL
             - "packages/app/src/services/project-start.ts" # sync CLI binary path checks before daemon spawn
 
             # Synchronous template & workflow resolvers:

package/config/rules/typescript/no-eslint-suppressions.yaml

@@ -0,0 +1,30 @@
+$schema: "@gobing-ai/spur/schemas/rule-file.schema.json"
+# No ESLint suppression comments. Spur lints with Biome, not ESLint; leftover
+# `eslint-disable*` comments are dead suppressions that hide the real fix and
+# would not even silence the live gate. Sibling of `no-biome-suppressions`
+# (AGENTS.md: never suppress a gate to force green).
+#
+# Tests ARE in scope: an eslint-disable in a test is the same bypass.
+include:
+  - "apps/**/*.ts"
+  - "apps/**/*.tsx"
+  - "packages/**/*.ts"
+  - "packages/**/*.tsx"
+  - "plugins/**/*.ts"
+  - "scripts/**/*.ts"
+exclude:
+  - "**/node_modules/**"
+  - "**/dist/**"
+  - "**/vendors/**"
+rules:
+  - id: no-eslint-suppressions
+    description: >
+      Do not use ESLint disable comments (file, line, or next-line forms).
+      Spur lints with Biome; an ESLint suppression does not silence the live
+      gate and hides the real fix. Remove the comment and fix the underlying
+      issue (AGENTS.md: no suppressions to force green).
+    severity: error
+    evaluator:
+      type: rg
+      config:
+        pattern: "eslint-disable"

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gobing-ai/spur",
-    "version": "0.3.75",
+    "version": "0.3.76",
     "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.56",
-        "@gobing-ai/ts-ai-runner": "^0.4.56",
-        "@gobing-ai/ts-dual-workflow-engine": "^0.4.56",
-        "@gobing-ai/ts-infra": "^0.4.56",
-        "@gobing-ai/ts-llm-jsonl-importer": "^0.4.56",
-        "@gobing-ai/ts-rule-engine": "^0.4.56",
-        "@gobing-ai/ts-runtime": "^0.4.56",
-        "@gobing-ai/ts-utils": "^0.4.56",
+        "@gobing-ai/ts-db": "^0.4.57",
+        "@gobing-ai/ts-ai-runner": "^0.4.57",
+        "@gobing-ai/ts-dual-workflow-engine": "^0.4.57",
+        "@gobing-ai/ts-infra": "^0.4.57",
+        "@gobing-ai/ts-llm-jsonl-importer": "^0.4.57",
+        "@gobing-ai/ts-rule-engine": "^0.4.57",
+        "@gobing-ai/ts-runtime": "^0.4.57",
+        "@gobing-ai/ts-utils": "^0.4.57",
         "@types/bun": "1.3.14",
         "@types/figlet": "^1.7.0",
         "@types/node-notifier": "8.0.5",

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

@@ -23,7 +23,7 @@ operation, applied to a resolved set (typically every task under a feature). Pas
 | `--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 |
+| `--status` `<s>` | Only refine tasks in these statuses (applied in-agent to the frozen set). | `backlog` + `todo` |
 | `--json` | Emit structured JSON. | off |
 | `--worktree` `[<name>]` | Run the batch in an isolated git worktree; FF-merge on success, retain on failure. Bare `--worktree` creates a fresh tree; `--worktree <name>` adopts an existing worktree by name/path/branch. | off |
 
@@ -39,7 +39,7 @@ For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag
 Flags: `--feature` (sugar for `feature:<id>`), `--tasks <selector>`, shared refine flags
 (`--focus`, `--description`, `--depth`, `--agent`, `--auto`),
 plus `--keep-going`,
-`--status` (default `backlog,todo`),
+`--status` (default `backlog` + `todo`),
 `--json`, `--worktree` `[<name>]` (run the batch in an isolated git worktree — FF-merge onto the base ref on
 full success, retain intact on any failure/halt/non-FF; bare form creates a fresh tree, `<name>`
 form adopts an existing worktree by name/path/branch; see `execution-batch.md` § Worktree

package/plugins/sp/plugin.json

@@ -1,6 +1,6 @@
 {
     "name": "sp",
-    "version": "0.3.75",
+    "version": "0.3.76",
     "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/skills/dogfood-testing/SKILL.md

@@ -75,8 +75,11 @@ The command forwards these via `$ARGUMENTS`:
 > independent mutation sources is present:
 >
 > - **Pipeline-driving testees** — tokens
->   [`--next`, `dev-runall`, `dev-wrapall`, `dev-run`, `dev-wrap`, `dev-idea`,
->   `runall`, `wrapall`, `run`, `wrap`, `idea`] matched as a **distinct hyphen-word**
+>   <!-- pipeline-tokens:start -->
+>   [`--next`, `dev-runall`, `dev-wrapall`, `dev-refineall`, `dev-verifyall`, `dev-run`, `dev-wrap`, `dev-idea`,
+>   `refineall`, `verifyall`, `runall`, `wrapall`, `run`, `wrap`, `idea`]
+>   <!-- pipeline-tokens:end -->
+>   matched as a **distinct hyphen-word**
 >   (machine-checked by
 >   [`detectPipelineDriving`](../../scripts/dogfood-testing/detect-pipeline-driving.ts);
 >   see [§Pipeline-driving word-boundary contract](#pipeline-driving-word-boundary-contract))
@@ -335,8 +338,8 @@ node "$(superskill script path sp dogfood-testing/detect-pipeline-driving.mjs)"
 
 | Token shape | Examples | Matches | Rejects |
 |-------------|----------|---------|---------|
-| Flag / complete | `--next`, `dev-run`, `dev-runall`, `dev-wrap`, `dev-wrapall`, `dev-idea` | `/sp:dev-run 0125`, bare `--next` | `--next-gen`, `dev-runner` |
-| Bare noun | `run`, `runall`, `wrap`, `wrapall`, `idea` | `task run 0042` | `runaway`, `wrapper`, `idealist` |
+| Flag / complete | <!-- pipeline-tokens:start -->`--next`, `dev-run`, `dev-runall`, `dev-wrap`, `dev-wrapall`, `dev-idea`, `dev-refineall`, `dev-verifyall`<!-- pipeline-tokens:end --> | `/sp:dev-run 0125`, bare `--next` | `--next-gen`, `dev-runner` |
+| Bare noun | <!-- pipeline-tokens:start -->`run`, `runall`, `wrap`, `wrapall`, `idea`, `refineall`, `verifyall`<!-- pipeline-tokens:end --> | `task run 0042` | `runaway`, `wrapper`, `idealist` |
 
 `-` is a **word character** for boundaries: a token must be a distinct hyphen-word. Contract tests:
 `plugins/sp/tests/dogfood-testing/pipeline-detect.test.ts`. Helpers:

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

@@ -9,8 +9,8 @@ see_also:
 
 Task bodies are edited section-by-section through `spur task update --section <name> --from-file
 <path>`. The write is **file-wins and crash-safe** (atomic write): the named section's body is
-replaced wholesale from the file you point at. There is no inline-body flag — always stage the new
-body in a file first.
+replaced wholesale from the file you point at — with one exception, `Q&A`, which appends (see
+below). There is no inline-body flag — always stage the new body in a file first.
 
 For **pipeline output**, section authorship is one-writer-per-section (F92 0593 R1):
 `Testing` comes from `spur task record` (deterministic, from a verify verdict artifact — the
@@ -23,6 +23,8 @@ for `Plan`, `Acceptance Criteria`, hand-authored `Solution`, and any narrative s
 
 1. **Assemble the full section body** in a temp file. The body is everything *under* the `###`
    heading — do not include the heading line itself; the CLI owns the heading.
+   Sub-headings inside the body MUST be `####` or deeper: a `###` in a body parses as a new
+   top-level section and trips `L2.disallowed-section` (task 0787 grew 8 phantom sections this way).
 
    ```bash
    cat > /tmp/review.md <<'EOF'
@@ -42,7 +44,11 @@ for `Plan`, `Acceptance Criteria`, hand-authored `Solution`, and any narrative s
 
 3. The whole `### Review` body is now that file's contents. To amend rather than overwrite, read
    the current body (`spur task show 0040`), edit the temp file to the full desired state, and
-   replace again — there is no append mode.
+   replace again — there is no append mode for ordinary sections.
+
+**`Q&A` is the exception.** `--section "Q&A"` APPENDS a timestamped `#### Q&A entry — <ISO>`
+block rather than replacing the section. Start the body with `<!-- qa:replace -->` to replace it
+wholesale.
 
 `--section` **requires** `--from-file` (exit `2` otherwise). Section names match the DD-08 headings
 exactly: `Background`, `Requirements`, `Acceptance Criteria`, `Q&A`, `Design`, `Plan`, `Solution`, `Root Cause`, `Testing`, `Review`, `References`, `History`, `Notes` (universal sections are `History`, `References`, `Notes`; `Root Cause` is carried by the `issue` template variant).

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

@@ -61,8 +61,10 @@ frontmatter scalar.
   to avoid orphaned nested lifecycle runs). **It is not a guard bypass** — the `wip→testing` and
   `testing→done` `check` gates above still run; the CLI evaluates them inline when the FSM guard
   does not. `--force-done` waives the verify **verdict** only, never the section matrix.
-- **Section** (`--section` **requires** `--from-file`): replaces the entire named section body from
-  the file. No inline-body flag. Section names: `Background`, `Requirements`, `Acceptance Criteria`, `Q&A`, `Design`, `Plan`, `Solution`, `Testing`, `Review`, `References`, `History`, `Notes`.
+- **Section** (`--section` **requires** `--from-file`): writes the named section body from the file.
+  Most sections replace wholesale. Exception: `--section "Q&A"` APPENDS a timestamped
+  `#### Q&A entry — <ISO>` block; start the body with `<!-- qa:replace -->` to replace the section
+  wholesale. No inline-body flag. Section names: `Background`, `Requirements`, `Acceptance Criteria`, `Q&A`, `Design`, `Plan`, `Solution`, `Testing`, `Review`, `References`, `History`, `Notes`.
 - **Frontmatter** (`--feature <id>`, `--priority <p>`): sets the scalar frontmatter field on an
   existing task — the only post-create path, allow-listed to `feature_id` / `parent_wbs` / `priority`.
 
@@ -85,7 +87,7 @@ Flags: `--folder <path>`, `--json`. Exit codes: `0` success, `1` error, `2` usag
 
 ## `sections <wbs> <op> [name]`
 
-CLI-safe, matrix-enforced task section mutation. Section names are validated against canonical sections (`Background`, `Requirements`, `Acceptance Criteria`, `Q&A`, `Design`, `Plan`, `Solution`, `Root Cause`, `Testing`, `Review`, `References`, `History`, `Notes`). Universal sections (`History`, `References`, `Notes`) are always allowed; `Root Cause` is carried by the `issue` template variant.
+CLI-safe, matrix-enforced task section mutation. Section names are validated against canonical sections (`Background`, `Requirements`, `Acceptance Criteria`, `Q&A`, `Design`, `Plan`, `Solution`, `Root Cause`, `Testing`, `Review`, `References`, `History`, `Notes`). Universal sections (`History`, `References`, `Notes`) are always allowed; `Root Cause` is carried by the `issue` template variant. `Q&A` on `update --section` appends rather than replacing (see the Section bullet above); `<!-- qa:replace -->` forces a wholesale replace.
 
 | Op | Usage | Description |
 | --- | --- | --- |

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

@@ -209,7 +209,7 @@ spur workflow run ./workflows/approval.yaml --steer                # interactive
   are exclusive (exit `2`); `--silent` cannot combine with either (exit `2`).
 - **`--detail <level>`** sets human verbosity: `minimal` (state changes only), `invocation` (default;
   per-step headers), `full` (transitions + correlation). `--verbose` is shorthand for `--detail full`.
-- **`--trace-file`** appends a redacted, schema-versioned JSONL trace under `.spur/runs/workflow/`
+- **`--trace-file`** appends a redacted, schema-versioned JSONL trace under `.spur/workflow/`
   for post-run analysis - independent of human/JSON output.
 - **`--no-log`** opts out of writing the consolidated all-in-one run log (`.spur/run/<RUNID>.log`).
   By default the log is written **and retained** after the run ends; this flag skips it entirely
@@ -280,7 +280,7 @@ not advertise `--json-envelope` because its JSON projection is a kept-raw docume
 | `--silent` | Suppress all routine output; errors still set a non-zero exit status. |
 | `--verbose` | Include transitions and correlation diagnostics in human progress (implies `--detail full`). |
 | `--detail <level>` | Human detail level: `minimal`, `invocation` (default), or `full`. |
-| `--trace-file` | Append a redacted schema-versioned JSONL trace under `.spur/runs/workflow/`. |
+| `--trace-file` | Append a redacted schema-versioned JSONL trace under `.spur/workflow/`. |
 | `--no-log` | Opt out of writing the consolidated `.spur/run/<RUNID>.log` (retained by default; propagates to `--async` workers). |
 | `--steer` | Accept in-process steering commands on stdin at declared action boundaries (sync only; incompatible with `--json`/`--async`). |
 
@@ -335,7 +335,7 @@ redirecting `agent.run` stages (ADR-047).
 - **Run-log reclamation** (0429): removes retained `.spur/run/<RUNID>.log` files whose mtime is older
   than `workflow.logRetentionDays` in `.spur/config.yaml` (default 30 days; integer days, not minutes).
   Age is the only gate; best-effort deletes never abort the rest. Never touches
-  `.spur/runs/workflow/<RUNID>.jsonl` or `*-partial.md`.
+  `.spur/workflow/<RUNID>.jsonl` or `*-partial.md`.
 - **`--logs`** scopes to log reclamation only (skips stale-run finalization). `--dry-run` applies to
   both scopes (lists what would be removed, writes nothing). `--json` returns
   `{ olderThanMinutes, dryRun, cleaned, logs: { retentionDays, dryRun, reclaimed, failures } }` (with

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

@@ -237,11 +237,11 @@ must not be changed without updating the backing skill.
 - **Inputs:**
   - `--feature <id>` **or** `--tasks <selector>` (required — at least one). `--feature` is sugar for `--tasks feature:<id>` (shared selector grammar: explicit WBS list, `feature:<id>`, `ready`, status pseudo-list — [execution-batch.md](execution-batch.md) Step 1). If both are present, `--tasks` wins (one-line note in the report).
   - Shared refine flags (passed through to each per-task refine): `--focus <mode>`, `--description <text>`, `--depth <standard|ready>`, `--agent <inline|auto|name>`, `--auto`.
-  - Batch-only flags: `--keep-going` (continue independents after a failure; default halt), `--status <s>` (filter resolved membership; default **`backlog,todo`** — planning-side fill candidates), `--json` (machine-readable batch report).
+  - Batch-only flags: `--keep-going` (continue independents after a failure; default halt), `--status <s>` (filter resolved membership; default **`backlog` + `todo`** — planning-side fill candidates. The filter is applied in-agent against the frozen set; `spur task list --status` takes exactly one canonical status per call (see `execution-batch.md` Step 1).), `--json` (machine-readable batch report).
 - **Backing:** `sp:spur-dev` skill, `refineall` operation (orchestrates; per-task body is the single-task `refine` operation — never a second refine implementation).
 - **Behavior:**
   1. Resolve + **freeze** the set at kickoff (never re-query membership mid-batch).
-  2. Apply `--status` filter (default `backlog,todo`). Tasks already `done`/`cancelled`/`testing` are excluded unless the operator widens `--status`. Report each exclusion with reason.
+  2. Apply `--status` filter (default `backlog` + `todo`; applied in-agent against the frozen set; `spur task list --status` takes exactly one canonical status per call — see `execution-batch.md` Step 1). Tasks already `done`/`cancelled`/`testing` are excluded unless the operator widens `--status`. Report each exclusion with reason.
   3. Topo-sort by `dependencies[]` (Kahn, WBS-ascending tie-break). Cycle → abort entire batch before any refine. Out-of-set deps: `done` → allow; else → block subtree (same as runall).
   4. For each WBS in order: invoke single-task refine with shared flags **including `--depth`**. Under `--auto` + **`--depth standard`** (default), the per-task **L3 pre-synthesis SKIP gate** still applies. Under **`--depth ready`**, each task runs the implement-ready checklist (no L3-only SKIP).
   5. Failure policy: **stop-the-batch** (default) or `--keep-going` (skip in-batch dependents of a failed refine; continue independents).

package/schemas/spur-config.schema.json

@@ -165,6 +165,10 @@
                                 "type": "string",
                                 "enum": ["cheap", "standard", "capable-1", "capable-2", "capable-3"],
                                 "description": "Capability tier for stage-registry adaptive model routing (ADR-033, 0343). Live values: cheap | standard | capable-1 | capable-2 | capable-3 (1=low output quality, 3=high within the capable band). A stage starts on the cheapest eligible executor meeting its model_policy min_tier. Bare legacy `capable` is accepted at runtime (zod preprocess \u2192 capable-1) during the deprecation window but is not part of this editor enum."
+                            },
+                            "disabled": {
+                                "type": "boolean",
+                                "description": "Routing kill-switch (111): a disabled profile never serves a role, team, stage, or explicit selection, and doctor inventories it without probing. Omitted = enabled; only true/false accepted (no string/number/null coercion)."
                             }
                         }
                     }