copilotkit 4.17.0 → 4.19.0

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

@@ -4,10 +4,53 @@ 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.
 
+## Waits, stops, and subagents
+
+A run that starts here has not read these rules yet, so they come first. They cover this
+prompt and every later one.
+
+Spawning a subagent returns almost at once. That return is the dispatch succeeding, not the
+work finishing: the result reaches you as a notification, or with the dispatch itself where
+your harness works that way. Do the work that does not depend on the result, then end your
+turn and wait for the result. That wait is a pause. Do not sleep or poll.
+
+A subagent that returns no usable result failed in your harness, not in this graph. Every
+assignment here is work you can do yourself, slower, so run that assignment yourself and
+carry on. Keep a read-only assignment read-only. If no subagent works at all, report it
+once:
+
+```text
+npx --prefer-offline --yes copilotkit@4.19.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.19.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.
+When the answer or the result arrives, continue from the step that paused.
+
+If you stop this run, send one short report before you stop. The friction command follows
+the telemetry setting the developer already chose, so it needs no separate question.
+
+```text
+npx --prefer-offline --yes copilotkit@4.19.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+```
+
+`--message` takes one or two sentences: the step you stopped at and what stopped it.
+Pick the category that fits from docs-missing, docs-wrong, docs-sequential, cli-gap,
+sdk-gap, environment, port-collision, credential, validation-loop, and other. Leave
+--cost-seconds off. Send no secrets, source code, logs, or command output. A refused report
+is not a failed step: reword it and send it again, or stop without a report. A stop that
+routes to `feature/stop` sends no report here: that prompt first asks the developer about
+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.17.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.19.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -22,7 +65,7 @@ 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.17.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -32,7 +75,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/stop
 ```
 
 Fetch the current official guides before planning:
@@ -58,7 +101,7 @@ one.
 After approval, record each approved path before implementation:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.19.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
@@ -68,7 +111,7 @@ authorize a path the approved plan did not list.
 Then report the plan this run is about to implement:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase plan-written
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/realtime-sync/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/realtime-sync/implement`.

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.17.0 login --json` and follow its single streaming session. Then
+`npx --prefer-offline --yes copilotkit@4.19.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
@@ -20,14 +20,14 @@ non-zero on an app that is working. Pass what `identifyUser` reads with a repeat
 It is not a defect to repair.
 
 Run focused type/test commands, then start the app and run
-`npx --prefer-offline --yes copilotkit@4.17.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.19.0 onboard audit
 ```
 
 From its result, copy the paths under `Authorized to modify:`. A passed or failed audit with
@@ -46,7 +46,7 @@ still go on the record. Name the file and why the work needs it, then end your t
 for the developer's answer. If they allow it, record their answer before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.19.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 +58,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.19.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -69,7 +69,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.17.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.19.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -82,17 +82,17 @@ 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.17.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase build-validated
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase build-validated
 ```
 
 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.17.0 onboard read feature/rich-threads/proof`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/rich-threads/proof`.

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

@@ -22,7 +22,7 @@ still go on the record. Name the file and why the fix needs it, then end your tu
 for the developer's answer. If they allow it, record their answer before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.19.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,24 +34,24 @@ route below.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard audit`. Continue only when it starts with
+`npx --prefer-offline --yes copilotkit@4.19.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
@@ -66,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.17.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/complete` with the actual browser
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/complete` with the actual browser
 outcome.

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

@@ -4,10 +4,53 @@ 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.
 
+## Waits, stops, and subagents
+
+A run that starts here has not read these rules yet, so they come first. They cover this
+prompt and every later one.
+
+Spawning a subagent returns almost at once. That return is the dispatch succeeding, not the
+work finishing: the result reaches you as a notification, or with the dispatch itself where
+your harness works that way. Do the work that does not depend on the result, then end your
+turn and wait for the result. That wait is a pause. Do not sleep or poll.
+
+A subagent that returns no usable result failed in your harness, not in this graph. Every
+assignment here is work you can do yourself, slower, so run that assignment yourself and
+carry on. Keep a read-only assignment read-only. If no subagent works at all, report it
+once:
+
+```text
+npx --prefer-offline --yes copilotkit@4.19.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.19.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.
+When the answer or the result arrives, continue from the step that paused.
+
+If you stop this run, send one short report before you stop. The friction command follows
+the telemetry setting the developer already chose, so it needs no separate question.
+
+```text
+npx --prefer-offline --yes copilotkit@4.19.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+```
+
+`--message` takes one or two sentences: the step you stopped at and what stopped it.
+Pick the category that fits from docs-missing, docs-wrong, docs-sequential, cli-gap,
+sdk-gap, environment, port-collision, credential, validation-loop, and other. Leave
+--cost-seconds off. Send no secrets, source code, logs, or command output. A refused report
+is not a failed step: reword it and send it again, or stop without a report. A stop that
+routes to `feature/stop` sends no report here: that prompt first asks the developer about
+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.17.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.19.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -22,7 +65,7 @@ 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.17.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -32,7 +75,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/stop
 ```
 
 Fetch the current official guides before planning:
@@ -60,7 +103,7 @@ one.
 After approval, record each approved path before implementation:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.19.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
@@ -70,7 +113,7 @@ authorize a path the approved plan did not list.
 Then report the plan this run is about to implement:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase plan-written
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/rich-threads/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/rich-threads/implement`.

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.17.0 onboard start --run <new-12-character-id>
+npx --prefer-offline --yes copilotkit@4.19.0 onboard start --run <new-12-character-id>
 ```
 
 Do not read a generic onboarding node from this run. A feature run and a generic run are
@@ -48,7 +48,7 @@ put to them, stop here and send the report below.
 If they approve it, make that one fix and nothing else. Then come back into this run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard resume --message "<approval>"
+npx --prefer-offline --yes copilotkit@4.19.0 onboard resume --message "<approval>"
 ```
 
 Put the developer's approval in `--message`, in one or two sentences: the fix they
@@ -65,11 +65,11 @@ said and stop.
 
 ## If no fix is approved
 
-Send one short report. Run the friction command without another developer question. Do not
-ask the developer about telemetry: the command applies the setting they already have.
+Send one short report. The friction command follows the telemetry setting the developer
+already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.19.0 onboard audit
 ```
 
 From its result, copy the paths under `Authorized to modify:`. A passed or failed audit with
@@ -33,7 +33,7 @@ still go on the record. Name the file and why the work needs it, then end your t
 for the developer's answer. If they allow it, record their answer before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.19.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 +45,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.19.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -56,7 +56,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.17.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.19.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -69,17 +69,17 @@ 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.17.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase build-validated
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase build-validated
 ```
 
 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.17.0 onboard read feature/voice/proof`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/voice/proof`.

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

@@ -21,7 +21,7 @@ still go on the record. Name the file and why the fix needs it, then end your tu
 for the developer's answer. If they allow it, record their answer before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.19.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,23 +33,23 @@ route below.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.19.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.17.0 onboard audit`.
+`skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.19.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
@@ -64,9 +64,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.17.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/complete` with the actual surface
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/complete` with the actual surface
 outcome.

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

@@ -3,10 +3,53 @@
 Treat voice as an OSS enhancement to an existing CopilotKit chat. Orchestrate with separate
 read-only, implementation, and proof subagents, each restricted to the target project.
 
+## Waits, stops, and subagents
+
+A run that starts here has not read these rules yet, so they come first. They cover this
+prompt and every later one.
+
+Spawning a subagent returns almost at once. That return is the dispatch succeeding, not the
+work finishing: the result reaches you as a notification, or with the dispatch itself where
+your harness works that way. Do the work that does not depend on the result, then end your
+turn and wait for the result. That wait is a pause. Do not sleep or poll.
+
+A subagent that returns no usable result failed in your harness, not in this graph. Every
+assignment here is work you can do yourself, slower, so run that assignment yourself and
+carry on. Keep a read-only assignment read-only. If no subagent works at all, report it
+once:
+
+```text
+npx --prefer-offline --yes copilotkit@4.19.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.19.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.
+When the answer or the result arrives, continue from the step that paused.
+
+If you stop this run, send one short report before you stop. The friction command follows
+the telemetry setting the developer already chose, so it needs no separate question.
+
+```text
+npx --prefer-offline --yes copilotkit@4.19.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+```
+
+`--message` takes one or two sentences: the step you stopped at and what stopped it.
+Pick the category that fits from docs-missing, docs-wrong, docs-sequential, cli-gap,
+sdk-gap, environment, port-collision, credential, validation-loop, and other. Leave
+--cost-seconds off. Send no secrets, source code, logs, or command output. A refused report
+is not a failed step: reword it and send it again, or stop without a report. A stop that
+routes to `feature/stop` sends no report here: that prompt first asks the developer about
+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.17.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.19.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -16,13 +59,13 @@ approved authorization before implementation.
 Before edits, inspect the runtime route, CopilotKit provider/chat composer, current agent,
 existing provider credential variable names (presence only), package versions, browser
 permissions approach, and test/dev commands. Prove the existing OSS baseline with `/info`,
-`npx --prefer-offline --yes copilotkit@4.17.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --prefer-offline --yes copilotkit@4.19.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and a real UI request when a browser is available.
 
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -32,7 +75,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/stop
 ```
 
 Do not run login, select Intelligence, create a credential, read a credential value, or
@@ -53,7 +96,7 @@ one.
 After approval, record each approved path before implementation:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.19.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
@@ -63,7 +106,7 @@ authorize a path the approved plan did not list.
 Then report the plan this run is about to implement:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase plan-written
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/voice/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/voice/implement`.

package/onboarding/prompts/framework/ag2.md

@@ -31,7 +31,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the A2UI documentation gap.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/agno.md

@@ -34,7 +34,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, the documented dependencies and adapter, and the context documentation gap.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

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

@@ -29,7 +29,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

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

@@ -34,7 +34,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

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

@@ -37,7 +37,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, and the context limit.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/crewai-flows.md

@@ -62,7 +62,7 @@ Record the selected framework, project-defined provider and model, the credentia
 variable names the repository proves or the developer named, these URLs, and the adapter.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/deep-agents.md

@@ -33,7 +33,7 @@ Record the selected framework, language, vendor, model, required credential vari
 names, these URLs, and each documentation gap.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/google-adk.md

@@ -30,7 +30,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/langgraph-fastapi.md

@@ -25,7 +25,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --prefer-offline --yes copilotkit@4.17.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read unsupported/no-validated-path`.