copilotkit 4.10.1 → 4.12.0

package/onboarding/prompts/frontend/plan.md

@@ -9,26 +9,31 @@ the alternatives short. When the frontend is unknown, use this rule: Ask one fro
 question that lists the recommendation and valid choices. Do not ask a yes-or-no question
 first. Do not ask about the model or project in this step.
 
+If the developer already named Slack or Microsoft Teams, use that choice.
+If the copied prompt came from a Slack or Teams docs page, use that page as the named frontend.
+
 If the project has a frontend, preserve it and use the matching route below. If the project
 needs a frontend, show the valid choices and one recommendation based on repository
 evidence, then ask the developer to choose.
 
-The valid choices are React SPA, Next.js, Angular, Vue 3, and React Native. They are valid
-in every starting state. Do not show the internal route.
+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.
 
 Recommend the frontend the project already uses. Where there is no existing frontend,
-recommend the one the developer names, and say what each choice implies for where the
-CopilotKit runtime lives: Next.js hosts it in a route handler, Angular in its SSR
-server, and Vue 3, React SPA and React Native reach a runtime that runs as its own
-process.
+include Slack and Microsoft Teams in the frontend question. They are chat UIs, not
+CopilotKit web apps. Then recommend the one the developer names, and say what each choice implies for where the CopilotKit runtime lives: Next.js hosts it in a route handler, Angular in its SSR server, and Vue 3, React SPA and React Native reach a runtime that runs as its own process. Slack and Microsoft Teams use a long-running Channel host, not a CopilotKit web app.
 
 Use exactly one matching internal route:
 
-1. React SPA: `npx --yes copilotkit@4.10.1 onboard read frontend/react-spa`
-2. Next.js: `npx --yes copilotkit@4.10.1 onboard read frontend/nextjs`
-3. Angular: `npx --yes copilotkit@4.10.1 onboard read frontend/angular`
-4. Vue 3: `npx --yes copilotkit@4.10.1 onboard read frontend/vue`
-5. React Native: `npx --yes copilotkit@4.10.1 onboard read frontend/react-native`
+1. React SPA: `npx --yes copilotkit@4.12.0 onboard read frontend/react-spa`
+2. Next.js: `npx --yes copilotkit@4.12.0 onboard read frontend/nextjs`
+3. Angular: `npx --yes copilotkit@4.12.0 onboard read frontend/angular`
+4. Vue 3: `npx --yes copilotkit@4.12.0 onboard read frontend/vue`
+5. React Native: `npx --yes copilotkit@4.12.0 onboard read frontend/react-native`
+6. Slack or Microsoft Teams: `npx --yes copilotkit@4.12.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 --yes copilotkit@4.10.1 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-native.md

@@ -15,7 +15,7 @@ documents `useRenderTool`, which is React Native's own hook for drawing a tool t
 already has. That is a different job and needs a tool in the agent.
 
 If the pages support the selection, record React Native and these URLs. Then run
-`npx --yes copilotkit@4.10.1 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.12.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.10.1 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-spa.md

@@ -11,7 +11,7 @@ not move the agent into it.
 - https://docs.copilotkit.ai/react-spa.md
 
 If the page supports the selection, record React SPA and this URL. Then run
-`npx --yes copilotkit@4.10.1 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.12.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.10.1 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/vue.md

@@ -16,7 +16,7 @@ page above. Vue has its own `useComponent`, which is not the React package. Take
 that reference page rather than from a Vue generative-UI guide, which is not published.
 
 If the pages support the selection, record Vue 3 and these URLs. Then run
-`npx --yes copilotkit@4.10.1 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.12.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.10.1 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

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

@@ -7,11 +7,12 @@ Do not implement the plan yourself. Use the step order in the approved plan.
 One rule below stops onboarding: a Learning Container create that fails for a reason other
 than the container already existing. It 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. The CLI telemetry gate decides whether the
-report is sent.
+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.
 
 ```text
-npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.12.0 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -24,6 +25,17 @@ carries any of those, prints the reason, and exits zero. A refused report is not
 step. Send the report, then stop. Reporting is not a route change and does not resume the
 run.
 
+## Departing from the approved plan
+
+The developer approved a written plan and was told that approval was the last thing this
+run needed from them. A step that cannot be built as written is therefore a change to the
+only thing they agreed to.
+
+Where you depart from a path, a version, or a step the plan named, record it: what the
+plan said, what you did instead, and why. Carry that record into the closing summary,
+which has an item for it. Do not stop for a departure that is the right call, and do not
+leave it unrecorded either.
+
 ## Authorization requested by the plan
 
 Approving the plan is the developer agreeing to every path it listed under
@@ -31,19 +43,24 @@ Approving the plan is the developer agreeing to every path it listed under
 app directory:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.12.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
 refused. Continue only if every result starts with `Status: passed`. If the plan listed
 nothing there, skip this section.
 
+What you record here covers changing the file. It does not cover removing it. Never delete,
+move, or rename a protected path, whatever the plan says: the audit fails a path that is
+gone even when consent was recorded for it, and no command clears that. If a step cannot
+proceed without removing one, route out and report the path.
+
 If a path the plan listed has already changed, the developer changed it after the capture.
 No implementation step has run yet, so the change is theirs rather than this run's. Record
 consent over it by adding one flag:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>" --with-prior-change
+npx --yes copilotkit@4.12.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
@@ -62,7 +79,7 @@ rather than this section.
 Run the audit from the target app directory:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard audit
+npx --yes copilotkit@4.12.0 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -75,7 +92,7 @@ answers the same.
 
 Decide each path the audit names, one at a time.
 
-A path the audit lists under `Authorized to change:` is not a finding. The developer approved
+A path the audit lists under `Authorized to modify:` is not a finding. The developer approved
 it, the record says why, and the audit reports it rather than failing on it. Carry it into the
 summary with its reason. Nothing else is needed for it.
 
@@ -97,14 +114,14 @@ A path that no Files changed section names changed outside the run, and it is th
 developer's own file. Accept it by name:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.12.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 --yes copilotkit@4.10.1 onboard protect --accept-credential --path <path>
+npx --yes copilotkit@4.12.0 onboard protect --accept-credential --path <path>
 ```
 
 That route proves no recorded credential was lost, instead of taking the run's word that it
@@ -123,7 +140,7 @@ neither does a one-line fix. Never repair, reset, or revert it. Ask the develope
 the change, and record the answer they give:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.12.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
@@ -144,7 +161,7 @@ create it now, from the target app directory. The developer approved the id befo
 made, so this is the first point at which it can be created:
 
 ```text
-npx --yes copilotkit@4.10.1 learning containers create --id <id> --name <name> --json
+npx --yes copilotkit@4.12.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
@@ -160,7 +177,7 @@ hold.
 Then report that the container is settled, before any edit:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase container-settled
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase container-settled
 ```
 
 Where the plan names a container the platform already held, report the same checkpoint and
@@ -169,11 +186,11 @@ create nothing. Where the plan names no container, skip this section.
 Report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase plan-written
 ```
 
 Spawn one implementation subagent. Tell it to run
-`npx --yes copilotkit@4.10.1 onboard read subagent/implement-and-validate` first and follow
+`npx --yes copilotkit@4.12.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
@@ -193,11 +210,11 @@ returned. Continue to proof only when that audit passes.
 After the selected implementation path passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase build-validated
 ```
 
 Then run
-`npx --yes copilotkit@4.10.1 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.12.0 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -219,9 +236,9 @@ the same command still fails after three repair attempts, or a result starts wit
 `Status: blocked`. A defect in a package this run installed is not a stack CopilotKit does
 not serve, a command this run cannot get to pass is not one either, and a blocked audit
 proved nothing about the stack. In those cases run
-`npx --yes copilotkit@4.10.1 onboard read stopped/run-failed`.
+`npx --yes copilotkit@4.12.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 --yes copilotkit@4.10.1 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -37,11 +37,15 @@ The handoff must include:
 - The URL of the running app.
 - The command that starts the app in the future.
 - The debugging surface this journey's frontend can reach, named below.
-- How to use https://intelligence.copilotkit.ai to manage the Intelligence
+- How to use https://intelligence.copilotkit.ai to manage the CopilotKit Intelligence
   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.
+- 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.
 - 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
@@ -66,17 +70,19 @@ 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.10.1 verify --round-trip`, the runtime's own log, the AG-UI
-Event Inspector in the CopilotKit VS Code extension, and the Intelligence thread view
+`npx --yes copilotkit@4.12.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
 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. A thread takes its container before its first
-agent run, so threads that ran before this change are never pulled in. The container starts
-empty on purpose.
+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 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
@@ -85,11 +91,11 @@ exists, and the developer then waits for insights from a container this run neve
 State that the servers remain running after proof.
 
 Report each thing that slowed this run down. Send at most four reports, worst first. Run
-the friction commands without another developer question. The CLI telemetry gate decides
-whether the report is sent.
+the friction commands without another developer question. Do not ask the developer about
+telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.10.1 onboard friction --category <slug> --cost-seconds <seconds>
+npx --yes copilotkit@4.12.0 onboard friction --category <slug> --cost-seconds <seconds>
 ```
 
 Write one or two sentences on the command's standard input. Pick one category from
@@ -101,7 +107,7 @@ Pass --docs-path only for a docs-missing or docs-wrong report, naming the page t
 is about:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
+npx --yes copilotkit@4.12.0 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
@@ -118,25 +124,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 --yes copilotkit@4.10.1 onboard complete`, carrying
+When the evidence is gathered, run `npx --yes copilotkit@4.12.0 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.10.1 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.12.0 onboard complete --visual-check <outcome>
 ```
 
-The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
+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.
 
 For React Native:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.12.0 onboard complete --device-check <outcome>
 ```
 
-The outcome is one of `performed`, `skipped-no-device`, or `failed`.
+The outcome is one of `performed`, `skipped-no-device`, `skipped-cloned-starter`, or
+`failed`.
 
 The two flags are not interchangeable and neither takes the other's outcomes. A browser
 proves nothing about a React Native view tree, and a device capture proves nothing about
@@ -145,7 +154,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.10.1 onboard complete --visual-check <outcome> \
+npx --yes copilotkit@4.12.0 onboard complete --visual-check <outcome> \
   --frontend-url <the url you opened>
 ```
 
@@ -164,7 +173,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.10.1 onboard complete --visual-check performed --blocked-by <cause>
+npx --yes copilotkit@4.12.0 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.10.1 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --yes copilotkit@4.12.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 --yes copilotkit@4.10.1 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --yes copilotkit@4.12.0 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.10.1 onboard read conversion/plan`. That project already works.
+`npx --yes copilotkit@4.12.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 --yes copilotkit@4.10.1 onboard read credentials/plan`. This prompt is served
+`npx --yes copilotkit@4.12.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.
 
@@ -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.10.1 onboard read stopped/run-failed`. None of those mean the
+`npx --yes copilotkit@4.12.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 --yes copilotkit@4.10.1 onboard read subagent/prove-round-trip` first and follow the
+`npx --yes copilotkit@4.12.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
@@ -20,8 +20,9 @@ starter smoke jobs already drive on every change, so opening a browser re-proves
 developer's run what those jobs prove before the starter ships, and it is the most
 expensive step in this setup. `verify --round-trip` reads the answer back off the thread,
 so it holds for every runtime mount and needs no browser. Give that subagent no browser or
-device control, and record the surface outcome as skipped for a cloned starter rather than
-as a missing capability: nothing was unavailable, the run declined to spend it.
+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.
 
 Give the subagent this guide for continued-development tools:
 https://docs.copilotkit.ai/build-with-agents.md
@@ -32,13 +33,13 @@ pass the time.
 Report each attempt at the journey as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.12.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. The
@@ -46,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.10.1 onboard audit` from the target app directory. If its result
+`npx --yes copilotkit@4.12.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
@@ -55,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.10.1 onboard protect --accept-external --path <path>`. Then run
+`npx --yes copilotkit@4.12.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.
 
@@ -63,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.10.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`,
+`npx --yes copilotkit@4.12.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 --yes copilotkit@4.10.1 onboard read proof/complete`. A performed surface outcome with
+`npx --yes copilotkit@4.12.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. Do not
 describe a skipped surface as proved. Keep the Skills and MCP results separate from the proof
@@ -124,7 +125,7 @@ Restart each project-owned process changed by the repair. Report the cycle, coun
 one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then spawn a fresh proof subagent
@@ -142,18 +143,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.10.1 onboard read stopped/run-failed`. The stack is supported:
+`npx --yes copilotkit@4.12.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.
 
 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. The CLI telemetry gate decides
-whether the report is sent.
+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.
 
 ```text
-npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.12.0 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

@@ -23,11 +23,33 @@ that waiting for the result does not, and it spends wall clock, which is one of
 this journey is measured on. One recorded run spent most of two hours asleep between
 dispatches that had all returned in seconds.
 
+## When a subagent cannot work
+
+This rule also covers every subagent this run spawns, here and in every later prompt.
+
+A subagent that returns no usable result has failed in your harness, not in this graph.
+Delegation buys parallelism and a clean context, not capability: every assignment in this
+run is work you can do yourself, slower. So run that assignment yourself and carry on,
+rather than treating it as the end of the run.
+
+Both research subagents failing means this harness has no working subagent at all, which
+is worth recording once:
+
+```text
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase delegation-unavailable
+```
+
+Then say once, in your own words, that this environment has no working subagents, so you
+will carry out each step yourself and the run will take longer than usual.
+
+For the rest of this run, wherever a prompt tells you to spawn a subagent, read that
+`subagent/` brief yourself and follow it in place of spawning one.
+
 Before you ask the developer any setup question, finish every read-only investigation and
 preflight check in this section.
 
 Prepare two research assignments. Give each research subagent one assignment. Tell it to run
-`npx --yes copilotkit@4.10.1 onboard read subagent/inspect-repository` first and follow the
+`npx --yes copilotkit@4.12.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.
@@ -89,10 +111,24 @@ 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:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -108,14 +144,24 @@ the item, both cited findings, and the research limits. Require its result to st
 not inspect the project to settle the conflict yourself. Use the stop route for a non-pass
 verifier result.
 
-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.
+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.10.1 onboard read research/route`.
+`npx --yes copilotkit@4.12.0 onboard read research/route`.
 
 If inspection stops onboarding, run
-`npx --yes copilotkit@4.10.1 onboard read stopped/run-failed`.
+`npx --yes copilotkit@4.12.0 onboard read stopped/run-failed`.