@gobing-ai/spur 0.4.8 → 0.4.10

package/plugins/sp/skills/dogfood-testing/SKILL.md

@@ -82,11 +82,11 @@ The command forwards these via `$ARGUMENTS`:
 >   <!-- pipeline-tokens:end -->
 >   matched as a **distinct hyphen-word**
 >   (machine-checked by
->   [`detectPipelineDriving`](../../lib/dogfood-pipeline.ts);
+>   `detectPipelineDriving` (`spur agent dogfood gate`);
 >   see [§Pipeline-driving word-boundary contract](#pipeline-driving-word-boundary-contract))
 >   → `⚠ pipeline-driving testee detected; pass --max-retry 0 (observe-only) or --max-retry N (fix mode, tree mutation acknowledged)`.
 > - **Mutating `--fix` modes** — `--fix all` / `--fix blockers-first`, boundary-guarded via
->   [`hasMutatingFixMode`](../../lib/dogfood-pipeline.ts) (never matches
+>   `hasMutatingFixMode` (`spur agent dogfood gate`) (never matches
 >   `--fix none` / `--focus all` / `--prefix all`). No pipeline token required: a verify/review leg
 >   with `--fix all` mutates the tree on its own (0280 dogfood P2, task 0293). Honesty note:
 >   `--max-retry 0` here bounds **the driver only** — the testee still mutates the tree — so the
@@ -100,7 +100,7 @@ The command forwards these via `$ARGUMENTS`:
    in-agent):
 
    ```bash
-   node "$(superskill script path sp dogfood-testing/detect-pipeline-driving.mjs)" \
+   spur agent dogfood gate \
      --testee "<raw testee string>" \
      [--max-retry-present]
    ```
@@ -109,7 +109,7 @@ The command forwards these via `$ARGUMENTS`:
      of two independent mutation sources (task 0293); its two refuse lines are the ones quoted
      verbatim in the repo-mutation warning above.
    - Exit **0** → proceed. Do not auto-substitute `--max-retry 0`.
-   - The matcher contract is unit-checked by `tests/dogfood-testing/pipeline-detect.test.ts`.
+   - The matcher contract is unit-checked by `packages/app/tests/services/dogfood/pipeline-detect.test.ts`.
      See [§Pipeline-driving word-boundary contract](#pipeline-driving-word-boundary-contract) and
      [§Mutating `--fix` mode contract](#mutating---fix-mode-contract).
 1. **Resolve + classify** the testee: slash command (`/sp:...`), agent skill (`Skill(...)`), or shell
@@ -121,7 +121,7 @@ The command forwards these via `$ARGUMENTS`:
     re-run the gate with the derived step labels:
 
     ```bash
-    node "$(superskill script path sp dogfood-testing/detect-pipeline-driving.mjs)" \
+    spur agent dogfood gate \
       --testee "<raw testee string>" \
       --max-retry-present \
       --steps "step1 label||step2 label||..."
@@ -232,7 +232,7 @@ contract violation**.
    **before** claiming `status: complete`:
 
    ```bash
-   node "$(superskill script path sp dogfood-testing/validate-report.mjs)" --file <report-path>
+   spur agent dogfood validate-report --file <report-path>
    ```
 
    Exit **0** → proceed. Exit **2** → set `status: aborted`, list every error code under §5
@@ -338,7 +338,7 @@ Do **not** use this skill for:
 Pipeline-driving detection is **word-boundary**, not leading-space substring. The live gate is:
 
 ```bash
-node "$(superskill script path sp dogfood-testing/detect-pipeline-driving.mjs)" --testee "<testee>" [--max-retry-present] [--steps "…"] [--json]
+spur agent dogfood gate --testee "<testee>" [--max-retry-present] [--steps "…"] [--json]
 ```
 
 | Token shape | Examples | Matches | Rejects |
@@ -347,9 +347,9 @@ node "$(superskill script path sp dogfood-testing/detect-pipeline-driving.mjs)"
 | 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:
+`packages/app/tests/services/dogfood/pipeline-detect.test.ts`. Helpers:
 `detectPipelineDriving`, `isImplementHeavyStep`, `detectImplementHeavy`, `evaluateDogfoodGate` in
-[`detect-pipeline-driving.ts`](../../scripts/dogfood-testing/detect-pipeline-driving.ts).
+`spur agent dogfood gate` (absorbed into the CLI; was `plugins/sp/scripts/dogfood-testing/detect-pipeline-driving.ts`).
 
 ## Mutating `--fix` mode contract
 

package/plugins/sp/skills/dogfood-testing/references/report-template.md

@@ -336,7 +336,7 @@ Before the skill may stop (success, partial, fail, observe-only end, or abort),
    and mirror the footer block at the **end of the report file**. A report whose body lacks the
    footer cannot set `status: complete`.
 8. **Self-validate (task 0278 R6):** run
-   `node "$(superskill script path sp dogfood-testing/validate-report.mjs)" --file <report-path>` before
+   `spur agent dogfood validate-report --file <report-path>` before
    claiming `status: complete`. Exit 2 → `status: aborted` + list error codes under
    `#### Unresolved` (never force complete on a non-@1.2 shape).
 9. **Refusal rule (@1.2):** when any check above fails, set `status: aborted` and list every

package/plugins/sp/skills/history-anatomy/references/modes.md

@@ -2,8 +2,8 @@
 
 The skill resolves exactly two modes. Everything else fails loud. This matrix is the enforcement
 surface the workflow (0660) and the skill share; keep the vocabulary frozen. Execution note
-(0920): argument validation runs deterministically in the `history-anatomy-cache` helper `paths`
-command (logic core: `packages/app/src/services/history-anatomy.ts`, task 1005) before the
+(0920): argument validation runs deterministically in `spur history anatomy paths`
+(formerly the `history-anatomy-cache` helper) (logic core: `packages/app/src/services/history-anatomy.ts`, task 1005) before the
 workflow starts; the model hop no longer performs it.
 
 ## Mode vocabulary (frozen)

package/plugins/sp/skills/history-anatomy/references/operations.md

@@ -31,10 +31,9 @@ Given the current and baseline artifacts, author the model half of the report. A
    calendar day; ad-hoc → immediately preceding equal-duration window. If baseline coverage is
    insufficient or materially different, emit `not comparable` and **no** trend/delta/percentage.
 3. **Findings** — each with the full per-finding field set (key, category, impact, trend,
-   observation, inference, confidence, contradictions, evidenceAnchor, severity, reproCommand,
+   observation, inference, contradictions, evidenceAnchor, severity, reproCommand,
    ownerSurface). Categories from the closed vocabulary; stable keys of the form
-   `<category>:<owner-surface>:<signal>`. Severity is the closed P1/P2/P3 vocabulary and is
-   orthogonal to confidence; reproCommand reproduces the observation verbatim; ownerSurface names
+   `<category>:<owner-surface>:<signal>`. Severity is the closed P1/P2/P3 vocabulary; reproCommand reproduces the observation verbatim; ownerSurface names
    the concrete owning surface (file/package/command), consistent with the key's middle segment.
 4. **Recurrence ledger** — classify every finding against the baseline on the **stable key**.
 5. **Telemetry gaps** — every dimension the artifact cannot support, rendered `not available`.
@@ -58,7 +57,7 @@ Given a candidate report and the artifacts, independently verify:
 - **Twelve-section completeness and order** — all twelve section names present in the frozen
   order; none renamed/omitted.
 - **Per-finding fields** — every finding (problem and positive) carries key, category, impact,
-  trend, observation, inference, confidence, contradictions, evidenceAnchor, severity (P1/P2/P3),
+  trend, observation, inference, contradictions, evidenceAnchor, severity (P1/P2/P3),
   reproCommand, ownerSurface; category in the closed vocabulary; stable-key grammar. A finding
   missing any triage field FAILs (the deterministic gate enforces the same set).
 - **Remediation handoff** — each accepted-proposal handoff carries a `spur task create`

package/plugins/sp/skills/history-anatomy/references/report-contract.md

@@ -62,10 +62,9 @@ Every finding — problem and positive alike — carries the full field set:
 | `trend` | `new` / `recurring` / `regressed` / `improved` / `resolved` / `not-comparable` (see recurrence). |
 | `observation` | What the artifacts show — evidence, not interpretation. |
 | `inference` | What the observation is reasoned to mean; names its supporting observations. |
-| `confidence` | Per-finding: `high` / `medium` / `low`. Never one blanket report-level score. |
 | `contradictions` | Any contradicting signal shown beside the finding, not silently reconciled. |
 | `evidenceAnchor` | At least one anchor to the forensics artifact or cited `file:line`. An entry with no anchor is invalid. |
-| `severity` | Closed vocabulary `P1` / `P2` / `P3` — how much the finding matters. Orthogonal to `confidence`: severity orders work, confidence says how sure we are (0680 R1). The structure gate fails a finding without one. |
+| `severity` | Closed vocabulary `P1` / `P2` / `P3` — how much the finding matters. Severity orders work (0680 R1); how well a finding is supported lives in its `observation`, `inference`, `contradictions` and `evidenceAnchor`, never a confidence label (ADR-138). The structure gate fails a finding without one. |
 | `reproCommand` | The invocation that reproduces the observation — one command a reader can run verbatim (0680 R2). Gate-enforced. |
 | `ownerSurface` | The concrete surface that owns the fix (a file path, package, or command), consistent with the key's `<owner-surface>` segment but named as a target rather than a slug (0680 R3). Gate-enforced. |
 
@@ -114,7 +113,7 @@ reclassify a recurring finding as new.
 ## Positive patterns
 
 Positive entries are held to the **same evidence standard as problems**: they carry observation,
-inference, confidence, and at least one evidence anchor. An entry without an anchor is invalid. The
+inference, and at least one evidence anchor. An entry without an anchor is invalid. The
 section renders successful workflows, resolved past issues that stay resolved, and healthy,
 repeating behavior worth keeping.
 

package/plugins/sp/skills/issue-finding/SKILL.md

@@ -411,7 +411,7 @@ Thin wrapper: `Skill(skill="sp:issue-finding", args="$ARGUMENTS")`.
 - Wholesale raw JSONL parsing when the source has a typed mapper.
 - Accepting `--use-history` or `--no-task` silently instead of naming their replacements.
 - GENERATE recipes inventing a title flag, dotted template forms, or quoted dotted section flags.
-- Claiming multi-agent forensics without stating source confidence (High/Medium/Low).
+- Claiming multi-agent forensics without citing the session source each finding came from.
 - Skipping batch section writes + single `spur task check` (when generating).
 - Emitting empty findings without inventorying sessions first.
 

package/plugins/sp/skills/next-router/references/routing-table.md

@@ -15,7 +15,7 @@ dispatcher: resolve target → load corpus → apply primary table → optional
 
 `sp:super-planner` (via `/sp:dev-runall`) **reads** TABLE A STOP preconditions for:
 
-1. **Preflight** — skip pipeline launch when A2/A7/A8/A9 would stop `dev-next` (`batch-preflight.ts`).
+1. **Preflight** — skip pipeline launch when A2/A7/A8/A9 would stop `dev-next` (`spur task preflight`).
 2. **One-shot recovery** — after a failed pipeline, map status → primary hop (A1/A3/A5/A6/A7) at most once.
 
 It does **not** reimplement TABLES or replace `task-pipeline.yaml` with a `dev-next` loop. Keep this

package/plugins/sp/skills/parallel-execution/SKILL.md

@@ -61,7 +61,7 @@ Parallel subagent outputs must be **synthesized**, not concatenated. The synthes
 
 1. **Dedup** — merge findings with the same `file:line` anchor; keep the highest-severity version.
 2. **Resolve conflicts** — when two subagents disagree on the same claim, surface the disagreement explicitly; don't silently pick one.
-3. **Rank by confidence** — sort synthesized results by confidence (HIGH → MEDIUM → LOW); unresolved conflicts go last.
+3. **Rank by evidence** — verified findings (executed check or cited source) first, unverified next, unresolved conflicts last; severity within each tier.
 4. **Unified format** — emit one coherent output, not N raw dumps.
 
 Full synthesis methodology: [result-synthesis.md](references/result-synthesis.md).
@@ -104,7 +104,7 @@ was meant to avoid. Let the reviewer reach its own conclusion.
 
 - **`sp:spur-dev`** owns task selection and lifecycle. When a batch contains independent tasks, the spine consults this skill for the fan-out pattern.
 - **`sp:super-planner`** is the orchestrator that executes the fan-out. Its parallel mode (documented in its agent definition) applies the patterns from this skill.
-- **`/sp:dev-runall --mode parallel|auto`** is the task-batch entry point; its `batch-plan.mjs order` schedule applies this skill's dependency and file-overlap rows deterministically.
+- **`/sp:dev-runall --mode parallel|auto`** is the task-batch entry point; its `spur task batch-plan order` schedule applies this skill's dependency and file-overlap rows deterministically.
 
 ## When to use
 

package/plugins/sp/skills/parallel-execution/references/result-synthesis.md

@@ -41,13 +41,12 @@ Synthesis:  ⚠ CONFLICT — Redis migration safety
 
 **Rule:** conflicts are findings, not failures. Surface them with both positions stated; let the operator resolve.
 
-### 3. Rank by confidence
+### 3. Rank by evidence
 
-Sort synthesized results:
-1. HIGH confidence (empirically verified, source-cited)
-2. MEDIUM confidence (reasoned, but not empirically verified)
-3. LOW confidence (heuristic, pattern-match, or uncertain)
-4. Unresolved conflicts (both sides stated)
+Sort synthesized results by what backs them, not a self-assigned confidence label (ADR-138):
+1. Verified (an executed check or a cited `path:line` / URL)
+2. Unverified (reasoned or pattern-matched; name the check that would ground it)
+3. Unresolved conflicts (both sides stated)
 
 Within each tier, sort by severity (P1 → P2 → P3 → P4).
 
@@ -58,11 +57,11 @@ Emit one coherent output. The unified report has:
 ```
 ## Synthesized Results
 
-### HIGH Confidence
-| # | Finding | Source | Severity | File:Line |
-|---|---------|--------|----------|-----------|
+### Verified
+| # | Finding | Source | Severity | File:Line | Evidence |
+|---|---------|--------|----------|-----------|----------|
 
-### MEDIUM Confidence
+### Unverified
 ...
 
 ### Conflicts (unresolved)

package/plugins/sp/skills/pr-reviewing/SKILL.md

@@ -40,9 +40,9 @@ sp:pr-reviewing (this skill — mode routing, triage, fix, rules)
       │  deterministic spine, state order + guards:
       ▼
 pr-review.yaml ← workflow SSOT (seeded by spur init; project-tunable)
-      │  every state resolves with `superskill script path` and shells out to:
+      │  every deterministic action shells out to:
       ▼
-staged pr-reviewing.ts         ← Bun entrypoint for the tested git/gh core
+`spur builder pr`         ← Bun entrypoint for the tested git/gh core
 ```
 
 - **State order and guards** are defined once, in the workflow YAML. Do not re-derive them in
@@ -128,44 +128,43 @@ root causes rather than wording, prefer the smallest coherent patch, avoid drive
 ## Workflow-backed spine (`full`, `submit`, `rerun`)
 
 Run the workflow YAML's declared states in order. Every deterministic state invokes the
-staged entrypoint below, supports `--json`, and must be parsed. Stop at the first red gate and
+`spur builder pr` operation below, supports `--json`, and must be parsed. Stop at the first red gate and
 report its artifact. The canonical installed invocation is:
 
 ```sh
-node "$(superskill script path sp pr-reviewing.mjs)" <subcommand> [flags]
+spur builder pr <subcommand> [flags]
 ```
 
-Installed targets resolve the staged `.mjs` twin and execute it with Node, matching the standard
-superskill script contract.
+The installed Spur CLI owns these operations; no staged script, Node twin or plugin resolver is used.
 
-1. **Preflight** — `<script> preflight --base "$base" --json`. Hard-fails on a
+1. **Preflight** — `spur builder pr preflight --base "$base" --json`. Hard-fails on a
    detached HEAD, missing `gh` auth, no GitHub remote, a dirty tree, or the current branch
    being the base branch (a PR reviews a feature branch against the base; nothing on the
    base branch is reviewable, and the guard runs before any push can publish it). On a
    dirty tree, triage with the user (commit/stash/exclude) before continuing — the
    workflow refuses to guess.
-2. **Hygiene** — `<script> hygiene --base "$base" --json`. `BLOCK` (secrets, `.env`, conflict markers,
+2. **Hygiene** — `spur builder pr hygiene --base "$base" --json`. `BLOCK` (secrets, `.env`, conflict markers,
    private keys) stops the run — never submit a tainted diff. `WARN` (debug residue) rides along
    into the report. This is a submission sanity check, not a second local review.
 3. **Precheck** — if the workflow YAML's `preReviewCmd` var is set, run it; a red check stops the
    run (do not spend a review request on code that fails its own gate). When unset, report that
    pre-review verification was not configured rather than inventing project commands.
-4. **Push** — `<script> push --json`. Normal push only; sets upstream when missing.
-5. **Ensure PR** — `<script> ensure-pr --base "$base" --json`. Reuses the branch's PR; creates with
+4. **Push** — `spur builder pr push --json`. Normal push only; sets upstream when missing.
+5. **Ensure PR** — `spur builder pr ensure-pr --base "$base" --json`. Reuses the branch's PR; creates with
    `gh pr create --fill` only when absent. Never a duplicate PR.
-6. **Request** — `<script> request --focus "<focus>" --json` (`--force` in `rerun` mode). Dedupes when
+6. **Request** — `spur builder pr request --focus "<focus>" --json` (`--force` in `rerun` mode). Dedupes when
    Codex already reviewed the exact pushed HEAD (`ALREADY_REVIEWED` → skip to collect) or a marked
    request by the current GitHub user is still in flight (`ALREADY_REQUESTED` → pending). The
    request body is concise when the repo has `## Code Review Rules`, else carries the default
    actionable-issues focus. Records PR, URL, HEAD, and request time.
 7. **Wait** (full/rerun unless `--no-wait`; submit stops before it) —
-   `<script> wait --since "$requestedAt" --head "$requestHead" --json`, using the request result so
+   `spur builder pr wait --since "$requestedAt" --head "$requestHead" --json`, using the request result so
    a fast response is not missed, `rerun` cannot reuse the prior review, and a moved HEAD fails loud.
    Polls every ~30s for up to
    ~10 minutes across the current HEAD's PR review and inline comments. Uncorrelated conversation
    comments are ignored. A current-HEAD clean review is a completed `CLEAN` outcome; findings are
    `FOUND`; timeout or no current-HEAD result is **pending, not failed** — collect later.
-8. **Collect** — `<script> collect --since "$requestedAt" --head "$requestHead" --json`. Normalize
+8. **Collect** — `spur builder pr collect --since "$requestedAt" --head "$requestHead" --json`. Normalize
    only the requested HEAD and request window; then invoke `status` with the same bounds for
    PR/base/CI/local state. Never turn an absent, stale, or moved-HEAD result into `clean`.
    `--head` is mandatory on wait/collect/status (0771): an empty or missing pin fails loud
@@ -288,7 +287,7 @@ or review requests.
 
 - **Workflow SSOT:** `pr-review.yaml` (seeded by `spur init`; tune per project —
   wait budget, `preReviewCmd`, dedupe policy)
-- **Script source:** [scripts/pr-reviewing.ts](../../scripts/pr-reviewing.ts) — subcommand CLI
-- **Tests:** [tests/pr-reviewing.test.ts](../../tests/pr-reviewing.test.ts) — stubbed git/gh suites
+- **Script source:** `spur builder pr` (absorbed; was `plugins/sp/scripts/pr-reviewing.ts`) — subcommand CLI
+- **Tests:** `packages/app/tests/services/pr-review/pr-review.test.ts` — stubbed git/gh suites
 - **Related skills:** `sp:code-verification` (local SECUA review), `sp:functional-review`
   (requirements traceability) — complements, never substitutes, the independent Codex review

package/plugins/sp/skills/reverse-engineering/SKILL.md

@@ -201,7 +201,6 @@ Audit categories:
 | Analysis Date | YYYY-MM-DD |
 | Target | `path` |
 | Mode / Focus / Format | `briefing` / `[focus]` / `markdown` |
-| Confidence | High / Medium / Low |
 
 ## Purpose Hypothesis
 
@@ -209,8 +208,8 @@ Audit categories:
 
 ## Tech Stack
 
-| Layer | Technology | Evidence | Confidence |
-|---|---|---|---|
+| Layer | Technology | Evidence |
+|---|---|---|
 
 ## Entry Points
 
@@ -282,7 +281,6 @@ Use this shape for `--format json` or `--format both`. Omit fields only when the
   "analysisDate": "YYYY-MM-DD",
   "mode": "architecture",
   "focus": "all",
-  "confidence": "high|medium|low",
   "stack": [],
   "entryPoints": [],
   "components": [],
@@ -301,7 +299,7 @@ Use this shape for `--format json` or `--format both`. Omit fields only when the
 - Cite `file/path:line` for claims derived from source files.
 - Cite manifest paths for stack and package manager claims.
 - Cite multiple files for architectural boundary claims when possible.
-- Mark inferred claims with `Confidence: Medium` or `Confidence: Low`.
+- Mark inferred claims `Inferred:` and name the evidence that would confirm them; no confidence label (ADR-138).
 - Never invent services, databases, tables, endpoints, actors, diagrams, or business flows that are not supported by evidence.
 - If line numbers are unavailable from a tool, cite the file path and state that line numbers were not available.
 
@@ -339,7 +337,7 @@ The indexed-context layer is optional and opportunistic.
 |---|---|
 | Empty/minimal codebase | Return `briefing` with "insufficient evidence", list missing artifacts, suggest next files needed. |
 | Monorepo | Identify packages/apps; ask for scope unless `--auto` or requested mode can safely summarize all packages. |
-| No clear entry point | List candidates with confidence and evidence; do not choose one as definitive. |
+| No clear entry point | List candidates with their evidence; do not choose one as definitive. |
 | Binary-heavy repo | Focus on manifests, scripts, config, docs, and visible source. |
 | Generated/vendor-heavy repo | Exclude generated/vendor paths from architecture conclusions unless directly relevant. |
 | Framework convention over configuration | State inferred convention and cite framework-specific file patterns. |

package/plugins/sp/skills/session-review/SKILL.md

@@ -90,15 +90,15 @@ issues with its evidence. Notes stay report-only.
 
 1. **Resolve scope.** Review the active session from the operator's initiating request through the
    latest result. Use `[focus]` only to rank relevant material. Measure it with
-   `node "$(superskill script path sp session-timeline.mjs)" --group "<ranges>"`: one segment per
+   `spur history timeline --group "<ranges>"`: one segment per
    operator prompt, read-only from the host transcript. Run it once without `--group` to list the
    segments, then map them to stages (`"1-3,4,5-6"`). It splits each segment into `work` and
    operator `wait` (idle before the next prompt plus AskUserQuestion answer time) and counts tokens
    once per message id. On pi the transcript is `$PI_SESSION_FILE` (pass it as `--transcript` when
    the run reports no host session id). **A measurement that returns `segments: []` with zero totals
    while the session had operator prompts is an unreadable or stale adapter, not an empty session:**
-   compare the installed copy against this tree's `plugins/sp/scripts/session-timeline.mjs` and
-   refresh it with `superskill install sp` before reporting numbers; report `n/a` until then.
+   check `spur --version` against this tree's release and upgrade the CLI before reporting
+   numbers; report `n/a` until then.
    The transcript resolves from `--transcript`, else `CLAUDE_CODE_SESSION_ID`, else `PI_SESSION_FILE`
    (the pi host sets it and no Claude session id); with none of them the measurement reports
    `available:false` with a reason and the table renders `n/a` instead of guessing. A pi
@@ -149,39 +149,23 @@ step 4 excludes. Use `n/a` for any value not supported by the measurement.
 
 ### Resolved issues
 
-| Issue | Root cause | Resolution | Evidence | Confidence |
-| --- | --- | --- | --- | --- |
+| Issue | Root cause | Resolution | Evidence |
+| --- | --- | --- | --- |
 
 Evidence names the tool result, verification command, or concrete repository state visible in the
 session. Do not list ordinary implementation steps as issues.
 
-**Confidence** is `HIGH`, `MEDIUM`, or `LOW` for that row's claim. The level is **derived from the
-check that produced the claim, never assessed from how the row reads**, and the cell carries that
-verifier (e.g. `HIGH — gate exit 0, /tmp/g0.log re-run this session`). Add the row's **falsifier**
-when the level is not `HIGH`: what would have made it fail, or what moves it up. The same ladder
-grades this report's Open-issues table.
-
-| Level | Verifies when | Not this |
-| --- | --- | --- |
-| `HIGH` | An executed check in this session produced the result and its raw output is reachable (command + exit code, test counts, query row, gate log). Re-runnable now. | The code or change "looks correct"; a claim asserted only in prose. |
-| `MEDIUM` | The claim is inferred from observed facts, rests on prior-session or delegated evidence, or names state that moved after the check (stale by construction). Name which of the three. | Presenting an inference as an observation. |
-| `LOW` | No executable check was run. Name the missing evidence **and** the command that would ground it. | Dropping the row instead of marking it. |
-
-Two guards against level inflation:
-
-- Evidence that cannot be re-run, or that is only the agent's own summary, **caps the row at
-  `MEDIUM`** — a re-run is what promotes it.
-- An all-`HIGH` multi-finding review is a signal the ladder was not applied, not a clean session.
-  Where every row genuinely is `HIGH`, the cells show distinct check results rather than repeated
-  phrasing.
-
-Any API/library statement in a row cites the installed source as `path:line` or a URL, and a claim
-the session could not ground is written `LOW` with the missing evidence named.
+**Evidence is the check, not a grade** (ADR-138). A row resolved by an executed check this session
+names the command and its result (e.g. `gate exit 0, /tmp/g0.log`). A row resting on inference,
+prior-session or delegated evidence says so. A row with no check run names the missing evidence
+**and** the command that would ground it — never drop the row instead. No HIGH/MEDIUM/LOW label:
+a self-assigned level is as easy to write as the claim. Any API/library statement in a row cites
+the installed source as `path:line` or a URL.
 
 ### Open issues and risks
 
-| Issue or risk | State | Evidence or confirmation needed | Confidence |
-| --- | --- | --- | --- |
+| Issue or risk | State | Evidence or confirmation needed |
+| --- | --- | --- |
 
 ### Process and environment improvements
 

package/plugins/sp/skills/source-driven-development/SKILL.md

@@ -55,27 +55,28 @@ Do **not** use this skill for:
 
 - **Your own code's correctness** — that is `sp:code-verification` (requirements/AC) and `sp:code-review`.
 - **Stress-testing a design decision** — that is `sp:doubt-driven-development` (artifact vs contract).
-- **Well-known, version-stable stdlib** you can state with HIGH confidence — verification has a cost;
+- **Well-known, version-stable stdlib** you have already checked — verification has a cost;
   spend it where being wrong is likely and expensive.
 
 ## The process
 
-### Step 1 — Classify your confidence before you write
+### Step 1 — Know where each fact came from before you write
 
-| Level | Meaning | Action |
-|---|---|---|
-| **HIGH** | Verified against the pinned version's docs/source **this session** | Generate; cite the source inline |
-| **MEDIUM** | Recalled from a prior session; plausibly stale | Verify before relying on it |
-| **LOW** | Memory only, no source in hand | Stop — verify first; never present as fact |
+| Source in hand | Action |
+|---|---|
+| Checked against the pinned version's docs/source **this session** | Generate; cite the source inline |
+| Recalled from a prior session; plausibly stale | Verify before relying on it |
+| Memory only, no source in hand | Stop — verify first; never present as fact |
 
-If you cannot honestly claim HIGH for a version-specific behavior, you are at MEDIUM or LOW — verify.
+Do not grade the claim with a confidence label (ADR-138): a label is as easy to write as the claim.
+The citation is the evidence.
 
 ### Step 2 — Go to the primary source, in priority order
 
 1. The **type signature / source** in the installed, pinned dependency (the ground truth for *this* build).
 2. The **official docs for the pinned version** (not the latest — the version in the lockfile).
 3. Authoritative references when docs are thin.
-4. Memory — **LOW only**, and never as the final authority.
+4. Memory — never the final authority; verify before relying on it.
 
 State the **version** inline whenever behavior is version-specific.
 
@@ -91,37 +92,36 @@ Generate the code and **cite the source** (doc URL + date, or `pkg@version` + th
 point of use or in the task's notes. A claim about external behavior without a citation is
 unverified — flag it as such rather than presenting it as fact.
 
-### Step 5 — Close with a verification verdict
-
-Before finishing, verify the citations for the API/library claims you emitted and close with one
-line: `Verification: HIGH|MEDIUM|LOW — <first failing check and deviation, or 'all checks passed'>`.
+### Step 5 — Check the citations before finishing
 
 - **Citation coverage** — every API/library claim in the output carries a source citation (doc URL + date, or `pkg@version` + file/symbol); no uncited claim is asserted as fact.
 - **Source authority** — each citation points at the pinned version's primary source (installed signature/source, or official docs for the lockfile version), not the latest docs or memory.
-- **Honest confidence** — the stated HIGH/MEDIUM/LOW matches the evidence: HIGH requires a check against the pinned source this session; MEDIUM/LOW items are labeled, and LOW is never presented as fact.
-- **HIGH** — all three checks pass. **MEDIUM** — coverage intact but some citations are off-version (latest docs for a pinned dependency) or secondary-source only. **LOW** — an API/library claim lacks any citation, or a LOW-confidence claim was asserted as fact.
 
-Deterministic backstop: the `cited-version-strings`, `cited-api-claims` and
-`cited-api-claims-confidence` rules (`.spur/rules/docs/sourced-api-claims.yaml`) flag markdown lines
-that assert a version string or a time-anchored API claim with no citation anchor on the same line,
-and claim lines that carry no HIGH/MEDIUM/LOW level. They are an info-severity advisory backstop for
-this contract and are deliberately NOT wired into `recommended-pre-check` — run them ad hoc with
-`spur rule run --file .spur/rules/docs/sourced-api-claims.yaml`. The checks above and the SECUA
-checklist remain the enforcement points.
+Report the first failing check and its deviation, if any. Do not append a confidence verdict.
+
+Deterministic backstop: the `cited-version-strings` and `cited-api-claims` rules
+(`.spur/rules/docs/sourced-api-claims.yaml`) flag markdown lines that assert a version string or a
+time- or version-anchored API claim (`deprecated since`, `removed in 0.9`, `fixers (since 0.3.4)`)
+with no citation anchor on the same line. They are an info-severity advisory
+backstop for this contract and are deliberately NOT wired into `recommended-pre-check` — run them ad
+hoc with `spur rule run --file .spur/rules/docs/sourced-api-claims.yaml`. Dated working records
+(`docs/report*`, `docs/dogfood`, `docs/plans`, `docs/analysis`) are excluded, as are the task
+archives: a version measured by a past run is not an authorable claim. The checks above and the
+SECUA checklist remain the enforcement points.
 
 ## Common Rationalizations
 
 | Rationalization | Reality |
 |---|---|
-| "I've used this API a hundred times — I know the signature." | APIs change across versions and your memory is a silent cache. Verify against the *pinned* version; recall is MEDIUM at best. |
+| "I've used this API a hundred times — I know the signature." | APIs change across versions and your memory is a silent cache. Verify against the *pinned* version; recall is not a source. |
 | "It compiled, so I used it right." | Compiling proves existence and types, not contract. Ordering, preconditions, and error modes are not checked by the compiler. |
 | "The latest docs say so." | You ship against the *pinned* version, not latest. Read the docs for the version in the lockfile. |
 | "Close enough — I'll fix it if it breaks." | Guessing at an external contract moves the cost to runtime/production. Verify before generating; it is cheaper here. |
-| "Verifying every call is too slow." | Verify what you are *not sure of*, at the confidence level you honestly hold. HIGH needs no re-check; LOW always does. |
+| "Verifying every call is too slow." | Verify what you have no source for. A fact checked this session needs no re-check; memory always does. |
 
 ## Red Flags
 
-- Generating version-specific code you would rate MEDIUM or LOW confidence, without opening a source.
+- Generating version-specific code from memory, without opening a source.
 - Presenting an API claim as fact with no citation (doc + date, or `pkg@version` + symbol).
 - Treating "it exists" as proof it is used correctly (the two questions collapsed into one).
 - Reading the *latest* docs for a dependency pinned to an older version.
@@ -133,8 +133,7 @@ checklist remain the enforcement points.
 - [ ] Every version-specific external behavior relied on was checked against the pinned version's source/docs **this session**.
 - [ ] Both questions answered — the API exists **and** is called within its contract.
 - [ ] Claims about external behavior carry a citation (source + date, or `pkg@version` + symbol); unverifiable ones are flagged, not asserted.
-- [ ] Confidence is stated honestly (HIGH/MEDIUM/LOW); nothing at LOW was presented as fact.
-- [ ] Run closes with the Step 5 verdict line: `Verification: HIGH|MEDIUM|LOW — <first failing check and deviation, or 'all checks passed'>`.
+- [ ] Nothing recalled from memory alone was presented as fact.
 
 ## See also
 

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

@@ -23,7 +23,7 @@ see_also:
 
 # sp:spur-check — the two-tier check primitive (ADR-124)
 
-One check primitive with two tiers behind the shipped `quality-gate` script
+One check primitive with two tiers behind `spur task gate <wbs> <mode>`
 ([task 0939](../../../../docs/tasks5/0939_add-the-two-tier-spur-check-primitive-with-fingerprint-bound.md),
 [workflow catalogue refactor §4](../../../../docs/design/workflow-catalogue-refactor.md)): light
 checks accumulate during development, the full chain runs once at the quality boundary, and every
@@ -33,11 +33,13 @@ gate writes a fingerprint-bound receipt that downstream stages read instead of r
 
 | Tier | Mode | When | Scope |
 | --- | --- | --- | --- |
-| `light` | `quality-gate.ts light` | after each implement/fix edit | `bunx biome check` on the changed files (`git diff --name-only HEAD` + untracked), `bun run typecheck` per touched workspace, and related tests (`<ws>/src/**/x.ts` → `<ws>/tests/**/x.test.ts` filename mapping) run via `cd <ws> && bun test …` — never from the repo root, whose bunfig preload does not apply inside the workspace |
-| `full` | `quality-gate.ts run` | once at the task quality boundary (`test`) | today's chain: `bun run lint` + `bun run test-pre-check` + `bun run test` + `bun run test-post-check` (=`bun run spur-check`), with bounded findings, SQLite-busy retry, and the `recheck` probe |
+| `light` | `spur task gate <wbs> light` | after each implement/fix edit | `bunx biome check` on the changed files (`git diff --name-only HEAD` + untracked), `bun run typecheck` per touched workspace, and related tests (`<ws>/src/**/x.ts` → `<ws>/tests/**/x.test.ts` filename mapping) run via `cd <ws> && bun test …` — never from the repo root, whose bunfig preload does not apply inside the workspace |
+| `full` | `spur task gate <wbs> run` | once at the task quality boundary (`test`) | today's chain: `bun run lint` + `bun run test-pre-check` + `bun run test` + `bun run test-post-check` (=`bun run spur-check`), with bounded findings, SQLite-busy retry, and the `recheck` probe |
 
-Soft-fail contract: both tiers always exit 0; the verdict lives in files (`*-test-gate.status`,
-receipt `status`), never in the exit code.
+Exit contract: `run` and `recheck` return 0 on PASS and 1 on FAIL; `deferred` returns 0 on
+DEFERRED and 1 on FAIL. `light` and `status` return 0; invalid usage returns 2. The pipeline
+wraps selected calls with `; exit 0` and branches on `*-test-gate.status` or receipt `status`;
+that soft shell wrapper does not change the standalone CLI contract.
 
 ## Receipt
 
@@ -59,8 +61,8 @@ receipt `status`), never in the exit code.
 - `inputDigest` is the shared `ProofInputFingerprint` (task markdown + git tree of tracked
   sources). The plugin never computes it — the pipeline captures it with the `proof.fingerprint`
   action into `env.proofDigest` (ADR-124: no second fingerprint, no `@gobing-ai/*` import);
-  standalone callers use `inline-run-setup.ts --fingerprint`.
-- Only `run`/`full` writes a reusable receipt. Without a digest, `run` writes no receipt and says
+  standalone callers use `spur workflow inline fingerprint`.
+- `run` and `recheck` write full-tier receipts; only a PASS at the current digest is reusable. Without a digest, `run` writes no receipt and says
   so in the gate log. The gate executes `qualityGateCmd` as one unit, so the full receipt carries a
   single `test` row for the whole chain; `lint`, `typecheck`, `test-pre-check`,
   `test-post-check` name the chain steps the full tier covers.
@@ -70,12 +72,11 @@ receipt `status`), never in the exit code.
 
 ## Reuse rule
 
-Check `status` mode before re-running a gate. Resolve the shipped script through the superskill
-runtime (shipped surfaces never hard-code repo paths):
+Check `status` mode before re-running a gate. The gate ships inside the CLI (no plugin script to
+resolve):
 
 ```bash
-QG="$(superskill script path sp quality-gate.mjs)"
-bun "$QG" status   # env: wbs, proofDigest → prints {"reuse":…,"reason":…}
+spur task gate <wbs> status --proof-digest "$proofDigest" --no-logo   # final stdout line: {"reuse":…,"reason":…}
 ```
 
 `reuse: true` only when the receipt is `status: PASS`, `tier: full`, and `inputDigest` equals the
@@ -103,8 +104,8 @@ preserved by construction. `recheck` stays the no-progress probe path for fix lo
 
 ## Gotchas
 
-1. **Never value-import `@gobing-ai/*` into the script** — the plugin standalone contract fails
-   the install; the digest arrives via `env.proofDigest`.
+1. **Keep gate logic in the CLI/application owner** — plugin skills invoke `spur task gate`;
+   they do not restore a script or bundle. The digest arrives via `--proof-digest` or `env.proofDigest`.
 2. **Never run light tests from the repo root** — the workspace `bunfig.toml` preload (coverage,
    thresholds) only applies inside the workspace; `cd <ws> && bun test …` is the contract.
 3. **Light is a filter, not a boundary** — unmapped files (root-level scripts, non-src layouts)

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

@@ -44,7 +44,7 @@ Pick the noun, read its reference. Each Tier A and Tier B reference owns that no
 | **Tier A** | **feature** | Feature tree: author with hierarchical IDs (DD-14), acceptance criteria (Gherkin), status lifecycle, move subtrees, `check --json` | [references/features.md](references/features.md) |
 | **Tier A** | **rule** | Constraint quality gate: run presets, author rules, fine-tune, validate rule files/presets, extend engine | [references/rules.md](references/rules.md) |
 | **Tier A** | **workflow** | Dual-mode workflow runtime: author state-machine / transition-flow workflows, validate, run, read traces | [references/workflows.md](references/workflows.md) |
-| **Tier A** | **builder** | Release plumbing: bump a package (or the `workspace:`-pinned set) with `bump-ver`, delete release tags with `drop-tags`, commit + tag + optional push | [references/builder.md](references/builder.md) |
+| **Tier A** | **builder** | Release/PR plumbing: `bump-ver` (including read-only `--check`), `drop-tags`, `publish`, and `pr` review operations | [references/builder.md](references/builder.md) |
 | **Tier B** | **agent** | Coding-agent execution surface: run prompts via detected/named agents, list agent specs (incl. `agent.fleet` members), start/stop supervised processes, fleet `report`/`join`/`leave`/`wait`/`trace`, readiness check | [references/agent.md](references/agent.md) |
 | **Tier B** | **message** | Durable inter-agent messaging: send, inbox, reply, watch | [references/message.md](references/message.md) |
 | **Tier B** | **self** | Self-management verbs: scaffold (`init`), database maintenance (`maintain`), schema migrations (`migrate`), local web server (`serve`), status overview (`status`); `self init` runs post-scaffold validation probes & layout classification | [references/self.md](references/self.md) |