copilotkit 4.9.60 → 4.10.0

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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.

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

@@ -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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.10.0 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -63,7 +63,7 @@ you create or build an Angular project. If the installed version is lower, selec
 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.60 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.10.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, or the two version lines do not fit
-together, run `npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+together, run `npx --yes copilotkit@4.10.0 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.60 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.10.0 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.60 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.10.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read frontend/react-spa`
-2. Next.js: `npx --yes copilotkit@4.9.60 onboard read frontend/nextjs`
-3. Angular: `npx --yes copilotkit@4.9.60 onboard read frontend/angular`
-4. Vue 3: `npx --yes copilotkit@4.9.60 onboard read frontend/vue`
-5. React Native: `npx --yes copilotkit@4.9.60 onboard read frontend/react-native`
+1. React SPA: `npx --yes copilotkit@4.10.0 onboard read frontend/react-spa`
+2. Next.js: `npx --yes copilotkit@4.10.0 onboard read frontend/nextjs`
+3. Angular: `npx --yes copilotkit@4.10.0 onboard read frontend/angular`
+4. Vue 3: `npx --yes copilotkit@4.10.0 onboard read frontend/vue`
+5. React Native: `npx --yes copilotkit@4.10.0 onboard read frontend/react-native`
 
 If no listed frontend fits, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.10.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.10.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 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.60 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.10.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.

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

@@ -2,6 +2,28 @@
 
 Do not implement the plan yourself. Use the step order in the approved plan.
 
+## If you stop in this phase
+
+One rule below stops onboarding: a Learning Container create that fails for a reason other
+than the container already existing. It ends a run the developer has already approved a
+plan for. Name the exact command, id, and error code that stopped you: a report that names
+only the step cannot be acted on. Send one short report before you stop. Run the friction command without another developer question. The CLI telemetry gate decides whether the
+report is sent.
+
+```text
+npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+```
+
+Write one or two sentences to standard input: the step you stopped at and what stopped it.
+Pick the category that fits from docs-missing, docs-wrong, docs-sequential, cli-gap,
+sdk-gap, environment, port-collision, credential, validation-loop, and other. Leave
+--cost-seconds off. A run that stopped cannot separate one papercut's cost from the cost
+of the whole run, so the estimate is optional on a stop report and only there.
+Send no secrets, source code, logs, or command output. The command refuses a report that
+carries any of those, prints the reason, and exits zero. A refused report is not a failed
+step. Send the report, then stop. Reporting is not a route change and does not resume the
+run.
+
 ## Authorization requested by the plan
 
 Approving the plan is the developer agreeing to every path it listed under
@@ -9,7 +31,7 @@ Approving the plan is the developer agreeing to every path it listed under
 app directory:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.10.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
 ```
 
 Consent has to be on the record before the file moves, so a call made after the change is
@@ -21,7 +43,7 @@ No implementation step has run yet, so the change is theirs rather than this run
 consent over it by adding one flag:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard protect --authorize --path <path> --reason "<the plan's sentence>" --with-prior-change
+npx --yes copilotkit@4.10.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>" --with-prior-change
 ```
 
 The flag records their change as drift beside the consent, so the closing report names both
@@ -40,7 +62,7 @@ rather than this section.
 Run the audit from the target app directory:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard audit
+npx --yes copilotkit@4.10.0 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -75,14 +97,14 @@ A path that no Files changed section names changed outside the run, and it is th
 developer's own file. Accept it by name:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.10.0 onboard protect --accept-external --path <path>
 ```
 
 A changed env file is its own case. This run asked the developer to place a credential
 there, so it takes the credential route rather than this one:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard protect --accept-credential --path <path>
+npx --yes copilotkit@4.10.0 onboard protect --accept-credential --path <path>
 ```
 
 That route proves no recorded credential was lost, instead of taking the run's word that it
@@ -101,7 +123,7 @@ neither does a one-line fix. Never repair, reset, or revert it. Ask the develope
 the change, and record the answer they give:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.10.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Use it only for an answer a developer actually gave. It records the consent as taken
@@ -115,14 +137,43 @@ protected path as changed. Report the printed reason and use the route-out rules
 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.
 
+## Create the approved Learning Container
+
+Where the approved plan names a Learning Container id that the platform does not hold yet,
+create it now, from the target app directory. The developer approved the id before it was
+made, so this is the first point at which it can be created:
+
+```text
+npx --yes copilotkit@4.10.0 learning containers create --id <id> --name <name> --json
+```
+
+Pass the id the plan names. Take the name from the selected project's own display name, so
+the container reads as this project's in the dashboard. Both flags are required alongside
+`--json`: a create that leaves either one out is refused as `NON_INTERACTIVE` rather than
+prompted for, whatever terminal the run has.
+
+`LEARNING_CONTAINER_ALREADY_EXISTS` means another run already made it. That is a container
+to reuse, not a failure to repair and not a reason to pick a new id. Any other error code:
+report it and stop onboarding, so no run wires a selector to an id the platform does not
+hold.
+
+Then report that the container is settled, before any edit:
+
+```text
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase container-settled
+```
+
+Where the plan names a container the platform already held, report the same checkpoint and
+create nothing. Where the plan names no container, skip this section.
+
 Report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase plan-written
 ```
 
 Spawn one implementation subagent. Tell it to run
-`npx --yes copilotkit@4.9.60 onboard read subagent/implement-and-validate` first and follow
+`npx --yes copilotkit@4.10.0 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
@@ -142,11 +193,11 @@ returned. Continue to proof only when that audit passes.
 After the selected implementation path passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase build-validated
 ```
 
 Then run
-`npx --yes copilotkit@4.9.60 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.10.0 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -160,8 +211,17 @@ implementation path.
 
 ## Route-out rules
 
-Route out for `Status: blocked`. Route out only when the failure is not yours to fix: the
-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.60 onboard read unsupported/no-validated-path`.
+Route out only when the failure is not yours to fix. Two endings are open from here, and
+what failed decides which one this run takes.
+
+A run that broke takes the failure ending: the failure is in code this run did not write,
+the same command still fails after three repair attempts, or a result starts with
+`Status: blocked`. A defect in a package this run installed is not a stack CopilotKit does
+not serve, a command this run cannot get to pass is not one either, and a blocked audit
+proved nothing about the stack. In those cases run
+`npx --yes copilotkit@4.10.0 onboard read stopped/run-failed`.
+
+A plan with no path to follow takes the unsupported ending: the fix requires changing the
+developer's existing agent or frontend, or the documentation does not support the plan. In
+those cases run
+`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -46,6 +46,8 @@ The handoff must include:
 - 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.
+- The Learning Container this run settled, or the fact that Learning is not available to
+  this organization and no container was created.
 - 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
@@ -64,11 +66,22 @@ Name the debugging surface this journey's frontend can reach, rather than the on
 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.60 verify --round-trip`, the runtime's own log, the AG-UI
+`npx --yes copilotkit@4.10.0 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.
 
+Where this run settled a Learning Container, tell the developer what happens next, because
+a correct run looks like a broken one otherwise. Learning runs on its own: the first
+automatic run needs new threads from 15 distinct conversations in this container, and only
+the newest snapshot of each thread counts. A thread takes its container before its first
+agent run, so threads that ran before this change are never pulled in. The container starts
+empty on purpose.
+
+Where the Learning step was skipped because this organization cannot use Learning, say so in
+one line and name what was not created. A skip nobody names reads as a container that
+exists, and the developer then waits for insights from a container this run never made.
+
 State that the servers remain running after proof.
 
 Report each thing that slowed this run down. Send at most four reports, worst first. Run
@@ -76,7 +89,7 @@ the friction commands without another developer question. The CLI telemetry gate
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.60 onboard friction --category <slug> --cost-seconds <seconds>
+npx --yes copilotkit@4.10.0 onboard friction --category <slug> --cost-seconds <seconds>
 ```
 
 Write one or two sentences on the command's standard input. Pick one category from
@@ -88,7 +101,7 @@ Pass --docs-path only for a docs-missing or docs-wrong report, naming the page t
 is about:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
+npx --yes copilotkit@4.10.0 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
 ```
 
 Give the page's site-relative path or its full URL, with no spaces, query string, or
@@ -105,14 +118,14 @@ Tell the developer when you send a friction report. Do not quote or summarize th
 unless the developer asks. If the CLI says the report was not sent,
 state what it said and continue without another question.
 
-When the evidence is gathered, run `npx --yes copilotkit@4.9.60 onboard complete`, carrying
+When the evidence is gathered, run `npx --yes copilotkit@4.10.0 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.60 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.10.0 onboard complete --visual-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
@@ -120,7 +133,7 @@ The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
 For React Native:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.10.0 onboard complete --device-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-device`, or `failed`.
@@ -132,7 +145,7 @@ browser-origin CORS, so the flag you pass is how this run states which surface i
 For a web frontend, also pass the URL the browser opened:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard complete --visual-check <outcome> \
+npx --yes copilotkit@4.10.0 onboard complete --visual-check <outcome> \
   --frontend-url <the url you opened>
 ```
 
@@ -151,7 +164,7 @@ 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.60 onboard complete --visual-check performed --blocked-by <cause>
+npx --yes copilotkit@4.10.0 onboard complete --visual-check performed --blocked-by <cause>
 ```
 
 The cause is one of `inspector` for a debugging surface that did not open,

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

@@ -1,7 +1,7 @@
 # Prove the existing OSS baseline
 
 Do not prove the baseline yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.9.60 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --yes copilotkit@4.10.0 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.
@@ -17,7 +17,7 @@ Wait for the subagent to finish.
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --yes copilotkit@4.10.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
 ```
 
 Report the gate whatever it returned. Pass `passed` when the subagent proved a predicate,
@@ -35,12 +35,12 @@ Do not change project files before this proof ends. Starting existing developmen
 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.60 onboard read conversion/plan`. That project already works.
+`npx --yes copilotkit@4.10.0 onboard read conversion/plan`. That project already works.
 What it needs is the conversion, not a build.
 
 If the proof does not establish the baseline, record the starting state
 `both-copilotkit-unproved` and run
-`npx --yes copilotkit@4.9.60 onboard read credentials/plan`. This prompt is served
+`npx --yes copilotkit@4.10.0 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. Keep the failing predicate with the plan.
 
@@ -54,4 +54,5 @@ and the plan preserves it rather than repeating it.
 
 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.60 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.0 onboard read stopped/run-failed`. None of those mean the
+project is unsupported: they mean this run did not establish what it needed to.

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.60 onboard read subagent/prove-round-trip` first and follow the
+`npx --yes copilotkit@4.10.0 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
@@ -14,6 +14,15 @@ drives the surface and cannot see your environment, so without that finding it s
 step discovering what you already know. A subagent told it has no control for the surface
 this frontend needs reports the skip outcome rather than looking for a way around it.
 
+A run that cloned a starter is the exception. Tell that subagent to stop after
+`verify --round-trip` and to open no browser. The cloned code is what this repository's
+starter smoke jobs already drive on every change, so opening a browser re-proves in the
+developer's run what those jobs prove before the starter ships, and it is the most
+expensive step in this setup. `verify --round-trip` reads the answer back off the thread,
+so it holds for every runtime mount and needs no browser. Give that subagent no browser or
+device control, and record the surface outcome as skipped for a cloned starter rather than
+as a missing capability: nothing was unavailable, the run declined to spend it.
+
 Give the subagent this guide for continued-development tools:
 https://docs.copilotkit.ai/build-with-agents.md
 
@@ -23,13 +32,13 @@ pass the time.
 Report each attempt at the journey as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Report the gate whatever it returned. A proof that never ran is `skipped`, not failed. The
@@ -37,7 +46,7 @@ command prints one line and sends nothing else. Where a repair cycle runs the pr
 record each attempt as it ends.
 
 For every protected-path audit in this prompt, run
-`npx --yes copilotkit@4.9.60 onboard audit` from the target app directory. If its result
+`npx --yes copilotkit@4.10.0 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, decide it the way the implementation prompt
@@ -46,7 +55,7 @@ returns none, so a finding with no Files changed section to test against routes
 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.60 onboard protect --accept-external --path <path>`. Then run
+`npx --yes copilotkit@4.10.0 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.
 
@@ -54,12 +63,12 @@ That holds for a repair cycle too. When the fix for a failing check lands on a p
 path, the path is still the developer's, however right the diagnosis is and however small
 the fix. Reading the file never settles who wrote it. Ask the developer to allow the
 change, and record their answer with
-`npx --yes copilotkit@4.9.60 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`,
+`npx --yes copilotkit@4.10.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`,
 or route out. Never repair it, and never send it to a repair worker.
 
 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.60 onboard read proof/complete`. A performed surface outcome with
+`npx --yes copilotkit@4.10.0 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
@@ -115,7 +124,7 @@ Restart each project-owned process changed by the repair. Report the cycle, coun
 one:
 
 ```text
-npx --yes copilotkit@4.9.60 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then spawn a fresh proof subagent
@@ -133,21 +142,25 @@ 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.60 onboard read unsupported/no-validated-path`. All three are
+`npx --yes copilotkit@4.10.0 onboard read stopped/run-failed`. The stack is supported:
+this run did not finish, which is a different ending and a different report. All three are
 about the round trip itself. A round trip that proved is not one of them, whatever failed
 after it.
 
 If you stop here without taking that route -- a repair cycle you cannot finish, a limit in
 your own harness, a run that has run out -- send one short report before you stop.
-Run the feedback command without another developer question. The CLI telemetry gate decides
+Run the friction command without another developer question. The CLI telemetry gate decides
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.60 onboard feedback
+npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
 ```
 
-Write at most four lines to standard input: the step you stopped at and what stopped it.
+Write one or two sentences to standard input: the step you stopped at and what stopped it.
+Pick the category that fits from docs-missing, docs-wrong, docs-sequential, cli-gap,
+sdk-gap, environment, port-collision, credential, validation-loop, and other. Leave
+--cost-seconds off. A run that stopped cannot separate one papercut's cost from the cost
+of the whole run, so the estimate is optional on a stop report and only there.
 Send no secrets, source code, logs, or command output. The command refuses a report that
 carries any of those, prints the reason, and exits zero. A refused report is not a failed
-step. Report friction only from a run that finished, never from a stop. A run that dies in
-this phase is the one this graph most needs to hear about and the one it hears from least.
+step. A run that dies in this phase is the one this graph most needs to hear about and the one it hears from least.