@gobing-ai/spur 0.4.21 → 0.4.23

package/plugins/sp/skills/spur-dev/references/execution-worktree-setup.md

@@ -352,7 +352,7 @@ fingerprints the invoking tree for the same reason (its own step 1b).
   [ "$(git branch --show-current)" = "$BRANCH" ] \
     || { echo "branch mismatch: expected $BRANCH, got $(git branch --show-current)" >&2; exit 1; }
   RUN_ID="<marker-id>"   # the WT-3 marker's id — the same id WT-3b's stage call uses
-  spur workflow commit-guard start --run "$RUN_ID"   # <worktree>/.spur/run/$RUN_ID-tree-start.json = { head, dirty[] }
+  spur workflow commit-guard-start --run "$RUN_ID"   # <worktree>/.spur/run/$RUN_ID-tree-start.json = { head, dirty[] }
 )
 ```
 
@@ -368,8 +368,8 @@ same call, verifies the WT-3 identity, and never relies on a persistent `cd` or
   cd -- "../<worktree-dir>" || { echo "tree missing: expected ../<worktree-dir>" >&2; exit 1; }
   [ "$(git branch --show-current)" = "$BRANCH" ] \
     || { echo "branch mismatch: expected $BRANCH, got $(git branch --show-current)" >&2; exit 1; }
-  spur workflow commit-guard check --run "$RUN_ID"        # 1129 R3: concurrent foreign writers; a non-empty list goes in the batch report
-  spur workflow commit-guard stage --run "$RUN_ID" -- <files-the-batch-wrote> \
+  spur workflow commit-guard-check --run "$RUN_ID"        # 1129 R3: concurrent foreign writers; a non-empty list goes in the batch report
+  spur workflow commit-guard-stage --run "$RUN_ID" -- <files-the-batch-wrote> \
     || { echo "WT-3b halt: commit-guard refused a path (foreign, unmerged or conflict-marked); nothing committed" >&2; exit 1; }
   git commit -m "<type>(<scope>): <command> <selector> batch writes"
 )
@@ -377,7 +377,7 @@ same call, verifies the WT-3 identity, and never relies on a persistent `cd` or
 
 > **Forbidden in every driver commit step:** `git add -A` and `git add .`. They stage whatever a
 > concurrent writer happened to leave in the tree — the two incidents this guard exists for are
-> `a94f9f431` and `36f274590` — so a driver stages only through `spur workflow commit-guard stage`.
+> `a94f9f431` and `36f274590` — so a driver stages only through `spur workflow commit-guard-stage`.
 
 > **`stage` takes files, never directories.** A directory argument is refused as `(unchanged since
 > base)` and stages *nothing*, so a task whose diff lives in a moved tree must expand the changed

package/plugins/sp/skills/wayfinder/SKILL.md

@@ -142,6 +142,8 @@ Invoked when a map already exists (operator provides the feature ID). A ticket i
    | **Prototype** | Cheap, rough, concrete artifact to react to — an outline, stub, or rough implementation via `sp:code-implementation`. | Linked prototype as a task artifact |
    | **Task** | Literal manual work — nothing to prototype or research. Moving data, provisioning access. | Checklist in task body; resolved when done |
 
+   **Search routing** (hybrid search, ADR-147): concept, cross-file, or "how does X work" questions → semantic first — the zg MCP tool `zvec_grep_search` when the host exposes it, else `spur self search "<query>" --mode fuzzy --json`. Literal, symbol, regex, or exhaustive occurrence lists → `rg`. If zg is absent or the search response carries a `skipped` reason → fall back to `rg`.
+
    An open question from the map is **not** resolved this way. It is settled with the operator in
    conversation (`AskUserQuestion` where available) and recorded straight into **## Decisions so far**
    — no task is claimed, and it does not consume the session's one ticket.