copilotkit 4.16.0 → 4.18.0

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.16.0 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --prefer-offline --yes copilotkit@4.18.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,30 +17,34 @@ Wait for the subagent to finish.
 Record what that proof returned before you route on it:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --prefer-offline --yes copilotkit@4.18.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,
-and `failed` when it cannot classify the baseline.
-A proof that never ran is `skipped`, not failed. The command prints one line and sends
+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
 nothing else.
 
-Add `--predicate` with the number the subagent returned, for a failure or a skip. The
-subagent returns all six results, and the number is the only part of them this command
-carries. Pass it on a failure with the predicate that failed, and on a skip with the
-predicate that was skipped, which is `6` where the preflight recorded no surface control.
+The subagent returns all six results. Report the gate from them this way:
+
+- Predicates 1 to 5 true, and predicate 6 passed: `--outcome passed`.
+- Predicates 1 to 5 true, and predicate 6 skipped because the preflight recorded no surface
+  control: `--outcome passed`. A skipped predicate 6 does not withhold `both-oss`.
+- Predicates 1 to 5 true, and predicate 6 failed on an available surface:
+  `--outcome failed --predicate 6`. That is a baseline failure, not a skip.
+- Any of predicates 1 to 5 failed: `--outcome failed --predicate <the first that failed>`.
+- The proof never ran: `--outcome skipped`.
+
 A passed gate takes no predicate.
 
 Do not change project files before this proof ends. Starting existing development
 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.16.0 onboard read conversion/plan`. That project already works.
+`npx --prefer-offline --yes copilotkit@4.18.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.16.0 onboard read credentials/plan`. This prompt is served
+`npx --prefer-offline --yes copilotkit@4.18.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 +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.16.0 onboard read stopped/run-failed`. None of those mean the
+`npx --prefer-offline --yes copilotkit@4.18.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.16.0 onboard read subagent/prove-round-trip` first and follow the
+`npx --prefer-offline --yes copilotkit@4.18.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
@@ -14,8 +14,8 @@ drives the surface and cannot see your environment, so without that finding it s
 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 run that cloned a starter is the exception. Tell that subagent to finish after
-`verify --round-trip` and to open no browser. The cloned code is what this repository's
+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
 starter smoke jobs already drive on every change, so opening a browser re-proves in the
 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,
@@ -33,21 +33,22 @@ pass the time.
 Report each attempt at the journey as it ends, counting from one:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --prefer-offline --yes copilotkit@4.18.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.16.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.18.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
-command prints one line and sends nothing else. Where a repair cycle runs the proof again,
+Report the gate whatever it returned. A proof that never ran is `skipped`, not failed. A
+round trip that `verify --round-trip` ran and saw fail is `failed`, and the command refuses
+to record it as `skipped`. The command prints one line and sends nothing else. Where a repair cycle runs the proof again,
 record each attempt as it ends.
 
 For every protected-path audit in this prompt, run
-`npx --prefer-offline --yes copilotkit@4.16.0 onboard audit` from the target app directory. If its result
+`npx --prefer-offline --yes copilotkit@4.18.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
@@ -56,7 +57,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.16.0 onboard protect --accept-external --path <path>`. Then run
+`npx --prefer-offline --yes copilotkit@4.18.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.
 
@@ -64,14 +65,15 @@ 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.16.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"`,
+`npx --prefer-offline --yes copilotkit@4.18.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.16.0 onboard read proof/complete`. A performed surface outcome with
+`npx --prefer-offline --yes copilotkit@4.18.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
+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.
 
@@ -85,14 +87,16 @@ developer that a framework and frontend that just worked are unsupported, and ha
 stop report instead of the application they now have.
 
 If the round trip fails, decide which kind of failure it is before you route. The proof
-subagent can repair only project-owned processes, ports, and request options. A failure caused
+subagent can repair only project-owned processes, ports, and request options, and it can
+make the credential write that its Step 4 names for `api_key_loadable_by_app`. A failure caused
 by a source, configuration, dependency, or tracked-file change is a defect in the new work.
 
-Retry the proof subagent only for a project-owned process, port, or request-option failure.
+Retry the proof subagent only for a project-owned process, port, request-option, or
+`api_key_loadable_by_app` failure.
 Give it the failure evidence and the failed attempt's pinned Step 1 record. Wait for the
 proof subagent after each operational repair.
-If the result passes, use the passed-result route above. Retry a failed result at most three
-times. Use the route-out rules below for a blocked or third failed result.
+If the result passes, use the passed-result route above. Run the proof at most three times
+in total. 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.
@@ -116,8 +120,9 @@ secret values. Require its result to start with `Status: passed`, `Status: faile
 `Status: blocked`, followed by Files changed, Validation, and Blockers. Otherwise, send the
 defect to the implementation subagent that validated the planned implementation path. Give it
 the approved plan and proof evidence. Treat the worker that gets the defect as the repair worker.
-Give the repair worker the protected path list. Do not let a generated or repaired path
-overlap a protected path.
+Give the repair worker the protected path list and the authorized list from the
+`Authorized to modify:` block of the latest audit. Do not let a generated or repaired path overlap a
+protected path, other than an authorized path itself.
 
 Require the full validation list to pass again. Wait for the repair worker to finish.
 Continue only if its result starts with `Status: passed`. If the repair worker returns
@@ -127,7 +132,14 @@ implementation worker for a planned implementation path. Use the repair worker f
 path. Wait for the validator to finish. If its result starts with `Status: passed`, continue.
 If the validator returns `Status: failed`, return its evidence to the repair
 worker. Repeat repair and validation at most three times. If either worker returns
-`Status: blocked`, use the route-out rules below.
+`Status: blocked`, use the route-out rules below. The exception is an implementation worker
+that returns blocked because the repair needs a file the plan does not name. Handle it the
+way `implementation/build-and-validate` does: pause and ask the developer, add the file to
+the handoff if they allow it, and use the route-out rules below if they decline. For a
+protected file, record their answer with `--authorize --unplanned` and run the audit again
+first. Then spawn a fresh repair worker with this repair handoff, not the whole-plan
+implementation handoff: the plan, the proof evidence, the protected path list, and the
+authorized list from that audit.
 
 Run the protected-path audit again after validation passes. Continue only if its result
 starts with `Status: passed`.
@@ -136,7 +148,7 @@ Restart each project-owned process changed by the repair. Report the cycle, coun
 one:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then spawn a fresh proof subagent
@@ -149,23 +161,23 @@ its grounding check then speaks about a question the failed attempt never asked.
 Wait for the fresh proof subagent to finish.
 If the fresh proof result starts with `Status: passed`, run the protected-path audit and use
 the passed-result route above. If it starts with `Status: failed`, begin the next bounded
-repair cycle. Use the route-out rules below for `Status: blocked`. Stop after three repair
-and proof cycles.
+repair cycle. Use the route-out rules below for `Status: blocked`. After three repair and
+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.16.0 onboard read stopped/run-failed`. The stack is supported:
+`npx --prefer-offline --yes copilotkit@4.18.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: it applies the telemetry setting the
-developer already set.
+your own harness, a run that has run out -- send one short report before you stop. The
+friction command follows the telemetry setting the developer already chose, so it needs no
+separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.18.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

@@ -28,7 +28,8 @@ This rule covers the whole run, here and in every later prompt.
 
 In this graph, stop means one thing: end the run through a named terminal. You send the
 stop report `authenticate/start` describes, then read the terminal that the rule names.
-Nothing else is a stop.
+Where a rule names a terminal, read that terminal first: if it sends the report itself or
+says to file none, follow it, so the run sends one report at most. Nothing else is a stop.
 
 A pause keeps the run open. "End your turn and wait for" something means: end this turn,
 and continue when that thing arrives. A pause waits for one of two things:
@@ -43,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.16.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase awaiting-developer
 ```
 
 When the answer or the result arrives, continue from the step that paused. Do not read an
@@ -63,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.16.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase delegation-unavailable
 ```
 
 Then say once, in your own words, that this environment has no working subagents, so you
@@ -76,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.16.0 onboard read subagent/inspect-repository` first and follow the
+`npx --prefer-offline --yes copilotkit@4.18.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.
@@ -90,7 +91,7 @@ Start both research subagents in parallel:
 Report that both subagents started:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard checkpoint --phase research-dispatched
+npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase research-dispatched
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -99,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.16.0 onboard read research/preflight
+npx --prefer-offline --yes copilotkit@4.18.0 onboard read research/preflight
 ```
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.16.0 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.18.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.16.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -54,7 +54,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.16.0 onboard read research/route`.
+`npx --prefer-offline --yes copilotkit@4.18.0 onboard read research/route`.
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.16.0 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.18.0 onboard read stopped/run-failed`.

package/onboarding/prompts/research/preflight.md

@@ -45,7 +45,7 @@ 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.16.0 onboard start --run <onboarding_run_id>`. That
+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.
 
 Do not add a browser or device driver to the project. A driver added there is a
@@ -62,14 +62,14 @@ whole finding.
 Report that the probe settled, whichever way it came out:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard checkpoint --phase surface-probed
+npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase surface-probed
 ```
 
 Then merge the research:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard read research/merge
+npx --prefer-offline --yes copilotkit@4.18.0 onboard read research/merge
 ```
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.16.0 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.18.0 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 --prefer-offline --yes copilotkit@4.16.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.18.0 onboard protect
 ```
 
 It reads the working tree itself, records every changed or untracked path with a digest,
@@ -41,7 +41,7 @@ On either, run this before you read the three findings below, and without asking
 purpose question:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard read feature/channels/start
+npx --prefer-offline --yes copilotkit@4.18.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 +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 --prefer-offline --yes copilotkit@4.16.0 onboard read proof/oss-baseline`.
+`npx --prefer-offline --yes copilotkit@4.18.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 +109,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.16.0 onboard read credentials/plan`.
+`npx --prefer-offline --yes copilotkit@4.18.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.
@@ -122,6 +122,6 @@ Slack and Microsoft Teams are choices at that step.
 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 --prefer-offline --yes copilotkit@4.16.0 onboard read stopped/run-failed`. Neither says anything
+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
 about whether this project's stack is supported, which is not yet known at this point.

package/onboarding/prompts/starter/clone.md

@@ -37,11 +37,14 @@ Each Framework ID selects a starter that the CLI ships with Intelligence. Do not
 different pair from a similar name. AG2 does not use this shortcut because its starter does
 not include Intelligence.
 
-Get the target directory name from its path. The project name must contain 1 to 30
-lowercase letters, numbers, or hyphens. It must not start or end with a hyphen. If the
+Get the target directory name from its path. The name can contain 1 to 100 letters,
+numbers, spaces, dots, underscores, or hyphens, in any case. It must not be `.` or `..`,
+start or end with a space, or end with a dot. `init` accepts the name of an existing empty
+directory as it is, so a name such as `MyApp` is valid. Do not rename the directory. If the
 selected pair is not in the table, or the directory name is not valid, stop the shortcut.
-Do not run `init`. Treat this result as a failed shortcut and follow the final failure
-instruction in this prompt.
+Do not run `init`. No command ran, so this is not a failed shortcut. Go back to the
+`## Documentation` section of the frontend prompt you read before this one, and build the
+project from its pages.
 
 If the developer did not name a project, create one for the app being
 cloned. This directory is new, so no existing project is already its own: take the project
@@ -52,7 +55,7 @@ the derived name.
 Only if the developer asks for an existing project, or asks to see the projects they have,
 read the choices:
 
-`npx --prefer-offline --yes copilotkit@4.16.0 project list --json`
+`npx --prefer-offline --yes copilotkit@4.18.0 project list --json`
 
 Then ask which one to use. Do not order the projects by creation time. If the developer
 already gave this answer, do not ask again. Do not read a secret value. Do not show or
@@ -77,9 +80,9 @@ way bills a project nobody chose.
 
 Run the command from the parent directory. Do not inspect another entry in the parent
 directory. Replace each placeholder with the recorded value. Do not run a placeholder as
-a shell argument.
+a shell argument. If the directory name holds a space, put it in double quotes.
 
-`npx --prefer-offline --yes copilotkit@4.16.0 init --name <directory-name> --framework <framework-id> --channel none --no-banner --no-key-prompt --create <name> --install`
+`npx --prefer-offline --yes copilotkit@4.18.0 init --name <directory-name> --framework <framework-id> --channel none --no-banner --no-key-prompt --create <name> --install`
 
 `--name` is always the target directory name derived above, because `init` creates the
 app at `<parent>/<name>`. Any other value puts the app in a new folder beside the target,
@@ -105,7 +108,7 @@ account. The command does not need terminal input.
 Report the clone before you inspect anything:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard checkpoint --phase starter-cloned
+npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase starter-cloned
 ```
 
 This is its own step, not an aside. A run that clones and then goes quiet is
@@ -146,10 +149,11 @@ The two Microsoft Agent Framework starters keep their key outside `<target>/.env
   `cd <target>/agent && dotnet user-secrets set OPENAI_API_KEY "<key>"` themselves, even
   if they named a key file.
 
-Then report the pause and end your turn:
+When you ask, name each variable and the file it goes in, and say that the run continues
+when they reply or resume this session. Then report the pause and end your turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.18.0 onboard checkpoint --phase awaiting-model-credential
 ```
 
 This is a pause, not a stop. Do not send a stop report, and do not take a stop route.
@@ -160,10 +164,10 @@ call.
 
 If no credential is missing, report no pause and continue.
 
-Then run `npx --prefer-offline --yes copilotkit@4.16.0 onboard read proof/round-trip`.
+Then run `npx --prefer-offline --yes copilotkit@4.18.0 onboard read proof/round-trip`.
 
 If the command fails, report its exact error and do not claim that the starter is ready.
 Then run
-`npx --prefer-offline --yes copilotkit@4.16.0 onboard read stopped/run-failed`. The starter is one this
+`npx --prefer-offline --yes copilotkit@4.18.0 onboard read stopped/run-failed`. The starter is one this
 graph ships and the stack was chosen from its own supported list, so a command that
 returned an error is a run that broke, not a setup this release does not support.

package/onboarding/prompts/stopped/run-failed.md

@@ -1,17 +1,17 @@
 # Stop because the run did not finish
 
-This is the ending for a run that broke. The developer's agent, frontend and package
-choices are supported. Something in this run stopped it, and that is what the report has
-to say.
+This is the ending for a run that broke. Something in this run stopped it, and that is
+what the report has to say. This ending makes no judgment about the stack.
 
-Do not tell the developer their setup is unsupported. It is not, and a run that says so
-sends them to change a stack that was never the problem.
+Do not tell the developer their setup is unsupported. A run that says so sends them to
+change a stack that was never shown to be the problem.
 
 Keep the developer's current agent, frontend, authentication, and package choices.
 
 Name the exact step that stopped the run, and what it returned. State whether
-authentication, project selection, project credentials, the journey, implementation,
-validation, or the round trip stopped it. Give the failure in the words the step printed,
+authentication, repository inspection, the protected-path baseline capture, the OSS baseline
+proof, project selection, project credentials, the plan, the starter clone, the journey,
+implementation, validation, or the round trip stopped it. Give the failure in the words the step printed,
 not a summary of them.
 
 If a protected path stopped this run, name that path and how it changed, in the words the
@@ -41,7 +41,7 @@ put to them, stop here and send the report below.
 If they approve it, make that one fix and nothing else. Then come back into this run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard resume --message "<approval>"
+npx --prefer-offline --yes copilotkit@4.18.0 onboard resume --message "<approval>"
 ```
 
 Put the developer's approval in `--message`, in one or two sentences: the fix they
@@ -60,11 +60,11 @@ said and stop.
 
 Stop onboarding without making more repository changes.
 
-Send one short report. Run the friction command without another developer question. Do not
-ask the developer about telemetry: the command applies the setting they already have.
+Send one short report. The friction command follows the telemetry setting the developer
+already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.16.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.18.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped

package/onboarding/prompts/subagent/create-plan.md

@@ -37,8 +37,9 @@ Plan the runtime to consume the Intelligence credential. The runtime takes an
 `runner` option instead is the OSS runtime. It never reads the Intelligence key, and the
 Inspector reads the project as locked. The default in-memory OSS runner is ephemeral.
 SQLite, custom, or framework persistence can be durable. The two options cannot be
-combined. Take the constructor from the connect-your-runtime page. Where a framework
-quickstart shows a `runner` option instead, the connect-your-runtime page wins.
+combined. Take the constructor from the Intelligence quickstart
+(https://docs.copilotkit.ai/intelligence/quickstart.md). Where a framework quickstart
+shows a `runner` option instead, the Intelligence quickstart wins.
 
 ## Plan the Learning Container and its selector
 
@@ -106,12 +107,14 @@ The intersection includes what a `@copilotkit/*` package on its own version line
 about the `1.x` line. `@copilotkit/angular` is the one that has this, and its declaration
 is materialized at publish time rather than written in the repository, so read it from the
 registry rather than from any checkout. Where it cannot be satisfied by the version the
-floor requires, there is no upgrade to plan: that is `unsupported/no-validated-path`.
+floor requires, there is no upgrade to plan: return `Status: blocked` and name
+`unsupported/no-validated-path` as the outcome.
 
 An exact pin is usually deliberate. Naming the move here is what makes it a step the
 developer approved rather than a repair the run invents halfway through. Do not move a pin
-the developer did not approve moving. Where the developer needs one held, that is
-`unsupported/no-validated-path`, and the upgrade step's revert is the way back.
+the developer did not approve moving. Where the developer needs one held, return
+`Status: blocked` and name `unsupported/no-validated-path` as the outcome. The upgrade
+step's revert is the way back.
 
 Name the exact version the target requires. A caret does not stand in for it below `0.1.0`:
 `^0.0.59` admits only `0.0.59`, so a pin rewritten that way is the same pin under a
@@ -136,8 +139,9 @@ If the value of the journey depends on data the project already holds, name that
 name where it lives, and name how it reaches the agent. Rendering a list in the DOM does
 not give the agent access to it. An agent wired without the page's data answers from
 entities it invents, and the answer looks correct. Take the frontend-context step from
-the selected documentation. Where no selected page documents it for this framework or
-frontend, record that as a documentation gap rather than guessing the API.
+the selected documentation, and never guess the API. Where no selected page documents it
+for this framework or frontend, the data has no documented way to reach the agent: return
+`Status: blocked` and name `unsupported/no-validated-path` as the outcome.
 
 Where that data exists, name the entities the proof compares against: the ids, names, or
 records the project holds and the answer has to reference. Where the outcome references
@@ -170,7 +174,7 @@ here is work the developer did not ask for.
 Plan the threads drawer itself: add it from the selected drawer page, where this frontend
 does not already render one. Where this journey's frontend framework ships no threads
 drawer -- React Native --, plan that the thread is proved by
-`npx --prefer-offline --yes copilotkit@4.16.0 verify --round-trip`, which needs no browser. Do not plan a
+`npx --prefer-offline --yes copilotkit@4.18.0 verify --round-trip`, which needs no browser. Do not plan a
 step that opens the managed Intelligence dashboard.
 
 ## Order the plan into steps
@@ -193,8 +197,9 @@ feature to an app the developer already built is the case this exists for: the o
 in a file they wrote, and on an app whose work was never committed that file is in the
 baseline. List every such path under `Authorization requested`, one line each, with the path
 and one sentence saying what the step changes there and why no other file will do. Keep the
-step in the plan. Return `Status: blocked` only when the plan needs a protected path you
-cannot justify in that sentence.
+step in the plan. Where a protected path you can justify is the only obstacle, the step
+stays. Where the plan needs a protected path you cannot justify in that sentence, return
+`Status: blocked`.
 
 Authorization covers changing a protected path, not removing it. Do not plan the deletion
 of a protected path, and do not plan a step that moves or renames one, which removes it
@@ -214,6 +219,15 @@ to make a build pass during onboarding.
 
 The type check runs against the project's own configuration. If the project has no
 type-check command, add one that uses the configuration the project already has.
+Where the repository findings carry a `typescript.migration` for an app, plan it as its
+own step, before the first step that imports a CopilotKit package in that app. Name the
+migration `file` and each change in `changes`, and give its `reason` in one sentence.
+Under `node` or `node10` resolution, TypeScript ignores a package's `exports` map, so
+every CopilotKit subpath import fails the type check while the app still runs. A plan
+without this step stops after approval to ask for it. If the file is a protected path,
+list it under `Authorization requested`. Where no migration is reported, do not change
+`moduleResolution` or `module`. This change does not weaken type safety.
+
 Do not add compiler strictness the project did not have. Nothing later in the run is
 allowed to weaken type safety, so a stricter gate named here is one the run cannot get
 back out of.