copilotkit 4.29.0 → 4.30.0

package/onboarding/index.json

@@ -1,5 +1,5 @@
 {
-  "graphTree": "097fa21703ca2deadf60b9e0f0ce9e895160c2ea",
+  "graphTree": "234fed89763eaf8a634da0ade464d772951157e7",
   "intentRoots": {
     "add-a2ui": "feature/a2ui/start",
     "add-chat-suggestions": "feature/chat-suggestions/start",
@@ -9,12 +9,13 @@
     "add-rich-threads": "feature/rich-threads/start",
     "add-voice": "feature/voice/start"
   },
-  "packageSpec": "copilotkit@4.29.0",
+  "packageSpec": "copilotkit@4.30.0",
   "root": "authenticate/start",
   "prompts": [
     {
       "edges": [
         "deployment/choose-local",
+        "starter/setup",
         "research/gather",
         "stopped/run-failed"
       ],
@@ -77,7 +78,8 @@
         "subagent/create-plan",
         "stopped/run-failed",
         "implementation/build-and-validate",
-        "unsupported/no-validated-path"
+        "unsupported/no-validated-path",
+        "stopped/declined"
       ],
       "milestone": "credentials",
       "name": "credentials/write-plan"
@@ -85,7 +87,8 @@
     {
       "edges": [
         "research/gather",
-        "stopped/run-failed"
+        "stopped/run-failed",
+        "stopped/declined"
       ],
       "milestone": "deployment",
       "name": "deployment/choose-local"
@@ -104,6 +107,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/a2ui/proof"
       ],
@@ -112,6 +116,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/a2ui/implement"
       ],
       "milestone": "feature",
@@ -119,6 +124,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/complete"
       ],
@@ -140,6 +146,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/channels/proof"
       ],
@@ -148,6 +155,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/channels/implement"
       ],
       "milestone": "feature",
@@ -155,6 +163,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/complete"
       ],
@@ -163,6 +172,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/channels/plan"
       ],
@@ -171,6 +181,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/chat-suggestions/proof"
       ],
@@ -179,6 +190,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/chat-suggestions/implement"
       ],
       "milestone": "feature",
@@ -186,6 +198,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/complete"
       ],
@@ -208,6 +221,7 @@
     {
       "edges": [
         "feature/blocked-by-plan",
+        "stopped/declined",
         "feature/stop",
         "feature/learning/proof"
       ],
@@ -216,6 +230,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/learning/implement"
       ],
       "milestone": "feature",
@@ -223,6 +238,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/complete"
       ],
@@ -240,6 +256,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/open-generative-ui/proof"
       ],
@@ -248,6 +265,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/open-generative-ui/implement"
       ],
       "milestone": "feature",
@@ -255,6 +273,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/complete"
       ],
@@ -271,6 +290,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/realtime-sync/proof"
       ],
@@ -279,6 +299,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/realtime-sync/implement"
       ],
       "milestone": "feature",
@@ -286,6 +307,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/complete"
       ],
@@ -302,6 +324,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/rich-threads/proof"
       ],
@@ -310,6 +333,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/rich-threads/implement"
       ],
       "milestone": "feature",
@@ -317,6 +341,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/complete"
       ],
@@ -338,6 +363,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/voice/proof"
       ],
@@ -346,6 +372,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/voice/implement"
       ],
@@ -354,6 +381,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "feature/stop",
         "feature/complete"
       ],
@@ -585,6 +613,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "subagent/implement-and-validate",
         "proof/round-trip",
         "stopped/run-failed",
@@ -612,7 +641,8 @@
       "edges": [
         "subagent/prove-round-trip",
         "proof/complete",
-        "stopped/run-failed"
+        "stopped/run-failed",
+        "stopped/declined"
       ],
       "milestone": "proof",
       "name": "proof/round-trip"
@@ -655,6 +685,7 @@
     },
     {
       "edges": [
+        "stopped/declined",
         "credentials/plan"
       ],
       "milestone": "setup",
@@ -668,6 +699,21 @@
       "milestone": "starter",
       "name": "starter/clone"
     },
+    {
+      "edges": [
+        "feature/channels/start",
+        "stopped/run-failed",
+        "stopped/declined",
+        "research/gather"
+      ],
+      "milestone": "starter",
+      "name": "starter/setup"
+    },
+    {
+      "edges": [],
+      "milestone": "stopped",
+      "name": "stopped/declined"
+    },
     {
       "edges": [],
       "milestone": "stopped",

package/onboarding/prompts/authenticate/start.md

@@ -8,58 +8,53 @@ and optional friction reports to CopilotKit under the developer's telemetry sett
 reads nothing outside the project
 directory. In an existing project, it changes files only after writing the plan, and asks
 before any change the plan says needs the developer's approval. An empty folder gets a
-new app. CopilotKit
-Intelligence has a free Developer plan, and this run needs no paid subscription.
+new app. A free CopilotKit account is required to continue setup. This run needs no paid
+subscription.
 
 ## Command approvals
 
 Run each CLI call exactly as written, as its own command: no pipe, `tee`, `&&`, redirect,
 or variable prefix. Every CLI call in this run matches the prefix rule
-`["npx", "--prefer-offline", "--yes", "copilotkit@4.29.0"]`.
+`["npx", "--prefer-offline", "--yes", "copilotkit@4.30.0"]`.
+
+Never add or edit a permission rule or a settings file yourself. That choice belongs to
+the developer.
 
 <!-- sandboxed-harness -->
 
 If a command can request escalation with a prefix rule, request this one on the
-`onboard identify` call.
+`onboard begin` call.
 
 <!-- /sandboxed-harness -->
 
-If your harness asks the developer to approve commands, tell them one approval of that
-prefix covers every CLI call. Say then that the install, the dev servers, `curl` to the local app, and
-`ps`, `lsof`, and `kill` ask for approval later.
-
-Never add or edit a permission rule or a settings file yourself. That choice belongs to
-the developer.
-
 <!-- antigravity-harness -->
 
 Antigravity's "always allow" saves only the one full command, so it does not cover the
 next CLI call. Tell the developer that one entry covers every CLI call, and that the
 choice is theirs. The entry goes in `/permissions`, or in `permissions.allow` in
 `~/.gemini/antigravity-cli/settings.json`:
-`command(npx --prefer-offline --yes copilotkit@4.29.0)`.
+`command(npx --prefer-offline --yes copilotkit@4.30.0)`.
 
 <!-- /antigravity-harness -->
 
 If your harness refuses a CLI call without asking the developer, do not retry it or run it
-another way. Report the pause: `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about harness-permission`.
+another way. Report the pause: `npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about harness-permission`.
 Name the refused command, ask the developer to approve it or to switch to a
 mode that asks them, and end your turn. When they answer, run it once more.
 That refusal is a pause, not a stop.
 
 ## First, say which coding agent you are
 
-Before you run any other command, write this one line in your own reply: "Setting up
-CopilotKit: I check your sign-in and your project, then show you the setup." The developer
-does not see your tool output, and the welcome comes later, with the setup message.
-
-Then run this:
+Run this before you write anything to the developer:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard begin --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
 ```
 
-Report your product slug, such as `codex` or `claude-code`.
+It records you and prints the welcome as a JSON line. Do what its `next` says: the
+developer reads the welcome and replies **go**. Then run the same command with
+`--welcomed` added. That call records the deployment, checks sign-in, and prints the next
+step. Report your product slug, such as `codex` or `claude-code`.
 
 - `--model`: copy the model id exactly as your instructions write it. Without an exact
   model id, leave out `--model` rather than guess.
@@ -67,6 +62,17 @@ Report your product slug, such as `codex` or `claude-code`.
   `claude-sonnet`, `claude-haiku`, `gpt-5`, `gemini`, `grok`, `glm`, `minimax`, `mimo`,
   `deepseek`, `qwen`, `kimi`, else the model's series. Leave it out if you do not know it.
 - Never give your product slug as a model, or as an unlisted family.
+- `--vendor`: only for a model vendor the developer named.
+- `--local`: only when the developer asked to run CopilotKit locally, with Docker, or
+  self-hosted, or this run recorded local. Otherwise `begin` records the managed default.
+  The developer approves it with **go** on the Hosting line of the setup message. Do not
+  choose or ask.
+
+If the `--welcomed` call prints a prompt, follow it. A JSON line after it is the first
+setup message: do what its `next` says. If it prints `Sign-in needed`, follow "Check sign-in".
+
+For a later local request, run
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read deployment/choose-local`.
 
 ## How to run this onboarding
 
@@ -81,9 +87,8 @@ the whole run. Every later command reports against it.
 
 `onboard read research/gather` gives the rules for the rest of the run.
 
-Do not write a welcome of your own. The CLI puts the run's welcome at the top of the setup
-message, which says to write it in your own reply, because the developer does not see your
-tool output.
+Do not write a welcome of your own. The welcome is the `message` that `onboard begin`
+prints, because the developer does not see your tool output.
 
 ## Report a stop, wherever it happens
 
@@ -94,7 +99,7 @@ Report the pause as the prompt that asks the question says.
 A terminal that sends the report itself, or says to file none, overrides this.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.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.
@@ -107,20 +112,10 @@ not a failed step. Reword it and send it again, or stop without a report.
 Reporting a stop is not a route change. It does not resume the run or replace what the
 rule that stopped you says next: send the report, then stop.
 
-## Choose where the app stores data
-
-Take the local route only when the developer already asked to run CopilotKit locally,
-with Docker, or self-hosted: in their request, the copied prompt, or a later reply, or
-when this run already recorded local. Then run
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard read deployment/choose-local` instead.
-
-Otherwise keep managed. Do not ask the developer to choose. Run
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard deployment --choice managed`, then continue with
-“Check sign-in”. If it refuses because of a local stack, take the local route.
-
 ## Check sign-in
 
-Run `npx --prefer-offline --yes copilotkit@4.29.0 login --json --onboarding` before any project work. It checks the
+Only when `onboard begin` printed `Sign-in needed`: run
+`npx --prefer-offline --yes copilotkit@4.30.0 login --json --onboarding` before any project work. It checks the
 session and starts sign-in only as needed. Treat this as a long-lived
 streaming process. Do not wait for the command to exit before you read its standard output.
 
@@ -134,10 +129,16 @@ Read each JSON Lines record as it arrives:
    `action_required` record carries a `message`: why to sign in, whether the page opened,
    then the link and the code. Write that `message` in your own reply, word for word, and add
    nothing else. The developer does not see your tool output. Do not open the page yourself.
-   Then report the pause with
-   `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about sign-in` and end your
-   turn. Until the developer says they signed in, send them nothing more. When the research or
-   another helper returns, record what it found and end your turn without a message. Your own
+   Start the research (below), then keep reading the login process. Do not end your turn yet.
+   On `type: completed`, follow its `action`. On `type: pause` (about 90 seconds with no
+   sign-in), write its `message`, report the pause with
+   `npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about sign-in` and end your
+   turn. Until the developer replies, send them nothing more. When the research or another
+   helper returns, record what it found, then read the login process: on `type: completed`,
+   follow its `action`. If it has written neither `completed` nor `pause`, keep reading it.
+   After a `pause`, end your turn without a message. A `completed` record after a `pause`
+   means the developer signed in: follow it. Plain `login --json`, on the local route, writes no
+   `pause`: after its message, report the pause and end your turn. Your own
    built-in browser does not carry the session the developer already signed in with,
    so do not use it.
    A later `authentication_url` record with `"renewed": true` means the earlier code expired.
@@ -150,25 +151,26 @@ Read each JSON Lines record as it arrives:
 7. If that process emits `type: failed`, report the error and stop onboarding. On
    `reason: repeated_expiry`, rerun `login` with `--force` only if the developer asks.
 
-On `type: completed`, run `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase sign-in-settled`
+On `type: completed`, run `npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase sign-in-settled`
 before you continue.
 
 If your harness ends the login process or your turn before the process emits
-`type: completed` or `type: failed`, that is a pause, not a failed sign-in. Report the pause: `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about sign-in`.
+`type: completed` or `type: failed`, that is a pause, not a failed sign-in. Report the pause: `npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about sign-in`.
 If the process
-still runs, end your turn and wait for the developer to say they signed in, then read the
-same process. If the process ended without emitting `type: failed`, run
+still runs, end your turn. When the developer replies, read the same process before anything
+else. If the process ended without emitting `type: failed`, run
 `login --json --onboarding`
 again and handle a new `authentication_url` as above. Step 4 forbids a second login only while the first one runs.
 
 Do not use `whoami` for this check. Do not put account tokens or credentials in the
 conversation.
 
-Research reads only this project and needs no account. Start it as soon as the session is
-valid or the developer has the sign-in page, and keep monitoring the login process while it
-runs: `npx --prefer-offline --yes copilotkit@4.29.0 onboard read research/gather`. If this run already
-started the research, do not start it again.
+As soon as the session is valid or the developer has the sign-in page, read the next node,
+and keep monitoring the login process. If `onboard start` printed `Route: starter`, read
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read starter/setup`. Otherwise start the research,
+which needs no account: `npx --prefer-offline --yes copilotkit@4.30.0 onboard read research/gather`. If
+this run already started the research, do not start it again.
 
 If sign-in stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard read stopped/run-failed`. It does not judge
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/run-failed --reason other`. It does not judge
 this project's stack.

package/onboarding/prompts/conversion/plan.md

@@ -100,7 +100,7 @@ of this journey, and a drawer that lists nothing is not a reason to mint one. Li
 tokens stay a self-hosted concern.
 
 Where this journey's frontend framework ships no threads drawer -- React Native --, the
-fifth item is proved by `npx --prefer-offline --yes copilotkit@4.29.0 verify --round-trip`, which sends a
+fifth item is proved by `npx --prefer-offline --yes copilotkit@4.30.0 verify --round-trip`, which sends a
 real request and reads the answer back off the thread it landed on. The run says which of
 the two it proved. Do not send a run to the managed Intelligence dashboard to prove this.
 An authenticated browser session at a hosted dashboard is the one thing an agent-driven run
@@ -116,7 +116,7 @@ and passed -- so a run scored on either one was scored on the same fact. Every r
 resolves that condition from, while `licenseStatus` is a compatibility projection of it
 for older thread surfaces and outlives them only until those surfaces go.
 
-Then run `npx --prefer-offline --yes copilotkit@4.29.0 onboard read credentials/finalize-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read credentials/finalize-plan`.
 
 If a selected page does not load after the second method, run
-`npx --prefer-offline --yes copilotkit@4.29.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/finalize-plan.md

@@ -1,14 +1,14 @@
 # Select the Intelligence project
 
 For a recorded local choice, run
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard read deployment/local-evaluation`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read deployment/local-evaluation`.
 That path connects the local project with the approval the setup message took.
 Skip hosted selection.
 Keep the implementation and feature-proof requirements.
 
 Use the selected framework, frontend, model vendor, model, documentation URLs, and
 repository findings. When the framework, frontend or vendor is not in your context, read it
-from `npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers`, and do not ask again. On a conversion, use the values the conversion prompt recorded, and
+from `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`, and do not ask again. On a conversion, use the values the conversion prompt recorded, and
 ask no framework or frontend question. Do not change application code in this phase. Do
 not read, show, store, or request a secret value.
 
@@ -20,7 +20,7 @@ reason only when it names something in the developer's own project. Do not ask a
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about setup-answers
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about setup-answers
 ```
 
 ## Record the audit cell
@@ -38,7 +38,7 @@ Choose the starting state from the repository findings:
 A run served `proof/oss-baseline` records one of the last two.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend> --model-vendor <model-vendor> --model-vendor-choice <model-vendor-choice>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend> --model-vendor <model-vendor> --model-vendor-choice <model-vendor-choice>
 ```
 
 `<model-vendor>` is `openai`, `anthropic`, `google`, `openai-compatible`, or `other`.
@@ -55,7 +55,7 @@ runtime `.env` file, that directory is the target, not the repository root. Do n
 the developer to another terminal.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard credentials --json
+npx --prefer-offline --yes copilotkit@4.30.0 onboard credentials --json
 ```
 
 Every credential this run writes goes to the environment path: the target's `.env`, or
@@ -80,7 +80,7 @@ the CLI kept: run `--create` with `question.recorded.create`, or `--project` wit
 project answer `setup/questions` gave you. A new project with no recorded name takes
 `suggestedName`. Ask the developer only when `question.taken` or `question.notFound` is
 present, or when no answer was recorded. When they then give another project, record it
-with `npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers --create <name>` or
+with `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers --create <name>` or
 `--project <slug>`.
 
 `project-name` means that no project is bound here, so creating a project for this
@@ -93,7 +93,7 @@ unless the developer says that it is this app's.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about project-name
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about project-name
 ```
 
 If no developer answers, create with the derived name in `suggestedName`. Never select a
@@ -102,9 +102,9 @@ project from a listing without an answer that names it.
 `--runtime-url` is the URL port research settled, mount path included:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard credentials --create <name> \
+npx --prefer-offline --yes copilotkit@4.30.0 onboard credentials --create <name> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
-npx --prefer-offline --yes copilotkit@4.29.0 onboard credentials --project <slug-or-id> \
+npx --prefer-offline --yes copilotkit@4.30.0 onboard credentials --project <slug-or-id> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
 ```
 
@@ -116,12 +116,12 @@ show only what they asked for, and do not order it by creation time:
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about which-project
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about which-project
 ```
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 project list --json
-npx --prefer-offline --yes copilotkit@4.29.0 project list --search <query> --json
+npx --prefer-offline --yes copilotkit@4.30.0 project list --json
+npx --prefer-offline --yes copilotkit@4.30.0 project list --search <query> --json
 ```
 
 `app-directory` means that the key landed where no app reads it. Pick the directory in
@@ -130,7 +130,7 @@ the `--project` command from there with `project.slug`. Do not copy or link the
 
 `env-file-exposed` means that git tracks the env file the key goes into, or does not
 ignore it. So nothing was written. Read `envFile` from
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers`, which keeps the developer's answer to
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`, which keeps the developer's answer to
 that line in the setup message: `approved` approves the change the line asks for,
 `alternative` chose `question.alternative`, and `declined` declined both. Act on it without
 asking again. An accepting reply to the setup message never approves a line with
@@ -144,7 +144,7 @@ run the same command again with `question.alternative.rerun` added. The CLI adds
 If they approve the untrack, add
 `question.ignoreLine` to `question.ignoreFile`. If `question.untrack` is present, run it
 too. Or the developer does both. Report the pause with
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about env-file-tracked`, end your
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about env-file-tracked`, end your
 turn, and wait for the answer. Then run the same command again. Write the key only to
 `question.file`, or to `question.alternative.file` by rerunning with
 `question.alternative.rerun`.
@@ -160,4 +160,4 @@ turn, and wait for the answer. Then run the same command again. Write the key on
   reused. The round-trip proof later runs the authenticated Intelligence checks, so record
   the reused project credentials as unverified in the plan until those checks pass.
 
-Then run `npx --prefer-offline --yes copilotkit@4.29.0 onboard read credentials/settle-credentials`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read credentials/settle-credentials`.