copilotkit 4.28.0 → 4.29.0

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

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

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

@@ -14,7 +14,7 @@ you stop. The friction command follows the telemetry setting the developer alrea
 so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.29.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -64,7 +64,7 @@ or frontend, stop onboarding.
 If the CLI prints `## Stop: this run deleted or moved the developer's work` instead of a
 step, show the developer the list it printed, and run what they choose:
 the `onboard restore` command the tripwire stop prints, which names each deleted file, or
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard tripwire --continue`. Then read the step again. If
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard tripwire --continue`. Then read the step again. If
 you cannot ask, stop onboarding. Never repair, reset, or revert a file the developer changed
 outside this run.
 
@@ -106,16 +106,16 @@ that the selected documentation proved an inferred step.
 Record what the proof returned before you complete:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.29.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
-When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.28.0 onboard complete`, carrying the
+When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.29.0 onboard complete`, carrying the
 surface-check result the proof subagent returned. Pass exactly one of `--visual-check` or
 `--device-check`, matching this journey's surface:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard complete --visual-check <outcome>
-npx --prefer-offline --yes copilotkit@4.28.0 onboard complete --device-check <outcome>
+npx --prefer-offline --yes copilotkit@4.29.0 onboard complete --visual-check <outcome>
+npx --prefer-offline --yes copilotkit@4.29.0 onboard complete --device-check <outcome>
 ```
 
 `--visual-check` is for a web frontend and takes `performed`, `skipped-no-browser-tool`, or

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

@@ -24,7 +24,7 @@ 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.29.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
@@ -34,16 +34,16 @@ cannot ask, or the developer declines, take the feature stop route below.
 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.29.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.29.0 onboard read feature/stop
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, use
 the feature stop route above without further changes.
 
 Otherwise run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/a2ui/proof`.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/a2ui/proof`.

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

@@ -12,7 +12,7 @@ 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.29.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.
@@ -49,7 +49,7 @@ renders a compact visible surface. Ask for approval as its own question.
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard checkpoint --phase awaiting-plan-approval
+npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 Ask the developer before you edit a file that has uncommitted changes. List those files in
@@ -57,4 +57,4 @@ the plan under `Uncommitted files`, each with one sentence explaining why, or wr
 `git status` names them. The CLI records no consent: the approved plan is the record. The
 plan must not delete, move, or rename one of those files.
 
-Then run `npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/a2ui/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/a2ui/implement`.

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

@@ -25,7 +25,7 @@ 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.29.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
@@ -35,13 +35,13 @@ or the developer declines, take the feature stop route below.
 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.29.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.29.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for a proved A2UI surface, `failed` for an attempted proof that failed,
@@ -50,9 +50,9 @@ and `skipped` when the proof could not run.
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/stop
 ```
 
 When the proof is recorded, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/complete` with the actual browser-proof
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/complete` with the actual browser-proof
 outcome.

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

@@ -10,7 +10,7 @@ run is doing in the developer's words instead.
 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.29.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,
@@ -39,15 +39,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.29.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.29.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`,
+`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.
 
@@ -55,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.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.29.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -77,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.28.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`.
+`npx --prefer-offline --yes copilotkit@4.29.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>`.
@@ -85,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.28.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.29.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.29.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/a2ui/plan
+npx --prefer-offline --yes copilotkit@4.29.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.28.0 login --json`: the same single streaming
+yourself with `npx --prefer-offline --yes copilotkit@4.29.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.28.0 onboard setup-answers`.
+feature stop route below. Then run `npx --prefer-offline --yes copilotkit@4.29.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,7 +84,7 @@ 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.29.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
@@ -94,12 +94,12 @@ cannot ask, or the developer declines, take the feature stop route below.
 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.29.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.29.0 onboard read feature/stop
 ```
 
 ## Values this run writes, and the one credential the developer supplies
@@ -132,7 +132,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.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-developer --about feature-binding
 ```
 
 The only credential the developer supplies is their model provider key, such as
@@ -146,4 +146,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.28.0 onboard read feature/channels/proof`.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/channels/proof`.

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

@@ -12,7 +12,7 @@ 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.29.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.
@@ -49,11 +49,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.28.0 onboard setup-answers` for the key answer the setup message
+`npx --prefer-offline --yes copilotkit@4.29.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.28.0 onboard credentials --model-key OPENAI_API_KEY --env-path <key.file> --copy-to .env --json`.
+  `npx --prefer-offline --yes copilotkit@4.29.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 +70,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.28.0 onboard checkpoint --phase awaiting-plan-approval
+npx --prefer-offline --yes copilotkit@4.29.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 +78,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/channels/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/channels/implement`.

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

@@ -29,7 +29,7 @@ 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.29.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
@@ -39,13 +39,13 @@ or the developer declines, take the feature stop route below.
 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.29.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.29.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 +54,11 @@ failed, and `skipped` when the proof did 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.29.0 onboard read feature/stop
 ```
 
 When the round trip you reported above was `passed`, run
-`npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/complete`, and pass
+`npx --prefer-offline --yes copilotkit@4.29.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,7 +10,7 @@ restricted to 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.29.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,
@@ -39,15 +39,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.29.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.29.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`,
+`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.
 
@@ -55,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.28.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.29.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -72,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.28.0 onboard setup-answers`. When it holds a recorded
+Run `npx --prefer-offline --yes copilotkit@4.29.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.
@@ -93,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.28.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase research-returned
 ```
 
 If the folder is empty, check Node 22, `uv`, and Python before cloning. Python 3.12 or
@@ -103,7 +112,7 @@ 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.28.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.29.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
@@ -113,13 +122,13 @@ and its install command in the message the developer sees: `nvm install 22` for
 for Python. Offer a custom headless build as a later path. Then route out:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.29.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.28.0 onboard read feature/channels/plan
+npx --prefer-offline --yes copilotkit@4.29.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,7 +21,7 @@ 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.29.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
@@ -31,16 +31,16 @@ cannot ask, or the developer declines, take the feature stop route below.
 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.29.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.29.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/chat-suggestions/proof`.
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/chat-suggestions/proof`.

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

@@ -12,7 +12,7 @@ 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.29.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.
@@ -48,7 +48,7 @@ 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.29.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 +56,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/chat-suggestions/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/chat-suggestions/implement`.

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

@@ -18,7 +18,7 @@ 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.29.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
@@ -28,13 +28,13 @@ or the developer declines, take the feature stop route below.
 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.29.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.29.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 +43,9 @@ and `skipped` when the proof could not run.
 To route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.28.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.29.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 real browser-proof
+`npx --prefer-offline --yes copilotkit@4.29.0 onboard read feature/complete` with the real browser-proof
 outcome.