copilotkit 4.28.0 → 4.30.0

package/onboarding/prompts/credentials/plan.md

@@ -1,6 +1,6 @@
 # Select the agent framework
 
-First run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`. It prints the answers that
+First run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`. It prints the answers that
 `setup/questions` recorded, even after this conversation lost them. Use its `framework` and
 its `vendor`, with `vendor.choice`, `vendor.baseUrl` and `vendor.modelId`. That node asked
 the developer, so ask nothing here. A run that proved its existing agent, frontend, and
@@ -18,14 +18,10 @@ it holds a framework and no vendor, ask the model provider line alone: without a
 framework node uses OpenAI, which the developer never chose. Recommend the framework that
 the repository findings show, or, for an empty project, a documented default. For the
 provider, recommend the framework's default vendor, and offer only the other vendors it takes:
-`onboard setup-answers` refuses any other and names the ones it takes. On most frameworks that is OpenAI or an
-OpenAI-compatible provider: if the developer names Anthropic or Google for a new agent
-there, say that this release supports the row's vendors on that framework, that Anthropic
-and Google come in a later release, and offer the Built-in CopilotKit agent if they need
-them now. Record the answers with
+`onboard setup-answers` refuses any other and names the ones it takes. Some frameworks hold back Anthropic or Google in this release: if the developer names one of those for a new agent there, say that this release supports the vendors that framework takes, that the vendor comes in a later release, and offer the Built-in CopilotKit agent if they need it now. Record the answers with
 `onboard setup-answers --framework <name> --vendor <vendor> --vendor-choice <choice>`.
 Report the pause with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer`, then end your
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about stack-choice`, then end your
 turn and wait for the answer. A route that records no framework or vendor on purpose is not
 this case: an empty project with Slack or Microsoft Teams, a "Project-defined" vendor, or
 "The agent's own" vendor.
@@ -49,7 +45,7 @@ Microsoft Teams docs page, do not ask the framework question. So does an empty p
 whose frontend `setup/questions` recorded as Slack or Microsoft Teams: it recorded no
 framework. The Channel starter brings its own agent, so an answer here decides nothing. Tell the developer that the Channel
 starter decides the agent, then run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read frontend/plan`.
 
 ## Route on the recorded framework
 
@@ -58,28 +54,28 @@ chosen: `developer`, `default`, or `existing`. The framework route uses this ven
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/ag2`
-2. Agno: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/crewai-flows`
-7. Custom agent: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/custom-ag-ui`
-8. Deep Agents: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/deep-agents`
-9. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/langgraph-python`
-10. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/langgraph-fastapi`
-11. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/langgraph-typescript`
-12. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/llamaindex`
-13. ADK: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/google-adk`
-14. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/ms-agent-python`
-15. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/ms-agent-dotnet`
-16. Mastra: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/mastra`
-17. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/ms-agent-harness-dotnet`
-18. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/pydantic-ai`
-19. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/strands-python`
-20. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.28.0 onboard read framework/strands-typescript`
+1. AG2: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/ag2`
+2. Agno: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/crewai-flows`
+7. Custom agent: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/custom-ag-ui`
+8. Deep Agents: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/deep-agents`
+9. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/langgraph-python`
+10. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/langgraph-fastapi`
+11. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/langgraph-typescript`
+12. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/llamaindex`
+13. ADK: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/google-adk`
+14. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/ms-agent-python`
+15. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/ms-agent-dotnet`
+16. Mastra: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/mastra`
+17. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/ms-agent-harness-dotnet`
+18. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/pydantic-ai`
+19. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/strands-python`
+20. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read framework/strands-typescript`
 
 An agent in any other framework takes route 7, whether or not it speaks AG-UI. So does a
 new agent on a framework that is not listed. If the developer declines route 7 and every
 listed framework, keep their current agent and run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/credentials/settle-credentials.md

@@ -21,10 +21,10 @@ The plan names the model credential variables. Run this from the directory that
 `environmentPath` in the project step's result, with one `--model-key` for each variable:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard credentials --model-key <variable> --json
+npx --prefer-offline --yes copilotkit@4.30.0 onboard credentials --model-key <variable> --json
 ```
 
-Run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers` for the key answer the setup
+Run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers` for the key answer the setup
 message recorded. If it holds `key.file`, add `--env-path <key.file>` to the first check.
 When the framework node names another env file for the credential, add
 `--env-path <file>`. When the agent runs as its own service, such as a remote AG-UI agent,
@@ -35,23 +35,23 @@ never prints a value. Read `status`:
 
 - `ready`: continue. Name each `unsupported` or `undetermined` `reason` in `modelKeys` in
   the closing report. Name each `copiedKeys` entry with the outcome `kept` or `no-value`
-  too: that service does not get the checked key. When `outsideRepository` names a file, the app does not load it by
+  too: that service does not get the checked key. Name each `addedIgnoreLines` entry to the developer and in the closing report. When `outsideRepository` names a file, the app does not load it by
   itself. By default, plan to copy the key into `environmentPath`, the app's env file that git ignores.
   The copy is a file the run writes itself, so list the copy under
   `Files the run writes itself`.
   The developer's answer to the key file line in the setup questions is their consent to
   the copy. After the run shows the plan, copy the key with the command that `next` names. It has this form:
-  `npx --prefer-offline --yes copilotkit@4.28.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file> --json`.
+  `npx --prefer-offline --yes copilotkit@4.30.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file> --json`.
   `<env file>` is `environmentPath`, never the tracked `.env` of a run that chose
   `question.alternative.file`. It writes the key without printing it. Do not copy the key
   yourself, and do not write a `sed`, `grep`, or `cat` command for it. If you cannot run
   the command, for example because a sandbox refuses the path, ask the developer to run it.
   Give them exactly this one line, with `<app directory>` as the directory that holds
   `environmentPath`:
-  `! cd <app directory> && npx --prefer-offline --yes copilotkit@4.28.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file>`.
+  `! cd <app directory> && npx --prefer-offline --yes copilotkit@4.30.0 onboard credentials --model-key <variable> --env-path <file> --copy-to <env file>`.
   The command needs no input. Without `!`, they run the same command in a terminal.
   Report the pause with
-  `npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-model-credential`,
+  `npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-model-credential`,
   end your turn, and wait. When they reply, run the same command with `--json` and read `copiedKeys`.
   If the developer declines the copy, the plan has the app read the key from an
   environment variable that the developer sets. The plan then says how to set it. Never
@@ -69,13 +69,18 @@ never prints a value. Read `status`:
   The `reason` `compatible-base-url-missing` or `key-not-openai` means that the key belongs
   to an OpenAI-compatible provider, but no file names its base URL, so nothing was sent.
   Ask the developer for the provider's base URL, record it with
-  `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers --vendor openai-compatible --base-url <url> --model-id <id>`,
+  `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers --vendor openai-compatible --base-url <url> --model-id <id>`,
   and run this step again.
 - `needs-developer` with `question.reason` `local-endpoint-no-key`: the base URL is a local
   server that needs no key, such as Ollama or LM Studio. The OpenAI SDKs refuse an empty
   key. Do what `next` says: write `<variable>=not-needed` to `question.envFile`, the key's
   own file, and run this step again. For the Microsoft Agent Framework Python starter,
   that file is `agent/.env`.
+- `needs-developer` with `question.reason` `endpoint-conflict`: the env files name
+  different base URLs, so nothing was sent and the key was not checked. Do what `next`
+  says. Do not plan or build before this step runs again. The one exception: if the
+  developer said they will add the key later, write in the plan that the key was not
+  checked, and continue.
 - `needs-developer` with `question.status` `missing`: if the developer said they will add the
   key later, do not ask or pause here. Carry the missing key into the plan: name the
   variable and `question.envFile`, then continue. Otherwise ask the developer `question.ask` in
@@ -113,4 +118,4 @@ Never read a file outside the project directory to find a credential: a key foun
 bills another project. Asking for a path is not requesting a secret. A path the developer
 names is theirs to give, including one outside the project. A path this run finds is not.
 
-Then run `npx --prefer-offline --yes copilotkit@4.28.0 onboard read credentials/write-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read credentials/write-plan`.

package/onboarding/prompts/credentials/write-plan.md

@@ -6,12 +6,10 @@ answer only when the plan makes a change that needs approval or still needs the
 
 ## If you stop in this phase
 
-Name the exact file, value, or check that stopped you, then send one short report. The
-friction command follows the telemetry setting the developer already chose, so it needs no
-separate question.
+Name the exact file, value, or check that stopped you, then send one short report.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.30.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -38,11 +36,10 @@ so either mount works. Keep the mount the project already has, together with its
 setting: `mode: "single-route"` with `useSingleEndpoint` true or unset, or the full route
 subtree with `useSingleEndpoint={false}`. For a new mount, use the full route subtree below.
 
-Below 1.73.1, mount the runtime on the full route subtree. An Intelligence runtime serves
-its runs over two REST paths: `/agent/<id>/run` and `/agent/<id>/connect`, and the
-Intelligence client of those versions addresses them for every transport the provider
-selects. A runtime mounted with `mode: "single-route"` answers every other call. It
-returns not found for every run and every thread reopen. The other fix is an upgrade of
+Below 1.73.1, mount the runtime on the full route subtree. The Intelligence client of those
+versions calls `/agent/<id>/run` and `/agent/<id>/connect` for every transport, so a
+runtime mounted with `mode: "single-route"` returns not found for every run and every
+thread reopen. The other fix is an upgrade of
 the CopilotKit packages to 1.73.1 or later, which the plan can name as its dependency
 upgrade. The round-trip check passes with either mount, so nothing later in this run
 catches the mistake.
@@ -58,7 +55,7 @@ proof subagents:
 - https://docs.copilotkit.ai/backend/runtime-endpoints.md
 - https://docs.copilotkit.ai/intelligence/managed-intelligence-platform.md
 
-Fetch them together with the pages already selected rather than on their own.
+Fetch them with the pages already selected, not on their own.
 
 The planning subagent adds a threads drawer from the selected drawer page. If no drawer
 page is selected yet, add the one for the frontend selected above to the same list:
@@ -73,25 +70,37 @@ When you start a subagent in the background, tell the developer in one sentence
 does. Then send nothing more until it returns.
 
 Spawn one planning subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read subagent/create-plan` first and follow the
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read subagent/create-plan` first and follow the
 prompt it returns. Tell it to return at once, and say so, if that read is refused or fails,
-and not to wait for an approval. If it returns that way, stop that subagent. Run the same
-command yourself, then spawn a fresh subagent with the returned prompt and the same handoff.
+and not to wait for an approval.
 Give it the repository findings, selected framework, frontend, model, credential variable
 names, selected documentation URLs, and documentation policy. Give it each finding that the
 framework route told you to record, such as how the agent connects or a `clone()` finding.
-Some of those rules, such as the `clone()` override, are on no documentation page. On a
+On a
 conversion, also give it the frozen criterion. Give the planning subagent the paths that
 had uncommitted changes when the run started, from the repository findings, and the
 `backup` result from `onboard credentials`. Also give it the JSON that
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers` prints, so the plan does not ask again
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers` prints, so the plan does not ask again
 for a change the setup message settled. Wait for the subagent to finish.
 
+If only its closing `subagent-returned` checkpoint was refused, the subagent finished.
+Record no `refused` return and spawn nothing: run that checkpoint yourself, with the result
+the subagent returned.
+
+If the subagent returns because its harness refused any other command, record that return:
+
+```text
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase subagent-returned --brief create-plan --result refused
+```
+
+Then run that command yourself, from the directory the subagent named. Spawn at most one
+fresh subagent for each refused command, with the same handoff and that command's result.
+If the fresh subagent is refused a command too, spawn no other. Follow the brief yourself.
+
 Continue only if the planning result starts with `Status: passed`. For `Status: failed`,
 send the result back to the planning subagent for repair, up to three attempts. For
 `Status: blocked`, or a third failed result, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read stopped/run-failed`. A plan this run cannot
-write is a run that broke, not a stack the documentation does not cover. The exception is
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/run-failed --reason other`. The exception is
 a blocked result that names `unsupported/no-validated-path`: the planning subagent found
 that no page supports the plan, so take the no-supported-path route at the end of this
 prompt instead. Do not show a
@@ -126,7 +135,7 @@ Changes that need your approval: none. `onboard restore` puts back what the back
 - App changes: what the app gains, and how many files change.
 - Packages: each package added, with the CopilotKit version. Name each version a move
   changes, or end with "No upgrades."
-- Learning: the container id, or that Learning is not available to this organization.
+- Learning: the container id, or why Learning is skipped.
 - A note is only for something that changes behavior or security, such as a local
   placeholder, a side effect the plan blocks, a TypeScript upgrade, or an ignore-file line
   this run adds.
@@ -150,8 +159,7 @@ What I will change:
 `onboard restore` puts back what the backup holds.
 ```
 
-An upgrade to a working install is the developer's call. Do not upgrade a dependency the
-plan does not name.
+Do not upgrade a dependency the plan does not name.
 
 ## Go on, or wait for one answer
 
@@ -170,7 +178,7 @@ approval or something blocks you. Before you end your turn to
 wait for the answer, report the pause, each time you show the plan:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-plan-approval --reason <reasons>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-plan-approval --reason <reasons>
 ```
 
 `--reason` names why the plan stopped, one reason for each kind of line that needs approval, separated
@@ -190,24 +198,26 @@ by commas, such as `--reason dependency_upgrade,file_count`:
 - `other`: a line that needs approval and fits none of these.
 
 When the developer leaves a change out, send the plan back to the planning subagent
-without it. Show the new plan the same way.
+without it. For Learning, also run
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers --learning declined`. Show the new plan
+the same way.
 
 If the plan carries a missing model key, the run cannot build without it, so wait for it
 even when `Changes that need your approval` says `none`. Name the variable and its file in the plan message,
 and ask the developer to add the key. Ask the approval question in the same message, if
 there is one. When the plan has no change that needs approval, report the pause with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-model-credential`
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-model-credential`
 instead. When the developer answers, run the same `onboard credentials --model-key` check
 again. On `ready`, continue. If the key is still missing, ask the developer `question.ask`
 in those words. Report the pause with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-model-credential`, end
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-model-credential`, end
 your turn, and run the check again when they answer.
 
 When the plan needs no answer, or after the developer answers, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read implementation/build-and-validate`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read unsupported/no-validated-path`.
 
 ## If the developer replies **stop**
 
@@ -217,11 +227,11 @@ run added stay, and that the restore also undoes any edit the developer made to
 during the run. Before you end your turn to wait for the answer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about restore-files
 ```
 
-If they say yes, run `npx --prefer-offline --yes copilotkit@4.28.0 onboard restore --force`. The run has
+If they say yes, run `npx --prefer-offline --yes copilotkit@4.30.0 onboard restore --force`. The run has
 not ended yet, so without `--force` the restore cannot tell the run's edits from the
 developer's and skips every changed file. Show the developer what it restored and what it
-skipped. If they say no, change nothing. Then send the stop report from the start of this
-prompt with the category `other`, and stop onboarding.
+skipped. If they say no, change nothing. Then run
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/declined --message "<their reason>"`.

package/onboarding/prompts/deployment/choose-local.md

@@ -9,15 +9,15 @@ A local request can arrive after this run created a hosted project: `init --crea
 Tell the developer that this run already created a hosted project, so it stays managed.
 Return to the step you were on.
 
-First run `npx --prefer-offline --yes copilotkit@4.28.0 local --help`. If it does not list `setup`
+First run `npx --prefer-offline --yes copilotkit@4.30.0 local --help`. If it does not list `setup`
 ("Configure model access and install or resume the local stack"), this release has no
-local evaluation. Tell the developer so, and keep managed. If this run has not recorded
-managed yet, run `npx --prefer-offline --yes copilotkit@4.28.0 onboard deployment --choice managed`.
-Then return to “Check sign-in” in the start prompt. If a login process from it still
-runs, keep reading that process and start no second one. Otherwise record the choice:
+local evaluation. Tell the developer so. Then run `onboard begin` again as the start
+prompt shows, without `--local`. It records the managed default, which the developer
+confirms on the Hosting line of the setup message. If a login process still runs, keep
+reading that process and start no second one. Otherwise record the choice:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard deployment --choice local
+npx --prefer-offline --yes copilotkit@4.30.0 onboard deployment --choice local
 ```
 
 Explain these conditions before sign-in:
@@ -48,10 +48,10 @@ choices:
 
 1. Configure later, the default. Install with `--defer-model`. In the closing report, write
    "Learning configuration incomplete". Name the command that adds the model later:
-   `npx --prefer-offline --yes copilotkit@4.28.0 local setup`, run in a terminal in the app directory.
+   `npx --prefer-offline --yes copilotkit@4.30.0 local setup`, run in a terminal in the app directory.
 2. Guided setup. If the developer named Learning as a goal, offer it first. Install
    the stack with `--defer-model`. After the stack is ready, the developer runs
-   `npx --prefer-offline --yes copilotkit@4.28.0 local setup` in their own terminal window, in the app
+   `npx --prefer-offline --yes copilotkit@4.30.0 local setup` in their own terminal window, in the app
    directory. Never give it as a `!` line: its guided prompt needs a terminal, and a coding
    agent's shell has none. The prompt asks for the model and its key, and it saves them
    privately. On a running stack, it restarts only Learning. Do not ask the developer to
@@ -71,7 +71,7 @@ If the managed sign-in message was already sent, send this once and no other sig
 message: “You asked to run it locally, so this project gets no managed CopilotKit project.
 Signing in only gets the renewable evaluation license.”
 
-Otherwise run `npx --prefer-offline --yes copilotkit@4.28.0 login --json`. Follow the streaming sign-in
+Otherwise run `npx --prefer-offline --yes copilotkit@4.30.0 login --json`. Follow the streaming sign-in
 protocol from “Check sign-in” in the start prompt: open the first authentication URL
 once, keep the same process running, and continue only after its completed record.
 When the first authentication URL arrives, send this message in place of the managed
@@ -79,9 +79,9 @@ sign-in message: “Sign in to get the renewable evaluation license. Your local
 will use CLI approval.”
 On failed or declined sign-in, take the failure path below.
 
-After sign-in completes, report it: `npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase sign-in-settled`.
+After sign-in completes, report it: `npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase sign-in-settled`.
 Then continue with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read research/gather`, unless research already started.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read research/gather`, unless research already started.
 If it already started, return to the step you were on. `starter/clone` and
 `credentials/finalize-plan` each have a branch for a recorded local choice.
 Keep the local choice and collected paths in the run's plan and worker context.
@@ -89,4 +89,5 @@ Keep the local choice and collected paths in the run's plan and worker context.
 ## Failure path
 
 If sign-in fails or is declined, stop before cluster creation.
-Run `npx --prefer-offline --yes copilotkit@4.28.0 onboard read stopped/run-failed`.
+If sign-in failed, run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/run-failed --reason other`.
+If the developer declined it, run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/declined --message "<their reason>"`.

package/onboarding/prompts/deployment/local-evaluation.md

@@ -19,7 +19,7 @@ settings are saved in private CLI state before the app changes. `local cancel` r
 settings that still match this setup's writes and reports conflicting setting names. It
 preserves later edits and the stack's data.
 
-Run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`. It holds the setup message's
+Run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`. It holds the setup message's
 answers, even after this conversation lost them. Take each answer below from the record,
 or this conversation when the record lacks it. A field the record lacks is not a "no".
 
@@ -41,7 +41,7 @@ authorize replacing an existing app's connection.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about local-connection
 ```
 
 ## Run the shared installer
@@ -50,16 +50,16 @@ From the exact app directory, use the `learning` answer from the record, or this
 conversation:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 local setup --defer-model --json
+npx --prefer-offline --yes copilotkit@4.30.0 local setup --defer-model --json
 ```
 
 For `learning.file`, replace `--defer-model` with `--model-config <learning.file>`.
-Before setup, run `npx --prefer-offline --yes copilotkit@4.28.0 onboard local-terms --json`. If `accepted`
+Before setup, run `npx --prefer-offline --yes copilotkit@4.30.0 onboard local-terms --json`. If `accepted`
 is false, pause here. Give the developer this exact command to run in their own terminal:
-`npx --prefer-offline --yes copilotkit@4.28.0 local accept-terms`. Never accept the agreement yourself.
+`npx --prefer-offline --yes copilotkit@4.30.0 local accept-terms`. Never accept the agreement yourself.
 Report the pause with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer`, end your turn,
-and wait for "done". Then run `local-terms` again, and continue only when `accepted` is
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about local-terms`, end your
+turn, and wait for "done". Then run `local-terms` again, and continue only when `accepted` is
 true. A local command that fails with `eula_acceptance_required` comes back to this step.
 The CLI selects the latest stable release. Add `--candidate <manifest.json>` only when the
 developer gave a candidate manifest for release testing.
@@ -75,7 +75,7 @@ A copied app needs explicit `--share-stack`. Do not infer sharing from a copied
 After setup reports the stack ready, run the approved connection step from that directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 local connect --approve-connection --json
+npx --prefer-offline --yes copilotkit@4.30.0 local connect --approve-connection --json
 ```
 
 Read the local `.copilotkit/project.json` for its project ID and slug. Do not run hosted
@@ -95,7 +95,7 @@ this conversation, wait until the stack is ready. Then:
 Ask the developer to run this command in their own terminal window, in the app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 local setup
+npx --prefer-offline --yes copilotkit@4.30.0 local setup
 ```
 
 Do not give it as a `!` line, and do not run it yourself. Its guided model prompt needs a
@@ -104,9 +104,9 @@ changes nothing. The prompt asks for the model and its key, and it saves them pr
 On a running stack, it restarts only Learning. Do not ask for a model file.
 
 Say that the run continues when they reply or resume this session. Report the pause with
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-model-credential`, end your
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-model-credential`, end your
 turn, and wait. When the developer replies, run
-`npx --prefer-offline --yes copilotkit@4.28.0 local status --json` and read `learning.configuration`.
+`npx --prefer-offline --yes copilotkit@4.30.0 local status --json` and read `learning.configuration`.
 
 If the model is still missing or was deferred, report “Learning configuration incomplete”
 and name the same command, run in a terminal window. No Learning run is required to finish
@@ -120,6 +120,6 @@ must not block Threads, the dashboard, or later Learning configuration.
 If the developer cancels the connection, run `local cancel --json` from the app directory.
 Report conflict names only. Keep the stack unless deletion is separately confirmed.
 
-Continue with `npx --prefer-offline --yes copilotkit@4.28.0 onboard read credentials/settle-credentials`.
+Continue with `npx --prefer-offline --yes copilotkit@4.30.0 onboard read credentials/settle-credentials`.
 For this local route, skip the hosted selection-result checks and use the local project
 record. Continue the existing implementation and proof paths against local endpoints.

package/onboarding/prompts/fallback/best-effort.md

@@ -14,7 +14,7 @@ you stop. The friction command follows the telemetry setting the developer alrea
 so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.30.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -64,7 +64,7 @@ or frontend, stop onboarding.
 If the CLI prints `## Stop: this run deleted or moved the developer's work` instead of a
 step, show the developer the list it printed, and run what they choose:
 the `onboard restore` command the tripwire stop prints, which names each deleted file, or
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard tripwire --continue`. Then read the step again. If
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard tripwire --continue`. Then read the step again. If
 you cannot ask, stop onboarding. Never repair, reset, or revert a file the developer changed
 outside this run.
 
@@ -106,27 +106,26 @@ that the selected documentation proved an inferred step.
 Record what the proof returned before you complete:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
-When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.28.0 onboard complete`, carrying the
+When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.30.0 onboard complete`, carrying the
 surface-check result the proof subagent returned. Pass exactly one of `--visual-check` or
 `--device-check`, matching this journey's surface:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard complete --visual-check <outcome>
-npx --prefer-offline --yes copilotkit@4.28.0 onboard complete --device-check <outcome>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard complete --visual-check <outcome>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard complete --device-check <outcome>
 ```
 
 `--visual-check` is for a web frontend and takes `performed`, `skipped-no-browser-tool`, or
 `failed`. `--device-check` is for React Native and takes `performed`, `skipped-no-device`,
 or `failed`. `failed` and `skipped-no-device` end this run as blocked, and the command's
 output names the evidence that is missing. Report it that way. The command also prints
-`## The developer's files`: relay that report as printed, with its restore command. When
-the report says the run started in an empty folder, relay that one line alone: list no
-files and offer no restore. `skipped-no-browser-tool` completes the run when the round
-trip was recorded as `passed`, and the output names what no browser checked. Without that
-record it blocks.
+`## Your files`: relay that report as printed, with its restore command. A run that
+started in an empty folder prints no such section: list no files and offer no restore.
+`skipped-no-browser-tool` completes the run when the round trip was recorded as `passed`,
+and the output tells the developer to open the page. Without that record it blocks.
 
 If the proof passed and something after it still blocked this run, add
 `--blocked-by <cause>` to the same command, with one of `inspector`, `plan-excluded-capability`,

package/onboarding/prompts/feature/a2ui/implement.md

@@ -24,26 +24,28 @@ That result is a question for the developer. Name the file and why the work need
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about uncommitted-file
 ```
 
 Then end your turn and wait for the developer's answer. If they allow it, spawn a fresh
 implementation subagent with the same handoff and the file added to the plan. If you
-cannot ask, or the developer declines, take the feature stop route below.
+cannot ask, take the feature stop route below. If the developer declines, such as **no** or **not now**,
+the run did not break. Run
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/declined --message "<their reason>"`.
 
 If the CLI prints `## Stop: this run deleted or moved the developer's work` instead of
 a step, show the developer the list it printed, and run what they choose:
 the `onboard restore` command the tripwire stop prints, which names each deleted file, or
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard tripwire --continue`. Then read the step again.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard tripwire --continue`. Then read the step again.
 
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/stop
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, use
 the feature stop route above without further changes.
 
 Otherwise run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/a2ui/proof`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/a2ui/proof`.

package/onboarding/prompts/feature/a2ui/plan.md

@@ -12,13 +12,17 @@ The approval is a wait for the developer. Before you end your turn to wait, repo
 pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
 When the answer arrives, continue from the step that paused. If the developer asks for a
 change, show the changed plan and ask again.
 
+If the developer declines the plan, such as **no**, **not now** or **do not add it**, change
+no files. Run
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/declined --message "<their reason>"`.
+
 ## What this prompt takes from the start
 
 Keep these from `feature/a2ui/start`, and give them to every subagent:
@@ -49,7 +53,7 @@ renders a compact visible surface. Ask for approval as its own question.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-plan-approval
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 Ask the developer before you edit a file that has uncommitted changes. List those files in
@@ -57,4 +61,4 @@ the plan under `Uncommitted files`, each with one sentence explaining why, or wr
 `git status` names them. The CLI records no consent: the approved plan is the record. The
 plan must not delete, move, or rename one of those files.
 
-Then run `npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/a2ui/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/a2ui/implement`.

package/onboarding/prompts/feature/a2ui/proof.md

@@ -25,23 +25,25 @@ That result is a question for the developer. Name the file and why the fix needs
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about uncommitted-file
 ```
 
 Then end your turn and wait for the developer's answer. If they allow it, spawn a fresh
 proof subagent with the same handoff and the file added to the plan. If you cannot ask,
-or the developer declines, take the feature stop route below.
+take the feature stop route below. If the developer declines, such as **no** or **not now**,
+the run did not break. Run
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/declined --message "<their reason>"`.
 
 If the CLI prints `## Stop: this run deleted or moved the developer's work` instead of
 a step, show the developer the list it printed, and run what they choose:
 the `onboard restore` command the tripwire stop prints, which names each deleted file, or
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard tripwire --continue`. Then read the step again.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard tripwire --continue`. Then read the step again.
 
 Report the outcome of each attempt as it ends, before any repair. The command counts the
 attempts and the repairs:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for a proved A2UI surface, `failed` for an attempted proof that failed,
@@ -50,9 +52,9 @@ and `skipped` when the proof could not run.
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/stop
 ```
 
 When the proof is recorded, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/complete` with the actual browser-proof
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/complete` with the actual browser-proof
 outcome.