copilotkit 4.13.0 → 4.13.1

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.13.0 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.13.1 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.13.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.13.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/plan.md

@@ -36,15 +36,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 --yes copilotkit@4.13.0 onboard read frontend/react-spa`
-2. Next.js: `npx --yes copilotkit@4.13.0 onboard read frontend/nextjs`
-3. Angular: `npx --yes copilotkit@4.13.0 onboard read frontend/angular`
-4. Vue 3: `npx --yes copilotkit@4.13.0 onboard read frontend/vue`
-5. React Native: `npx --yes copilotkit@4.13.0 onboard read frontend/react-native`
-6. Slack or Microsoft Teams: `npx --yes copilotkit@4.13.0 onboard read feature/channels/start`
+1. React SPA: `npx --yes copilotkit@4.13.1 onboard read frontend/react-spa`
+2. Next.js: `npx --yes copilotkit@4.13.1 onboard read frontend/nextjs`
+3. Angular: `npx --yes copilotkit@4.13.1 onboard read frontend/angular`
+4. Vue 3: `npx --yes copilotkit@4.13.1 onboard read frontend/vue`
+5. React Native: `npx --yes copilotkit@4.13.1 onboard read frontend/react-native`
+6. Slack or Microsoft Teams: `npx --yes copilotkit@4.13.1 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 --yes copilotkit@4.13.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.13.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.13.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.13.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.13.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.13.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.13.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -12,7 +12,7 @@ command without another developer question. Do not ask the developer about telem
 command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.13.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.13.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -53,7 +53,7 @@ Approving the plan is the developer agreeing to every path it listed under
 app directory:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.13.1 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
@@ -70,7 +70,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.13.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>" --with-prior-change
+npx --yes copilotkit@4.13.1 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
@@ -89,7 +89,7 @@ rather than this section.
 Run the audit from the target app directory:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard audit
+npx --yes copilotkit@4.13.1 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -124,14 +124,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.13.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.13.1 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.13.0 onboard protect --accept-credential --path <path>
+npx --yes copilotkit@4.13.1 onboard protect --accept-credential --path <path>
 ```
 
 That route proves no recorded credential was lost, instead of taking the run's word that it
@@ -150,7 +150,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.13.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.13.1 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
@@ -171,7 +171,7 @@ create it now, from the target app directory. The developer approved the id befo
 made, so this is the first point at which it can be created:
 
 ```text
-npx --yes copilotkit@4.13.0 learning containers create --id <id> --name <name> --json
+npx --yes copilotkit@4.13.1 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
@@ -187,7 +187,7 @@ hold.
 Then report that the container is settled, before any edit:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase container-settled
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase container-settled
 ```
 
 Where the plan names a container the platform already held, report the same checkpoint and
@@ -196,11 +196,11 @@ 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.13.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase plan-written
 ```
 
 Spawn one implementation subagent. Tell it to run
-`npx --yes copilotkit@4.13.0 onboard read subagent/implement-and-validate` first and follow
+`npx --yes copilotkit@4.13.1 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
@@ -228,11 +228,11 @@ returned. Continue to proof only when that audit passes.
 After the selected implementation path passes, report it:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase build-validated
 ```
 
 Then run
-`npx --yes copilotkit@4.13.0 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.13.1 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -254,9 +254,9 @@ the same command still fails after three repair attempts, or a result starts wit
 `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.13.0 onboard read stopped/run-failed`.
+`npx --yes copilotkit@4.13.1 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.13.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -84,7 +84,7 @@ 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.13.0 verify --round-trip`, the runtime's own log, the AG-UI
+`npx --yes copilotkit@4.13.1 verify --round-trip`, the runtime's own log, the AG-UI
 Event Inspector in the CopilotKit VS Code extension, and the CopilotKit Intelligence
 thread view
 instead. Naming the Inspector to a developer who cannot open it costs them the time it
@@ -114,7 +114,7 @@ the friction commands without another developer question. Do not ask the develop
 telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.13.0 onboard friction --category <slug> --cost-seconds <seconds>
+npx --yes copilotkit@4.13.1 onboard friction --category <slug> --cost-seconds <seconds>
 ```
 
 Write one or two sentences on the command's standard input. Pick one category from
@@ -126,7 +126,7 @@ Pass --docs-path only for a docs-missing or docs-wrong report, naming the page t
 is about:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
+npx --yes copilotkit@4.13.1 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
@@ -143,14 +143,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.13.0 onboard complete`, carrying
+When the evidence is gathered, run `npx --yes copilotkit@4.13.1 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.13.0 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.13.1 onboard complete --visual-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-browser-tool`, `skipped-cloned-starter`, or
@@ -160,7 +160,7 @@ open no browser. It is the one skip that does not block.
 For React Native:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.13.1 onboard complete --device-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-device`, `skipped-cloned-starter`, or
@@ -173,7 +173,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.13.0 onboard complete --visual-check <outcome> \
+npx --yes copilotkit@4.13.1 onboard complete --visual-check <outcome> \
   --frontend-url <the url you opened>
 ```
 
@@ -192,7 +192,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.13.0 onboard complete --visual-check performed --blocked-by <cause>
+npx --yes copilotkit@4.13.1 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.13.0 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --yes copilotkit@4.13.1 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.13.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --yes copilotkit@4.13.1 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.13.0 onboard read conversion/plan`. That project already works.
+`npx --yes copilotkit@4.13.1 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.13.0 onboard read credentials/plan`. This prompt is served
+`npx --yes copilotkit@4.13.1 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,5 +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.13.0 onboard read stopped/run-failed`. None of those mean the
+`npx --yes copilotkit@4.13.1 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.13.0 onboard read subagent/prove-round-trip` first and follow the
+`npx --yes copilotkit@4.13.1 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
@@ -33,13 +33,13 @@ pass the time.
 Report each attempt at the journey as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.13.1 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
@@ -47,7 +47,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.13.0 onboard audit` from the target app directory. If its result
+`npx --yes copilotkit@4.13.1 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
@@ -56,7 +56,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.13.0 onboard protect --accept-external --path <path>`. Then run
+`npx --yes copilotkit@4.13.1 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.
 
@@ -64,12 +64,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.13.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`,
+`npx --yes copilotkit@4.13.1 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.13.0 onboard read proof/complete`. A performed surface outcome with
+`npx --yes copilotkit@4.13.1 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
@@ -136,7 +136,7 @@ Restart each project-owned process changed by the repair. Report the cycle, coun
 one:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then spawn a fresh proof subagent
@@ -154,7 +154,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.13.0 onboard read stopped/run-failed`. The stack is supported:
+`npx --yes copilotkit@4.13.1 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.
@@ -165,7 +165,7 @@ friction command without another developer question: it applies the telemetry se
 developer already set.
 
 ```text
-npx --yes copilotkit@4.13.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.13.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.

package/onboarding/prompts/research/gather.md

@@ -34,7 +34,7 @@ Both research subagents failing means this harness has no working subagent at al
 is worth recording once:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase delegation-unavailable
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase delegation-unavailable
 ```
 
 Then say once, in your own words, that this environment has no working subagents, so you
@@ -47,7 +47,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 --yes copilotkit@4.13.0 onboard read subagent/inspect-repository` first and follow the
+`npx --yes copilotkit@4.13.1 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.
@@ -61,7 +61,7 @@ Start both research subagents in parallel:
 Report that both subagents started:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase research-dispatched
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase research-dispatched
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -70,8 +70,8 @@ failed step.
 The research is under way. Continue to the surface-control preflight while it runs:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard read research/preflight
+npx --yes copilotkit@4.13.1 onboard read research/preflight
 ```
 
 If inspection stops onboarding, run
-`npx --yes copilotkit@4.13.0 onboard read stopped/run-failed`.
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`.

package/onboarding/prompts/research/merge.md

@@ -21,7 +21,7 @@ Project selection is where the settled port is written down, through `--runtime-
 Then report that the research came back:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -54,7 +54,7 @@ worker a focused directory check. Continue only when both workers return the sam
 app directory. Both results must start with `Status: passed`. Otherwise, use the stop route.
 
 When both research results are merged, run
-`npx --yes copilotkit@4.13.0 onboard read research/route`.
+`npx --yes copilotkit@4.13.1 onboard read research/route`.
 
 If inspection stops onboarding, run
-`npx --yes copilotkit@4.13.0 onboard read stopped/run-failed`.
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`.

package/onboarding/prompts/research/preflight.md

@@ -45,7 +45,7 @@ mechanism a later step uses for the CopilotKit documentation server.
 
 Some coding agents, Claude Code among them, load a newly registered MCP server only at the
 next session start. Tell the developer in one line to expect one restart, then restart and
-re-bind with `npx --yes copilotkit@4.13.0 onboard start --run <onboarding_run_id>`. That
+re-bind with `npx --yes copilotkit@4.13.1 onboard start --run <onboarding_run_id>`. That
 restart is a step here, not an error.
 
 Do not add a browser or device driver to the project. A driver added there is a
@@ -62,14 +62,14 @@ whole finding.
 Report that the probe settled, whichever way it came out:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase surface-probed
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase surface-probed
 ```
 
 Then merge the research:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard read research/merge
+npx --yes copilotkit@4.13.1 onboard read research/merge
 ```
 
 If inspection stops onboarding, run
-`npx --yes copilotkit@4.13.0 onboard read stopped/run-failed`.
+`npx --yes copilotkit@4.13.1 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 --yes copilotkit@4.13.0 onboard protect
+npx --yes copilotkit@4.13.1 onboard protect
 ```
 
 It reads the working tree itself, records every changed or untracked path with a digest,
@@ -41,7 +41,7 @@ On either, run this before you read the three findings below, and without asking
 purpose question:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard read feature/channels/start
+npx --yes copilotkit@4.13.1 onboard read feature/channels/start
 ```
 
 Name the provider to that node so it does not ask again. A Slack page names Slack. A Teams
@@ -96,7 +96,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 --yes copilotkit@4.13.0 onboard read proof/oss-baseline`.
+`npx --yes copilotkit@4.13.1 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
@@ -107,9 +107,9 @@ these three findings.
 For every other combination of the three, take one more step first. If neither the
 developer nor the repository findings prove what the project is for, ask one guided
 question about the user outcome. This asks what the developer wants to build before you
-select a framework. Give two or three short examples and offer a minimal starter. Record
-the answer and give it to each later subagent. Then run
-`npx --yes copilotkit@4.13.0 onboard read credentials/plan`.
+select a framework. Give two or three short examples. Record the answer and give it to
+each later subagent. Then run
+`npx --yes copilotkit@4.13.1 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.
@@ -121,5 +121,5 @@ A purpose question here names a domain before that choice.
 Take the same read named above without asking.
 
 If authentication or inspection stops onboarding, run
-`npx --yes copilotkit@4.13.0 onboard read stopped/run-failed`. Neither says anything
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`. Neither says anything
 about whether this project's stack is supported, which is not yet known at this point.

package/onboarding/prompts/starter/clone.md

@@ -46,7 +46,7 @@ the derived name.
 Only if the developer asks for an existing project, or asks to see the projects they have,
 read the choices:
 
-`npx --yes copilotkit@4.13.0 project list --json`
+`npx --yes copilotkit@4.13.1 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
@@ -56,7 +56,7 @@ 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.13.0 init --name <project-name> --framework <framework-id> --channel none --no-banner --create <name> --install`
+`npx --yes copilotkit@4.13.1 init --name <project-name> --framework <framework-id> --channel none --no-banner --create <name> --install`
 
 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,
@@ -72,7 +72,7 @@ account. The command does not need terminal input.
 Report the clone before you inspect anything:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase starter-cloned
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase starter-cloned
 ```
 
 This is its own step, not an aside. A run that clones and then goes quiet is
@@ -82,10 +82,10 @@ separates them.
 Do not rebuild the starter by hand. Then 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.13.0 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.13.1 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.13.0 onboard read stopped/run-failed`. The starter is one this
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`. The starter is one this
 graph ships and the stack was chosen from its own supported list, so a command that
 returned an error is a run that broke, not a setup this release does not support.

package/onboarding/prompts/stopped/run-failed.md

@@ -35,7 +35,7 @@ put to them, stop here and send the report below.
 If they approve it, make that one fix and nothing else. Then come back into this run:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard resume
+npx --yes copilotkit@4.13.1 onboard resume
 ```
 
 Write the developer's approval to standard input, in one or two sentences: the fix they
@@ -58,7 +58,7 @@ Send one short report. Run the friction command without another developer questi
 ask the developer about telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.13.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.13.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped

package/onboarding/prompts/subagent/create-plan.md

@@ -170,7 +170,7 @@ here is work the developer did not ask for.
 Plan the threads drawer itself: add it from the selected drawer page, where this frontend
 does not already render one. Where this journey's frontend framework ships no threads
 drawer -- React Native --, plan that the thread is proved by
-`npx --yes copilotkit@4.13.0 verify --round-trip`, which needs no browser. Do not plan a
+`npx --yes copilotkit@4.13.1 verify --round-trip`, which needs no browser. Do not plan a
 step that opens the managed Intelligence dashboard.
 
 ## Order the plan into steps

package/onboarding/prompts/subagent/implement-and-validate.md

@@ -39,6 +39,13 @@ for the symbol you are about to write. Where the selected documentation page its
 a deprecated symbol, name that page under Blockers as `docs-wrong` friction and use the
 current symbol the package's own type definitions or changelog names.
 
+A symbol this graph names is not that case. The approved plan and the framework
+node carry the connection API for this stack, and `LangGraphAgent` from
+`@copilotkit/runtime/langgraph` is one of them: deprecated at its entrypoint,
+still the documented LangSmith path, and given no replacement by its own tooltip.
+Write what the plan names. Do not rewrite a cloned starter to satisfy this rule,
+and do not name the page that shows it under Blockers.
+
 The documentation supplies the wiring. The project supplies the application. Use that
 wiring in the project's domain. Do not copy an example's agent name, tools, or data.
 

package/onboarding/prompts/subagent/inspect-repository.md

@@ -7,7 +7,7 @@ Work only on the packet you were assigned. Inspect the repository without changi
 Run this first, from the target project directory:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard inspect --json
+npx --yes copilotkit@4.13.1 onboard inspect --json
 ```
 
 It answers the deterministic half of both packets exactly, from the same code

package/onboarding/prompts/subagent/prove-oss-baseline.md

@@ -19,7 +19,7 @@ Prove the live runtime in this order:
 4. Confirm from project files that the runtime constructor passes a `runner` option rather
    than an `intelligence` option. A package, import, project file, or key is not use proof.
 5. Run
-   `npx --yes copilotkit@4.13.0 verify --expect-runtime oss --round-trip --agent <expected-agent-id> --json`,
+   `npx --yes copilotkit@4.13.1 verify --expect-runtime oss --round-trip --agent <expected-agent-id> --json`,
    with the runtime URL or auth header options that this project needs. Require exit zero
    and the JSON `ok` field to be `true`.
 6. Drive one real request through the existing frontend, CopilotKit runtime, and expected