@gobing-ai/spur 0.3.86 → 0.3.88

package/plugins/sp/skills/taste-refactoring-tests/SKILL.md

@@ -1,6 +1,18 @@
 ---
 name: taste-refactoring-tests
 description: Refactor unit tests for failure sensitivity, deterministic confidence, and regression protection without mock-heavy brittle tests or vanity coverage. Backs test suite quality audits.
+license: Apache-2.0
+metadata:
+  author: spur
+  version: "1.0"
+  platforms: "claude-code,codex,openclaw,opencode,antigravity"
+  category: execution
+  interactions:
+    - technique
+  operations:
+    - refactor-tests
+  openclaw:
+    emoji: "🧪"
 ---
 
 # taste-refactoring-tests
@@ -480,3 +492,33 @@ A test refactor is complete only when:
 - delivery speed is not degraded without a justified risk trade-off.
 
 The goal is **earned confidence**: green means something because the suite has demonstrated that it can turn red when the product is wrong.
+
+## Spur contract
+
+Machine-facing adapter for `sp:code-refactoring` dispatch (feature H13). Everything above is the
+lens's native output and is unchanged; this section only maps it to the shared finding schema.
+
+**Inputs received:** a scope path, an optional change description, and the `tests` focus. Read
+first: the intervention ladder, Confidence Contract, and review severity above, then
+`../code-refactoring/references/finding-schema.md` for shared field semantics.
+
+**Native finding → schema mapping:** `ID` → `id` as `RF-tests-<nnn>`; `Action` (T0–T7) → `rung`
+verbatim; `Severity` → `severity` via the map below; `Evidence` → `evidence` as `{file, line}`
+entries inside scope; `Why it matters` → `title`; `Proposed change` → `proposal` (imperative);
+`Expected regression-detection improvement` → folded into `proposal`; new findings start at
+`status: open`.
+
+**Severity mapping (design §5):** native P0 → `P1`; P1 → `P2`; P2 → `P3`; P3 → `P4`.
+
+**Preserved-behavior inventory (required before proposals):** emit the Confidence Contract —
+critical business rules, compatibility contracts, authorization/security decisions, data
+integrity invariants, error semantics, and incident regressions the suite must keep protecting —
+before the first finding.
+
+**Preservation class:** T0 and rungs that keep or add protection (fixture cleanup, adding a
+missing test) → `preserving`; removing a test or test file (T1) → `cutting`; weakening or
+semantically changing existing assertions → `breaking`.
+
+**Stop rules:** unknown protection is a risk, never permission to delete; a `cutting`/`breaking`
+finding is never `fix_eligibility: auto` and never below `P2`; tests are never removed or
+weakened by an `auto` fix; anything outside the scope path is not a finding.

package/plugins/sp/skills/taste-refactoring-ui/SKILL.md

@@ -1,6 +1,18 @@
 ---
 name: taste-refactoring-ui
 description: Design, review, and refactor UI hierarchy, layout, typography, spacing, color, and interactions.
+license: Apache-2.0
+metadata:
+  author: spur
+  version: "1.0"
+  platforms: "claude-code,codex,openclaw,opencode,antigravity"
+  category: execution
+  interactions:
+    - technique
+  operations:
+    - refactor-ui
+  openclaw:
+    emoji: "🎨"
 ---
 
 # taste-refactoring-ui
@@ -288,3 +300,34 @@ For deeper reasoning and daily use, read:
 - `references/refactoring-ui-playbook.md` — chapter-by-chapter distilled guidance.
 - `checklists/daily-ui-review.md` — fast audit and ship checklist.
 - `examples/review-template.md` — reusable UI critique response structure.
+
+## Spur contract
+
+Machine-facing adapter for `sp:code-refactoring` dispatch (feature H13). Everything above is the
+lens's native output and is unchanged; this section only maps it to the shared finding schema.
+
+**Inputs received:** a scope path, an optional change description, and the `ui` focus. Read
+first: the refactoring protocol and output contract above, then
+`../code-refactoring/references/finding-schema.md` for shared field semantics.
+
+**Native finding → schema mapping:** each issue → `id` as `RF-ui-<nnn>`; the pass that owns it
+(hierarchy, spacing, typography, color, states) → `rung`; `Observation` + `Refactor` → `title`
+and `proposal` (imperative); the cited component/file and line → `evidence` as `{file, line}`
+entries inside scope; the `System rule` → folded into `proposal`; new findings start at
+`status: open`.
+
+**Severity mapping (design §5):** native P0 (task failure) → `P1`; P1 (hierarchy/structure) →
+`P2`; P2 (system inconsistency) → `P3`; P3 (polish) → `P4`.
+
+**Preserved-behavior inventory (required before proposals):** emit the controls and interactions
+in scope — primary/secondary actions, navigation, form semantics, accessible names, states —
+before the first finding.
+
+**Preservation class:** token normalization and layout/typography consolidation with identical
+function → `preserving`; adding a missing state or a11y attribute → `preserving`; removing or
+merging a control or interaction → `cutting`; changes to user-visible flows or behavior →
+`breaking`.
+
+**Stop rules:** meaning is never carried by color alone; preserve component semantics and
+accessibility; a `cutting`/`breaking` finding is never `fix_eligibility: auto` and never below
+`P2`; anything outside the scope path is not a finding.

package/schemas/spur-config.schema.json

@@ -167,8 +167,20 @@
                                 "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)."
+                                "description": "Routing kill-switch (111; ownership widened 0890): a disabled profile never serves a role, team, stage, or explicit selection, and doctor inventories it without probing. Omitted = enabled. Bare `true` is operator-owned (only humans write booleans); automatic writers emit the object form carrying owner (operator|quota|probe), since (RFC 3339) and reason.",
+                                "anyOf": [
+                                    { "type": "boolean" },
+                                    {
+                                        "type": "object",
+                                        "additionalProperties": false,
+                                        "required": ["owner", "since", "reason"],
+                                        "properties": {
+                                            "owner": { "enum": ["operator", "quota", "probe"] },
+                                            "since": { "type": "string", "format": "date-time", "minLength": 1 },
+                                            "reason": { "type": "string", "minLength": 1 }
+                                        }
+                                    }
+                                ]
                             }
                         }
                     }

package/schemas/task-batch.schema.json

@@ -20,7 +20,7 @@
             },
             "requirements": {
                 "type": "string",
-                "description": "R-numbered requirement items (R1. R2. …) — a referenceable list."
+                "description": "Pre-filled ### Requirements body: one R-item per line, exactly `- [ ] R1. <text>` (checkbox + `R<n>.`); any other form fails `spur task check`."
             },
             "design": {
                 "type": "string",
@@ -32,7 +32,7 @@
             },
             "acceptance_criteria": {
                 "type": "string",
-                "description": "Pre-filled ### Acceptance Criteria body (Gherkin or checklist)."
+                "description": "Pre-filled ### Acceptance Criteria body: items numbered AC1, AC2, … (never R<n>, the Requirements namespace): `- [ ] AC1 — <feature scenario title without its R-number>` bullets or `Scenario: AC1 — <title>` blocks (L4.uncovered-task-scenario matches the title after the prefix); `(req: R<n>)` binds a task requirement; task-only checks go in prose after the bullets."
             },
             "feature_id": {
                 "type": "string",