copilotkit 4.18.0 → 4.19.0

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

@@ -12,7 +12,7 @@ acted on. Send one short report before you stop. The friction command follows th
 setting the developer already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.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.
@@ -67,7 +67,7 @@ Approving the plan is the developer agreeing to every path it listed under
 app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.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
@@ -95,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.18.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
@@ -115,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.18.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
@@ -150,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.18.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.18.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
@@ -176,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.18.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
@@ -188,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.
@@ -203,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.18.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
@@ -219,7 +227,7 @@ hold.
 Then report that the container is settled, before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.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
@@ -230,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.18.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.18.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
@@ -263,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.18.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.18.0 onboard read proof/round-trip`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -293,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.18.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.18.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.18.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
@@ -120,7 +124,7 @@ friction commands follow the telemetry setting the developer already chose, so t
 separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.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.18.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.18.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.18.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.18.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.18.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.18.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.18.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.18.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.18.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.18.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.18.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.

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

@@ -1,7 +1,7 @@
 # Prove the user journey
 
 Do not do the proof work yourself. Spawn one proof subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read subagent/prove-round-trip` first and follow the
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read subagent/prove-round-trip` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the selected framework, frontend, model, approved plan, selected
@@ -13,6 +13,8 @@ Give it the browser or device control you recorded in the preflight as well. The
 drives the surface and cannot see your environment, so without that finding it spends the
 step discovering what you already know. A subagent told it has no control for the surface
 this frontend needs reports the skip outcome rather than looking for a way around it.
+A web run with no browser tool reports `skipped-no-browser-tool`. That outcome completes the
+run once the round trip is recorded as `passed`.
 
 A run that cloned a starter is the exception. Tell that subagent that this run cloned a
 starter, to finish after `verify --round-trip`, and to open no browser. The cloned code is what this repository's
@@ -22,7 +24,7 @@ expensive step in this setup. `verify --round-trip` reads the answer back off th
 so it holds for every runtime mount and needs no browser. Give that subagent no browser or
 device control, and have it report `skipped-cloned-starter` rather than a missing
 capability: nothing was unavailable, the run declined to spend it. That outcome completes
-the run. Every other skip says nothing drove the surface, and blocks it.
+the run.
 
 Give the subagent this guide for continued-development tools:
 https://docs.copilotkit.ai/build-with-agents.md
@@ -33,13 +35,13 @@ pass the time.
 Report each attempt at the journey as it ends, counting from one:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Record what that proof returned before you route on it:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.19.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Report the gate whatever it returned. A proof that never ran is `skipped`, not failed. A
@@ -48,7 +50,7 @@ to record it as `skipped`. The command prints one line and sends nothing else. W
 record each attempt as it ends.
 
 For every protected-path audit in this prompt, run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard audit` from the target app directory. If its result
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard audit` from the target app directory. If its result
 starts with `Status: blocked`, report the printed reason and use the route-out rules below.
 A blocked audit proved nothing changed and is not a preservation failure. If a
 protected-path audit reports a changed path, decide it the way the implementation prompt
@@ -57,7 +59,7 @@ returns none, so a finding with no Files changed section to test against routes
 path one of those sections names is this run's own change and routes out too. Accept a
 path only when a section this run collected covers the step that wrote it and does not
 name it:
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard protect --accept-external --path <path>`. Then run
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard protect --accept-external --path <path>`. Then run
 the audit again and name the path in the closing summary. Never repair, reset, or revert a
 protected path.
 
@@ -65,17 +67,23 @@ That holds for a repair cycle too. When the fix for a failing check lands on a p
 path, the path is still the developer's, however right the diagnosis is and however small
 the fix. Reading the file never settles who wrote it. Ask the developer to allow the
 change, and record their answer with
-`npx --prefer-offline --yes copilotkit@4.18.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>"`,
 or route out. Never repair it, and never send it to a repair worker.
 
 If the proof result starts with `Status: passed`, run the protected-path audit. Continue to
 `proof/complete` only if that audit passes. After the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read proof/complete`. A performed surface outcome with
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read proof/complete`. A performed surface outcome with
 the full round trip is core success even if a continued-development tool fails. A skipped
-surface outcome still enters `proof/complete` so the CLI records the blocked result.
-`skipped-cloned-starter` is the exception: the CLI records that run as complete. Do not
-describe a skipped surface as proved. Keep the Skills and MCP results separate from the proof
-result.
+surface outcome still enters `proof/complete`. The CLI records `skipped-cloned-starter` and
+`skipped-no-browser-tool` after a passed round trip as complete, and `skipped-no-device` as
+blocked. Do not describe a
+skipped surface as proved. Keep the Skills result separate from the proof result.
+
+A passed result can carry the surface-check outcome `failed` with the cause
+`browser-control-unresponsive`. It means that the browser tool stopped answering, not that
+the journey failed. Record the round trip as `passed`, and carry the cause to
+`proof/complete`. Do not send it to a repair worker, and do not run the proof again. No
+repair to the project reaches the tool, and a second attempt waits on the same hang.
 
 If the round trip proves and something after it blocks this run anyway -- the debugging
 surface, or a capability the approved plan already excluded for this framework -- read
@@ -148,7 +156,7 @@ Restart each project-owned process changed by the repair. Report the cycle, coun
 one:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then spawn a fresh proof subagent
@@ -166,7 +174,7 @@ proof cycles, use the route-out rules below.
 
 Route out only when the failure is not yours to fix, when the same proof still fails after
 three attempts, or when no evidence of the round trip can be produced. In those cases run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read stopped/run-failed`. The stack is supported:
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read stopped/run-failed`. The stack is supported:
 this run did not finish, which is a different ending and a different report. All three are
 about the round trip itself. A round trip that proved is not one of them, whatever failed
 after it.
@@ -177,7 +185,7 @@ friction command follows the telemetry setting the developer already chose, so i
 separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.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.

package/onboarding/prompts/research/gather.md

@@ -44,7 +44,7 @@ Before you end your turn to wait for the developer where the prompt states no de
 report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase awaiting-developer
 ```
 
 When the answer or the result arrives, continue from the step that paused. Do not read an
@@ -64,7 +64,7 @@ Both research subagents failing means this harness has no working subagent at al
 is worth recording once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase delegation-unavailable
 ```
 
 Then say once, in your own words, that this environment has no working subagents, so you
@@ -77,7 +77,7 @@ Before you ask the developer any setup question, finish every read-only investig
 preflight check in this section.
 
 Prepare two research assignments. Give each research subagent one assignment. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read subagent/inspect-repository` first and follow the
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read subagent/inspect-repository` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Require only its assigned packet.
@@ -91,7 +91,7 @@ Start both research subagents in parallel:
 Report that both subagents started:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase research-dispatched
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase research-dispatched
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -100,8 +100,8 @@ failed step.
 The research is under way. Continue to the surface-control preflight while it runs:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard read research/preflight
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read research/preflight
 ```
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.19.0 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 --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -39,7 +39,8 @@ verifier result.
 
 A target project directory that holds no project has no app directory to key on, and
 that is a merged result rather than a failed merge. Record that this run has no target app
-directory and no environment row, then take the read below. Do not send a focused directory
+directory and no environment row. Keep the toolchain reading: it is about this machine, not
+a directory, and the framework question reads it. Then take the read below. Do not send a focused directory
 check, and do not use the stop route: neither worker can find a directory a developer has
 not created yet, and the route below is where such a project picks its starter.
 
@@ -54,7 +55,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 --prefer-offline --yes copilotkit@4.18.0 onboard read research/route`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read research/route`.
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read stopped/run-failed`.

package/onboarding/prompts/research/preflight.md

@@ -5,71 +5,36 @@ every later step reads one recorded answer instead of guessing. Do not change ap
 code here, and do not wait for the research packets yet.
 
 Prove whether your coding-agent environment has browser or device control. Do not assume it
-either way, and do not report what you expect to be true. Use a browser or device tool already
-configured for the coding agent you are running as, the same way a later step uses the
-CopilotKit documentation server. With a browser tool, open one inert page such as
+either way, and do not report what you expect to be true. Use a browser or device tool that
+is already loaded in this session. With a browser tool, open one inert page such as
 `about:blank` and read its title. With a device tool and no browser, list the booted devices
 in one command: `adb devices -l`. Record the outcome of that attempt: `available` when the
-tool answered, `unavailable` when there was none to call or the page did not open. Use
-the control that matches the selected surface later.
+tool answered, `unavailable` when there was none to call or the page did not open. Use the
+control that matches the selected surface later.
 
-Where the browser probe answered, register nothing. The harness came equipped.
-
-Where no browser tool answered, register one for the coding agent you are running as, then
-run the same probe again and record what the second attempt did.
-
-Tell the developer in one line what you are about to register, that it lives in this coding
-agent's configuration rather than in their repository, and that they can remove it again.
-Say that before you run the command. The run does not ask again.
-
-Register this server:
-
-```text
-npx --yes @playwright/mcp@latest --browser chrome --isolated --output-dir <project>/.copilotkit/proof/browser
-```
-
-Replace `<project>` with the absolute path of the target project directory. The server is
-registered against the coding agent rather than against a directory, so a relative path here
-resolves wherever that server happens to start.
-
-`--browser chrome` drives an installed Google Chrome. Where this machine has none, use
-`--browser chromium` instead and expect Playwright to download a browser build. Tell the
-developer before that download starts. If the server then reports no build, run
-`npx playwright install chromium`, and if it still cannot find one, run
-`npx @playwright/mcp install-browser chrome-for-testing`. `--isolated` keeps the profile in
-memory, so it never touches their own Chrome profile. `--output-dir` keeps the snapshots and
-screenshots out of the developer's repository root: without it this server writes them to
-`.playwright-mcp/` beside their code, which a project that never asked for a browser has no
-reason to carry. Register it the way your own harness registers a server, which is the
-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 --prefer-offline --yes copilotkit@4.18.0 onboard start --run <onboarding_run_id>`. That
-restart is a step here, not an error.
+Register nothing. Do not add a browser MCP server to this coding agent, and do not install a
+browser. A server registered during a run loads only in the next session, so it cannot help
+this one. Where no tool answered, the run still completes: the proof step reports
+`skipped-no-browser-tool`, and the closing report tells the developer how to add a browser
+for their next session. Say in one line that the live UI check will be skipped and that the
+run can still complete.
 
 Do not add a browser or device driver to the project. A driver added there is a
-devDependency and a browser download in the diff of a repository that never asked for one,
-which is a different thing from a server registered against the coding agent.
-
-Where the second probe still does not answer -- no browser to drive, no network, or a
-harness that cannot register a server -- record `unavailable` and carry it. Do not keep
-trying. Say so in one line. Nothing here is for the developer to decide.
+devDependency and a browser download in the diff of a repository that never asked for one.
 
-Registering a server does not boot a device. Where the device probe found none, that is the
-whole finding.
+Where the device probe found no booted device, that is the whole finding.
 
 Report that the probe settled, whichever way it came out:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase surface-probed
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase surface-probed
 ```
 
 Then merge the research:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard read research/merge
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read research/merge
 ```
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read stopped/run-failed`.

package/onboarding/prompts/research/route.md

@@ -9,11 +9,12 @@ sends the run down one path.
 Before you route on, run this from the target app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.19.0 onboard protect
 ```
 
 It reads the working tree itself, records every changed or untracked path with a digest,
-and prints the list. Require its result to start with `Status: passed`.
+and prints the list. Require its result to start with `Status: passed`. On a restart of the
+same run, it prints the baseline the run already holds and re-reads nothing.
 
 Use the printed list as the protected path list for the rest of the run. Do not assemble
 that list yourself, and do not ask a subagent to hold it: every later audit reads the
@@ -41,7 +42,7 @@ On either, run this before you read the three findings below, and without asking
 purpose question:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.18.0 onboard read feature/channels/start
+npx --prefer-offline --yes copilotkit@4.19.0 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 +97,7 @@ settle these three from your own reading of the project. Each one comes from the
 packets or it is not proved.
 
 If all three are proved, prove the live starting state before any project file changes. Run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read proof/oss-baseline`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read proof/oss-baseline`.
 
 Route there before you ask the developer anything else. The questions after this prompt
 select a framework and a frontend that the findings already name, so a developer who
@@ -109,7 +110,7 @@ developer nor the repository findings prove what the project is for, ask one gui
 question about the user outcome. This asks what the developer wants to build before you
 select a framework. Give two or three short examples. Record the answer and give it to
 each later subagent. Then run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read credentials/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read credentials/plan`.
 
 Do not ask that question on the route above. A project carrying all three states its
 purpose in the application it already serves.
@@ -123,5 +124,5 @@ A purpose question here names a domain before that choice.
 Take the same read named above without asking.
 
 If authentication, inspection, or the baseline capture stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.18.0 onboard read stopped/run-failed`. None of them says anything
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read stopped/run-failed`. None of them says anything
 about whether this project's stack is supported, which is not yet known at this point.