copilotkit 4.9.17 → 4.9.31

package/onboarding/prompts/framework/langgraph-python.md

@@ -15,7 +15,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/langgraph-typescript.md

@@ -15,7 +15,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/llamaindex.md

@@ -34,7 +34,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, the documented dependencies and adapter, and both documentation limits.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/mastra.md

@@ -45,7 +45,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/ms-agent-dotnet.md

@@ -34,7 +34,7 @@ Record the selected framework, provider, model, required credential variable nam
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/ms-agent-harness-dotnet.md

@@ -44,7 +44,7 @@ Record the selected framework, provider, model, required credential variable nam
 URLs, and the quickstart gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/ms-agent-python.md

@@ -28,7 +28,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/pydantic-ai.md

@@ -19,7 +19,7 @@ documented backend set with
 `uv add 'pydantic-ai-slim[ag-ui,openai]>=2,<3' 'starlette>=0.46.2' uvicorn`.
 Keep the Starlette endpoint that calls `AGUIAdapter.dispatch_request`, unless the app
 context route below replaces it with the two-step form. Register it in Copilot Runtime
-with `HttpAgent` and keep `InMemoryAgentRunner` for the documented local OSS setup. Do not replace this transport with a different Pydantic AI adapter.
+with `HttpAgent`. Do not replace this transport with a different Pydantic AI adapter.
 
 A2UI is not on this path. If the developer asks for it, say first that the documented
 Python setup does not support `action_handlers` on `a2ui.render`, so its button callback
@@ -43,7 +43,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the two-step context route.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/strands-python.md

@@ -27,7 +27,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the context documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/strands-typescript.md

@@ -28,7 +28,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the context documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/angular.md

@@ -5,7 +5,7 @@ Preserve an existing Angular frontend. Use the selected page for a new frontend.
 Use the starter shortcut only if all these facts are true: the target directory contains
 no entries, its name is a valid `init` project name, and the selected framework is ADK.
 If all three facts are true, record Angular as the selected frontend. Then run
-`npx --yes copilotkit@4.9.17 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.9.31 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -30,12 +30,40 @@ same `component` and `handler: async () => {}` instead, and record that substitu
 not give the handler a body: a display-only tool that returns a value writes it into the
 thread as the tool's result.
 
+## Version lines
+
+`@copilotkit/angular` publishes on a `0.x` line of its own. Every other `@copilotkit/*`
+package publishes on the `1.x` line. Never move either onto the other's line.
+
+The two lines are released separately, so a published `@copilotkit/angular` declares a
+`@copilotkit/core` chosen when that Angular release was cut, not when this run happens.
+Read that declaration before you plan any dependency change:
+
+```text
+npm view @copilotkit/angular@latest dependencies
+```
+
+If the `@copilotkit/core` it declares cannot be satisfied by the version the floor
+requires, the two published packages do not fit together. Installing both resolves two
+copies of `@copilotkit/core`, the Angular package's calls land on the copy that does not
+export what they need, and the threads drawer and the Inspector threads view throw in the
+browser while every command-line check passes.
+
+That is a version-line mismatch. Report it naming both versions -- the `@copilotkit/core`
+the Angular package declares, and the one the floor requires -- and take the unsupported
+route at the end of this page. Do not add an `overrides`, `resolutions`, or
+`pnpm.overrides` block to force them together. That is a repair the developer did not
+approve, it silently pins their whole tree, and it hides a mismatch between two packages
+CopilotKit publishes rather than reporting it.
+
+## Node
+
 Angular CLI 22 requires Node `^22.22.3 || ^24.15.0 || >=26`. Check the Node version before
 you create or build an Angular project. If the installed version is lower, select a
 supported version first and use it for every later command in this project.
 
 If the pages support the selection, record Angular and these URLs. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.31 onboard read credentials/finalize-plan`.
 
-If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+If the documentation does not support the selection, or the two version lines do not fit
+together, run `npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/nextjs.md

@@ -15,7 +15,7 @@ These TypeScript options have starters: Claude Agent SDK TypeScript, LangGraph T
 Mastra, and Strands Agents TypeScript. The .NET option is Microsoft Agent Framework .NET.
 
 If all shortcut conditions are true, record Next.js as the selected frontend. Then run
-`npx --yes copilotkit@4.9.17 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.9.31 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -27,7 +27,7 @@ agent as the default agent, which is correct only for a project that has no agen
 Do not replace the developer's existing agent with the built-in agent.
 
 If the page supports the selection, record Next.js and this URL. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.31 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/plan.md

@@ -24,11 +24,11 @@ process.
 
 Use exactly one matching internal route:
 
-1. React SPA: `npx --yes copilotkit@4.9.17 onboard read frontend/react-spa`
-2. Next.js: `npx --yes copilotkit@4.9.17 onboard read frontend/nextjs`
-3. Angular: `npx --yes copilotkit@4.9.17 onboard read frontend/angular`
-4. Vue 3: `npx --yes copilotkit@4.9.17 onboard read frontend/vue`
-5. React Native: `npx --yes copilotkit@4.9.17 onboard read frontend/react-native`
+1. React SPA: `npx --yes copilotkit@4.9.31 onboard read frontend/react-spa`
+2. Next.js: `npx --yes copilotkit@4.9.31 onboard read frontend/nextjs`
+3. Angular: `npx --yes copilotkit@4.9.31 onboard read frontend/angular`
+4. Vue 3: `npx --yes copilotkit@4.9.31 onboard read frontend/vue`
+5. React Native: `npx --yes copilotkit@4.9.31 onboard read frontend/react-native`
 
 If no listed frontend fits, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-native.md

@@ -15,7 +15,7 @@ documents `useRenderTool`, which is React Native's own hook for drawing a tool t
 already has. That is a different job and needs a tool in the agent.
 
 If the pages support the selection, record React Native and these URLs. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.31 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-spa.md

@@ -11,7 +11,7 @@ not move the agent into it.
 - https://docs.copilotkit.ai/react-spa.md
 
 If the page supports the selection, record React SPA and this URL. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.31 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/vue.md

@@ -16,7 +16,7 @@ page above. Vue has its own `useComponent`, which is not the React package. Take
 that reference page rather than from a Vue generative-UI guide, which is not published.
 
 If the pages support the selection, record Vue 3 and these URLs. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.31 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/implementation/build-and-validate.md

@@ -7,25 +7,46 @@ Do not implement the plan yourself. Use the step order in the approved plan.
 Run the audit from the target app directory:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard audit
+npx --yes copilotkit@4.9.31 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
 with `Status: passed`, `Status: failed`, or `Status: blocked`. The audit passes only when
 the result starts with `Status: passed`.
 
-`Status: failed` names each protected path that changed and how. If an audit reports a
-changed protected path, use the route-out rules. Never repair, reset, or revert a protected
-path. Also do not retry the audit: it reads files, so a second run of it answers the same.
+`Status: failed` names each protected path that changed and how. Never repair, reset, or
+revert a protected path. Also do not retry the audit: it reads files, so a second run of it
+answers the same.
+
+Decide each path the audit names, one at a time. Accept a path only when you can show that
+this run did not write it. Every implementation subagent reports what it touched in its
+Files changed section, so the test is whether the path appears in any Files changed section
+this run collected. If it appears in one, or the sections do not settle it, the change is
+this run's own: use the route-out rules. The plan cannot name a protected path, so a plan
+that does not name it proves nothing on its own.
+
+A path that no Files changed section names changed outside the run, and it is the
+developer's own file. Accept it by name:
+
+```text
+npx --yes copilotkit@4.9.31 onboard protect --accept-external --path <path>
+```
+
+Pass one `--path` for each path you accept. Accept only a path the audit named, and only
+when no step of this run wrote it. The command re-captures that path, records that this
+run accepted the change, and prints it. Run the audit again afterwards: it passes and
+names every accepted path, and the closing summary must name them too. An acceptance is
+not a repair. It proves nothing about what the file now holds.
 
 `Status: blocked` means the audit has no baseline to read. A blocked audit compared
 nothing and proved nothing changed. It is not a preservation failure: do not report a
 protected path as changed. Report the printed reason and use the route-out rules.
 
-A non-pass audit never continues the run. Do not send an audit result to a repair worker.
+An audit that has not passed never continues the run by itself. Continue only after an
+acceptance clears it, or route out. Do not send an audit result to a repair worker.
 
 Spawn one implementation subagent. Tell it to run
-`npx --yes copilotkit@4.9.17 onboard read subagent/implement-and-validate` first and follow
+`npx --yes copilotkit@4.9.31 onboard read subagent/implement-and-validate` first and follow
 the prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the plan, selected framework, frontend, model, exact target app
@@ -38,11 +59,12 @@ One subagent implements the whole plan. Do not divide the work across concurrent
 and do not spawn a second subagent to reconcile a split.
 
 If the implementation result does not start with `Status: passed`, do not continue to proof.
-Run the protected-path audit after the implementation subagent passes. If any protected path
-changed, use the route-out rules. Continue to proof only when that audit passes.
+Run the protected-path audit after the implementation subagent passes. Decide each path it
+names the same way as above, against the Files changed section that subagent just
+returned. Continue to proof only when that audit passes.
 
 After the selected implementation path passes, run
-`npx --yes copilotkit@4.9.17 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.9.31 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -60,4 +82,4 @@ Route out for `Status: blocked`. Route out only when the failure is not yours to
 failure is in code this run did not write, the fix requires changing the developer's existing
 agent or frontend, the same command still fails after three repair attempts, or the
 documentation does not support the plan. In those cases run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -37,17 +37,34 @@ The handoff must include:
 - The URL of the running app.
 - The command that starts the app in the future.
 - The debugging surface this journey's frontend can reach, named below.
-- How to use https://intelligence.copilotkit.ai to manage the Intelligence installation.
+- How to use https://intelligence.copilotkit.ai to manage the Intelligence
+  installation. Do not open it. This item makes the developer aware the dashboard is
+  there, and it is a sentence to write rather than a check to perform. Nothing in this
+  graph gates on the dashboard, so a dashboard this run never opened is not a finding,
+  not a caveat, and not a blocker.
 - The process IDs and stop commands for the running agent and frontend.
 - The `@copilotkit/*` versions this conversion changed, and what they were before.
 - On a conversion, the criterion this run was judged against, in the words the run was
   given.
+- Any path this run created that git does not ignore, and what to do with each.
+- Any protected path this run accepted as changed from outside it, and what changed. The
+  command at the end of this prompt prints each one, so copy them from its output rather
+  than from memory. This run did not change them and cannot say what did, so the developer
+  decides what to do about each.
+
+A run leaves paths beside the credential file. Tool output such as `.playwright-mcp/` and
+`.langgraph_api/` is regenerable, so the developer normally wants it ignored.
+`.copilotkit/` is not debris: `project.json` and `channels.json` are the project's own
+declared state and belong in the commit, while `.copilotkit/artifacts/` holds regenerable
+manifests and does not. Name each path and say which of the two it is. Do not add an
+ignore line for any of them yourself. None of these carries a secret, unlike the
+credential path, so the developer decides.
 
 Name the debugging surface this journey's frontend can reach, rather than the one the rest
 of the documentation leads with. For a web frontend it is the CopilotKit Inspector. For
 React Native there is no Inspector: it is a browser overlay built on a DOM custom element,
 and `@copilotkit/react-native` does not ship it. Give a mobile developer
-`npx --yes copilotkit@4.9.17 verify --round-trip`, the runtime's own log, the AG-UI
+`npx --yes copilotkit@4.9.31 verify --round-trip`, the runtime's own log, the AG-UI
 Event Inspector in the CopilotKit VS Code extension, and the Intelligence thread view
 instead. Naming the Inspector to a developer who cannot open it costs them the time it
 takes to conclude their own wiring is broken.
@@ -59,7 +76,7 @@ the friction commands without another developer question. The CLI telemetry gate
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.17 onboard friction --category <slug> --cost-seconds <seconds>
+npx --yes copilotkit@4.9.31 onboard friction --category <slug> --cost-seconds <seconds>
 ```
 
 Write one or two sentences on the command's standard input. Pick one category from
@@ -76,14 +93,14 @@ Tell the developer when you send a friction report. Do not quote or summarize th
 unless the developer asks. If the CLI says that telemetry is disabled or unavailable,
 state that the report was not sent and continue without another question.
 
-When the evidence is gathered, run `npx --yes copilotkit@4.9.17 onboard complete`, carrying
+When the evidence is gathered, run `npx --yes copilotkit@4.9.31 onboard complete`, carrying
 the surface-check outcome the proof subagent returned. Pass exactly one flag, and pass the
 one that matches this journey's surface.
 
 For a web frontend -- React SPA, Next.js, Angular, Vue:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.9.31 onboard complete --visual-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
@@ -91,7 +108,7 @@ The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
 For React Native:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.9.31 onboard complete --device-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-device`, or `failed`.
@@ -109,14 +126,18 @@ If the round trip proved and something after it still blocked this run, add `--b
 to the same command:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard complete --visual-check performed --blocked-by <cause>
+npx --yes copilotkit@4.9.31 onboard complete --visual-check performed --blocked-by <cause>
 ```
 
-The cause is one of `hosted-dashboard` for a managed dashboard that did not load or refused
-a sign-in, `inspector` for a debugging surface that did not open, `plan-excluded-capability`
-for a capability the approved plan had already excluded for this framework, and `other` for
-anything else. Pick `other` rather than leaving the flag off. The command ends the run as
-blocked and prints what the blocker leaves unverified.
+The cause is one of `inspector` for a debugging surface that did not open,
+`plan-excluded-capability` for a capability the approved plan had already excluded for this
+framework, and `other` for anything else. Pick `other` rather than leaving the flag off.
+The command ends the run as blocked and prints what the blocker leaves unverified.
+
+The managed Intelligence dashboard is not among these, because nothing in this graph asks a
+run to open it. A run that records a blocker for a surface it was never sent to looks worse
+than an identical run that wrote the same handoff sentence, and the two are then not
+comparable.
 
 This is the flag for a journey that worked. It is not a way to report an unsupported path,
 and a blocked run here is still owed the full handoff above: the URL, the start command,

package/onboarding/prompts/proof/oss-baseline.md

@@ -1,24 +1,31 @@
 # Prove the existing OSS baseline
 
 Do not prove the baseline yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.9.17 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --yes copilotkit@4.9.31 onboard read subagent/prove-oss-baseline` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
-and the same handoff. Give it the repository findings and exact CLI package spec. Wait for the
-subagent to finish.
+and the same handoff. Give it the repository findings and exact CLI package spec.
+
+Give it the browser or device control you recorded in the preflight as well. The subagent
+proves the runtime from a shell and needs no browser for that. The control is for the one
+predicate that drives the existing frontend. Where the preflight recorded `unavailable`, say
+so, so the subagent records that predicate as skipped instead of spending the step looking
+for a substitute.
+
+Wait for the subagent to finish.
 
 Do not change project files before this proof ends. Starting existing development
 processes and their ignored runtime files is allowed.
 
 If the subagent proves the `both-oss` predicate, keep its evidence with the plan and run
-`npx --yes copilotkit@4.9.17 onboard read conversion/plan`. That project already works.
+`npx --yes copilotkit@4.9.31 onboard read conversion/plan`. That project already works.
 What it needs is the conversion, not a build.
 
 If it proves another supported starting state, record that state and run
-`npx --yes copilotkit@4.9.17 onboard read credentials/plan`. This prompt is served
+`npx --yes copilotkit@4.9.31 onboard read credentials/plan`. This prompt is served
 whenever a project looks like an OSS integration, so a baseline that did not prove is an
 ordinary starting state rather than a failure.
 
 If it cannot identify the running process safely, exposes a secret, or finds a baseline
 failure that cannot be classified, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/round-trip.md

@@ -1,7 +1,7 @@
 # Prove the user journey
 
 Do not do the proof work yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.9.17 onboard read subagent/prove-round-trip` first and follow the
+`npx --yes copilotkit@4.9.31 onboard read subagent/prove-round-trip` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the selected framework, frontend, model, approved plan, selected
@@ -17,27 +17,35 @@ this frontend needs reports the skip outcome rather than looking for a way aroun
 Give the subagent this guide for continued-development tools:
 https://docs.copilotkit.ai/build-with-agents.md
 
-Wait for the subagent to finish.
+Wait for the subagent to finish. Its result arrives as a notification. Do not sleep to
+pass the time.
 
 For every protected-path audit in this prompt, run
-`npx --yes copilotkit@4.9.17 onboard audit` from the target app directory. If its result
+`npx --yes copilotkit@4.9.31 onboard audit` from the target app directory. If its result
 starts with `Status: blocked`, report the printed reason and use the route-out rules below.
 A blocked audit proved nothing changed and is not a preservation failure. If a
-protected-path audit reports a changed path, use the route-out rules below. Never repair,
-reset, or revert a protected path.
+protected-path audit reports a changed path, decide it the way the implementation prompt
+does, against the Files changed sections this run has collected. The proof subagent
+returns none, so a finding with no Files changed section to test against routes out. A
+path one of those sections names is this run's own change and routes out too. Accept a
+path only when a section this run collected covers the step that wrote it and does not
+name it:
+`npx --yes copilotkit@4.9.31 onboard protect --accept-external --path <path>`. Then run
+the audit again and name the path in the closing summary. Never repair, reset, or revert a
+protected path.
 
 If the proof result starts with `Status: passed`, run the protected-path audit. Continue to
 `proof/complete` only if that audit passes. After the audit passes, run
-`npx --yes copilotkit@4.9.17 onboard read proof/complete`. A performed surface outcome with
+`npx --yes copilotkit@4.9.31 onboard read proof/complete`. A performed surface outcome with
 the full round trip is core success even if a continued-development tool fails. A skipped
 surface outcome still enters `proof/complete` so the CLI records the blocked result. Do not
 describe a skipped surface as proved. Keep the Skills and MCP results separate from the proof
 result.
 
-If the round trip proves and something after it blocks this run anyway -- the managed
-Intelligence dashboard, the debugging surface, or a capability the approved plan already
-excluded for this framework -- read `proof/complete` all the same, with the command above,
-and carry the blocker there with `--blocked-by`.
+If the round trip proves and something after it blocks this run anyway -- the debugging
+surface, or a capability the approved plan already excluded for this framework -- read
+`proof/complete` all the same, with the command above, and carry the blocker there with
+`--blocked-by`.
 The stop terminal is for a journey this release cannot carry. It is
 not for a journey that worked and then hit a wall: routing a proved run there tells the
 developer that a framework and frontend that just worked are unsupported, and hands them a
@@ -95,7 +103,7 @@ and proof cycles.
 
 Route out only when the failure is not yours to fix, when the same proof still fails after
 three attempts, or when no evidence of the round trip can be produced. In those cases run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`. All three are
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`. All three are
 about the round trip itself. A round trip that proved is not one of them, whatever failed
 after it.
 
@@ -105,7 +113,7 @@ Run the feedback command without another developer question. The CLI telemetry g
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.17 onboard feedback
+npx --yes copilotkit@4.9.31 onboard feedback
 ```
 
 Write at most four lines to standard input: the step you stopped at and what stopped it.

package/onboarding/prompts/starter/clone.md

@@ -34,11 +34,18 @@ selected pair is not in the table, or the directory name is not valid, stop the
 Do not run `init`. Treat this result as a failed shortcut and follow the final failure
 instruction in this prompt.
 
-If the developer did not name an Intelligence project, list the available projects:
+If the developer did not name an Intelligence project, create one for the app being
+cloned. This directory is new, so no existing project is already its own: take the project
+name from the target directory name derived above, and ask the developer to confirm it or
+give another. Do not list the projects in the organization. If no developer answers, use
+the derived name.
 
-`npx --yes copilotkit@4.9.17 project list --json`
+Only if the developer asks for an existing project, or asks to see the projects they have,
+read the choices:
 
-Ask the developer to select a project or give a name for a new project. If the developer
+`npx --yes copilotkit@4.9.31 project list --json`
+
+Then ask which one to use. Do not order the projects by creation time. If the developer
 already gave this answer, do not ask again. Do not read a secret value. Do not show or
 store a secret value.
 
@@ -46,10 +53,12 @@ Run the command from the parent directory. Do not inspect another entry in the p
 directory. Replace each placeholder with the recorded value. Do not run a placeholder as
 a shell argument.
 
-`npx --yes copilotkit@4.9.17 init --name <project-name> --framework <framework-id> --channel none --no-banner --project <slug-or-id> --install`
+`npx --yes copilotkit@4.9.31 init --name <project-name> --framework <framework-id> --channel none --no-banner --create <name> --install`
 
-If the developer wants a new project, use `--create <name>` instead of
-`--project <slug-or-id>`. If the developer asked to skip the dependency install, use
+Pass the confirmed name to both `--name` and `--create`: the app directory and its
+Intelligence project take the same name here. If the developer names an existing project,
+use `--project <slug-or-id>` instead of `--create <name>`. If the developer asked to skip
+the dependency install, use
 `--no-install` instead of `--install`. Do not wait for an interactive prompt. Pass every
 answer as a flag.
 
@@ -60,8 +69,8 @@ account. The command does not need terminal input.
 If the command succeeds, do not rebuild the starter by hand. Inspect only the generated
 paths inside the target directory. Record the files, install result, project connection,
 and validation commands. Then run
-`npx --yes copilotkit@4.9.17 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.9.31 onboard read proof/round-trip`.
 
 If the command fails, report its exact error and do not claim that the starter is ready.
 Then run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.