copilotkit 4.23.1 → 4.25.0

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.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.
@@ -37,7 +37,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
@@ -67,19 +67,27 @@ only `channels add <name> --adapter slack|teams`, with the project's directory o
 name as `<name>`. On Teams, skip Slack-only tools and the Slack e2e harness. Name focused
 tests and a real mention proof on the chosen provider. 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/channels/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/channels/implement`.

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

@@ -27,11 +27,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
@@ -44,11 +51,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 a proved mention reply, `failed` for an attempted proof that
-failed, and `skipped` when the proof did not run. Then run `npx --prefer-offline --yes copilotkit@4.23.1 onboard audit`.
+failed, and `skipped` when the proof did 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
@@ -63,11 +70,11 @@ 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 and the round trip you reported above was `passed`, run
-`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/complete` and complete with
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/complete` and complete with
 `--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
 browser drove Slack or Teams web and proved the mention reply. Do not use

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

@@ -1,22 +1,27 @@
 # Add a managed Channel for Slack or Microsoft Teams
 
-First, report your coding agent identity using the same command as generic onboarding:
+Treat Slack or Teams as the UI for this run. A CopilotKit web app is not required.
+Empty folders, agent-only folders, and existing CopilotKit apps are all valid starts.
+Orchestrate with separate read-only, implementation, and proof subagents, each
+restricted to 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.23.1 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
+npx --prefer-offline --yes copilotkit@4.25.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
 ```
 
-Use your own product's slug, such as `codex` or `claude-code`. For `--model`, copy the
-model id exactly as your instructions write it. If they name no exact model id, leave out
-`--model` rather than guess. For `--model-family`, give the family of the model you run,
-such as `claude-opus` or `gpt-5`, and leave it out if you do not know it. Never give your
-product slug as a model or a family. This also covers entry commands that omit `--coding-agent`. It needs no login,
-browser, or project setup.
+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.
 
-Treat Slack or Teams as the UI for this run. A CopilotKit web app is not required.
-Empty folders, agent-only folders, and existing CopilotKit apps are all valid starts.
-Orchestrate with separate read-only, implementation, and proof subagents, each
-restricted to the target project.
+- `--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
 
@@ -34,13 +39,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.
@@ -50,7 +55,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.
@@ -64,7 +69,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. Do not
@@ -94,13 +99,19 @@ 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.23.1 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase research-returned
 ```
 
 If the folder is empty, check Node 22, `uv`, and Python before cloning. Python 3.12 or
 newer satisfies the check. If no Python 3.12 or newer is present and `uv` is, offer once
 to install one with `uv python install 3.12`, and continue after the developer approves.
 
+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
+```
+
 Stop here without cloning only when Node 22 is missing, `uv` is missing, or the developer
 declines that install. Do not switch to a custom build in silence. Name the missing tool
 and its install command in the message the developer sees: `nvm install 22` for Node 22,
@@ -108,13 +119,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.23.1 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.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.23.1 onboard read feature/channels/plan
+npx --prefer-offline --yes copilotkit@4.25.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

@@ -15,7 +15,7 @@ Run focused type/test checks and start the app. Record the changed files and val
 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
@@ -30,11 +30,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
@@ -46,7 +53,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
@@ -57,7 +64,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
@@ -70,11 +77,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/chat-suggestions/proof`.
+`npx --prefer-offline --yes copilotkit@4.25.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.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.
@@ -33,7 +33,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
@@ -53,19 +53,27 @@ context-dependent follow-ups. Show an approved-plan-sized diff, a focused test,
 proof that a visible suggestion submits the intended message. 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/chat-suggestions/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/chat-suggestions/implement`.

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

@@ -16,11 +16,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
@@ -33,11 +40,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 a proved sent suggestion, `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
@@ -52,9 +59,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 real browser-proof
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/complete` with the real browser-proof
 outcome.

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

@@ -3,6 +3,24 @@
 Treat this as an additive OSS chat-surface feature. Delegate repository inspection,
 implementation, and proof to separate subagents and keep all work inside 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
@@ -19,13 +37,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.
@@ -35,7 +53,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.
@@ -49,7 +67,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
@@ -58,26 +76,26 @@ approved authorization before implementation.
 
 Before edits, identify the current CopilotKit provider, chat component, message lifecycle,
 agent id, package version, and test/dev commands. Prove the existing OSS round trip with
-`/info`, `npx --prefer-offline --yes copilotkit@4.23.1 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`/info`, `npx --prefer-offline --yes copilotkit@4.25.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and one real frontend request when browser control is available.
 
 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/chat-suggestions/plan
+npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/chat-suggestions/plan
 ```
 
 That prompt holds the plan, the developer's approval, and the paths the plan changes.

package/onboarding/prompts/feature/complete.md

@@ -3,7 +3,7 @@
 Use the outcome the proof step observed. Run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard complete --visual-check <performed|skipped-no-browser-tool|channels-proof-passed|failed>
+npx --prefer-offline --yes copilotkit@4.25.0 onboard complete --visual-check <performed|skipped-no-browser-tool|channels-proof-passed|failed>
 ```
 
 Use `channels-proof-passed` for a Slack or Teams run that recorded a passed round-trip proof
@@ -22,7 +22,7 @@ Before `onboard complete`, send the friction this run mentioned to the developer
 report each, at most four, costliest first:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.25.0 onboard friction --category <slug> --cost-seconds <seconds> --message "<sentences>"
 ```
 
 Put one or two sentences in `--message`, with no secrets, source, or logs. Pick the

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

@@ -17,7 +17,7 @@ follows the telemetry setting the developer already chose, so it needs no separa
 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.
@@ -49,7 +49,7 @@ settled refusal rather than a missing baseline, so stop here, before any file ch
 take its own ending:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/blocked-by-plan
+npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/blocked-by-plan
 ```
 
 `LEARNING_AVAILABILITY_UNAVAILABLE` means the platform did not resolve the answer. It is
@@ -63,7 +63,7 @@ then, so the read below is where its refusal surfaces.
 When the plan or the repository already names an id, ask about that one id and nothing else:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 learning containers get <id> --json
+npx --prefer-offline --yes copilotkit@4.25.0 learning containers get <id> --json
 ```
 
 One call answers it, and no list is needed.
@@ -71,7 +71,7 @@ One call answers it, and no list is needed.
 When no id is in hand, survey what the project holds:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 learning containers list --json
+npx --prefer-offline --yes copilotkit@4.25.0 learning containers list --json
 ```
 
 One call returns at most 500 containers. When `nextCursor` in the result is not null, read
@@ -82,6 +82,12 @@ second container for work the first one already covers.
 Reuse an existing container when one covers the workflow this run is instrumenting, and ask
 the developer which one when more than one could. Otherwise create one.
 
+Before you end your turn to wait for the developer, report the pause:
+
+```text
+npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-developer
+```
+
 Default to one container for this project, and name it after the project. Learning needs
 evidence to work with: the first automatic run wants threads from 15 distinct conversations
 in one container, so splitting a new project across several leaves every one of them below
@@ -94,7 +100,7 @@ user, so the callback can return a different id per tier or per customer.
 Ask the CLI for the id rather than spelling one yourself:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 learning containers default-id --json
+npx --prefer-offline --yes copilotkit@4.25.0 learning containers default-id --json
 ```
 
 It derives the project-scoped id from the selected project's slug, reads the local project
@@ -108,7 +114,7 @@ run that spells the id differently gives one project two containers, each below
 above on its own. One command is what keeps the two spellings identical.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.23.1 learning containers create --id <id> --name <name> --json
+npx --prefer-offline --yes copilotkit@4.25.0 learning containers create --id <id> --name <name> --json
 ```
 
 An id already in use answers `LEARNING_CONTAINER_ALREADY_EXISTS`. That is a container to
@@ -129,18 +135,19 @@ and persistence.
 
 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 tests and
-`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 and record secret-safe 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
@@ -155,11 +162,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.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.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+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
@@ -171,7 +185,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
@@ -182,7 +196,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
@@ -196,11 +210,11 @@ with `Status: blocked`, route out and stop. Route out the same way when
 `--accept-credential` refuses because it names a lost variable:
 
 ```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/learning/proof`.
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/learning/proof`.