copilotkit 4.15.0 → 4.17.0

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.15.0 onboard start --run <onboarding_run_id>`. That
+re-bind with `npx --prefer-offline --yes copilotkit@4.17.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.15.0 onboard checkpoint --phase surface-probed
+npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase surface-probed
 ```
 
 Then merge the research:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.15.0 onboard read research/merge
+npx --prefer-offline --yes copilotkit@4.17.0 onboard read research/merge
 ```
 
 If inspection stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.15.0 onboard read stopped/run-failed`.
+`npx --prefer-offline --yes copilotkit@4.17.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.15.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.17.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.15.0 onboard read feature/channels/start
+npx --prefer-offline --yes copilotkit@4.17.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.15.0 onboard read proof/oss-baseline`.
+`npx --prefer-offline --yes copilotkit@4.17.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.15.0 onboard read credentials/plan`.
+`npx --prefer-offline --yes copilotkit@4.17.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.15.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.17.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.15.0 project list --json`
+`npx --prefer-offline --yes copilotkit@4.17.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.15.0 init --name <directory-name> --framework <framework-id> --channel none --no-banner --no-key-prompt --create <name> --install`
+`npx --prefer-offline --yes copilotkit@4.17.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,
@@ -91,6 +94,13 @@ the dependency install, use
 answer as a flag. `--no-key-prompt` stops `init` from asking for a model key. The `init`
 output still names each missing key as `Set <VARIABLE> in .env`.
 
+If the developer named a key file, add `--model-key-file <key-file>` with the path they gave.
+`init` copies only the variable the starter needs into the starter's own env file,
+including `agent/.env` for the Microsoft Agent Framework Python starter. It prints the
+variable name and never the value. Do not read or copy the key file yourself. If `init`
+reports that it cannot read the model key file, it stopped before it cloned anything. Ask
+the developer for the right path, or run the command again without the flag.
+
 The command clones the starter into the empty target directory. It also connects the
 starter to the developer's Intelligence project. The earlier login phase supplies the
 account. The command does not need terminal input.
@@ -98,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.15.0 onboard checkpoint --phase starter-cloned
+npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase starter-cloned
 ```
 
 This is its own step, not an aside. A run that clones and then goes quiet is
@@ -111,6 +121,10 @@ and validation commands.
 
 ## Settle the model credential
 
+The `init` output names each key it copied from a key file as
+`Copied <VARIABLE> from the model key file into <file>`. A copied key is in place, so do
+not check it. If the key file did not hold a variable, the output warns by name.
+
 The `init` output names each missing credential as `Set <VARIABLE> in .env`. For each
 one, check the starter's own `.env` without reading the value:
 
@@ -121,19 +135,15 @@ grep -c '^<VARIABLE>=.' <target>/.env
 `1` means the variable holds a value. `0` means it is empty or absent. The command prints
 a count and never the value.
 
-If the developer named a key file, copy that one variable from it into `<target>/.env`,
-in place of the empty line. Do not print either file, and do not print the value. Then
-run the check again.
-
-If a variable is still empty, ask the developer to add it to `<target>/.env` themselves.
+If a variable is empty, ask the developer to add it to `<target>/.env` themselves.
 
 The two Microsoft Agent Framework starters keep their key outside `<target>/.env`, so
 `init` prints no `Set` line for them. Settle the key from the Model key column instead:
 
-- For the Python starter, run the same check for `OPENAI_API_KEY` against
-  `<target>/agent/.env`. A missing file counts as `0`. If the developer named a key file,
-  copy the variable into `<target>/agent/.env` the same way. If it is still empty, ask the
-  developer to add it there themselves.
+- For the Python starter, a key file passed to `init` fills `<target>/agent/.env`, and the
+  output says so. Otherwise, run the same check for `OPENAI_API_KEY` against
+  `<target>/agent/.env`. A missing file counts as `0`. If it is empty, ask the developer to
+  add it there themselves.
 - For the .NET starter, the key lives in `dotnet user-secrets`, and no check can read it
   without printing the value. Ask the developer to run
   `cd <target>/agent && dotnet user-secrets set OPENAI_API_KEY "<key>"` themselves, even
@@ -142,7 +152,7 @@ The two Microsoft Agent Framework starters keep their key outside `<target>/.env
 Then report the pause and end your turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.15.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase awaiting-developer
 ```
 
 This is a pause, not a stop. Do not send a stop report, and do not take a stop route.
@@ -153,10 +163,10 @@ call.
 
 If no credential is missing, report no pause and continue.
 
-Then run `npx --prefer-offline --yes copilotkit@4.15.0 onboard read proof/round-trip`.
+Then run `npx --prefer-offline --yes copilotkit@4.17.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.15.0 onboard read stopped/run-failed`. The starter is one this
+`npx --prefer-offline --yes copilotkit@4.17.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
@@ -23,6 +23,12 @@ Say what the developer has now. Name the processes still running and the files t
 changed, so they can carry on by hand or start again from a known state. A run that stops
 without saying what it left behind leaves the developer to discover it.
 
+A step can fail on a network error: `EAI_AGAIN`, `ECONNRESET`, `ETIMEDOUT`, a timeout,
+or a message that names a proxy. The CLI has already tried that step again. Ask the
+developer to check their network, VPN, or proxy setting. This fix needs no file changes.
+When the network works, propose it as the one fix below, and come back with
+`onboard resume`.
+
 ## If one scoped fix can finish this run
 
 Do not decide this yourself. This run refused to widen its own scope, and that refusal
@@ -35,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.15.0 onboard resume --message "<approval>"
+npx --prefer-offline --yes copilotkit@4.17.0 onboard resume --message "<approval>"
 ```
 
 Put the developer's approval in `--message`, in one or two sentences: the fix they
@@ -58,7 +64,7 @@ Send one short report. Run the friction command without another developer questi
 ask the developer about telemetry: the command applies the setting they already have.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.15.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.17.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.15.0 verify --round-trip`, which needs no browser. Do not plan a
+`npx --prefer-offline --yes copilotkit@4.17.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

package/onboarding/prompts/subagent/implement-and-validate.md

@@ -3,15 +3,26 @@
 Implement every step of the approved plan in plan order, and run the full validation list.
 Do not repeat the full repository inspection.
 
-Do not change a protected path. Do not delete, move, or rename one either, whatever the
-plan says: a protected path that is gone fails the audit and no command clears that.
-Do not change a path that overlaps a protected path. Paths overlap when they are equal or
+Do not change a protected path unless it is on the authorized list the main coding agent
+gave you. That list comes from the CLI, which recorded the developer's consent for each
+path on it. An authorization covers that exact path only, not an ancestor directory and not
+a file inside it. Never delete, move, or rename a protected path, authorized or not,
+whatever the plan says: a protected path that is gone fails the audit and no command
+clears that. Do not change a path that overlaps a protected path. An authorized path
+itself is the one exception. Paths overlap when they are equal or
 either path is an ancestor directory on a path-segment boundary. `apps/a` overlaps
 `apps/a/src`, but not `apps/ab`. `app.ts` does not overlap `app.tsx`.
 
-Change only the files and directories the approved plan names as changeable. If the work
-requires a file the plan does not name, return the blocker and end your turn. Do not run a
-repository-wide formatter.
+Change only the files and directories the approved plan names as changeable. A path on
+the authorized list counts as one the plan names, and so does a path the main coding agent
+adds to your handoff as one the developer approved. Two kinds of file outside that list are
+departures, not blockers. The first is a file that has the same role as a planned file at a
+different path, for example `app/page.tsx` for a planned `src/app/page.tsx`. The second is
+the documentation file this prompt tells you to write. Mark each departure in Files
+changed: the path the plan named, if any, the path you changed, and why. Neither kind
+covers a protected path. If the work requires any other file the plan does not name, return
+`Status: blocked`, name the file and why the work needs it under Blockers, and end your
+turn. Do not run a repository-wide formatter.
 
 All implementation work happens in the run root's own working tree: the target app
 directory the main coding agent named. Never work in a separate worktree, a branch
@@ -21,10 +32,12 @@ completion step verifies that the changed files exist in this project, so work l
 another tree ends the run with nothing in the developer's hands.
 
 Before validation, read the protected path list. Inspect the current changed and untracked
-paths. Keep protected paths out of the run path set. Compare every changed path with the
+paths. Keep protected paths out of the run path set, except the authorized paths, which
+belong in it. Compare every changed path with the
 paths the plan named. Here, a changed path means one in the run path set. If a changed path
-is outside them, return `Status: blocked` before validation. Run the approved validation
-commands one at a time. Fix validation and proof defects only in the paths the plan named.
+is outside them and is not a departure you marked, return `Status: blocked` before
+validation. Run the approved validation commands one at a time. Fix validation and proof
+defects only in the paths the plan named and the departures you marked.
 
 Use only the approved plan and the selected documentation URLs. Follow the documentation
 policy the main coding agent gives you before you change the project.
@@ -61,7 +74,7 @@ to bypass this rule.
 
 If the scaffolder cannot preserve a protected file, generate into a temporary directory
 inside the project only when the approved plan permits it. Copy only approved paths that
-do not overlap a protected path. Otherwise, return the conflict and end your turn before
+do not overlap a protected path. A path on the authorized list is the one exception. Otherwise, return the conflict and end your turn before
 running the scaffolder. Ask the main coding agent to revise credential setup when a
 required variable is missing. Do not provision another key to repair a scaffold overwrite.
 
@@ -83,7 +96,8 @@ change, and the check that asked for it. Do not edit the agent's prompt to make
 component render.
 
 An existing `README.md` is the developer's, not this run's. Leave it exactly as you found
-it: not the title, not a section, not a line. Where this run has documentation to write,
+it: not the title, not a section, not a line. The one exception is a README on the
+authorized list. Where this run has documentation to write,
 write it to a new file and name that file when you report the result. On an empty project
 the README is the whole of the brief -- the only place the developer said what they
 wanted, and the thing they read this run's result against -- so the rule binds hardest

package/onboarding/prompts/subagent/inspect-repository.md

@@ -7,15 +7,21 @@ Work only on the packet you were assigned. Inspect the repository without changi
 Run this first, from the target project directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.15.0 onboard inspect --json
+npx --prefer-offline --yes copilotkit@4.17.0 onboard inspect --json
 ```
 
 It answers the deterministic half of both packets exactly, from the same code
 `copilotkit verify` uses: the project record by presence, and, for each app or runtime
 directory on its own, the env files, which variable carries the Intelligence key and which
 file it came from, whether that directory's own process can load it, the package manager
-its lockfile proves, the port it declares, and the exact installed version of every
-`@copilotkit/*` dependency. It reads only and prints no secret value.
+its lockfile proves, the port it declares, the exact installed version of every
+`@copilotkit/*` dependency, and every provider base URL its process will read. It reads
+only and prints no secret value.
+
+Report each `providerEndpoints` entry with the variable, its origin, and where it came
+from. A `null` `source` means the process environment supplied it. A coding agent's shell
+passes that value on to every dev server it starts, so it decides where the model calls
+go before any project file does. Carry its `warning` as it came back.
 
 Carry those readings into your findings as they came back. Do not work one of them out
 again by reading files. The directory that owns `.env` is the hard case and the CLI holds
@@ -43,7 +49,7 @@ Find evidence for:
 Return the initial changed and untracked paths as paths only. Do not return their
 contents. Do not retain a before-state for them. The CLI captures the baseline that the
 protected-path audit compares against, so nothing later in the run depends on this
-subagent still existing, and a path that can hold secrets is captured as a digest you
+subagent still holding its state, and a path that can hold secrets is captured as a digest you
 never read.
 
 Take the target app or runtime directory from the CLI packet rather than working it out
@@ -53,7 +59,8 @@ reading of the files will not reproduce.
 ## Environment evidence packet
 
 - names of required credential variables, beyond the Intelligence key the CLI reported
-- retain the `.env` modification time for a later comparison without returning it
+- the `.env` modification time, or that no `.env` exists, for a later comparison. It is a
+  timestamp, not a value from the file
 - required toolchains and their installed versions
 - whether each port the CLI reported as declared is free
 - whether the runtime constructor uses a `runner` option, an `intelligence` option, or
@@ -85,6 +92,7 @@ access or an environment limit prevents the inspection.
 Return one row for each assigned item with its status, evidence path, and a short finding.
 Use only `proved`, `absent`, or `unproved` for the status. State each absent or unproved item.
 Do not read, print, or return secret values. For `.env` and `.copilotkit/project.json`
-checks, return only paths, presence checks, and missing field names. Do not read a file
+checks, return only paths, presence checks, missing field names, and the one `.env`
+modification time named above. Do not read a file
 outside the project directory. Do not run or return an onboarding command other than
 `onboard inspect`. End your turn after returning the findings to the main coding agent.

package/onboarding/prompts/subagent/prove-oss-baseline.md

@@ -7,6 +7,12 @@ Find the expected agent id from the project. Start the existing agent and fronte
 when they are not already running. Before using a port, identify its process and working
 directory. Do not stop a process outside this project.
 
+`next dev` locks its build directory, not its port. Next 16 writes `.next/dev/lock`. A
+second `next dev` in the same app exits with `Unable to acquire lock at ..., is another
+instance of next dev running?`. A free port does not help. If a `next dev` process already
+runs from this app, reuse that server. Prove against its port. If a start still fails with
+that message, name the process that holds the lock. Give its PID and working directory.
+
 If your harness runs commands in a sandbox, a sandboxed command cannot listen on a port or
 connect to localhost. Before the first server start, request escalation with a prefix rule
 for the project's own dev script. Before the first request to a local server, request
@@ -26,7 +32,7 @@ Prove the live runtime in this order:
 4. Confirm from project files that the runtime constructor passes a `runner` option rather
    than an `intelligence` option. A package, import, project file, or key is not use proof.
 5. Run
-   `npx --prefer-offline --yes copilotkit@4.15.0 verify --expect-runtime oss --round-trip --agent <expected-agent-id> --json`,
+   `npx --prefer-offline --yes copilotkit@4.17.0 verify --expect-runtime oss --round-trip --agent <expected-agent-id> --json`,
    with the runtime URL or auth header options that this project needs. Require exit zero
    and the JSON `ok` field to be `true`.
 6. Drive one real request through the existing frontend, CopilotKit runtime, and expected
@@ -40,9 +46,10 @@ asked for one, which is a different thing from a server registered against the c
 Where the recorded control is `unavailable`, record predicate 6 as skipped, with that as the
 reason, and prove the rest.
 
-Classify the state as `both-oss` when predicates 1 to 5 are all true. Predicate 5 proves the
-CopilotKit round trip from a shell, so those five settle the starting state on their own.
-Predicate 6 adds the user-visible surface on top of a state already proved: record it as
+Classify the state as `both-oss` when predicates 1 to 5 are all true and predicate 6 did
+not fail. Predicate 5 proves the
+CopilotKit round trip from a shell, so a skipped predicate 6 leaves those five to settle
+the starting state. Predicate 6 adds the user-visible surface on top of a state already proved: record it as
 passed, failed, or skipped, and do not withhold `both-oss` for a skip. A failed predicate 6
 on an available surface is a baseline failure and is not a skip. Return each predicate and
 its secret-safe evidence.

package/onboarding/prompts/subagent/prove-round-trip.md

@@ -5,7 +5,8 @@ policy the main coding agent gives you before you start.
 
 During Steps 1 through 8, do not edit source files, configuration files, dependencies, or
 tracked files.
-You can make only operational repairs to project-owned processes, ports, and request options.
+You can make only operational repairs to project-owned processes, ports, and request options,
+and the credential write that Step 4 names for `api_key_loadable_by_app`.
 Do not write a path that overlaps a protected path. If a required proof or tool path
 overlaps one, return `Status: blocked` before writing it.
 
@@ -24,8 +25,13 @@ different sequence of your own, and do not drop a step because an earlier one lo
 convincing. Step 6 has a web form and a React Native form: run the one that matches this
 journey's frontend, and run only that one.
 
+A run that cloned a starter is the one exception. When the main coding agent tells you
+that this run cloned a starter, run Steps 1 through 5 up to and including the
+`verify --round-trip` command, then go to Step 10. Skip Steps 5a through 9, open no browser
+or device, and report `skipped-cloned-starter` as the surface-check outcome.
+
 Where this is a second attempt after a repair, run every step from Step 2 through Step 7
-again. The repair changed tracked files and restarted processes, so the wiring, the agent
+again, or through the Step 5 `verify --round-trip` command for a cloned-starter run. The repair changed tracked files and restarted processes, so the wiring, the agent
 identity, and both preconditions are stale. Step 1 is the exception, and it is carried
 rather than derived a second time. Compare the Step 5a and Step 5b results against the
 failed attempt's before you drive the surface. A repair that leaves the failed precondition
@@ -89,6 +95,16 @@ agent and the frontend from one `dev` script, which runs them under
 other. A second start against a project already running that script collides with a server
 that is up.
 
+`next dev` locks its build directory, not its port. Next 16 writes `.next/dev/lock`. A
+second `next dev` in the same app exits with `Unable to acquire lock at ..., is another
+instance of next dev running?`. A free port does not help.
+
+Before you start a Next.js frontend, look for a `next dev` process that runs from this app.
+If one runs, reuse that server. Read its port from its command line or its listener, and
+prove against that port. If a start still fails with that message, name the process that
+holds the lock. Give its PID and working directory. Do not stop it unless it belongs to
+this project.
+
 If your harness runs commands in a sandbox, a sandboxed command cannot listen on a port or
 connect to localhost. Before the first server start, request escalation with a prefix rule
 for the project's own dev script. Before the first request to a local server, request
@@ -147,7 +163,7 @@ IPv6 only, so an IPv4 literal fails against the correct port.
 ## Step 4 -- Check the wiring
 
 With both running, check the wiring in one command before you open a browser:
-`npx --prefer-offline --yes copilotkit@4.15.0 verify --json`. It reads the port from this project, so a
+`npx --prefer-offline --yes copilotkit@4.17.0 verify --json`. It reads the port from this project, so a
 non-default port needs no flag. The payload reports `runtimeUrl` and `runtimeUrlSource`. A
 `runtimeUrlSource` of `default` means nothing in the project named a port, so pass
 `--runtime-url` with the URL from step 1 in that case. Read the individual checks rather than
@@ -181,7 +197,7 @@ named no port the CLI can read: keep step 2's URL, and rewrite its host as `loca
 before you use it.
 
 Then run the command once more with the URL you are about to open:
-`npx --prefer-offline --yes copilotkit@4.15.0 verify --frontend-url <that url> --json`. The
+`npx --prefer-offline --yes copilotkit@4.17.0 verify --frontend-url <that url> --json`. The
 `frontend_assets_served` check asks that server for its page and for one of the page's own
 assets, on that exact host. A `fail` there means the dev server refuses its own static
 assets on the host you were about to use, and the check names the URL to use instead. This
@@ -189,7 +205,7 @@ is the cheapest step that can save the most expensive one, so run it before the
 
 ## Step 5 -- Prove that the agent runs
 
-Run `npx --prefer-offline --yes copilotkit@4.15.0 verify --round-trip --json`. It sends one request through
+Run `npx --prefer-offline --yes copilotkit@4.17.0 verify --round-trip --json`. It sends one request through
 the runtime and reads the answer back from the thread, so it separates an agent that is
 configured from an agent that works. Use `--agent <id>` when the runtime declares more
 than one. If it reports `user-not-identified`, this project's `identifyUser` reads a
@@ -202,7 +218,7 @@ Where this run settled a Learning Container, add the flag to the call above rath
 running a second round trip:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.15.0 verify --round-trip --expect-learning-container <container id> --json
+npx --prefer-offline --yes copilotkit@4.17.0 verify --round-trip --expect-learning-container <container id> --json
 ```
 
 The check reads the thread that this run created, so a second round trip proves a second
@@ -236,7 +252,7 @@ the credential was written holds an empty key while the file beside it carries t
 one. Run this from the target app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.15.0 onboard env-staleness
+npx --prefer-offline --yes copilotkit@4.17.0 onboard env-staleness
 ```
 
 A `stale` line names the env file and how long after launch it was written. Report that,
@@ -246,6 +262,21 @@ process and never its owner, and one project's dev script often serves the agent
 frontend together. Editing a file to answer a 401 that a restart clears changes the project
 for a fault it does not have.
 
+Where the runtime answers with a 404 from the model provider, check the base URLs the
+processes inherited before you change anything. A coding agent's shell passes its own
+environment on to every process it starts, so a provider base URL exported for the agent
+reaches the dev servers. Run this from the target app directory:
+
+```text
+npx --prefer-offline --yes copilotkit@4.17.0 onboard inspect --json
+```
+
+Read `providerEndpoints` for the app directory. An entry with a `null` `source` came from
+the process environment rather than from a project file. A `warning` names why that value
+fails. Report the variable, where it came from, and the warning, and say that the server
+has to start from an environment without that value before the 404 means anything. Do not
+edit a project file to answer it: the value lives in the shell, not in the project.
+
 ### Step 5a -- Prove that the page's data reaches the model
 
 `verify --round-trip` sends `context: []` and asks a question that needs no context. It
@@ -308,13 +339,14 @@ holds. Streamed text alone is not this step's outcome, whatever it says.
 This is the step that covers realtime delivery, the frontend provider being wired to this
 runtime, and the component actually rendering, and no command-line check reaches any of
 them. It is not optional polish: a run that skips it has proven the agent and not the
-journey, and such a run ends as blocked rather than complete.
+journey, and such a run ends as blocked rather than complete. The cloned-starter skip is
+the one exception, and it completes the run.
 
 For a recorded `both-oss` starting state, this step has no component to render. Send the
 same request the baseline recorded, require the same kind of user-visible result the
 baseline produced, and require that the thread for that request is listed in the drawer.
 Where this journey's frontend framework ships no threads drawer -- React Native --, prove
-that thread with `npx --prefer-offline --yes copilotkit@4.15.0 verify --round-trip`, which reads the
+that thread with `npx --prefer-offline --yes copilotkit@4.17.0 verify --round-trip`, which reads the
 answer back off the thread and needs no browser. Record which of the two you proved.
 
 Use the surface control the main coding agent recorded for your environment. It either had
@@ -342,7 +374,7 @@ request never exercises. Drive it with the browser control step 6 named.
    the page to finish loading. Do not retype the host, and do not substitute a URL a tool
    offers you by default. Where the page loads but its styling is missing or the chat
    control is dead, run
-   `npx --prefer-offline --yes copilotkit@4.15.0 verify --frontend-url <the url you opened> --json`
+   `npx --prefer-offline --yes copilotkit@4.17.0 verify --frontend-url <the url you opened> --json`
    before you diagnose anything else. A dev server can serve its page and refuse every
    static chunk behind it, and on screen that is indistinguishable from a broken
    integration. The `frontend_assets_served` check tells the two apart.
@@ -367,8 +399,9 @@ request never exercises. Drive it with the browser control step 6 named.
    the answer from, and what that element showed.
 
 Report exactly one of `performed`, `skipped-no-browser-tool`, `skipped-cloned-starter`, or
-`failed` for a web frontend. Report `skipped-cloned-starter` when this prompt told you to
-open no browser because the run cloned a starter.
+`failed` for a web frontend. Report `skipped-cloned-starter` when the main coding agent told
+you to open no browser because the run cloned a starter. The cloned-starter exception above
+Step 1 says which steps to run.
 
 ### Step 6b -- React Native
 
@@ -485,8 +518,9 @@ whatever these two tools did.
 
 Start with `Status: passed`, `Status: failed`, or `Status: blocked`.
 Use `Status: passed` when the proof attempt completed with `performed`,
-`skipped-no-browser-tool`, or `skipped-no-device`. The parent records a skip through the
-standard blocked completion route. Use `Status: failed` for a failed proof step. Use
+`skipped-no-browser-tool`, `skipped-no-device`, or `skipped-cloned-starter`. The parent
+records a skip through the standard completion route, which ends every skip but
+`skipped-cloned-starter` as blocked. Use `Status: failed` for a failed proof step. Use
 `Status: blocked` when a safety or access limit stops the attempt before a surface outcome.
 Return the proof or the exact failed step to the main coding agent, together with the
 input, the visible result, the relevant process status, the evidence locations, the