copilotkit 4.23.1 → 4.25.0

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

@@ -19,11 +19,18 @@ not edit it. It returns a result that starts with `Status: blocked` and names th
 Blockers.
 
 That result is a question for the developer. The file has not changed yet, so consent can
-still go on the record. Name the file and why the fix needs it, then end your turn and wait
-for the developer's answer. If they allow it, record their answer before any edit:
+still go on the record. Name the file and why the fix needs it.
+Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
+```
+
+Then end your turn and wait for the developer's answer. If they allow it, record their
+answer before any edit:
+
+```text
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -36,11 +43,11 @@ Report the outcome of each attempt as it ends, before any repair. The command co
 attempts and the repairs:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.25.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,
-and `skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.23.1 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.25.0 onboard audit`.
 Continue only when it starts with `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -55,8 +62,8 @@ the path and the change the audit reports. Run the audit again after each accept
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/complete` with the actual outcome.
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/complete` with the actual outcome.

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

@@ -4,6 +4,24 @@ Treat realtime sync as the Intelligence thread-realtime plane, not as a generic
 exercise. Act as the orchestrator and delegate read-only inspection, implementation, and
 two-context proof to subagents within the target project.
 
+## First, say which coding agent you are
+
+Run this before anything else in this prompt:
+
+```text
+npx --prefer-offline --yes copilotkit@4.25.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.
+
+- `--model`: copy the model id exactly as your instructions write it. Without an exact
+  model id, leave out `--model` rather than guess.
+- `--model-family`: give it even without `--model`. Closest of: `claude-opus`,
+  `claude-sonnet`, `claude-haiku`, `gpt-5`, `gemini`, `grok`, `glm`, `minimax`, `mimo`,
+  `deepseek`, `qwen`, `kimi`, else the model's series. Leave it out if you do not know it.
+- Never give your product slug as a model, or as an unlisted family.
+
 ## Waits, stops, and subagents
 
 A run that starts here has not read these rules yet, so they come first. They cover this
@@ -20,13 +38,13 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -36,7 +54,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.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -50,7 +68,7 @@ one scoped fix, and sends the report itself when no fix is approved.
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -65,20 +83,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.23.1 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard read feature/realtime-sync/plan
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 login --json` and follow its single streaming session. Then
+`npx --prefer-offline --yes copilotkit@4.25.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
@@ -15,19 +15,20 @@ surface. Add the documented drawer only if the approved plan selected it.
 
 An Intelligence runtime requires `identifyUser`, and it usually reads a signed-in session
 that a CLI request does not carry. That makes the round trip UNKNOWN and the command exit
-non-zero on an app that is working. Pass what `identifyUser` reads with a repeatable
-`--header "Name: value"`, or record UNKNOWN as the expected result for an auth-gated app.
-It is not a defect to repair.
+non-zero on an app that is working. It is not a defect to repair. The proof step proves
+such an app on a thread the app created, with `--thread <id>`, which needs no session. Pass
+`--header "Name: value"` only when the developer offers what `identifyUser` reads, or
+record UNKNOWN as the expected result here.
 
 Run focused type/test commands, then start the app and run
-`npx --prefer-offline --yes copilotkit@4.23.1 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --prefer-offline --yes copilotkit@4.25.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 Repair changed-file failures before continuing. Record changed paths and secret-safe
 validation evidence.
 
 Before you spawn the implementation subagent, take the authorized list from the CLI:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard audit
+npx --prefer-offline --yes copilotkit@4.25.0 onboard audit
 ```
 
 From its result, copy the paths under `Authorized to modify:`. A passed or failed audit with
@@ -42,11 +43,18 @@ protected path, it must not edit it. It returns a result that starts with `Statu
 and names the file under Blockers.
 
 That result is a question for the developer. The file has not changed yet, so consent can
-still go on the record. Name the file and why the work needs it, then end your turn and wait
-for the developer's answer. If they allow it, record their answer before any edit:
+still go on the record. Name the file and why the work needs it.
+Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
+```
+
+Then end your turn and wait for the developer's answer. If they allow it, record their
+answer before any edit:
+
+```text
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -58,7 +66,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard audit
+npx --prefer-offline --yes copilotkit@4.25.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -69,7 +77,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -82,11 +90,11 @@ Run the audit again after each accepted change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard read feature/rich-threads/proof`.
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/rich-threads/proof`.

package/onboarding/prompts/feature/rich-threads/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.23.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -34,7 +34,7 @@ you plan. Run `onboard protect` again from the target app directory: on the same
 prints the baseline the run already holds.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect
 ```
 
 Then have one read-only subagent repeat the inspection for the findings above, and wait
@@ -59,19 +59,27 @@ The plan must name the documented Intelligence runtime wiring, server-side `iden
 catch-all thread routes, the selected UI (drawer or existing headless UI), preserved behavior,
 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.25.0 onboard checkpoint --phase awaiting-plan-approval
+```
+
 The plan must list every protected path it needs to change under `Authorization requested`,
-with one sentence explaining why. Write `None` when it needs none. Authorization covers
-changing a protected path, not removing it, so the plan must not delete, move, or rename
-one.
+with one sentence explaining why. Write `None` when it needs none. A step that installs or
+upgrades a package changes its manifest, so list a protected manifest such as `package.json`
+or `pyproject.toml`. Its consent covers its lockfile, beside it or at the workspace root.
+Authorization covers changing a protected path, not removing it, so the plan must not
+delete, move, or rename one.
 
 After approval, record each approved path before implementation:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
 ```
 
 If an approved path changed after capture and no implementation step has run, add
 `--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
 authorize a path the approved plan did not list.
 
-Then run `npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/rich-threads/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/rich-threads/implement`.

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

@@ -18,11 +18,18 @@ not edit it. It returns a result that starts with `Status: blocked` and names th
 Blockers.
 
 That result is a question for the developer. The file has not changed yet, so consent can
-still go on the record. Name the file and why the fix needs it, then end your turn and wait
-for the developer's answer. If they allow it, record their answer before any edit:
+still go on the record. Name the file and why the fix needs it.
+Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
+```
+
+Then end your turn and wait for the developer's answer. If they allow it, record their
+answer before any edit:
+
+```text
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -35,12 +42,12 @@ Report the outcome of each attempt as it ends, before any repair. The command co
 attempts and the repairs:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.25.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for proved persistence and reopen, `failed` for an attempted proof that
 failed, and `skipped` when the proof could not run. Then run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard audit`. Continue only when it starts with
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard audit`. Continue only when it starts with
 `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -55,9 +62,9 @@ the path and the change the audit reports. Run the audit again after each accept
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/complete` with the actual browser
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/complete` with the actual browser
 outcome.

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

@@ -4,6 +4,24 @@ Treat Rich Threads as a managed Intelligence feature layered onto the existing a
 reason to replace its agent or chat. Act as the orchestrator and delegate inspection,
 implementation, and proof to separate subagents within the target project.
 
+## First, say which coding agent you are
+
+Run this before anything else in this prompt:
+
+```text
+npx --prefer-offline --yes copilotkit@4.25.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.
+
+- `--model`: copy the model id exactly as your instructions write it. Without an exact
+  model id, leave out `--model` rather than guess.
+- `--model-family`: give it even without `--model`. Closest of: `claude-opus`,
+  `claude-sonnet`, `claude-haiku`, `gpt-5`, `gemini`, `grok`, `glm`, `minimax`, `mimo`,
+  `deepseek`, `qwen`, `kimi`, else the model's series. Leave it out if you do not know it.
+- Never give your product slug as a model, or as an unlisted family.
+
 ## Waits, stops, and subagents
 
 A run that starts here has not read these rules yet, so they come first. They cover this
@@ -20,13 +38,13 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -36,7 +54,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.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -50,7 +68,7 @@ one scoped fix, and sends the report itself when no fix is approved.
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -65,20 +83,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.23.1 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard read feature/rich-threads/plan
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard start --run <new-12-character-id>
+npx --prefer-offline --yes copilotkit@4.25.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
@@ -45,10 +45,16 @@ Name the one fix you propose, and say which file, setting, or process it touches
 developer whether they approve that one fix. If they decline, or the question cannot be
 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.25.0 onboard checkpoint --phase awaiting-developer
+```
+
 If they approve it, make that one fix and nothing else. Then come back into this run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard resume --message "<approval>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard resume --message "<approval>"
 ```
 
 Put the developer's approval in `--message`, in one or two sentences: the fix they
@@ -69,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.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.25.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

@@ -14,7 +14,7 @@ voice proof. Record changed paths and validation results.
 Before you spawn the implementation subagent, take the authorized list from the CLI:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard audit
+npx --prefer-offline --yes copilotkit@4.25.0 onboard audit
 ```
 
 From its result, copy the paths under `Authorized to modify:`. A passed or failed audit with
@@ -29,11 +29,18 @@ protected path, it must not edit it. It returns a result that starts with `Statu
 and names the file under Blockers.
 
 That result is a question for the developer. The file has not changed yet, so consent can
-still go on the record. Name the file and why the work needs it, then end your turn and wait
-for the developer's answer. If they allow it, record their answer before any edit:
+still go on the record. Name the file and why the work needs it.
+Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
+```
+
+Then end your turn and wait for the developer's answer. If they allow it, record their
+answer before any edit:
+
+```text
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -45,7 +52,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard audit
+npx --prefer-offline --yes copilotkit@4.25.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -56,7 +63,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -69,11 +76,11 @@ Run the audit again after each accepted change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard read feature/voice/proof`.
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/voice/proof`.

package/onboarding/prompts/feature/voice/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.23.1 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -34,7 +34,7 @@ you plan. Run `onboard protect` again from the target app directory: on the same
 prints the baseline the run already holds.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect
 ```
 
 Then have one read-only subagent repeat the inspection for the findings above, and wait
@@ -50,25 +50,33 @@ 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.23.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/stop
 ```
 
 Show a small plan for the documented transcription service, the existing composer, focused
 tests, and a microphone/canned-transcript 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.25.0 onboard checkpoint --phase awaiting-plan-approval
+```
+
 The plan must list every protected path it needs to change under `Authorization requested`,
-with one sentence explaining why. Write `None` when it needs none. Authorization covers
-changing a protected path, not removing it, so the plan must not delete, move, or rename
-one.
+with one sentence explaining why. Write `None` when it needs none. A step that installs or
+upgrades a package changes its manifest, so list a protected manifest such as `package.json`
+or `pyproject.toml`. Its consent covers its lockfile, beside it or at the workspace root.
+Authorization covers changing a protected path, not removing it, so the plan must not
+delete, move, or rename one.
 
 After approval, record each approved path before implementation:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
 ```
 
 If an approved path changed after capture and no implementation step has run, add
 `--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
 authorize a path the approved plan did not list.
 
-Then run `npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/voice/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/voice/implement`.

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

@@ -17,11 +17,18 @@ not edit it. It returns a result that starts with `Status: blocked` and names th
 Blockers.
 
 That result is a question for the developer. The file has not changed yet, so consent can
-still go on the record. Name the file and why the fix needs it, then end your turn and wait
-for the developer's answer. If they allow it, record their answer before any edit:
+still go on the record. Name the file and why the fix needs it.
+Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
+```
+
+Then end your turn and wait for the developer's answer. If they allow it, record their
+answer before any edit:
+
+```text
+npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -34,11 +41,11 @@ Report the outcome of each attempt as it ends, before any repair. The command co
 attempts and the repairs:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.25.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
-`skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.23.1 onboard audit`.
+`skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.25.0 onboard audit`.
 Continue only when it starts with `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -53,9 +60,9 @@ the path and the change the audit reports. Run the audit again after each accept
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/complete` with the actual surface
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/complete` with the actual surface
 outcome.