copilotkit 4.23.1 → 4.24.0

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

@@ -9,7 +9,7 @@ you change the project. If it fails, no .NET SDK is on this shell's PATH. Do not
 the project, and do not install the SDK yourself. Tell the developer to install the .NET
 SDK from https://dotnet.microsoft.com/download. Say that the coding agent's shell cannot
 see a new install until the developer restarts the coding agent. Give them
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard start --run <onboarding_run_id>` to resume the run
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard start --run <onboarding_run_id>` to resume the run
 after the restart. Then end your turn and wait for the developer.
 
 ## Documentation
@@ -49,7 +49,7 @@ Record the selected framework, provider, model, required credential variable nam
 URLs, and the quickstart gap.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

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

@@ -30,7 +30,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.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 --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

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

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

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

@@ -30,7 +30,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 --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.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 holds no
 project, 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 --prefer-offline --yes copilotkit@4.23.1 onboard read starter/clone` before you fetch documentation.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -52,7 +52,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 --prefer-offline --yes copilotkit@4.23.1 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.24.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 --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+together, run `npx --prefer-offline --yes copilotkit@4.24.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 --prefer-offline --yes copilotkit@4.23.1 onboard read starter/clone` before you fetch documentation.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -40,7 +40,7 @@ developer's work.
 - Do not claim, revert, or delete these files. Name them in the report as Next.js output.
 
 If the page supports the selection, record Next.js and this URL. Then run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/plan.md

@@ -37,15 +37,15 @@ CopilotKit web apps. Then recommend the one the developer names, and say what ea
 
 Use exactly one matching internal route:
 
-1. React SPA: `npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/react-spa`
-2. Next.js: `npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/nextjs`
-3. Angular: `npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/angular`
-4. Vue 3: `npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/vue`
-5. React Native: `npx --prefer-offline --yes copilotkit@4.23.1 onboard read frontend/react-native`
-6. Slack or Microsoft Teams: `npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/channels/start`
+1. React SPA: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/react-spa`
+2. Next.js: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/nextjs`
+3. Angular: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/angular`
+4. Vue 3: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/vue`
+5. React Native: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read frontend/react-native`
+6. Slack or Microsoft Teams: `npx --prefer-offline --yes copilotkit@4.24.0 onboard read feature/channels/start`
 
 If they chose Slack or Microsoft Teams, tell that node which one they chose so it
 does not ask again.
 
 If no listed frontend fits, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

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

@@ -18,7 +18,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 --prefer-offline --yes copilotkit@4.23.1 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

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

@@ -14,7 +14,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 --prefer-offline --yes copilotkit@4.23.1 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/vue.md

@@ -19,7 +19,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 --prefer-offline --yes copilotkit@4.23.1 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

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

@@ -12,7 +12,7 @@ acted on. Send one short report before you stop. The friction command follows th
 setting the developer already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.24.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -67,7 +67,7 @@ Approving the plan is the developer agreeing to every path it listed under
 app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.24.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
@@ -75,8 +75,10 @@ refused. Continue only if every result starts with `Status: passed`. If the plan
 nothing there, skip this section.
 
 Do not authorize a path the plan lists under `Files the run writes itself`. The CLI refuses
-`--authorize` for `.env` and `.copilotkit/project.json`, because this run writes them. A
-copied model key is recorded with `--accept-credential`, after the copy.
+`--authorize` for `.env` and `.copilotkit/project.json`, because this run writes them.
+A copied model key is recorded by the command that copied it.
+`onboard credentials --copy-to` protects the file it writes. Record a key that the run
+copied another way with `--accept-credential`, after the copy.
 
 The implementation subagent cannot change a protected path unless it has the authorized
 list. Take that list from the CLI rather than from the plan: run `onboard audit` after the
@@ -99,7 +101,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 --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>" --with-prior-change
+npx --prefer-offline --yes copilotkit@4.24.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
@@ -119,7 +121,7 @@ audit below describes, rather than use this section.
 Run the audit from the target app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard audit
+npx --prefer-offline --yes copilotkit@4.24.0 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -154,14 +156,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 --prefer-offline --yes copilotkit@4.23.1 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.24.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 --prefer-offline --yes copilotkit@4.23.1 onboard protect --accept-credential --path <path>
+npx --prefer-offline --yes copilotkit@4.24.0 onboard protect --accept-credential --path <path>
 ```
 
 That route proves no recorded credential was lost, instead of taking the run's word that it
@@ -180,7 +182,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 --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.24.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
@@ -215,7 +217,7 @@ directory. The developer approved the id before it was made, so this is the firs
 which it can be created:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 learning containers create --id <id> --name <name> --json
+npx --prefer-offline --yes copilotkit@4.24.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
@@ -232,7 +234,7 @@ plan names no container, skip this section.
 ## Implement the plan
 
 Spawn one implementation subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read subagent/implement-and-validate` first and follow
+`npx --prefer-offline --yes copilotkit@4.24.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
@@ -260,7 +262,7 @@ names the same way as above, against the Files changed section that subagent jus
 returned. Continue to proof only when that audit passes.
 
 Then run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read proof/round-trip`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -286,9 +288,9 @@ the same command still fails after three repair attempts, a result starts with
 declined a file the plan does not name, or the run cannot ask them about it. 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 --prefer-offline --yes copilotkit@4.23.1 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.24.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 --prefer-offline --yes copilotkit@4.23.1 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -24,7 +24,7 @@ friction commands follow the telemetry setting the developer already chose, so t
 separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.24.0 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
 ```
 
 Put one or two sentences in `--message`. Pick one category from docs-missing, docs-wrong,
@@ -46,7 +46,7 @@ Pass the surface-check outcome the proof subagent returned, not the one you want
 web frontend, pass `--visual-check` and the URL the browser opened, unchanged:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard complete --visual-check <outcome> \
+npx --prefer-offline --yes copilotkit@4.24.0 onboard complete --visual-check <outcome> \
   --frontend-url <the url you opened>
 ```
 
@@ -74,7 +74,7 @@ this graph opens.
 nothing drove the frontend:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard complete --visual-check failed --blocked-by browser-control-unresponsive
+npx --prefer-offline --yes copilotkit@4.24.0 onboard complete --visual-check failed --blocked-by browser-control-unresponsive
 ```
 
 ## Write the handoff

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 --prefer-offline --yes copilotkit@4.23.1 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --prefer-offline --yes copilotkit@4.24.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 --prefer-offline --yes copilotkit@4.23.1 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --prefer-offline --yes copilotkit@4.24.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
 ```
 
 Report the gate whatever it returned. Use the list below. A proof that never ran is `skipped`, not failed. The command prints one line and sends
@@ -39,12 +39,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 --prefer-offline --yes copilotkit@4.23.1 onboard read conversion/plan`. That project already works.
+`npx --prefer-offline --yes copilotkit@4.24.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 --prefer-offline --yes copilotkit@4.23.1 onboard read credentials/plan`. This prompt is served
+`npx --prefer-offline --yes copilotkit@4.24.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.
 
@@ -58,5 +58,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 --prefer-offline --yes copilotkit@4.23.1 onboard read stopped/run-failed`. None of those mean the
+`npx --prefer-offline --yes copilotkit@4.24.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 --prefer-offline --yes copilotkit@4.23.1 onboard read subagent/prove-round-trip` first and follow the
+`npx --prefer-offline --yes copilotkit@4.24.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
@@ -40,7 +40,7 @@ pass the time.
 Record what that proof returned before you route on it:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.24.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. A
@@ -49,7 +49,7 @@ to record it as `skipped`. The command prints one line and sends nothing else. W
 record each attempt as it ends.
 
 For every protected-path audit in this prompt, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard audit` from the target app directory. If its result
+`npx --prefer-offline --yes copilotkit@4.24.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
@@ -58,7 +58,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 --prefer-offline --yes copilotkit@4.23.1 onboard protect --accept-external --path <path>`. Then run
+`npx --prefer-offline --yes copilotkit@4.24.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.
 
@@ -66,12 +66,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 --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`,
+`npx --prefer-offline --yes copilotkit@4.24.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 --prefer-offline --yes copilotkit@4.23.1 onboard read proof/complete`. A performed surface outcome with
+`npx --prefer-offline --yes copilotkit@4.24.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`. The CLI records `skipped-cloned-starter` and
 `skipped-no-browser-tool` after a passed round trip as complete, and `skipped-no-device` as
@@ -166,7 +166,7 @@ proof cycles, use the route-out rules below.
 
 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 --prefer-offline --yes copilotkit@4.23.1 onboard read stopped/run-failed`. The stack is supported:
+`npx --prefer-offline --yes copilotkit@4.24.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.
@@ -177,7 +177,7 @@ friction command follows the telemetry setting the developer already chose, so i
 separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.24.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.

package/onboarding/prompts/research/gather.md

@@ -45,7 +45,7 @@ Before you end your turn to wait for the developer where the prompt states no de
 report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.24.0 onboard checkpoint --phase awaiting-developer
 ```
 
 When the answer or the result arrives, continue from the step that paused. Do not read an
@@ -65,7 +65,7 @@ Both research subagents failing means this harness has no working subagent at al
 is worth recording once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.24.0 onboard checkpoint --phase delegation-unavailable
 ```
 
 Then say once, in your own words, that this environment has no working subagents, so you
@@ -78,7 +78,7 @@ Before you ask the developer any setup question, finish every read-only investig
 preflight check in this section.
 
 Prepare two research assignments. Give each research subagent one assignment. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read subagent/inspect-repository` first and follow the
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read subagent/inspect-repository` 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. Require only its assigned packet.
@@ -92,8 +92,8 @@ Start both research subagents in parallel:
 The research is under way. Continue to the surface-control preflight while it runs:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard read research/preflight
+npx --prefer-offline --yes copilotkit@4.24.0 onboard read research/preflight
 ```
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read stopped/run-failed`.

package/onboarding/prompts/research/merge.md

@@ -49,7 +49,7 @@ Read the next step only after `login --json` has emitted `type: completed`. If s
 waits on the developer, end your turn and wait for it: that is a pause.
 
 When both research results are merged and sign-in is done, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read research/route`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read research/route`.
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read stopped/run-failed`.

package/onboarding/prompts/research/preflight.md

@@ -27,8 +27,8 @@ Where the device probe found no booted device, that is the whole finding.
 Then merge the research:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard read research/merge
+npx --prefer-offline --yes copilotkit@4.24.0 onboard read research/merge
 ```
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read stopped/run-failed`.

package/onboarding/prompts/research/route.md

@@ -9,7 +9,7 @@ sends the run down one path.
 Before you route on, run this from the target app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
+npx --prefer-offline --yes copilotkit@4.24.0 onboard protect
 ```
 
 It reads the working tree itself, records every changed or untracked path with a digest,
@@ -44,7 +44,7 @@ On any one of them, run this before you read the three findings below, and witho
 the purpose question:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/channels/start
+npx --prefer-offline --yes copilotkit@4.24.0 onboard read feature/channels/start
 ```
 
 Name the provider to that node so it does not ask again. A `/slack` page names Slack. A
@@ -105,7 +105,7 @@ settle these three from your own reading of the project. Each one comes from the
 packets or it is not proved.
 
 If all three are proved, prove the live starting state before any project file changes. Run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read proof/oss-baseline`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read proof/oss-baseline`.
 
 Route there before you ask the developer anything else. The questions after this prompt
 select a framework and a frontend that the findings already name, so a developer who
@@ -118,7 +118,7 @@ developer nor the repository findings prove what the project is for, ask one gui
 question about the user outcome. This asks what the developer wants to build before you
 select a framework. Give two or three short examples. Record the answer and give it to
 each later subagent. Then run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read credentials/plan`.
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read credentials/plan`.
 
 Do not ask that question on the route above. A project carrying all three states its
 purpose in the application it already serves.
@@ -132,5 +132,5 @@ A purpose question here names a domain before that choice.
 Take the same read named above without asking.
 
 If authentication, inspection, or the baseline capture stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read stopped/run-failed`. None of them says anything
+`npx --prefer-offline --yes copilotkit@4.24.0 onboard read stopped/run-failed`. None of them says anything
 about whether this project's stack is supported, which is not yet known at this point.