copilotkit 4.24.0 → 4.25.0

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

@@ -4,8 +4,27 @@ This node records the developer's local deployment choice in the onboarding rout
 Use that choice for both new and existing apps throughout this run. Pass it to each
 worker. Do not offer a hosted project later in this run.
 
+A local request can arrive after this run created a hosted project: `init --create` or
+`onboard credentials` already ran. Then do not take the local route, and record nothing.
+Tell the developer that this run already created a hosted project, so it stays managed.
+Return to the step you were on.
+
+First run `npx --prefer-offline --yes copilotkit@4.25.0 local --help`. If it does not list `setup`
+("Configure model access and install or resume the local stack"), this release has no
+local evaluation. Tell the developer so, and keep managed. If this run has not recorded
+managed yet, run `npx --prefer-offline --yes copilotkit@4.25.0 onboard deployment --choice managed`.
+Then return to “Check sign-in” in the start prompt. If a login process from it still
+runs, keep reading that process and start no second one. Otherwise record the choice:
+
+```text
+npx --prefer-offline --yes copilotkit@4.25.0 onboard deployment --choice local
+```
+
 Explain these conditions before sign-in:
 
+- This is self-hosting on the developer's machine, for evaluation. The CLI does not
+  install into a cluster. To self-host in their own cluster, they follow the Helm guide
+  (https://docs.copilotkit.ai/intelligence/self-hosting.md).
 - The developer supplies Docker with 4 CPUs, 12 GiB RAM, and 40 GiB free storage
   available for this stack, after other workloads.
 - The CLI installs Threads, Learning, Channels, the dashboard, CLI-approved local sign-in,
@@ -26,10 +45,10 @@ and Learning starts its first run only after 15 conversations. Offer these choic
 
 1. Configure later, the default. Install with `--defer-model`. In the closing report, write
    "Learning configuration incomplete". Name the command that adds the model later:
-   `npx --prefer-offline --yes copilotkit@4.24.0 local setup`, run in a terminal in the app directory.
+   `npx --prefer-offline --yes copilotkit@4.25.0 local setup`, run in a terminal in the app directory.
 2. Guided setup. If the developer named Learning as a goal, offer it first. Install
    the stack with `--defer-model`. After the stack is ready, the developer runs
-   `npx --prefer-offline --yes copilotkit@4.24.0 local setup` in their own terminal window, in the app
+   `npx --prefer-offline --yes copilotkit@4.25.0 local setup` in their own terminal window, in the app
    directory. Never give it as a `!` line: its guided prompt needs a terminal, and a coding
    agent's shell has none. The prompt asks for the model and its key, and it saves them
    privately. On a running stack, it restarts only Learning. Do not ask the developer to
@@ -37,21 +56,39 @@ and Learning starts its first run only after 15 conversations. Offer these choic
 3. A private model file that the developer has already. Pass its path with
    `--model-config <file>`. Do not read or print the file.
 
+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
+```
+
 Record the model choice, and any candidate path, in the plan, but no secret values.
 Create no cluster and change no app files at this step. The developer can still decline sign-in.
 If declined, take the failure path below.
 
-Run `npx --prefer-offline --yes copilotkit@4.24.0 login --json`. Follow the streaming sign-in
+A developer can ask for local after sign-in started. If a login process from the start
+prompt still runs, keep reading that process and start no second one. If sign-in already
+completed, skip sign-in. If research already started, do not start it again.
+If the managed sign-in message was already sent, send this once and no other sign-in
+message: “You asked to run it locally, so this project gets no managed CopilotKit project.
+Signing in only gets the renewable evaluation license.”
+
+Otherwise run `npx --prefer-offline --yes copilotkit@4.25.0 login --json`. Follow the streaming sign-in
 protocol from “Check sign-in” in the start prompt: open the first authentication URL
 once, keep the same process running, and continue only after its completed record.
-Explain that this sign-in obtains the evaluation license, not the local dashboard login.
+When the first authentication URL arrives, send this message in place of the managed
+sign-in message: “Sign in to get the renewable evaluation license. Your local dashboard
+will use CLI approval.”
 On failed or declined sign-in, take the failure path below.
 
-After sign-in completes, continue with
-`npx --prefer-offline --yes copilotkit@4.24.0 onboard read research/gather`.
+After sign-in completes, report it: `npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase sign-in-settled`.
+Then continue with
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read research/gather`, unless research already started.
+If it already started, return to the step you were on. `starter/clone` and
+`credentials/finalize-plan` each have a branch for a recorded local choice.
 Keep the local choice and collected paths in the run's plan and worker context.
 
 ## Failure path
 
 If sign-in fails or is declined, stop before cluster creation.
-Run `npx --prefer-offline --yes copilotkit@4.24.0 onboard read stopped/run-failed`.
+Run `npx --prefer-offline --yes copilotkit@4.25.0 onboard read stopped/run-failed`.

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

@@ -22,12 +22,18 @@ Get approval for the local installation and these connection writes. Apply the e
 protected-path authorization rules to these exact files. Approval for a scaffold alone
 does not 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.25.0 onboard checkpoint --phase awaiting-developer
+```
+
 ## Run the shared installer
 
 From the exact app directory, use the collected model choice:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.24.0 local setup --defer-model --json
+npx --prefer-offline --yes copilotkit@4.25.0 local setup --defer-model --json
 ```
 
 For supplied model access, replace `--defer-model` with `--model-config <private-file>`.
@@ -45,7 +51,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.24.0 local connect --approve-connection --json
+npx --prefer-offline --yes copilotkit@4.25.0 local connect --approve-connection --json
 ```
 
 Read the local `.copilotkit/project.json` for its project ID and slug. Do not run hosted
@@ -65,7 +71,7 @@ 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.24.0 local setup
+npx --prefer-offline --yes copilotkit@4.25.0 local setup
 ```
 
 Do not give it as a `!` line, and do not run it yourself. Its guided model prompt needs a
@@ -74,9 +80,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.24.0 onboard checkpoint --phase awaiting-model-credential`, end your
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard checkpoint --phase awaiting-model-credential`, end your
 turn, and wait. When the developer replies, run
-`npx --prefer-offline --yes copilotkit@4.24.0 local status --json` and read `learning.configuration`.
+`npx --prefer-offline --yes copilotkit@4.25.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
@@ -90,6 +96,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.24.0 onboard read credentials/settle-credentials`.
+Continue with `npx --prefer-offline --yes copilotkit@4.25.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

@@ -16,7 +16,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.24.0 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.
@@ -62,19 +62,19 @@ or frontend, stop onboarding.
 
 Use these rules for every protected-path check in this fallback:
 
-- Run `npx --prefer-offline --yes copilotkit@4.24.0 onboard audit` from the target app directory.
+- Run `npx --prefer-offline --yes copilotkit@4.25.0 onboard audit` from the target app directory.
 - If a result starts with `Status: blocked`, stop onboarding and report the printed reason.
   It proved nothing changed, so do not report a preservation failure.
 - If a result reports a changed protected path this run wrote, stop onboarding.
 - If a result reports a changed env file, this rule replaces the one above, even when this
   run wrote the file. This run asked the developer to place a
   credential there, so take the credential route rather than the external one. Accept it
-  with `npx --prefer-offline --yes copilotkit@4.24.0 onboard protect --accept-credential --path <path>`,
+  with `npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --accept-credential --path <path>`,
   run the audit again, and name it in the closing report. If the command refuses because
   it names a lost variable, stop onboarding.
 - Before any proof subagent runs, a changed path that no Files changed section from this
   run names came from outside the run. Accept it by name with
-  `npx --prefer-offline --yes copilotkit@4.24.0 onboard protect --accept-external --path <path>`, run the
+  `npx --prefer-offline --yes copilotkit@4.25.0 onboard protect --accept-external --path <path>`, run the
   audit again, and name it in the closing report.
 - After a proof subagent runs, a changed path that no Files changed section from this run
   names is unsettled rather than outside the run, because the proof subagent here returns
@@ -133,16 +133,16 @@ that the selected documentation proved an inferred step.
 Record what the proof returned before you complete:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.24.0 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>
 ```
 
-When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.24.0 onboard complete`, carrying the
+When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.25.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.24.0 onboard complete --visual-check <outcome>
-npx --prefer-offline --yes copilotkit@4.24.0 onboard complete --device-check <outcome>
+npx --prefer-offline --yes copilotkit@4.25.0 onboard complete --visual-check <outcome>
+npx --prefer-offline --yes copilotkit@4.25.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

@@ -18,7 +18,7 @@ without exposing secrets.
 Before you spawn the implementation subagent, take the authorized list from the CLI:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.24.0 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
@@ -33,11 +33,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.24.0 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
@@ -49,7 +56,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.24.0 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
@@ -60,7 +67,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.24.0 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
@@ -73,11 +80,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.24.0 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.24.0 onboard read feature/a2ui/proof`.
+`npx --prefer-offline --yes copilotkit@4.25.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.24.0 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.24.0 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
@@ -54,19 +54,27 @@ Show a concise plan that names the existing runtime/provider files, the smallest
 catalog or runtime wiring required, the test command, and a browser proof request that
 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.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.24.0 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.24.0 onboard read feature/a2ui/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/a2ui/implement`.

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

@@ -23,11 +23,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.24.0 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
@@ -40,11 +47,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.24.0 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 A2UI surface, `failed` for an attempted proof that failed,
-and `skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.24.0 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
@@ -59,9 +66,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.24.0 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.24.0 onboard read feature/complete` with the actual browser-proof
+`npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/complete` with the actual browser-proof
 outcome.

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

@@ -10,17 +10,18 @@ run is doing in the developer's words instead.
 Run this before anything else in this prompt:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.24.0 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>
 ```
 
 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. If they name no
-  exact model id, leave out `--model` rather than guess.
-- `--model-family`: your model's family, such as `claude-opus` or `gpt-5`. Give it even
-  without `--model`, and leave out `--model-family` if you do not know it.
-- Never give your product slug as a model or a family.
+- `--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
 
@@ -38,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.24.0 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.24.0 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.
@@ -54,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.24.0 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.
@@ -68,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.24.0 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
@@ -83,26 +84,26 @@ 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.24.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`.
+`npx --prefer-offline --yes copilotkit@4.25.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`.
 Also drive one existing request through the frontend 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.24.0 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.24.0 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.24.0 onboard read feature/a2ui/plan
+npx --prefer-offline --yes copilotkit@4.25.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,7 +19,7 @@ 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.24.0 login --json`: the same single streaming
+yourself with `npx --prefer-offline --yes copilotkit@4.25.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
@@ -75,7 +75,7 @@ starter to satisfy this rule, and do not report the page that shows it.
 Before you spawn the implementation subagent, take the authorized list from the CLI:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.24.0 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
@@ -90,11 +90,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.24.0 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
@@ -106,7 +113,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.24.0 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
@@ -117,7 +124,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.24.0 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
@@ -130,7 +137,7 @@ 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.24.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.25.0 onboard read feature/stop
 ```
 
 ## Values this run writes, and the one credential the developer supplies
@@ -160,6 +167,11 @@ in a report, a command line, or a commit.
 
 If that file already sets `INTELLIGENCE_CHANNEL_NAME` to a different Channel, change
 nothing. Ask the developer which Channel this project serves and wait for their answer.
+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
+```
 
 The only credential the developer supplies is their model provider key, such as
 `OPENAI_API_KEY`, and the run asks for it once as part of plan approval. Never ask for it
@@ -174,4 +186,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.24.0 onboard read feature/channels/proof`.
+`npx --prefer-offline --yes copilotkit@4.25.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.24.0 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.24.0 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.24.0 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.24.0 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.24.0 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.24.0 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.24.0 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.24.0 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.24.0 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