copilotkit 4.28.0 → 4.30.0

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.28.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,15 +38,24 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.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.28.0 onboard checkpoint --phase awaiting-developer
+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: `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`,
+`scoped-fix`, `feature-binding`, `other`. Report the pause before every turn that ends while
+the run is still open, even a turn where you asked nothing, with `other` then. A run that
+goes quiet without it reads as a run that died.
+
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
 When the answer or the result arrives, continue from the step that paused.
 
@@ -54,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.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.30.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -76,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.28.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.28.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.28.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.

package/onboarding/prompts/feature/rich-threads/implement.md

@@ -2,7 +2,7 @@
 
 Delegate implementation to one subagent with the approved plan and fetched official guides.
 If repository evidence does not prove an existing valid Intelligence selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 login --json` and follow its single streaming session. Then
+`npx --prefer-offline --yes copilotkit@4.30.0 login --json` and follow its single streaming session. Then
 list projects, show the developer the current/recent choices, and select or create one only
 after they choose. Require the secret-safe selection summary to confirm the project file,
 environment file, and key provisioning; never display a key. If existing configuration is
@@ -21,7 +21,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 type/test commands, then start the app and run
-`npx --prefer-offline --yes copilotkit@4.28.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 before continuing. Record changed paths and secret-safe
@@ -36,26 +36,28 @@ That result is a question for the developer. Name the file and why the work need
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about uncommitted-file
 ```
 
 Then end your turn and wait for the developer's answer. If they allow it, spawn a fresh
 implementation subagent with the same handoff and the file added to the plan. If you
-cannot ask, or the developer declines, take the feature stop route below.
+cannot ask, take the feature stop route below. If the developer declines, such as **no** or **not now**,
+the run did not break. Run
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/declined --message "<their reason>"`.
 
 If the CLI prints `## Stop: this run deleted or moved the developer's work` instead of
 a step, show the developer the list it printed, and run what they choose:
 the `onboard restore` command the tripwire stop prints, which names each deleted file, or
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard tripwire --continue`. Then read the step again.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard tripwire --continue`. Then read the step again.
 
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/stop
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, use
 the feature stop route above without further changes.
 
 Otherwise run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/rich-threads/proof`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/rich-threads/proof`.

package/onboarding/prompts/feature/rich-threads/plan.md

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

package/onboarding/prompts/feature/rich-threads/proof.md

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

package/onboarding/prompts/feature/rich-threads/start.md

@@ -9,11 +9,11 @@ implementation, and proof to separate subagents within the target project.
 Run this before anything else in this prompt:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.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,15 +38,24 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.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.28.0 onboard checkpoint --phase awaiting-developer
+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: `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`,
+`scoped-fix`, `feature-binding`, `other`. Report the pause before every turn that ends while
+the run is still open, even a turn where you asked nothing, with `other` then. A run that
+goes quiet without it reads as a run that died.
+
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
 When the answer or the result arrives, continue from the step that paused.
 
@@ -54,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.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.30.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -76,20 +85,20 @@ the current frontend-to-runtime-to-agent 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.28.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.28.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.28.0 onboard read feature/rich-threads/plan
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/rich-threads/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

package/onboarding/prompts/feature/stop.md

@@ -20,7 +20,7 @@ a `start` with no `--run` reprints the id this stopped run already holds, and on
 covering both reads as one run that did two different things.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard start --run <new-12-character-id>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard start --run <new-12-character-id>
 ```
 
 Do not read a generic onboarding node from this run. A feature run and a generic run are
@@ -48,13 +48,13 @@ put to them, stop here and send the report below.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-developer --about scoped-fix
 ```
 
 If they approve it, make that one fix and nothing else. Then come back into this run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard resume --message "<approval>"
+npx --prefer-offline --yes copilotkit@4.30.0 onboard resume --message "<approval>"
 ```
 
 Put the developer's approval in `--message`, in one or two sentences: the fix they
@@ -75,7 +75,7 @@ Send one short report. The friction command follows the telemetry setting the de
 already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.30.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.

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

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

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

@@ -12,13 +12,17 @@ The approval is a wait for the developer. Before you end your turn to wait, repo
 pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
 When the answer arrives, continue from the step that paused. If the developer asks for a
 change, show the changed plan and ask again.
 
+If the developer declines the plan, such as **no**, **not now** or **do not add it**, change
+no files. Run
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read stopped/declined --message "<their reason>"`.
+
 ## What this prompt takes from the start
 
 Keep these from `feature/voice/start`, and give them to every subagent:
@@ -42,7 +46,7 @@ the repository proves its variable name is configured. Otherwise, explain the se
 take the feature stop route rather than writing a placeholder:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/stop
 ```
 
 Show a small plan for the documented transcription service, the existing composer, focused
@@ -51,7 +55,7 @@ tests, and a microphone/canned-transcript proof. Ask for approval as its own que
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-plan-approval
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 Ask the developer before you edit a file that has uncommitted changes. List those files in
@@ -59,4 +63,4 @@ the plan under `Uncommitted files`, each with one sentence explaining why, or wr
 `git status` names them. The CLI records no consent: the approved plan is the record. The
 plan must not delete, move, or rename one of those files.
 
-Then run `npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/voice/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/voice/implement`.

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

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

@@ -8,11 +8,11 @@ read-only, implementation, and proof subagents, each restricted to the target pr
 Run this before anything else in this prompt:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.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,15 +37,24 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.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.28.0 onboard checkpoint --phase awaiting-developer
+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: `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`,
+`scoped-fix`, `feature-binding`, `other`. Report the pause before every turn that ends while
+the run is still open, even a turn where you asked nothing, with `other` then. A run that
+goes quiet without it reads as a run that died.
+
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
 When the answer or the result arrives, continue from the step that paused.
 
@@ -53,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.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.30.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -70,7 +79,7 @@ before a subagent or a project process runs.
 Before edits, inspect the runtime route, CopilotKit provider/chat composer, current agent,
 existing provider credential variable names (presence only), package versions, browser
 permissions approach, and test/dev commands. Prove the existing OSS baseline with `/info`,
-`npx --prefer-offline --yes copilotkit@4.28.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 UI request when a browser 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>`.
@@ -78,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.28.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.28.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.28.0 onboard read feature/voice/plan
+npx --prefer-offline --yes copilotkit@4.30.0 onboard read feature/voice/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

package/onboarding/prompts/framework/ag2.md

@@ -1,18 +1,11 @@
 # Configure AG2
 
-First run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`. Its `vendor` is the
+First run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`. Its `vendor` is the
 vendor the framework step recorded, even after this conversation lost it, with
 `vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
 
 Preserve an existing AG2 model setup. For a new agent, use the vendor that the framework
-step recorded. Use OpenAI only when the record and this conversation have no vendor. This
-release offers a new agent on this framework OpenAI or an OpenAI-compatible provider only.
-For a new agent, if the developer names Anthropic or Google, say that this release
-supports OpenAI or an OpenAI-compatible provider on this framework, that Anthropic and
-Google come in a later release, and offer the built-in CopilotKit agent if they need
-Anthropic or Google now. An existing agent keeps its vendor and model. If it runs on
-Anthropic or Google, add one line to the plan: the page context that CopilotKit sends can
-fail with that vendor until a CopilotKit SDK release fixes it (PE-728). Take that vendor's
+step recorded. Use OpenAI only when the record and this conversation have no vendor. This release offers a new agent on this framework OpenAI or an OpenAI-compatible provider only. For a new agent, if the developer names Anthropic or Google, say that this release supports OpenAI or an OpenAI-compatible provider on this framework, that Anthropic and Google come in a later release, and offer the built-in CopilotKit agent if they need Anthropic or Google now. An existing agent keeps its vendor and model. If it runs on Anthropic or Google, add one line to the plan: this CopilotKit CLI release has not proven Anthropic or Google on this framework, so a chat can fail with it. Take that vendor's
 package, class, and credential variable names from the framework's own documentation, and
 use a model id that the vendor serves to a new key today. For an OpenAI-compatible
 provider, keep `OPENAI_API_KEY`, use the model id that `setup/questions` recorded, and
@@ -47,7 +40,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the A2UI documentation gap.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/agno.md

@@ -1,18 +1,11 @@
 # Configure Agno
 
-First run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`. Its `vendor` is the
+First run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`. Its `vendor` is the
 vendor the framework step recorded, even after this conversation lost it, with
 `vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
 
 Preserve an existing Agno model setup. For a new agent, use the vendor that the framework
-step recorded. Use OpenAI only when the record and this conversation have no vendor. This
-release offers a new agent on this framework OpenAI or an OpenAI-compatible provider only.
-For a new agent, if the developer names Anthropic or Google, say that this release
-supports OpenAI or an OpenAI-compatible provider on this framework, that Anthropic and
-Google come in a later release, and offer the built-in CopilotKit agent if they need
-Anthropic or Google now. An existing agent keeps its vendor and model. If it runs on
-Anthropic or Google, add one line to the plan: the page context that CopilotKit sends can
-fail with that vendor until a CopilotKit SDK release fixes it (PE-728). Take that vendor's
+step recorded. Use OpenAI only when the record and this conversation have no vendor. OpenAI, an OpenAI-compatible provider, Anthropic, and Google work. An existing agent keeps its vendor and model. Take that vendor's
 package, class, and credential variable names from the framework's own documentation, and
 use a model id that the vendor serves to a new key today. For an OpenAI-compatible
 provider, keep `OPENAI_API_KEY`, use the model id that `setup/questions` recorded, and
@@ -51,7 +44,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, the documented dependencies and adapter, and how the agent reads `context`.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/built-in.md

@@ -1,6 +1,6 @@
 # Configure the built-in CopilotKit agent
 
-First run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`. Its `vendor` is the
+First run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`. Its `vendor` is the
 vendor the framework step recorded, even after this conversation lost it, with
 `vendor.baseUrl` and `vendor.modelId` for an OpenAI-compatible provider.
 
@@ -47,7 +47,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/claude-sdk-python.md

@@ -1,6 +1,6 @@
 # Configure Claude Agent SDK for Python
 
-First run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`. Its `vendor` is the
+First run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`. Its `vendor` is the
 vendor the framework step recorded, even after this conversation lost it.
 
 Preserve an existing Claude Agent SDK model setup. The Claude Agent SDK runs only
@@ -40,7 +40,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/claude-sdk-typescript.md

@@ -1,6 +1,6 @@
 # Configure Claude Agent SDK for TypeScript
 
-First run `npx --prefer-offline --yes copilotkit@4.28.0 onboard setup-answers`. Its `vendor` is the
+First run `npx --prefer-offline --yes copilotkit@4.30.0 onboard setup-answers`. Its `vendor` is the
 vendor the framework step recorded, even after this conversation lost it.
 
 Preserve an existing Claude Agent SDK model setup. The Claude Agent SDK runs only
@@ -44,7 +44,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the context limit.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read unsupported/no-validated-path`.