copilotkit 4.17.0 → 4.19.0

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

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

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

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

package/onboarding/prompts/framework/llamaindex.md

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

package/onboarding/prompts/framework/mastra.md

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

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

@@ -11,7 +11,12 @@ For a user secret, run `dotnet user-secrets set OPENAI_API_KEY` from the agent d
 The app must read the same name through .NET configuration. An exported environment
 variable with that name takes precedence over the user secret.
 
-Run `dotnet --version` before you change the project.
+Run `dotnet --version` before you change the project. If it fails, no .NET SDK is on this
+shell's PATH. Do not change 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.19.0 onboard start --run <onboarding_run_id>`
+to resume the run after the restart. Then end your turn and wait for the developer.
 
 ## Documentation
 
@@ -36,7 +41,7 @@ Record the selected framework, provider, model, required credential variable nam
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

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

@@ -5,7 +5,12 @@ Use direct OpenAI for a new setup. Name its credential `OPENAI_API_KEY`.
 
 For a user secret, run `dotnet user-secrets set OPENAI_API_KEY` from the agent directory.
 The app must read the same name through .NET configuration. Run `dotnet --version` before
-you change the project.
+you change the project. If it fails, no .NET SDK is on this shell's PATH. Do not change
+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.19.0 onboard start --run <onboarding_run_id>` to resume the run
+after the restart. Then end your turn and wait for the developer.
 
 ## Documentation
 
@@ -44,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.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read starter/clone` before you fetch documentation.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -63,7 +63,7 @@ you create or build an Angular project. If the installed version is lower, selec
 supported version first and use it for every later command in this project.
 
 If the pages support the selection, record Angular and these URLs. Then run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read unsupported/no-validated-path`.
+together, run `npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read starter/clone` before you fetch documentation.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/plan.md

@@ -28,7 +28,8 @@ needs a frontend, show the valid choices and one recommendation based on reposit
 evidence, then ask the developer to choose.
 
 The valid choices are React SPA, Next.js, Angular, Vue 3, React Native, Slack, and
-Microsoft Teams. They are valid in every starting state. Do not show the internal route.
+Microsoft Teams. They are valid in every starting state. Route names are this graph's own
+bookkeeping. Say what the run is doing in the developer's words instead.
 
 Recommend the frontend the project already uses. Where there is no existing frontend,
 include Slack and Microsoft Teams in the frontend question. They are chat UIs, not
@@ -36,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.17.0 onboard read frontend/react-spa`
-2. Next.js: `npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/nextjs`
-3. Angular: `npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/angular`
-4. Vue 3: `npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/vue`
-5. React Native: `npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/react-native`
-6. Slack or Microsoft Teams: `npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/channels/start`
+1. React SPA: `npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/react-spa`
+2. Next.js: `npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/nextjs`
+3. Angular: `npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/angular`
+4. Vue 3: `npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/vue`
+5. React Native: `npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/react-native`
+6. Slack or Microsoft Teams: `npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read credentials/finalize-plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

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

@@ -6,14 +6,13 @@ Do not implement the plan yourself. Use the step order in the approved plan.
 
 Two rules below stop onboarding: a Learning Container create that fails for a reason other
 than the container already existing, and a `--accept-credential` refusal that names a lost
-variable. Each one ends a run the developer has already approved a plan for. Name the
-exact command, id, and error code that stopped you: a report that names only the step
-cannot be acted on. Send one short report before you stop. Run the friction
-command without another developer question. Do not ask the developer about telemetry: the
-command applies the setting they already have.
+variable. Each one ends a run the developer has already approved a plan for. Name the exact
+command, id, and error code that stopped you: a report that names only the step cannot be
+acted on. Send one short report before you stop. The friction command follows the telemetry
+setting the developer already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.19.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -68,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.17.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.19.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
@@ -96,7 +95,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.17.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>" --with-prior-change
+npx --prefer-offline --yes copilotkit@4.19.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
@@ -116,7 +115,7 @@ audit below describes, rather than use this section.
 Run the audit from the target app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.19.0 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -151,14 +150,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.17.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard protect --accept-credential --path <path>
+npx --prefer-offline --yes copilotkit@4.19.0 onboard protect --accept-credential --path <path>
 ```
 
 That route proves no recorded credential was lost, instead of taking the run's word that it
@@ -177,7 +176,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.17.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.19.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
@@ -189,6 +188,14 @@ and spawn a fresh implementation subagent with the same handoff and that list. I
 audit starts with `Status: blocked`, use the route-out rules instead. A subagent
 that already returned cannot pick up consent recorded after it was spawned.
 
+A failed audit can also list project files that name a credential file outside the
+repository. Such a file is not a protected path, and no route accepts it. It ties the commit
+to a folder in the developer's home directory, so the app has no model key on any other
+machine. Spawn a fresh implementation subagent with the same handoff and this one change:
+remove the outside path, and load the key the way the approved plan says, from the app's
+env file or from an environment variable. Then run the audit again. If the file is a
+protected path, or the plan names no other way to load the key, use the route-out rules.
+
 `Status: blocked` means the audit has no baseline to read. A blocked audit compared
 nothing and proved nothing changed. It is not a preservation failure: do not report a
 protected path as changed. Report the printed reason and use the route-out rules.
@@ -204,7 +211,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 --prefer-offline --yes copilotkit@4.17.0 learning containers create --id <id> --name <name> --json
+npx --prefer-offline --yes copilotkit@4.19.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
@@ -220,7 +227,7 @@ hold.
 Then report that the container is settled, before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase container-settled
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase container-settled
 ```
 
 Where the plan names a container the platform already held, report the same checkpoint and
@@ -231,11 +238,11 @@ create nothing. Where the plan names no container, skip this section.
 Report the plan this run is about to implement:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase plan-written
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase plan-written
 ```
 
 Spawn one implementation subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read subagent/implement-and-validate` first and follow
+`npx --prefer-offline --yes copilotkit@4.19.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
@@ -264,11 +271,11 @@ returned. Continue to proof only when that audit passes.
 After the selected implementation path passes, report it:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase build-validated
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase build-validated
 ```
 
 Then run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read proof/round-trip`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -294,9 +301,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.17.0 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -8,12 +8,16 @@ Do not complete onboarding without this evidence.
 Report whether the real UI was driven on this journey's own surface -- in a browser for a
 web frontend, on a device for React Native -- using the outcome the proof subagent
 returned. Do not soften it and do not leave it out: a run that never drove the UI proved
-the agent, not the surface, and the developer needs to know which they have.
+the agent, not the surface, and the developer needs to know which they have. For
+`skipped-no-browser-tool`, the command's list of what no browser checked is that report. Give
+it once, in the section about what was proved. Do not add a separate line, heading, or
+opening sentence about the missing browser.
 
 **Whether this run is complete is decided by the command at the end of this prompt, not
 here.** Run it before you write the summary, and let its output decide which summary you
 write. A run whose surface was never driven is blocked, not complete, unless it cloned a
-starter and records `skipped-cloned-starter`. For a blocked run, say so in the first
+starter and records `skipped-cloned-starter`, or had no browser tool loaded, records
+`skipped-no-browser-tool`, and recorded a passed round trip. For a blocked run, say so in the first
 line, name the evidence the command lists as missing, and do not describe the run as
 finished, working, or ready. Everything else below applies to either outcome.
 
@@ -85,7 +89,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 --prefer-offline --yes copilotkit@4.17.0 verify --round-trip`, the runtime's own log, the AG-UI
+`npx --prefer-offline --yes copilotkit@4.19.0 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
@@ -115,12 +119,12 @@ Learning Container. The servers end when that host ends, and a `localhost` URL o
 developer's machine only through a forwarded port. Write the items that output lists in
 place of this sentence.
 
-Report each thing that slowed this run down. Send at most four reports, worst first. Run
-the friction commands without another developer question. Do not ask the developer about
-telemetry: the command applies the setting they already have.
+Report each thing that slowed this run down. Send at most four reports, worst first. The
+friction commands follow the telemetry setting the developer already chose, so they need no
+separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.19.0 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
 ```
 
 Put one or two sentences in `--message`. Pick one category from
@@ -132,7 +136,7 @@ Pass --docs-path only for a docs-missing or docs-wrong report, naming the page t
 is about:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.19.0 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer --message "<sentences>"
 ```
 
 Give the page's site-relative path or its full URL, with no spaces, query string, or
@@ -149,24 +153,28 @@ 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 --prefer-offline --yes copilotkit@4.17.0 onboard complete`, carrying
+When the evidence is gathered, run `npx --prefer-offline --yes copilotkit@4.19.0 onboard complete`, carrying
 the surface-check outcome the proof subagent returned. Pass exactly one of `--visual-check`
 or `--device-check`, and pass the one that matches this journey's surface.
 
 For a web frontend -- React SPA, Next.js, Angular, Vue:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard complete --visual-check <outcome>
+npx --prefer-offline --yes copilotkit@4.19.0 onboard complete --visual-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-browser-tool`, `skipped-cloned-starter`, or
 `failed`. Use `skipped-cloned-starter` only for a run that cloned a starter and was told to
-open no browser. It is the one skip that does not block.
+open no browser. Use `skipped-no-browser-tool` for a run with no browser tool loaded in this
+session. `skipped-cloned-starter` does not block. `skipped-no-browser-tool` does not block
+when this run recorded a passed round trip with `onboard proof`. The command then prints
+what no browser checked and how to add a browser for the next session. Put each in the
+summary once, as the command prints it.
 
 For React Native:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard complete --device-check <outcome>
+npx --prefer-offline --yes copilotkit@4.19.0 onboard complete --device-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-device`, `skipped-cloned-starter`, or
@@ -179,7 +187,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 --prefer-offline --yes copilotkit@4.17.0 onboard complete --visual-check <outcome> \
+npx --prefer-offline --yes copilotkit@4.19.0 onboard complete --visual-check <outcome> \
   --frontend-url <the url you opened>
 ```
 
@@ -189,9 +197,9 @@ name -- and never the host itself. A run that opened the loopback IP literal los
 static chunk to a refusal, and the field is how that stops being invisible. Leave the flag
 off for React Native, which opens no URL.
 
-Pass the outcome you were given rather than the one you wanted. Anything but `performed` or
-`skipped-cloned-starter` prints what the missing check leaves unverified and ends this run
-as blocked. That output
+Pass the outcome you were given rather than the one you wanted. `failed` and
+`skipped-no-device` print what the missing check leaves unverified and end this run as
+blocked. That output
 is the developer's finding, so carry it into the summary rather than restating it as a
 smaller caveat.
 
@@ -199,13 +207,21 @@ If the round trip proved and something after it still blocked this run, add `--b
 to the same command:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard complete --visual-check performed --blocked-by <cause>
+npx --prefer-offline --yes copilotkit@4.19.0 onboard complete --visual-check performed --blocked-by <cause>
 ```
 
 The cause is one of `inspector` for a debugging surface that did not open,
 `plan-excluded-capability` for a capability the approved plan had already excluded for this
-framework, and `other` for anything else. Pick `other` rather than leaving the flag off.
-The command ends the run as blocked and prints what the blocker leaves unverified.
+framework, `browser-control-unresponsive` for a browser tool that stopped answering during
+the surface check, and `other` for anything else. Pick `other` rather than leaving the flag
+off. The command ends the run as blocked and prints what the blocker leaves unverified.
+
+`browser-control-unresponsive` is the one cause that goes with the failed check, because
+nothing drove the frontend:
+
+```text
+npx --prefer-offline --yes copilotkit@4.19.0 onboard complete --visual-check failed --blocked-by browser-control-unresponsive
+```
 
 The managed Intelligence dashboard is not among these, because nothing in this graph asks a
 run to open it. A run that records a blocker for a surface it was never sent to looks worse

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.17.0 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read conversion/plan`. That project already works.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read credentials/plan`. This prompt is served
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard read stopped/run-failed`. None of those mean the
+`npx --prefer-offline --yes copilotkit@4.19.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.