@gobing-ai/spur 0.3.60 → 0.3.62

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
     "plugins": [
         {
             "name": "sp",
-            "version": "0.3.60",
+            "version": "0.3.62",
             "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

@@ -1,16 +1,20 @@
 # 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.
+# 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.
+#   - 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
@@ -18,6 +22,10 @@
 
 $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
@@ -28,26 +36,27 @@ agent:
     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;
+    # 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.
+    # 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.
+    # 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
+    # `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`).
+    # projections (this table, the constant, and
+    # `plugins/sp/references/roles.md`).
     roles:
         scribe:
             tier: cheap
@@ -62,40 +71,42 @@ agent:
             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
+    # 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
+    # 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.
+    # 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.
+    # 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.
+        # 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
@@ -121,13 +132,13 @@ agent:
           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 global workflow tree is already reachable without it: the
-# lifecycle adapter resolves bundled → project `.spur/workflows/` →
-# `~/.config/spur/workflows/` on its own (make-lifecycle-adapter.ts:44).
-# Set it per project when a project keeps workflows somewhere non-standard.
-# workflows:
-#     paths:
-#         - .spur/workflows/
+# `bundled:workflows` resolves against the installed package's own config root
+# at read time (BUNDLED_PATH_PREFIX in apps/cli/src/commands/workflow.ts), so
+# every project discovers the shipped workflows without a machine-specific
+# absolute path ever being persisted here. A project's own `workflows.paths`
+# concatenates over this (loader merge), and the run-time adapter resolves
+# bundled → project on its own (make-lifecycle-adapter.ts, two tiers since
+# task 0648).
+workflows:
+    paths:
+        - bundled:workflows