copilotkit 4.29.0 → 4.30.0

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

@@ -10,11 +10,11 @@ run is doing in the developer's words instead.
 Run this before anything else in this prompt:
 
 ```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 identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
 ```
 
 Report your product slug, such as `codex` or `claude-code`. The command needs no sign-in,
-browser, or project. If this run already ran `onboard identify`, skip this step.
+browser, or project. If this run already ran `onboard identify` or `onboard begin`, skip this step.
 
 - `--model`: copy the model id exactly as your instructions write it. Without an exact
   model id, leave out `--model` rather than guess.
@@ -39,17 +39,17 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase delegation-unavailable
 ```
 
 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 <question>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about <question>
 ```
 
 Name the question with `--about`. Use the one the prompt that asks it names, or else the
-closest of: `harness-permission`, `sign-in`, `setup-answers`, `stack-choice`,
+closest of: `welcome`, `harness-permission`, `sign-in`, `setup-answers`, `stack-choice`,
 `project-name`, `which-project`, `env-file-tracked`, `local-connection`, `local-terms`,
 `existing-folder`,
 `environment-fix`, `uncommitted-file`, `agent-change`, `restore-files`, `thread-id`,
@@ -64,7 +64,7 @@ If you stop this run, send one short report before you stop. The friction comman
 the telemetry setting the developer already chose, so it needs no separate question.
 
 ```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.
@@ -86,7 +86,7 @@ development/test commands. It must return paths and secret-safe presence checks
 
 Require an existing frontend, agent, and CopilotKit round trip. Start only project-owned
 processes when needed, inspect `/info`, and run
-`npx --prefer-offline --yes copilotkit@4.29.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`.
+`npx --prefer-offline --yes copilotkit@4.30.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`.
 Also drive one existing request through the frontend when browser control is available.
 The `verify` report names the runtime URL it probed. If the dev server serves the
 runtime at another URL, add `--runtime-url <url>`.
@@ -94,20 +94,20 @@ runtime at another URL, add `--runtime-url <url>`.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase research-returned
 ```
 
 If the inspection did not prove the baseline this intent extends, stop here without
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/stop
 ```
 
 When the inspection proved what this intent needs, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/a2ui/plan
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/a2ui/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

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

@@ -19,14 +19,14 @@ On Teams, skip Slack-only tools and the Slack e2e harness. Do not add a CopilotK
 web app to make this run look complete. Do not replace the existing agent.
 
 If repository evidence does not prove an existing valid Intelligence selection, sign in
-yourself with `npx --prefer-offline --yes copilotkit@4.29.0 login --json`: the same single streaming
+yourself with `npx --prefer-offline --yes copilotkit@4.30.0 login --json`: the same single streaming
 session generic onboarding uses. Read its JSON Lines while the process runs. The CLI opens
 the page itself when it can: with `"browser_opened": false` in `action_required`, show the
 developer the clickable URL and ask them to finish sign-in there. If the record carries
 `user_code`, show the developer the code to check against the page. Never ask the developer
 to run a login command. Keep reading the same process. Continue only after that same process emits
 `type: completed`. Only when it emits `type: failed`, report the error and take the
-feature stop route below. Then run `npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers`.
+feature stop route below. Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`.
 When it holds a `project` answer from the setup message, create or select that project
 without asking again. Otherwise list projects and select or create one only after they
 choose. Require the secret-safe project/key provisioning summary before wiring the
@@ -84,22 +84,24 @@ 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.29.0 onboard checkpoint --phase awaiting-developer --about uncommitted-file
+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.29.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.29.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/stop
 ```
 
 ## Values this run writes, and the one credential the developer supplies
@@ -132,7 +134,7 @@ nothing. Ask the developer which Channel this project serves and wait for their
 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 feature-binding
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about feature-binding
 ```
 
 The only credential the developer supplies is their model provider key, such as
@@ -146,4 +148,4 @@ If validation cannot pass, or this run needs a prerequisite the app does not hav
 the feature stop route above without further changes.
 
 Otherwise run
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/channels/proof`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/channels/proof`.

package/onboarding/prompts/feature/channels/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.29.0 onboard checkpoint --phase awaiting-plan-approval
+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/channels/start`, and give them to every subagent:
@@ -49,11 +53,11 @@ Retry it a second way if needed.
 For an empty folder, OpenTag runs its own agent on `OPENAI_API_KEY`. State that before the
 plan. Check the target `.env` and the environment for that name. Report presence only, and
 never read, print, or store the value. If it is absent, run
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers` for the key answer the setup message
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers` for the key answer the setup message
 recorded, and do not ask for the key again when it holds one:
 
 - `key.file`: the plan copies the key from that file after approval, with
-  `npx --prefer-offline --yes copilotkit@4.29.0 onboard credentials --model-key OPENAI_API_KEY --env-path <key.file> --copy-to .env --json`.
+  `npx --prefer-offline --yes copilotkit@4.30.0 onboard credentials --model-key OPENAI_API_KEY --env-path <key.file> --copy-to .env --json`.
 - `key.later`: the plan says the developer adds it to the project `.env` before the backend
   starts.
 
@@ -70,7 +74,7 @@ tests and a real mention proof on the chosen provider. Ask for approval as its o
 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-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
@@ -78,4 +82,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.29.0 onboard read feature/channels/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/channels/implement`.

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

@@ -29,23 +29,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.29.0 onboard checkpoint --phase awaiting-developer --about uncommitted-file
+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.29.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.29.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 mention reply, `failed` for an attempted proof that
@@ -54,11 +56,11 @@ failed, and `skipped` when the proof did not run.
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/stop
 ```
 
 When the round trip you reported above was `passed`, run
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/complete`, and pass
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/complete`, and pass
 `onboard complete` the flag `--visual-check channels-proof-passed`. The recorded mention and
 reply are this run's proof, so no web app check is missing. Use `--visual-check performed`
 only when a

package/onboarding/prompts/feature/channels/start.md

@@ -10,11 +10,11 @@ restricted to the target project.
 Run this before anything else in this prompt:
 
 ```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 identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
 ```
 
 Report your product slug, such as `codex` or `claude-code`. The command needs no sign-in,
-browser, or project. If this run already ran `onboard identify`, skip this step.
+browser, or project. If this run already ran `onboard identify` or `onboard begin`, skip this step.
 
 - `--model`: copy the model id exactly as your instructions write it. Without an exact
   model id, leave out `--model` rather than guess.
@@ -39,17 +39,17 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase delegation-unavailable
 ```
 
 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 <question>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about <question>
 ```
 
 Name the question with `--about`. Use the one the prompt that asks it names, or else the
-closest of: `harness-permission`, `sign-in`, `setup-answers`, `stack-choice`,
+closest of: `welcome`, `harness-permission`, `sign-in`, `setup-answers`, `stack-choice`,
 `project-name`, `which-project`, `env-file-tracked`, `local-connection`, `local-terms`,
 `existing-folder`,
 `environment-fix`, `uncommitted-file`, `agent-change`, `restore-files`, `thread-id`,
@@ -64,7 +64,7 @@ If you stop this run, send one short report before you stop. The friction comman
 the telemetry setting the developer already chose, so it needs no separate question.
 
 ```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.
@@ -81,7 +81,7 @@ before a subagent or a project process runs.
 Before changing files, send a short welcome. Say you will inspect the project, show a
 Channel plan, implement only after approval, and prove a real mention reply.
 
-Run `npx --prefer-offline --yes copilotkit@4.29.0 onboard setup-answers`. When it holds a recorded
+Run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`. When it holds a recorded
 `frontend` of Slack or Microsoft Teams, use that one. Ask Slack or Teams as its own question
 only when neither the record, the copied prompt, nor the developer already named one. If either named Slack, use Slack. If either named Teams or
 Microsoft Teams, use Teams. Do not ask again.
@@ -102,7 +102,7 @@ This one does not.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase research-returned
 ```
 
 If the folder is empty, check Node 22, `uv`, and Python before cloning. Python 3.12 or
@@ -112,23 +112,27 @@ to install one with `uv python install 3.12`, and continue after the developer 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 environment-fix
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about environment-fix
 ```
 
-Stop here without cloning only when Node 22 is missing, `uv` is missing, or the developer
-declines that install. Do not switch to a custom build in silence. Name the missing tool
+If the developer declines that install, such as **no** or **not now**, the run did not
+break. Clone nothing, and run
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/declined --message "<their reason>"`.
+
+Stop here without cloning only when Node 22 is missing or `uv` is missing. Do not switch
+to a custom build in silence. Name the missing tool
 and its install command in the message the developer sees: `nvm install 22` for Node 22,
 `curl -LsSf https://astral.sh/uv/install.sh | sh` for `uv`, and `uv python install 3.12`
 for Python. Offer a custom headless build as a later path. Then route out:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/stop
 ```
 
 When the tools this run needs are present, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/channels/plan
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/channels/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

package/onboarding/prompts/feature/chat-suggestions/implement.md

@@ -21,26 +21,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.29.0 onboard checkpoint --phase awaiting-developer --about uncommitted-file
+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.29.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.29.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.29.0 onboard read feature/chat-suggestions/proof`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/chat-suggestions/proof`.

package/onboarding/prompts/feature/chat-suggestions/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.29.0 onboard checkpoint --phase awaiting-plan-approval
+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/chat-suggestions/start`, and give them to every subagent:
@@ -48,7 +52,7 @@ question.
 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-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
@@ -56,4 +60,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.29.0 onboard read feature/chat-suggestions/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/chat-suggestions/implement`.

package/onboarding/prompts/feature/chat-suggestions/proof.md

@@ -18,23 +18,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.29.0 onboard checkpoint --phase awaiting-developer --about uncommitted-file
+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.29.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.29.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 sent suggestion, `failed` for an attempted proof that failed,
@@ -43,9 +45,9 @@ and `skipped` when the proof could not run.
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.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.29.0 onboard read feature/complete` with the real browser-proof
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/complete` with the real browser-proof
 outcome.

package/onboarding/prompts/feature/chat-suggestions/start.md

@@ -8,11 +8,11 @@ implementation, and proof to separate subagents and keep all work inside the tar
 Run this before anything else in this prompt:
 
 ```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 identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
 ```
 
 Report your product slug, such as `codex` or `claude-code`. The command needs no sign-in,
-browser, or project. If this run already ran `onboard identify`, skip this step.
+browser, or project. If this run already ran `onboard identify` or `onboard begin`, skip this step.
 
 - `--model`: copy the model id exactly as your instructions write it. Without an exact
   model id, leave out `--model` rather than guess.
@@ -37,17 +37,17 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase delegation-unavailable
 ```
 
 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 <question>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about <question>
 ```
 
 Name the question with `--about`. Use the one the prompt that asks it names, or else the
-closest of: `harness-permission`, `sign-in`, `setup-answers`, `stack-choice`,
+closest of: `welcome`, `harness-permission`, `sign-in`, `setup-answers`, `stack-choice`,
 `project-name`, `which-project`, `env-file-tracked`, `local-connection`, `local-terms`,
 `existing-folder`,
 `environment-fix`, `uncommitted-file`, `agent-change`, `restore-files`, `thread-id`,
@@ -62,7 +62,7 @@ If you stop this run, send one short report before you stop. The friction comman
 the telemetry setting the developer already chose, so it needs no separate question.
 
 ```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.
@@ -78,7 +78,7 @@ before a subagent or a project process runs.
 
 Before edits, identify the current CopilotKit provider, chat component, message lifecycle,
 agent id, package version, and test/dev commands. Prove the existing OSS round trip with
-`/info`, `npx --prefer-offline --yes copilotkit@4.29.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`/info`, `npx --prefer-offline --yes copilotkit@4.30.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and one real frontend request when browser control is available.
 The `verify` report names the runtime URL it probed. If the dev server serves the
 runtime at another URL, add `--runtime-url <url>`.
@@ -86,20 +86,20 @@ runtime at another URL, add `--runtime-url <url>`.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase research-returned
 ```
 
 If the inspection did not prove the baseline this intent extends, stop here without
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/stop
 ```
 
 When the inspection proved what this intent needs, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/chat-suggestions/plan
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/chat-suggestions/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

package/onboarding/prompts/feature/complete.md

@@ -3,7 +3,7 @@
 Use the outcome the proof step observed. Run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard complete --visual-check <performed|skipped-no-browser-tool|channels-proof-passed|failed>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard complete --visual-check <performed|skipped-no-browser-tool|channels-proof-passed|failed>
 ```
 
 Use `channels-proof-passed` for a Slack or Teams run that recorded a passed round-trip proof
@@ -14,7 +14,7 @@ Use `performed` only when browser control drove the real user-visible surface. U
 `skipped-no-browser-tool` only when no browser tool was available. Use `failed` when the
 browser proof ran but did not prove the feature.
 
-Paste the **Handoff facts** block the command prints into your summary, as it is.
+Write the message the command prints into your summary, word for word.
 
 ## Report friction before completing
 
@@ -22,7 +22,7 @@ Before `onboard complete`, send the friction this run mentioned to the developer
 report each, at most four, costliest first:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.30.0 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
 ```
 
 Put one or two sentences in `--message`, with no secrets, source, or logs. Pick the

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

@@ -16,7 +16,7 @@ follows the telemetry setting the developer already chose, so it needs no separa
 question.
 
 ```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.
@@ -48,7 +48,7 @@ settled refusal rather than a missing baseline, so stop here, before any file ch
 take its own ending:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/blocked-by-plan
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/blocked-by-plan
 ```
 
 `LEARNING_AVAILABILITY_UNAVAILABLE` means the platform did not resolve the answer. It is
@@ -62,7 +62,7 @@ then, so the read below is where its refusal surfaces.
 When the plan or the repository already names an id, ask about that one id and nothing else:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 learning containers get <id> --json
+npx --prefer-offline --yes copilotkit@4.30.0 learning containers get <id> --json
 ```
 
 One call answers it, and no list is needed.
@@ -70,7 +70,7 @@ One call answers it, and no list is needed.
 When no id is in hand, survey what the project holds:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 learning containers list --json
+npx --prefer-offline --yes copilotkit@4.30.0 learning containers list --json
 ```
 
 One call returns at most 500 containers. When `nextCursor` in the result is not null, read
@@ -84,7 +84,7 @@ the developer which one when more than one could. Otherwise create one.
 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 feature-binding
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about feature-binding
 ```
 
 Default to one container for this project, and name it after the project. Learning needs
@@ -99,7 +99,7 @@ user, so the callback can return a different id per tier or per customer.
 Ask the CLI for the id rather than spelling one yourself:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 learning containers default-id --json
+npx --prefer-offline --yes copilotkit@4.30.0 learning containers default-id --json
 ```
 
 It derives the project-scoped id from the selected project's slug, reads the local project
@@ -116,7 +116,7 @@ run that spells the id differently gives one project two containers, each below
 above on its own. One command is what keeps the two spellings identical.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 learning containers create --id <id> --name <name> --json
+npx --prefer-offline --yes copilotkit@4.30.0 learning containers create --id <id> --name <name> --json
 ```
 
 An id already in use answers `LEARNING_CONTAINER_ALREADY_EXISTS`. That is a container to
@@ -143,7 +143,7 @@ such an app on a thread the app created, with `--thread <id>`, which needs no se
 record UNKNOWN as the expected result here.
 
 Run focused tests and
-`npx --prefer-offline --yes copilotkit@4.29.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --prefer-offline --yes copilotkit@4.30.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 The `verify` report names the runtime URL it probed. If the dev server serves the
 runtime at another URL, add `--runtime-url <url>`.
 Repair changed-file failures and record secret-safe evidence.
@@ -157,26 +157,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.29.0 onboard checkpoint --phase awaiting-developer --about uncommitted-file
+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.29.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.29.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.29.0 onboard read feature/learning/proof`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/learning/proof`.