copilotkit 4.29.0 → 4.30.0

package/onboarding/prompts/feature/learning/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/learning/start`, and give them to every subagent:
@@ -52,7 +56,7 @@ now. If the list from `feature/learning/start` holds a container that covers thi
 name that one. Otherwise ask the CLI for the id of a new one:
 
 ```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 id from the selected project's slug and needs no credential.
@@ -87,7 +91,7 @@ tracked file, and it accepts a Learning run only after the proof's container che
 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
@@ -95,4 +99,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/learning/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/learning/implement`.

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

@@ -12,13 +12,13 @@ A local stack runs Learning only with a model that the developer gave it. Before
 run this command from the app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 local status --json
+npx --prefer-offline --yes copilotkit@4.30.0 local status --json
 ```
 
 Read `learning.configuration`. If it is `configured`, continue with the proof. Any other
 value means that the stack has no Learning model.
 
-Run `npx --prefer-offline --yes copilotkit@4.29.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 the Learning answer from the record,
 or this conversation. If it is `later`, the developer chose "configure later" for the
 Learning model on the local route, so do not ask again. The same holds when neither holds a
@@ -30,7 +30,7 @@ it has a model. Ask them to run this command in their own terminal window, in th
 directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.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
@@ -40,13 +40,13 @@ On a running stack, it restarts only Learning. The container and its threads sta
 ask the developer to write a model file, and do not read or print the model key.
 
 Say that the run continues when they reply or resume this session. Report the pause with
-`npx --prefer-offline --yes copilotkit@4.29.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 `local status --json` again.
 When it reports `configured`, continue with the proof.
 
 If the developer declines, continue with the proof, because the container assignment can
 still be proved. In the closing report, write "Learning configuration incomplete". Name the
-command that adds the model later: `npx --prefer-offline --yes copilotkit@4.29.0 local setup`, run from
+command that adds the model later: `npx --prefer-offline --yes copilotkit@4.30.0 local setup`, run from
 the app directory. `learning.verified` is always `false`. It does not mean that Learning
 failed.
 
@@ -55,7 +55,7 @@ failed.
 One command decides it:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --expect-learning-container <id> --json
+npx --prefer-offline --yes copilotkit@4.30.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --expect-learning-container <id> --json
 ```
 
 It reads the thread back from the platform, so it answers for any runtime mount, and it
@@ -74,11 +74,11 @@ a signed-in user, read that request's `threadId` from the request body the page
 the runtime, and prove the same thread. Where the page needs a sign-in, do not create an
 account and do not enter credentials. Where you cannot send the request yourself, ask the
 developer to send one message on a new thread and give you its thread id. Report the pause
-with `npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about thread-id`, then
+with `npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about thread-id`, then
 end your turn and wait. When the developer gives the id, prove that thread:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 verify --expect-runtime intelligence --thread <thread-id> --expect-learning-container <id> --json
+npx --prefer-offline --yes copilotkit@4.30.0 verify --expect-runtime intelligence --thread <thread-id> --expect-learning-container <id> --json
 ```
 
 It reads that thread from the platform with the project key and starts no run.
@@ -108,23 +108,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 Container assignment, `failed` for an attempted proof that
@@ -133,9 +135,9 @@ failed, 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 actual surface
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/complete` with the actual surface
 outcome.

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

@@ -9,11 +9,11 @@ subagents. Work only inside the target project and preserve its existing agent a
 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.
@@ -38,17 +38,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`,
@@ -63,7 +63,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.
@@ -93,7 +93,7 @@ status:
   before the capture, the inspection, and any edit:
 
 ```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
@@ -121,20 +121,20 @@ test/dev commands. Prove the current round trip and inspect `/info`.
 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/learning/plan
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/learning/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

package/onboarding/prompts/feature/open-generative-ui/implement.md

@@ -22,26 +22,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/open-generative-ui/proof`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/open-generative-ui/proof`.

package/onboarding/prompts/feature/open-generative-ui/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/open-generative-ui/start`, and give them to every subagent:
@@ -47,7 +51,7 @@ likely CSP/sandbox implications, tests, and a user-visible generated UI proof. 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-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
@@ -55,4 +59,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/open-generative-ui/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/open-generative-ui/implement`.

package/onboarding/prompts/feature/open-generative-ui/proof.md

@@ -19,23 +19,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 generated UI, `failed` for an attempted proof that failed,
@@ -44,9 +46,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 outcome actually
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/complete` with the outcome actually
 observed.

package/onboarding/prompts/feature/open-generative-ui/start.md

@@ -8,11 +8,11 @@ implementation, and proof subagents, all restricted to the target project direct
 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.
@@ -79,7 +79,7 @@ before a subagent or a project process runs.
 Before edits, have a research subagent identify the current CopilotKit runtime route,
 provider/chat component, agent id, package versions, existing middleware, sandbox/CSP
 constraints, and normal test/dev commands. Prove the existing app first with `/info`,
-`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`,
 and a 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>`.
@@ -87,20 +87,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/open-generative-ui/plan
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/open-generative-ui/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

package/onboarding/prompts/feature/realtime-sync/implement.md

@@ -18,7 +18,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 changed paths and secret-safe validation
@@ -33,26 +33,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/realtime-sync/proof`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/realtime-sync/proof`.

package/onboarding/prompts/feature/realtime-sync/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/realtime-sync/start`, and give them to every subagent:
@@ -52,7 +56,7 @@ need a `wsUrl`. 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.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
@@ -60,4 +64,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/realtime-sync/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/realtime-sync/implement`.

package/onboarding/prompts/feature/realtime-sync/proof.md

@@ -21,23 +21,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 proved two-client sync, `failed` for an attempted proof that failed,
@@ -46,8 +48,8 @@ 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 actual outcome.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/complete` with the actual outcome.

package/onboarding/prompts/feature/realtime-sync/start.md

@@ -9,11 +9,11 @@ two-context proof to subagents within 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.
@@ -38,17 +38,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`,
@@ -63,7 +63,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.
@@ -85,20 +85,20 @@ round trip and inspect `/info`.
 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/realtime-sync/plan
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/realtime-sync/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.