copilotkit 4.12.0 → 4.13.1

package/onboarding/prompts/proof/complete.md

@@ -32,6 +32,12 @@ about it: keep this version pin, wire this constructor, run this build. It never
 as an account of hitting it. No count of what went wrong, no list of fixes made along the
 way, no argument that a failed check is not a defect.
 
+Where this run connected and proved Rich Threads, explain in your own words that they
+preserve messages, generative UI, tool interactions, and application state so users
+can return to earlier work. Explain that these interactions can also provide evidence
+for Automatic Learning. Describe only the capabilities supported by this run's result.
+This is required content within the handoff, not a separate message or a new check.
+
 The handoff must include:
 
 - The URL of the running app.
@@ -41,11 +47,19 @@ The handoff must include:
   installation. Do not open it. This item makes the developer aware the dashboard is
   there, and it is a sentence to write rather than a check to perform. Nothing in this
   graph gates on the dashboard, so a dashboard this run never opened is not a finding,
-  not a caveat, and not a blocker.
+  not a caveat, and not a blocker. Where this run settled a Learning Container, tell the
+  developer they can use their project there to follow progress, review Insights and
+  supporting conversations, and approve proposed Skills as they become available.
 - What changed since the developer approved the plan. Name every path, version, or step
   the run departed from, and why. A deviation can be the right call and still has to
   reach the person who approved the thing it departed from. Where nothing departed, say
   that in one line rather than leaving the item out.
+- Every change to the existing agent's behavior: its system prompt or instructions, its
+  tools or what those tools do, its model or provider configuration, or its memory or
+  state handling. Name each one, name the file, and say the developer approved it. Where
+  none of them changed, write `none` on that line rather than leaving the item out. Such a
+  change answers differently everywhere the agent is used, not only in CopilotKit, and the
+  developer is the only one who can tell whether that is wanted.
 - The process IDs and stop commands for the running agent and frontend.
 - The `@copilotkit/*` versions this conversion changed, and what they were before.
 - On a conversion, the criterion this run was judged against, in the words the run was
@@ -70,19 +84,24 @@ 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.12.0 verify --round-trip`, the runtime's own log, the AG-UI
+`npx --yes copilotkit@4.13.1 verify --round-trip`, the runtime's own log, the AG-UI
 Event Inspector in the CopilotKit VS Code extension, and the CopilotKit Intelligence
 thread view
 instead. Naming the Inspector to a developer who cannot open it costs them the time it
 takes to conclude their own wiring is broken.
 
-Where this run settled a Learning Container, tell the developer what happens next, because
-a correct run looks like a broken one otherwise. Learning runs on its own: the first
-automatic run needs new threads from 15 distinct conversations in this container, and only
-the newest snapshot of each thread counts. Existing threads can receive their first
-container assignment after prior runs. Their surviving earlier history becomes eligible
-for collection and counts toward the same threshold. Creating a container does not enroll
-existing threads automatically.
+Where this run settled a Learning Container, explain in your own words that new
+conversations are routed to it, where Automatic Learning can find recurring patterns
+and propose reusable Skills to help the agent improve. The developer controls which
+Skills get approved. Explain that Learning results appear as new conversations provide
+enough evidence.
+
+These are required explanations within the existing handoff, not fixed wording or
+additional actions. Describe only the setup supported by this run's evidence. Do not
+claim this run produced Insights or Skills or configured automatic Skill delivery
+unless its evidence proves that. If no container was configured, report the actual
+reason and retain the project-management destination without implying that Learning
+is collecting evidence.
 
 Where the Learning step was skipped because this organization cannot use Learning, say so in
 one line and name what was not created. A skip nobody names reads as a container that
@@ -95,7 +114,7 @@ the friction commands without another developer question. Do not ask the develop
 telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.12.0 onboard friction --category <slug> --cost-seconds <seconds>
+npx --yes copilotkit@4.13.1 onboard friction --category <slug> --cost-seconds <seconds>
 ```
 
 Write one or two sentences on the command's standard input. Pick one category from
@@ -107,7 +126,7 @@ Pass --docs-path only for a docs-missing or docs-wrong report, naming the page t
 is about:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
+npx --yes copilotkit@4.13.1 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
 ```
 
 Give the page's site-relative path or its full URL, with no spaces, query string, or
@@ -124,14 +143,14 @@ Tell the developer when you send a friction report. Do not quote or summarize th
 unless the developer asks. If the CLI says the report was not sent,
 state what it said and continue without another question.
 
-When the evidence is gathered, run `npx --yes copilotkit@4.12.0 onboard complete`, carrying
+When the evidence is gathered, run `npx --yes copilotkit@4.13.1 onboard complete`, carrying
 the surface-check outcome the proof subagent returned. Pass exactly one flag, and pass the
 one that matches this journey's surface.
 
 For a web frontend -- React SPA, Next.js, Angular, Vue:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.13.1 onboard complete --visual-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-browser-tool`, `skipped-cloned-starter`, or
@@ -141,7 +160,7 @@ open no browser. It is the one skip that does not block.
 For React Native:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.13.1 onboard complete --device-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-device`, `skipped-cloned-starter`, or
@@ -154,7 +173,7 @@ browser-origin CORS, so the flag you pass is how this run states which surface i
 For a web frontend, also pass the URL the browser opened:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard complete --visual-check <outcome> \
+npx --yes copilotkit@4.13.1 onboard complete --visual-check <outcome> \
   --frontend-url <the url you opened>
 ```
 
@@ -173,7 +192,7 @@ If the round trip proved and something after it still blocked this run, add `--b
 to the same command:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard complete --visual-check performed --blocked-by <cause>
+npx --yes copilotkit@4.13.1 onboard complete --visual-check performed --blocked-by <cause>
 ```
 
 The cause is one of `inspector` for a debugging surface that did not open,

package/onboarding/prompts/proof/oss-baseline.md

@@ -1,7 +1,7 @@
 # Prove the existing OSS baseline
 
 Do not prove the baseline yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.12.0 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --yes copilotkit@4.13.1 onboard read subagent/prove-oss-baseline` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the repository findings and exact CLI package spec.
@@ -17,7 +17,7 @@ Wait for the subagent to finish.
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --yes copilotkit@4.13.1 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
 ```
 
 Report the gate whatever it returned. Pass `passed` when the subagent proved a predicate,
@@ -35,12 +35,12 @@ Do not change project files before this proof ends. Starting existing developmen
 processes and their ignored runtime files is allowed.
 
 If the subagent proves the `both-oss` predicate, keep its evidence with the plan and run
-`npx --yes copilotkit@4.12.0 onboard read conversion/plan`. That project already works.
+`npx --yes copilotkit@4.13.1 onboard read conversion/plan`. That project already works.
 What it needs is the conversion, not a build.
 
 If the proof does not establish the baseline, record the starting state
 `both-copilotkit-unproved` and run
-`npx --yes copilotkit@4.12.0 onboard read credentials/plan`. This prompt is served
+`npx --yes copilotkit@4.13.1 onboard read credentials/plan`. This prompt is served
 whenever a project looks like an OSS integration, so a baseline that did not prove is an
 ordinary starting state rather than a failure. Keep the failing predicate with the plan.
 
@@ -54,5 +54,5 @@ and the plan preserves it rather than repeating it.
 
 If it cannot identify the running process safely, exposes a secret, or finds a baseline
 failure that cannot be classified, run
-`npx --yes copilotkit@4.12.0 onboard read stopped/run-failed`. None of those mean the
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`. None of those mean the
 project is unsupported: they mean this run did not establish what it needed to.

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

@@ -1,7 +1,7 @@
 # Prove the user journey
 
 Do not do the proof work yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.12.0 onboard read subagent/prove-round-trip` first and follow the
+`npx --yes copilotkit@4.13.1 onboard read subagent/prove-round-trip` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the selected framework, frontend, model, approved plan, selected
@@ -33,13 +33,13 @@ pass the time.
 Report each attempt at the journey as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.13.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Report the gate whatever it returned. A proof that never ran is `skipped`, not failed. The
@@ -47,7 +47,7 @@ command prints one line and sends nothing else. Where a repair cycle runs the pr
 record each attempt as it ends.
 
 For every protected-path audit in this prompt, run
-`npx --yes copilotkit@4.12.0 onboard audit` from the target app directory. If its result
+`npx --yes copilotkit@4.13.1 onboard audit` from the target app directory. If its result
 starts with `Status: blocked`, report the printed reason and use the route-out rules below.
 A blocked audit proved nothing changed and is not a preservation failure. If a
 protected-path audit reports a changed path, decide it the way the implementation prompt
@@ -56,7 +56,7 @@ returns none, so a finding with no Files changed section to test against routes
 path one of those sections names is this run's own change and routes out too. Accept a
 path only when a section this run collected covers the step that wrote it and does not
 name it:
-`npx --yes copilotkit@4.12.0 onboard protect --accept-external --path <path>`. Then run
+`npx --yes copilotkit@4.13.1 onboard protect --accept-external --path <path>`. Then run
 the audit again and name the path in the closing summary. Never repair, reset, or revert a
 protected path.
 
@@ -64,12 +64,12 @@ That holds for a repair cycle too. When the fix for a failing check lands on a p
 path, the path is still the developer's, however right the diagnosis is and however small
 the fix. Reading the file never settles who wrote it. Ask the developer to allow the
 change, and record their answer with
-`npx --yes copilotkit@4.12.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`,
+`npx --yes copilotkit@4.13.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`,
 or route out. Never repair it, and never send it to a repair worker.
 
 If the proof result starts with `Status: passed`, run the protected-path audit. Continue to
 `proof/complete` only if that audit passes. After the audit passes, run
-`npx --yes copilotkit@4.12.0 onboard read proof/complete`. A performed surface outcome with
+`npx --yes copilotkit@4.13.1 onboard read proof/complete`. A performed surface outcome with
 the full round trip is core success even if a continued-development tool fails. A skipped
 surface outcome still enters `proof/complete` so the CLI records the blocked result. Do not
 describe a skipped surface as proved. Keep the Skills and MCP results separate from the proof
@@ -97,6 +97,17 @@ times. Use the route-out rules below for a blocked or third failed result.
 Enter the code-repair branch only for a source, configuration, dependency, or tracked-file
 defect.
 
+The existing agent's behavior stays outside that branch. It is four things: the agent's
+system prompt and instructions, its tools and what those tools do, its model and provider
+configuration, and its memory or state handling. Repair a failing proof on the CopilotKit
+side first -- the frontend rendering, the tool schema, the runtime wiring. Where the only
+fix the repair worker can find is a change to the agent's instructions or tools, it stops
+and returns the failing predicate with the change it proposes. Report both to the
+developer and send that repair only after they approve it. An approved change is a
+behavior change and the closing report names it as one. Never call a change to the agent's
+instructions or tools a repair, and never send one to a repair worker without that
+approval. If you cannot ask, or the developer declines, use the route-out rules below.
+
 If the starter shortcut created the selected path, spawn one repair subagent. Give it the
 failed step, proof evidence, generated path list, selected framework, frontend, model, exact
 target app directory, documentation, and policy.
@@ -125,7 +136,7 @@ Restart each project-owned process changed by the repair. Report the cycle, coun
 one:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then spawn a fresh proof subagent
@@ -143,18 +154,18 @@ 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.12.0 onboard read stopped/run-failed`. The stack is supported:
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`. The stack is supported:
 this run did not finish, which is a different ending and a different report. All three are
 about the round trip itself. A round trip that proved is not one of them, whatever failed
 after it.
 
 If you stop here without taking that route -- a repair cycle you cannot finish, a limit in
 your own harness, a run that has run out -- 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.
+friction command without another developer question: it applies the telemetry setting the
+developer already set.
 
 ```text
-npx --yes copilotkit@4.12.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.13.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.

package/onboarding/prompts/research/gather.md

@@ -14,14 +14,12 @@ notification. Where your own harness hands you the report from the dispatch itse
 you already hold the result. Either way there is nothing to poll.
 
 After you dispatch, do the work that does not depend on the result -- dispatch the other
-subagent, run the preflight below -- and then stop and wait. Wherever a prompt in this graph
-says to wait for a subagent to finish, that is what it means.
+subagent, run the preflight the next prompt gives you -- and then stop and wait. Wherever a
+prompt in this graph says to wait for a subagent to finish, that is what it means.
 
 Do not sleep to pass the time. Not `sleep`, not `/bin/sleep`, not a timer under another
 name, and not a loop that re-checks whether a result has arrived. Sleeping tells you nothing
-that waiting for the result does not, and it spends wall clock, which is one of the things
-this journey is measured on. One recorded run spent most of two hours asleep between
-dispatches that had all returned in seconds.
+that waiting for the result does not, and it spends wall clock.
 
 ## When a subagent cannot work
 
@@ -36,7 +34,7 @@ Both research subagents failing means this harness has no working subagent at al
 is worth recording once:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard checkpoint --phase delegation-unavailable
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase delegation-unavailable
 ```
 
 Then say once, in your own words, that this environment has no working subagents, so you
@@ -49,7 +47,7 @@ Before you ask the developer any setup question, finish every read-only investig
 preflight check in this section.
 
 Prepare two research assignments. Give each research subagent one assignment. Tell it to run
-`npx --yes copilotkit@4.12.0 onboard read subagent/inspect-repository` first and follow the
+`npx --yes copilotkit@4.13.1 onboard read subagent/inspect-repository` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Require only its assigned packet.
@@ -60,108 +58,20 @@ Start both research subagents in parallel:
 2. Spawn a second research subagent. Assign it the environment evidence packet.
 3. Start both research subagents. Then continue.
 
-Continue to the surface-control preflight.
-
-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: a run that guesses here records a
-capability every later step then trusts. 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
-`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.
-
-Where the browser probe answered, register nothing. The harness came equipped and the run
-owes it no setup.
-
-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. 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 the Google Chrome the developer already has, so this downloads no
-browser. `--isolated` keeps the profile in memory, so it never touches their own Chrome
-profile. `--output-dir` is what 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, and which this setup's
-own evidence rule already has a place for. Register it the way your own harness registers a
-server, which is the mechanism a later step uses for the CopilotKit documentation server.
-
-Tell the developer in one line what you registered, that it drives their installed Chrome,
-and that it lives in this coding agent's configuration rather than in their repository. Do
-not ask them to approve it, and do not ask a second question about it.
-
-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 Chrome to drive, no network, or a
-harness that cannot register a server -- record `unavailable` and carry it. Do not keep
-trying, and do not ask the developer about this tool limit.
-
-Registering a server does not boot a device. Where the device probe found none, that is the
-whole finding, and a browser is not a substitute for a device.
-
-Wait for both research subagents to finish.
-
-## Settle the port
-
-The findings name the ports this project declares and the ports already held on this
-machine. Pick one free port for the frontend now, and use that number for the rest of the
-run: in the plan, in the implementation, and in the proof. Record it with the findings you
-hand to every later subagent.
-
-Do not let a later step pick again. A run that decides the port three times produces three
-numbers, and `verify` reads none of them: with no recorded URL it assumes port 3000, and
-whatever holds that port answers. An unrelated checkout on this machine then reports as
-this project's proven wiring.
-
-Project selection is where the settled port is written down, through `--runtime-url`.
-
-Then report that the research came back:
+Report that both subagents started:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase research-dispatched
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
 failed step.
 
-Continue only if both research results start with `Status: passed`. For `Status: failed`,
-retry only that packet with its failed items, up to three attempts. For `Status: blocked`,
-or a third failed result, use the stop route at the end of this prompt.
+The research is under way. Continue to the surface-control preflight while it runs:
 
-Merge both evidence packets by item. On a conflict, spawn one fresh read-only verifier with
-the item, both cited findings, and the research limits. Require its result to start with
-`Status: passed`, `Status: failed`, or `Status: blocked`. Use only a passed cited result. Do
-not inspect the project to settle the conflict yourself. Use the stop route for a non-pass
-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
-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.
-
-A directory holding only a Git repository, a coding agent's own configuration, editor
-settings or scratch notes holds no project. `onboard inspect` reports that as
-`appDiscovery.reason` of `no-project`.
-
-For a target project that does hold an app, match environment evidence to the target app
-directory from the project packet. Require one target app directory and one matching
-environment row. If either packet gives no match or more than one match, send each research
-worker a focused directory check. Continue only when both workers return the same one target
-app directory. Both results must start with `Status: passed`. Otherwise, use the stop route.
-
-When both research results are merged, run
-`npx --yes copilotkit@4.12.0 onboard read research/route`.
+```text
+npx --yes copilotkit@4.13.1 onboard read research/preflight
+```
 
 If inspection stops onboarding, run
-`npx --yes copilotkit@4.12.0 onboard read stopped/run-failed`.
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`.

package/onboarding/prompts/research/merge.md

@@ -0,0 +1,60 @@
+# Merge the research and settle the port
+
+The surface is settled. This phase collects both research packets, picks the port the rest
+of the run uses, and merges the findings into one answer.
+
+Wait for both research subagents to finish.
+
+## Settle the port
+
+The findings name the ports this project declares and the ports already held on this
+machine. Pick one free port for the frontend now, and use that number for the rest of the
+run: in the plan, in the implementation, and in the proof. Record it with the findings you
+hand to every later subagent.
+
+Do not let a later step pick again. A run that decides the port three times produces three
+numbers, and `verify` reads none of them: with no recorded URL it assumes port 3000, and
+whatever holds that port answers.
+
+Project selection is where the settled port is written down, through `--runtime-url`.
+
+Then report that the research came back:
+
+```text
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase research-returned
+```
+
+A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
+failed step.
+
+Continue only if both research results start with `Status: passed`. For `Status: failed`,
+retry only that packet with its failed items, up to three attempts. For `Status: blocked`,
+or a third failed result, use the stop route at the end of this prompt.
+
+Merge both evidence packets by item. On a conflict, spawn one fresh read-only verifier with
+the item, both cited findings, and the research limits. Require its result to start with
+`Status: passed`, `Status: failed`, or `Status: blocked`. Use only a passed cited result. Do
+not inspect the project to settle the conflict yourself. Use the stop route for a non-pass
+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
+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.
+
+A directory holding only a Git repository, a coding agent's own configuration, editor
+settings or scratch notes holds no project. `onboard inspect` reports that as
+`appDiscovery.reason` of `no-project`.
+
+For a target project that does hold an app, match environment evidence to the target app
+directory from the project packet. Require one target app directory and one matching
+environment row. If either packet gives no match or more than one match, send each research
+worker a focused directory check. Continue only when both workers return the same one target
+app directory. Both results must start with `Status: passed`. Otherwise, use the stop route.
+
+When both research results are merged, run
+`npx --yes copilotkit@4.13.1 onboard read research/route`.
+
+If inspection stops onboarding, run
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`.

package/onboarding/prompts/research/preflight.md

@@ -0,0 +1,75 @@
+# Prove what this environment can drive
+
+The research subagents are running. This phase settles what your coding agent can drive, so
+every later step reads one recorded answer instead of guessing. Do not change application
+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
+`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.
+
+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 --yes copilotkit@4.13.1 onboard start --run <onboarding_run_id>`. That
+restart is a step here, not an error.
+
+Do not add a browser or device driver to the project. A driver added there is a
+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.
+
+Registering a server does not boot a device. Where the device probe found none, that is the
+whole finding.
+
+Report that the probe settled, whichever way it came out:
+
+```text
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase surface-probed
+```
+
+Then merge the research:
+
+```text
+npx --yes copilotkit@4.13.1 onboard read research/merge
+```
+
+If inspection stops onboarding, run
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`.

package/onboarding/prompts/research/route.md

@@ -9,7 +9,7 @@ sends the run down one path.
 Before you route on, run this from the target app directory:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard protect
+npx --yes copilotkit@4.13.1 onboard protect
 ```
 
 It reads the working tree itself, records every changed or untracked path with a digest,
@@ -28,6 +28,30 @@ graph exists to create is never stopped by them.
 If the result starts with `Status: blocked`, report the printed reason and use the stop
 route at the end of this prompt.
 
+## Route a named Channel before the findings
+
+The prompt the developer copied names the docs page it came from. A Slack or Teams docs
+page names the surface this run is for. So does a developer who has already said Slack or
+Microsoft Teams. Either one settles the frontend.
+
+Record that docs page and give it to every later node and subagent. The copied prompt is
+the only carrier of the surface the developer wants, and no flag states it.
+
+On either, run this before you read the three findings below, and without asking the
+purpose question:
+
+```text
+npx --yes copilotkit@4.13.1 onboard read feature/channels/start
+```
+
+Name the provider to that node so it does not ask again. A Slack page names Slack. A Teams
+page names Teams.
+
+Take this route whatever the three findings prove. An agent, a frontend and a CopilotKit
+integration are a valid start for a Channel, not a reason to convert the application: the
+run keeps that code as it is and wires a managed Channel onto it. Do not send a Channel
+request to the conversion route.
+
 ## What the merged findings must contain
 
 If a repository file exists, each finding must cite it. For an empty project, the subagents
@@ -72,7 +96,7 @@ settle these three from your own reading of the project. Each one comes from the
 packets or it is not proved.
 
 If all three are proved, prove the live starting state before any project file changes. Run
-`npx --yes copilotkit@4.12.0 onboard read proof/oss-baseline`.
+`npx --yes copilotkit@4.13.1 onboard read proof/oss-baseline`.
 
 Route there before you ask the developer anything else. The questions after this prompt
 select a framework and a frontend that the findings already name, so a developer who
@@ -83,9 +107,9 @@ these three findings.
 For every other combination of the three, take one more step first. If neither the
 developer nor the repository findings prove what the project is for, ask one guided
 question about the user outcome. This asks what the developer wants to build before you
-select a framework. Give two or three short examples and offer a minimal starter. Record
-the answer and give it to each later subagent. Then run
-`npx --yes copilotkit@4.12.0 onboard read credentials/plan`.
+select a framework. Give two or three short examples. Record the answer and give it to
+each later subagent. Then run
+`npx --yes copilotkit@4.13.1 onboard read credentials/plan`.
 
 Do not ask that question on the route above. A project carrying all three states its
 purpose in the application it already serves.
@@ -97,5 +121,5 @@ A purpose question here names a domain before that choice.
 Take the same read named above without asking.
 
 If authentication or inspection stops onboarding, run
-`npx --yes copilotkit@4.12.0 onboard read stopped/run-failed`. Neither says anything
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`. Neither says anything
 about whether this project's stack is supported, which is not yet known at this point.