copilotkit 4.9.47 → 4.9.50

package/onboarding/prompts/feature/voice/start.md

@@ -0,0 +1,45 @@
+# Add voice input to the existing CopilotKit app
+
+Treat voice as an OSS enhancement to an existing CopilotKit chat. Orchestrate with separate
+read-only, implementation, and proof subagents, each restricted to the target project.
+
+Before edits, inspect the runtime route, CopilotKit provider/chat composer, current agent,
+existing provider credential variable names (presence only), package versions, browser
+permissions approach, and test/dev commands. Prove the existing OSS baseline with `/info`,
+`npx --yes copilotkit@4.9.50 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+and a real UI request when a browser is available. If that baseline is absent, change nothing
+and direct the developer to generic onboarding first.
+
+Wait for the inspection subagent to finish. Then report that the inspection came back:
+
+```text
+npx --yes copilotkit@4.9.50 onboard checkpoint --phase research-returned
+```
+
+A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
+failed step.
+
+If the inspection did not prove the baseline this intent extends, stop here without
+changing files:
+
+```text
+npx --yes copilotkit@4.9.50 onboard read feature/stop
+```
+
+Do not run login, select Intelligence, create a credential, read a credential value, or
+replace the existing chat/runtime. Fetch the official voice guide before planning:
+https://docs.copilotkit.ai/voice.md
+Retry it a second way if needed. Use an existing user-owned provider credential only when
+the repository proves its variable name is configured; otherwise explain the setup gate and
+stop rather than writing a placeholder.
+
+Show a small plan for the documented transcription service, the existing composer, focused
+tests, and a microphone/canned-transcript proof. Ask for approval separately.
+
+After approval, report the plan this run is about to implement:
+
+```text
+npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+```
+
+Then run `npx --yes copilotkit@4.9.50 onboard read feature/voice/implement`.

package/onboarding/prompts/framework/ag2.md

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

package/onboarding/prompts/framework/agno.md

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

package/onboarding/prompts/framework/built-in.md

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

package/onboarding/prompts/framework/claude-sdk-python.md

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

package/onboarding/prompts/framework/claude-sdk-typescript.md

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

package/onboarding/prompts/framework/crewai-flows.md

@@ -54,7 +54,7 @@ variable names the repository proves or the developer named, these URLs, the ada
 shared-state limit.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/deep-agents.md

@@ -29,7 +29,7 @@ Record the selected framework, language, vendor, model, required credential vari
 names, these URLs, and each documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/google-adk.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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.

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

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

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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.9.50 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.47 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read unsupported/no-validated-path`.
+together, run `npx --yes copilotkit@4.9.50 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.47 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.9.50 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.47 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.50 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read frontend/react-spa`
-2. Next.js: `npx --yes copilotkit@4.9.47 onboard read frontend/nextjs`
-3. Angular: `npx --yes copilotkit@4.9.47 onboard read frontend/angular`
-4. Vue 3: `npx --yes copilotkit@4.9.47 onboard read frontend/vue`
-5. React Native: `npx --yes copilotkit@4.9.47 onboard read frontend/react-native`
+1. React SPA: `npx --yes copilotkit@4.9.50 onboard read frontend/react-spa`
+2. Next.js: `npx --yes copilotkit@4.9.50 onboard read frontend/nextjs`
+3. Angular: `npx --yes copilotkit@4.9.50 onboard read frontend/angular`
+4. Vue 3: `npx --yes copilotkit@4.9.50 onboard read frontend/vue`
+5. React Native: `npx --yes copilotkit@4.9.50 onboard read frontend/react-native`
 
 If no listed frontend fits, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.50 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.50 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 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.47 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.50 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.

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

@@ -2,12 +2,26 @@
 
 Do not implement the plan yourself. Use the step order in the approved plan.
 
+## Authorization requested by the plan
+
+Approving the plan is the developer agreeing to every path it listed under
+`Authorization requested`. Record each one before any implementation starts, from the target
+app directory:
+
+```text
+npx --yes copilotkit@4.9.50 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
+refused. Continue only if every result starts with `Status: passed`. If the plan listed
+nothing there, skip this section.
+
 ## Protected-path audit
 
 Run the audit from the target app directory:
 
 ```text
-npx --yes copilotkit@4.9.47 onboard audit
+npx --yes copilotkit@4.9.50 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -18,18 +32,24 @@ the result starts with `Status: passed`.
 revert a protected path. Also do not retry the audit: it reads files, so a second run of it
 answers the same.
 
-Decide each path the audit names, one at a time. Accept a path only when you can show that
-this run did not write it. Every implementation subagent reports what it touched in its
-Files changed section, so the test is whether the path appears in any Files changed section
-this run collected. If it appears in one, or the sections do not settle it, the change is
-this run's own: use the route-out rules. The plan cannot name a protected path, so a plan
-that does not name it proves nothing on its own.
+Decide each path the audit names, one at a time.
+
+A path the audit lists under `Authorized to change:` is not a finding. The developer approved
+it, the record says why, and the audit reports it rather than failing on it. Carry it into the
+summary with its reason. Nothing else is needed for it.
+
+For every other path, the rule is unchanged. Accept a path only when you can show that this
+run did not write it. Every implementation subagent reports what it touched in its Files
+changed section, so the test is whether the path appears in any Files changed section this
+run collected. If it appears in one, or the sections do not settle it, the change is this
+run's own: use the route-out rules. A plan names a protected path only under
+`Authorization requested`, so a plan that does not name it there proves nothing on its own.
 
 A path that no Files changed section names changed outside the run, and it is the
 developer's own file. Accept it by name:
 
 ```text
-npx --yes copilotkit@4.9.47 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.9.50 onboard protect --accept-external --path <path>
 ```
 
 Pass one `--path` for each path you accept. Accept only a path the audit named, and only
@@ -48,11 +68,11 @@ acceptance clears it, or route out. Do not send an audit result to a repair work
 Report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.47 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
 ```
 
 Spawn one implementation subagent. Tell it to run
-`npx --yes copilotkit@4.9.47 onboard read subagent/implement-and-validate` first and follow
+`npx --yes copilotkit@4.9.50 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
@@ -72,11 +92,11 @@ returned. Continue to proof only when that audit passes.
 After the selected implementation path passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.47 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.9.50 onboard checkpoint --phase build-validated
 ```
 
 Then run
-`npx --yes copilotkit@4.9.47 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.9.50 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -94,4 +114,4 @@ Route out for `Status: blocked`. Route out only when the failure is not yours to
 failure is in code this run did not write, the fix requires changing the developer's existing
 agent or frontend, the same command still fails after three repair attempts, or the
 documentation does not support the plan. In those cases run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -64,7 +64,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.9.47 verify --round-trip`, the runtime's own log, the AG-UI
+`npx --yes copilotkit@4.9.50 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.
@@ -76,7 +76,7 @@ the friction commands without another developer question. The CLI telemetry gate
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.47 onboard friction --category <slug> --cost-seconds <seconds>
+npx --yes copilotkit@4.9.50 onboard friction --category <slug> --cost-seconds <seconds>
 ```
 
 Write one or two sentences on the command's standard input. Pick one category from
@@ -88,7 +88,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.47 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
+npx --yes copilotkit@4.9.50 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 +105,14 @@ Tell the developer when you send a friction report. Do not quote or summarize th
 unless the developer asks. If the CLI says that telemetry is disabled or unavailable,
 state that the report was not sent and continue without another question.
 
-When the evidence is gathered, run `npx --yes copilotkit@4.9.47 onboard complete`, carrying
+When the evidence is gathered, run `npx --yes copilotkit@4.9.50 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.47 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.9.50 onboard complete --visual-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
@@ -120,7 +120,7 @@ The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
 For React Native:
 
 ```text
-npx --yes copilotkit@4.9.47 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.9.50 onboard complete --device-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-device`, or `failed`.
@@ -132,7 +132,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.47 onboard complete --visual-check <outcome> \
+npx --yes copilotkit@4.9.50 onboard complete --visual-check <outcome> \
   --frontend-url <the url you opened>
 ```
 
@@ -151,7 +151,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.47 onboard complete --visual-check performed --blocked-by <cause>
+npx --yes copilotkit@4.9.50 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.47 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --yes copilotkit@4.9.50 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.47 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --yes copilotkit@4.9.50 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,14 +35,14 @@ 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.47 onboard read conversion/plan`. That project already works.
+`npx --yes copilotkit@4.9.50 onboard read conversion/plan`. That project already works.
 What it needs is the conversion, not a build.
 
 If it proves another supported starting state, record that state and run
-`npx --yes copilotkit@4.9.47 onboard read credentials/plan`. This prompt is served
+`npx --yes copilotkit@4.9.50 onboard read credentials/plan`. This prompt is served
 whenever a project looks like an OSS integration, so a baseline that did not prove is an
 ordinary starting state rather than a failure.
 
 If it cannot identify the running process safely, exposes a secret, or finds a baseline
 failure that cannot be classified, run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.

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

@@ -1,7 +1,7 @@
 # Prove the user journey
 
 Do not do the proof work yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.9.47 onboard read subagent/prove-round-trip` first and follow the
+`npx --yes copilotkit@4.9.50 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
@@ -23,13 +23,13 @@ pass the time.
 Report each attempt at the journey as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.47 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.9.50 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.9.47 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.9.50 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 +37,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.47 onboard audit` from the target app directory. If its result
+`npx --yes copilotkit@4.9.50 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,13 +46,13 @@ 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.47 onboard protect --accept-external --path <path>`. Then run
+`npx --yes copilotkit@4.9.50 onboard protect --accept-external --path <path>`. Then run
 the audit again and name the path in the closing summary. Never repair, reset, or revert a
 protected path.
 
 If the proof result starts with `Status: passed`, run the protected-path audit. Continue to
 `proof/complete` only if that audit passes. After the audit passes, run
-`npx --yes copilotkit@4.9.47 onboard read proof/complete`. A performed surface outcome with
+`npx --yes copilotkit@4.9.50 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
@@ -108,7 +108,7 @@ Restart each project-owned process changed by the repair. Report the cycle, coun
 one:
 
 ```text
-npx --yes copilotkit@4.9.47 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.9.50 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then spawn a fresh proof subagent
@@ -126,7 +126,7 @@ and proof cycles.
 
 Route out only when the failure is not yours to fix, when the same proof still fails after
 three attempts, or when no evidence of the round trip can be produced. In those cases run
-`npx --yes copilotkit@4.9.47 onboard read unsupported/no-validated-path`. All three are
+`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`. All three are
 about the round trip itself. A round trip that proved is not one of them, whatever failed
 after it.
 
@@ -136,7 +136,7 @@ Run the feedback command without another developer question. The CLI telemetry g
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.47 onboard feedback
+npx --yes copilotkit@4.9.50 onboard feedback
 ```
 
 Write at most four lines to standard input: the step you stopped at and what stopped it.