@iowarp/clio-coder 0.4.3 → 0.4.5

package/skills/planning/prd/SKILL.md

@@ -7,7 +7,7 @@ triggers:
   - define this feature
   - structure this product brain dump
   - create milestone prompts
-version: 0.4.0
+version: 0.4.1
 license: Apache-2.0
 allowed-tools:
   - read
@@ -50,8 +50,9 @@ the user saying so. Markdown only, no external templates, repo-aware.
   own prompt — let the user describe the idea raw — rather than an invented
   idea.
 
-There is no operator in a headless run: `ask_user` is either not registered
-or nothing answers it, and stalling a gate to wait for it never resolves.
+There is no operator in a headless run: `ask_user` is not registered, so
+any call is refused as an unregistered tool rather than answered, and
+stalling a gate to wait for it never resolves.
 When a gate goes unanswered, do not skip the phase and do not go quiet: run
 it as a monologue instead — state the phase's question, your
 recommendation (grounded in the repo and any evidence read, or the most

package/skills/planning/product-intent/SKILL.md

@@ -7,7 +7,7 @@ triggers:
   - problem-first PRD
   - define a falsifiable product hypothesis
   - greenfield product intent
-version: 0.4.0
+version: 0.4.1
 license: Apache-2.0
 allowed-tools:
   - read
@@ -50,10 +50,10 @@ decisions (library, data model, boundaries) never enter it; they belong to
 - Nothing is required beyond some text; a blank invocation gets Step 0's own
   "What do you want to build? A few sentences." question.
 
-There is no operator in a headless run: `ask_user` still executes, but with
-nothing to answer it every call returns immediately with no answers, every
-time — calling it again will not produce a different result. Treat the
-first empty response exactly like the user saying "just write it" (see "If
+There is no operator in a headless run: `ask_user` is not registered, so
+any call is refused as an unregistered tool rather than answered, every
+time; calling it again will not produce a different result. Treat the
+first refusal exactly like the user saying "just write it" (see "If
 the user declines the interview" below), and apply that treatment from
 wherever it happened onward — Step 0's evidence check included, not just
 the five clusters: state the question, your best evidence-grounded answer
@@ -89,8 +89,8 @@ the same turn. Thin answers get reflected back and dug into.
 If the user declines the interview ("just write it"): honor it, name what
 you will have to leave TBD, ask only the two or three highest-leverage
 questions, and mark everything else "TBD — needs validation". This is also
-the headless default: see Arguments above for what an empty `ask_user`
-response means and how to apply this same treatment cluster by cluster
+the headless default: see Arguments above for what a refused `ask_user`
+call means and how to apply this same treatment cluster by cluster
 instead of stopping after the first one.
 
 1. **Initiate.** Input given → restate and confirm. Blank → "What do you
@@ -159,7 +159,7 @@ outcome-shaped metrics · explicit non-goals · zero engineering decisions.
   counter-signal.
 - The literal filename `PRD.md`, or anything outside `docs/`, instead of
   `docs/<kebab-slug>.prd.md`.
-- Calling `ask_user` again after an empty response, instead of switching to
+- Calling `ask_user` again after a refusal, instead of switching to
   the decline treatment for every step from there on.
 - Opening a task list for the interview clusters; `tasks` is refused.
 - Reaching Generate without ever attempting Step 0 or the first cluster —

package/skills/planning/tech-spec/SKILL.md

@@ -7,7 +7,7 @@ triggers:
   - code-shaped contracts
   - implementation-ready technical specification
   - specify execution flows
-version: 0.3.0
+version: 0.3.1
 license: Apache-2.0
 disable-model-invocation: true
 allowed-tools:
@@ -63,9 +63,9 @@ and save a file only when the user asks; otherwise return the spec inline.
   installed to reference in the TDD Test Plan section; both are frontmatter
   facts, not something to explain to the user unless asked.
 
-There is no operator in a headless run: `ask_user` either isn't registered
-or nothing answers it, and a call that goes unanswered will not resolve
-differently on a second try. In Path B (below), that means: state the
+There is no operator in a headless run: `ask_user` is not registered, so
+any call is refused as an unregistered tool rather than answered, and a
+second try will not resolve differently. In Path B (below), that means: state the
 question, your recommendation grounded in the codebase and any docs read
 (or the most defensible engineering default when nothing grounds it), and
 the reasoning; adopt the recommendation; mark it `assumed — confirm`; move

package/skills/registry.yaml

@@ -1,5 +1,5 @@
 # Pinned marketplace skill content hashes (provenance-stripped sha256).
-# Generated by `npm run skills:pin`. At activation, an installed skill
+# Generated by `pnpm run skills:pin`. At activation, an installed skill
 # carrying registry-id provenance is compared against its pinned hash;
 # a mismatch surfaces a drift warning.
 skills:
@@ -10,8 +10,8 @@ skills:
     sha256: 0a72f4c906303f550be78f80a927da7e24e5c2076f058ccafdec80dfbed275af
   - name: coding-standards
     path: coding/coding-standards
-    version: 0.3.0
-    sha256: 3ee3481430591a8f8d041bd1c5fa078becd301d88eb49610e41d056494d3413d
+    version: 0.4.0
+    sha256: d573cdc5b430ae94ebfb5ef69c4a0ac9ac074aae815959ab4e6515012846ce3b
   - name: prototype
     path: coding/prototype
     version: 0.4.0
@@ -23,12 +23,12 @@ skills:
   # ── context ──
   - name: context-handoff
     path: context/context-handoff
-    version: 0.5.0
-    sha256: e69adb1533a6a850cb83babe7e580dd260e034781d7c35e65921453e3fa191a5
+    version: 0.5.1
+    sha256: e05a8dc9d09b4decbf79afade1f530d7c81d5412112723faab104a83893c34f8
   - name: context-prime
     path: context/context-prime
-    version: 0.4.0
-    sha256: 21587263297a7ee9e81a2d66f6fc800a1ee6db15f76de1e650563b71fdf19d8e
+    version: 0.4.1
+    sha256: 3e6783d3fd95bd5635fe274ea0b9f73f3c4606ce64b832524cc242b114d8ef12
   # ── git ──
   - name: branch-closeout
     path: git/branch-closeout
@@ -90,55 +90,55 @@ skills:
     sha256: d9e891eb5f3c27678de14165a0eb35d1eb2289be480e55009f9a57bcfe55be2d
   - name: architecture
     path: planning/architecture
-    version: 0.4.0
-    sha256: e9017412b6261492b987fe27f7573b72013a340c0d3eb0e7e568fd588b22a214
+    version: 0.4.1
+    sha256: 0d62ded74021d148f3091e044c32d205edfa3d1298706e68c84ad0f032d0feba
   - name: backlog
     path: planning/backlog
-    version: 0.4.0
-    sha256: e634e2fb5035731e7daa2ef246ae4ab3ef5d792b0b604f4216dfe10335ee10c0
+    version: 0.4.1
+    sha256: 8fc700ad8f1b2f44fb6ea013c54ce06314cf9c4fdee63bd65c36686f5c25d092
   - name: prd
     path: planning/prd
-    version: 0.4.0
-    sha256: 39fe417f495be4153541dd70c886cf773265636dc9fa1844cfc7012b71cbbec1
+    version: 0.4.1
+    sha256: 3841f2f9635229c8208382e40123de1b5a496ec562cb851758d2ac013921c069
   - name: product-intent
     path: planning/product-intent
-    version: 0.4.0
-    sha256: d41689db9a8c9b2dad0cd630412bebaed5792f9d22d4edb18770e4b1b3308699
+    version: 0.4.1
+    sha256: 95d629fe8688003a9816a0774674f0c9fd5a922a82835415c3c1806799436832
   - name: tech-spec
     path: planning/tech-spec
-    version: 0.3.0
-    sha256: 5f9add0d01e43feb6808b2eaeae9ac68075cf369cbfc793e020181a642d4d2c4
+    version: 0.3.1
+    sha256: e8e6a1326aeb8b010647fc9fa9dc5ff827e13550f54524555f5e6a83341eb27f
   # ── research ──
   - name: arxiv-literature
     path: research/arxiv-literature
-    version: 0.5.0
-    sha256: 0bc6b39d12934568804fc11b23219de4c6c2172e28c4bfedcee3104e2217aae6
+    version: 0.5.1
+    sha256: 4668827aa0f13527de5fc34914911ef942d2103ed3d139008fbd1c0ce2c4bd3d
   - name: experiment-protocol
     path: research/experiment-protocol
-    version: 0.3.0
-    sha256: 235256cbdf44ebdd25d87cce60940e00ad1fca42a1b2b4e534bfc245f0d1135c
+    version: 0.3.1
+    sha256: da151931fb1961b19fcb6d4ae1957cef908f8b35692e301f109125488ad65302
   - name: scientific-debugging
     path: research/scientific-debugging
-    version: 0.3.0
-    sha256: 9c29d70b4b82a440640b41665c23731b4112125915bde0e91016fc60aec67207
+    version: 0.3.1
+    sha256: ba94f8ad2655396a3791c7599631513f16651ffa61c8148044b996a25c0bc1cc
   - name: scientific-modernization
     path: research/scientific-modernization
-    version: 0.4.0
-    sha256: 491522d547fa0bddef19d2ec92bc35236b169787bded6ecc3a29dfec19892886
+    version: 0.4.1
+    sha256: eb31099d764cba913c19726f6ba85d7081c5e01c81a3b2cd45eb136a4e47b858
   # ── workflow ──
   - name: cut-it
     path: workflow/cut-it
-    version: 0.4.0
-    sha256: d3742221f0ace1f1b62c07f5902030e478496059a58ef194e7cb3303ccdff05e
+    version: 0.4.1
+    sha256: d0ce7dc6ea633d87e9e68c6b59ad402c24644b9eac580774410b235e0ca1c93f
   - name: design-council
     path: workflow/design-council
-    version: 0.5.0
-    sha256: c279a94a4cd66d46980f9a5024aedac3e673144fadc9d36b53ad87fc2ee63501
+    version: 0.6.0
+    sha256: 42fbf2e54524253b2955b22576ae0aca998dc04a902b8a59440edcfd051e0f5a
   - name: grill-me
     path: workflow/grill-me
-    version: 0.5.0
-    sha256: f48687566a8419aa52f30f8234f8dcfd050eaefdfdcfa281723d3603f3e08fcc
+    version: 0.5.1
+    sha256: 3844770b507f9b2904aaa5c944c2b26f9ecf114383758dfff3bd7f39b2c717a6
   - name: workflow-distiller
     path: workflow/workflow-distiller
-    version: 0.4.0
-    sha256: dd7c312d6904f861fa105334c7c2f18c9d6e26a70a76874c85858cee90bede58
+    version: 0.4.1
+    sha256: 067b097299b0b630729a4a6ddde629dec5c798d5b4634f90f7feab380b8575e1

package/skills/research/arxiv-literature/SKILL.md

@@ -7,7 +7,7 @@ triggers:
   - compare these papers
   - find recent research papers
   - build a literature survey
-version: 0.5.0
+version: 0.5.1
 license: Apache-2.0
 allowed-tools:
   - web_fetch
@@ -40,8 +40,8 @@ immediately; only paper cards reach the user.
 ```
 
 The request is free text: a paper URL/ID, a topic, or two or more IDs to
-compare. There is no operator in a headless run — `ask_user` is not in this
-skill's tool surface and nothing answers it. If the request is ambiguous (no
+compare. There is no operator in a headless run: `ask_user` is not registered, so
+any call is refused as an unregistered tool rather than answered. If the request is ambiguous (no
 clear topic, an ID that doesn't resolve), state your best reading and
 proceed; never stall waiting for clarification. `tasks` sits outside this
 skill's tool surface and is refused; the steps below are the whole plan, do

package/skills/research/experiment-protocol/SKILL.md

@@ -8,7 +8,7 @@ triggers:
   - define numerical tolerances
   - reproduce these results
   - compare solver accuracy
-version: 0.3.0
+version: 0.3.1
 license: Apache-2.0
 allowed-tools:
   - read
@@ -45,8 +45,8 @@ diagnosis, not an experiment; use scientific-debugging.
 /skill experiment-protocol <what to benchmark, compare, or sweep>
 ```
 
-There is no operator in a headless run — `ask_user` is not in this skill's
-tool surface. If a threshold, tolerance, or environment detail is unstated,
+There is no operator in a headless run: `ask_user` is not registered, so
+any call is refused as an unregistered tool rather than answered. If a threshold, tolerance, or environment detail is unstated,
 pick the most defensible default, record it as an explicit assumption in the
 pre-registration, and proceed; never stall Phase 0 waiting for confirmation.
 

package/skills/research/scientific-debugging/SKILL.md

@@ -8,7 +8,7 @@ triggers:
   - diagnose NaNs
   - debug with falsifiable hypotheses
   - scientific root cause
-version: 0.3.0
+version: 0.3.1
 license: Apache-2.0
 allowed-tools:
   - read
@@ -46,7 +46,8 @@ below is for failures that survived the first obvious fix.
 
 Everything after the skill name is the failure report: the observed wrong
 behavior and whatever has already been tried. There is no operator in a
-headless run — `ask_user` is not in this skill's tool surface. If the goal,
+headless run: `ask_user` is not registered, so any call is refused as an
+unregistered tool rather than answered. If the goal,
 a fault-class split, or a ranking call is ambiguous, state your best reading
 in Step 1 or Step 3 and proceed; never stall a step waiting for confirmation.
 

package/skills/research/scientific-modernization/SKILL.md

@@ -8,7 +8,7 @@ triggers:
   - migrate the scientific build system
   - create a maintained fork
   - preserve scientific parity
-version: 0.4.0
+version: 0.4.1
 license: Apache-2.0
 allowed-tools:
   - read
@@ -42,8 +42,8 @@ has an explicit exit condition.
 /skill scientific-modernization <what to modernize, port, rewrite, or replace, and why>
 ```
 
-There is no operator in a headless run — `ask_user` is not in this skill's
-tool surface. Stage 1's "the user has seen them" exit condition means,
+There is no operator in a headless run: `ask_user` is not registered, so
+any call is refused as an unregistered tool rather than answered. Stage 1's "the user has seen them" exit condition means,
 headlessly: state the four bullets in your reply and proceed, never stall
 waiting for acknowledgment. Every other stage gate below works the same way
 — state the decision and its reasoning, then continue.

package/skills/skill-marketplace.json

@@ -1,5 +1,5 @@
 {
-	"generatedBy": "npm run skills:pin",
+	"generatedBy": "pnpm run skills:pin",
 	"skills": [
 		{
 			"name": "ast-grep",
@@ -27,7 +27,7 @@
 				"functional core imperative shell"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/coding/coding-standards",
-			"version": "0.3.0",
+			"version": "0.4.0",
 			"audit": "pass",
 			"category": "coding"
 		},
@@ -72,7 +72,7 @@
 				"write a continuation brief"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/context/context-handoff",
-			"version": "0.5.0",
+			"version": "0.5.1",
 			"audit": "pass",
 			"category": "context"
 		},
@@ -87,7 +87,7 @@
 				"resume repository work after a break"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/context/context-prime",
-			"version": "0.4.0",
+			"version": "0.4.1",
 			"audit": "pass",
 			"category": "context"
 		},
@@ -316,7 +316,7 @@
 				"compare architecture options"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/planning/architecture",
-			"version": "0.4.0",
+			"version": "0.4.1",
 			"audit": "pass",
 			"category": "planning"
 		},
@@ -331,7 +331,7 @@
 				"create GitHub issues from this architecture"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/planning/backlog",
-			"version": "0.4.0",
+			"version": "0.4.1",
 			"audit": "pass",
 			"category": "planning"
 		},
@@ -346,7 +346,7 @@
 				"create milestone prompts"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/planning/prd",
-			"version": "0.4.0",
+			"version": "0.4.1",
 			"audit": "pass",
 			"category": "planning"
 		},
@@ -361,7 +361,7 @@
 				"greenfield product intent"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/planning/product-intent",
-			"version": "0.4.0",
+			"version": "0.4.1",
 			"audit": "pass",
 			"category": "planning"
 		},
@@ -376,7 +376,7 @@
 				"specify execution flows"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/planning/tech-spec",
-			"version": "0.3.0",
+			"version": "0.3.1",
 			"audit": "pass",
 			"category": "planning"
 		},
@@ -391,7 +391,7 @@
 				"build a literature survey"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/research/arxiv-literature",
-			"version": "0.5.0",
+			"version": "0.5.1",
 			"audit": "pass",
 			"category": "research"
 		},
@@ -407,7 +407,7 @@
 				"compare solver accuracy"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/research/experiment-protocol",
-			"version": "0.3.0",
+			"version": "0.3.1",
 			"audit": "pass",
 			"category": "research"
 		},
@@ -423,7 +423,7 @@
 				"scientific root cause"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/research/scientific-debugging",
-			"version": "0.3.0",
+			"version": "0.3.1",
 			"audit": "pass",
 			"category": "research"
 		},
@@ -439,7 +439,7 @@
 				"preserve scientific parity"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/research/scientific-modernization",
-			"version": "0.4.0",
+			"version": "0.4.1",
 			"audit": "pass",
 			"category": "research"
 		},
@@ -454,7 +454,7 @@
 				"write dependency-ordered vertical slices"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/workflow/cut-it",
-			"version": "0.4.0",
+			"version": "0.4.1",
 			"audit": "pass",
 			"category": "workflow"
 		},
@@ -469,7 +469,7 @@
 				"what would experts say"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/workflow/design-council",
-			"version": "0.5.0",
+			"version": "0.6.0",
 			"audit": "pass",
 			"category": "workflow"
 		},
@@ -484,7 +484,7 @@
 				"clarify this plan one question at a time"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/workflow/grill-me",
-			"version": "0.5.0",
+			"version": "0.5.1",
 			"audit": "pass",
 			"category": "workflow"
 		},
@@ -499,7 +499,7 @@
 				"create a skill from this session"
 			],
 			"sourceUrl": "https://github.com/iowarp/clio-coder/tree/main/skills/workflow/workflow-distiller",
-			"version": "0.4.0",
+			"version": "0.4.1",
 			"audit": "pass",
 			"category": "workflow"
 		}

package/skills/workflow/cut-it/SKILL.md

@@ -7,7 +7,7 @@ triggers:
   - make this plan executable
   - turn this milestone into a sprint
   - write dependency-ordered vertical slices
-version: 0.4.0
+version: 0.4.1
 license: Apache-2.0
 allowed-tools:
   - read
@@ -52,9 +52,8 @@ destination like "write it to docs/SPRINT.md", is Step 3's output location,
 not the input. When neither is named, Step 1 finds the plan and Step 3
 writes to the repo-root default.
 
-This run has no back-and-forth. `ask_user` still executes — it is registered
-and the call succeeds — but nothing answers it in a headless run: every round
-returns `{cancelled: true}` immediately, as an ordinary result, not an error.
+This run has no back-and-forth. `ask_user` is not registered in a headless
+run, so any call is refused as an unregistered tool rather than answered.
 The happy path here rarely needs a question at all — Step 1's "stop and say
 so" for a missing or vague plan is already headless-safe, and Step 3's output
 path defaults without asking. If several plans or milestones are plausible

package/skills/workflow/design-council/SKILL.md

@@ -7,7 +7,7 @@ triggers:
   - get multiple expert perspectives
   - weigh the architecture options
   - what would experts say
-version: 0.5.0
+version: 0.6.0
 license: Apache-2.0
 allowed-tools:
   - dispatch
@@ -52,10 +52,9 @@ argument.
 **Headless is the enforced default, not a suggestion.** A council is several
 worker runs; nobody is waiting between rounds in a headless run, and every
 round that actually runs costs real wall-clock time on top of the
-orchestrator's own turns. `ask_user` still executes here even though it is
-not in the list below — it is always available regardless — but nothing
-answers it: the single question Step 1 asks comes back `{cancelled: true}`
-immediately, as an ordinary result, not an error. Treat that cancellation (or
+orchestrator's own turns. `ask_user` is not registered in a headless run,
+so the single question Step 1 asks is refused as an unregistered tool
+rather than answered. Treat that refusal (or
 skip the call and reason from this paragraph directly — one is not more valid
 than the other) as the fixed answer **quick mode: exactly three perspectives,
 exactly one round (Positions) plus synthesis.** Do not compose four or five
@@ -85,11 +84,7 @@ Declare `intent: {read_roots: [...], relevant_paths: [...]}` with paths
 relative to the repo root on every dispatch call instead of pasting an
 absolute path into `task`/`briefing` prose (a config value, a mount point).
 An absolute path token in briefing/task text with no declared `intent` is
-rejected as `legacy_scope_path_absolute`. Keep a persona's argument in prose,
-never literal shell syntax — a phrase like "you can `rm -rf` the directory"
-inside a dispatch call's text can trip the same damage-control pattern that
-blocks a real destructive shell command, even though nothing executes; say
-"delete the directory" instead.
+rejected as `legacy_scope_path_absolute`.
 
 A dispatch call's own synchronous result already carries every worker's
 output — do not follow it with a `bash`/`read` pass over the receipt file on

package/skills/workflow/grill-me/SKILL.md

@@ -7,7 +7,7 @@ triggers:
   - stress-test this design
   - poke holes in this idea
   - clarify this plan one question at a time
-version: 0.5.0
+version: 0.5.1
 license: Apache-2.0
 allowed-tools:
   - read
@@ -52,13 +52,12 @@ is coming. Ending the turn on an open question — even one question, even a
 well-posed one — is this skill's single most common failure and worse than
 skipping the interview format entirely.
 
-There is no operator in a headless run. `ask_user` still executes — it is
-registered and the call succeeds — but nothing answers it: every round
-returns `{cancelled: true}` immediately, as an ordinary result, not an
-error, every time, with no exceptions. Calling it again will not produce a
-different result, so one call is enough to confirm it (not required —
-reasoning from this paragraph alone is just as valid as calling it and
-observing the cancellation). Whichever phase this lands in — even round
+There is no operator in a headless run: `ask_user` is not registered, so
+any call is refused as an unregistered tool rather than answered, every
+time, with no exceptions. Calling it again will not produce a different
+result, so one call is enough to confirm it (not required: reasoning from
+this paragraph alone is just as valid as calling it and observing the
+refusal). Whichever phase this lands in — even round
 1 — switch immediately to the assumed-confirm monologue for every phase
 from here on, in the same turn: state the question you would have asked,
 give your own best/recommended answer with the reasoning behind it, mark
@@ -160,7 +159,7 @@ If an answer is vague, ask a follow-up on the same branch. Do not jump to a new
 branch while the current one is still unresolved.
 
 **Headless: there is no reply coming, whether `ask_user` comes back
-`cancelled` or you never call it at all.** Neither is a vague answer to
+refused as unregistered or you never call it at all.** Neither is a vague answer to
 follow up on and neither is a signal to try again or to wait — both mean
 there is no operator this run, from round 1 on. Do not call `ask_user`
 again for this or any later phase, and do not phrase a question in plain
@@ -175,7 +174,7 @@ This step applies to a live session with a real operator. Stop immediately
 when the user says "stop", "enough", "later", "done", "next time", or cancels
 the modal. Do not ask another question to confirm stopping.
 
-A headless `cancelled` result is not a stop signal from a user — it is the
+A headless refusal of `ask_user` is not a stop signal from a user — it is the
 absence of an operator (see Step 3). Do not treat it as "the user cancelled
 this session"; treat it as the cue to switch to the assumed-confirm
 monologue and keep going to a complete decision log, not to stop early.
@@ -205,9 +204,9 @@ state the partial decisions and the next unresolved root question.
 
 In a live session, close with `ask_user` `action: "complete"` and a compact
 `decisions` array before final prose. In a headless run where `ask_user`
-already came back cancelled, skip straight to the decision log below — do
-not attempt another `ask_user` call just to close out; it will cancel too
-and adds nothing. Write the final decision log:
+already came back refused, skip straight to the decision log below — do
+not attempt another `ask_user` call just to close out; it will be refused
+too and adds nothing. Write the final decision log:
 
 ```markdown
 ## Decision Log - <topic>
@@ -256,7 +255,7 @@ Use this ordering when several questions are possible:
 - Letting `ask_user` hit the round limit without completing the interview.
 - Ending with a summary paragraph instead of the decision log.
 - Re-calling `ask_user` for a later phase after an earlier round already came
-  back `cancelled` — the answer will not be different; that budget is wasted.
+  back refused — the answer will not be different; that budget is wasted.
 - Ending a turn on "Answer 1/2/3", "let me know which you prefer", or any
   other wording that expects a reply in a headless run — there is no next
   turn for a reply to land in. This is the single most common failure mode
@@ -264,5 +263,5 @@ Use this ordering when several questions are possible:
   stopping, instead of running the assumed-confirm monologue through every
   remaining phase to the decision log in the same turn.
 - Opening a `tasks` list for the phase map; `tasks` is refused.
-- Treating a headless `cancelled` result as the user's stop signal (Step 4)
+- Treating a headless `ask_user` refusal as the user's stop signal (Step 4)
   instead of the absence-of-operator cue it actually is.

package/skills/workflow/workflow-distiller/SKILL.md

@@ -7,7 +7,7 @@ triggers:
   - turn this into a reusable workflow
   - distill this repeated process
   - create a skill from this session
-version: 0.4.0
+version: 0.4.1
 license: Apache-2.0
 allowed-tools:
   - read
@@ -50,10 +50,10 @@ whichever workflow just ran in this session. Everything else in the request
 not more arguments.
 
 A live operator can answer Phase 2's interview and Phase 4's design gate for
-real - treat a real, non-cancelled `ask_user` reply as proof an operator is
+real - treat a real, answered `ask_user` reply as proof an operator is
 present and continue asking one question per round. There is no operator in
-a headless run: `ask_user` is not registered and every call resolves
-`cancelled` immediately, whether or not it is ever called at all. When that
+a headless run: `ask_user` is not registered, so any call is refused as an
+unregistered tool rather than answered. When that
 is the run's condition, do not wait for a reply that cannot come: answer
 every remaining interview question and the Phase 4 gate yourself as an
 assumed-confirm monologue (state the question, give your best-grounded

package/src/cli/args.ts

@@ -37,7 +37,6 @@ export interface RunCliArgs {
 	noSkills: boolean;
 	skillPaths: string[];
 	maxContextTokens?: number;
-	kvCacheMode?: string;
 	steerChannel?: string;
 	/** Resume this exact session and append the turn to it. */
 	sessionId?: string;
@@ -207,13 +206,6 @@ export function parseRunCliArgs(argv: ReadonlyArray<string>): RunCliArgs {
 			}
 			continue;
 		}
-		if (arg === "--kv-cache-mode") {
-			const value = need(arg);
-			if (value !== null) {
-				parsed.kvCacheMode = value;
-			}
-			continue;
-		}
 		if (arg === "--session") {
 			const value = need(arg);
 			if (value !== null) {

package/src/cli/bootstrap-generate.ts

@@ -22,6 +22,7 @@ import {
 } from "../domains/context/index.js";
 import type { DispatchContract } from "../domains/dispatch/contract.js";
 import { DispatchDomainModule } from "../domains/dispatch/index.js";
+import { declaredScopeIntent } from "../domains/dispatch/intent.js";
 import type { RunReceipt } from "../domains/dispatch/types.js";
 import { MiddlewareDomainModule } from "../domains/middleware/index.js";
 import { createObservabilityDomainModule } from "../domains/observability/index.js";
@@ -384,6 +385,10 @@ async function generateBootstrapWithModel(
 	route?: BootstrapRoute,
 ): Promise<BootstrapStructuredOutput> {
 	const prompt = buildBootstrapPrompt(input);
+	// The internal researcher reads this repository and returns JSON. Authored
+	// handbook text is evidence, not a source of inferred filesystem authority.
+	const scope = declaredScopeIntent({ readRoots: ["."] });
+	if (!scope.ok) throw new Error(`${scope.reason}: ${scope.message}`);
 	const startedAtClock = performance.now();
 	input.progress?.({
 		phase: "generate",
@@ -393,6 +398,7 @@ async function generateBootstrapWithModel(
 	});
 	const dispatchBootstrap = (nativeSchema: boolean) =>
 		dispatch.dispatch({
+			intent: scope.intent,
 			agentId: CONTEXT_BOOTSTRAP_AGENT_ID,
 			executionRole: "researcher",
 			task: prompt,