copilotkit 4.17.0 → 4.19.0

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

@@ -12,12 +12,12 @@ resolve, a container id that never resolves, an audit that still fails or is blo
 cannot be cleared, validation that cannot pass, and an intent that needs a prerequisite the
 app does not have. Each one stops onboarding for a developer who has already approved a
 plan. Name the exact command, id, and error code that stopped you: a report that names only
-the step cannot be acted on. Send one short report before you stop. Run the friction
-command without another developer question. Do not ask the developer about telemetry: the
-command applies the setting they already have.
+the step cannot be acted on. 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.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.
@@ -36,6 +36,11 @@ scoped fix, and sends the report itself when no fix is approved.
 
 After the project is selected, settle the container from the terminal.
 
+The `learning containers` commands and `project select` need a CLI sign-in. A project API
+key in `.env` does not replace it, even when the app already authenticates with that key:
+the key serves the app's runtime only. So `AUTH_FAILED` from these commands means sign in
+with `login --json`, not look for another credential.
+
 Whichever of the two reads below runs first also answers the entitlement question, because
 a read carries the same availability gate as the create. Read `status` and `error.code`
 from its payload. Route on the code rather than on the exit status.
@@ -44,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.17.0 onboard read feature/blocked-by-plan
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/blocked-by-plan
 ```
 
 `LEARNING_AVAILABILITY_UNAVAILABLE` means the platform did not resolve the answer. It is
@@ -58,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.17.0 learning containers get <id> --json
+npx --prefer-offline --yes copilotkit@4.19.0 learning containers get <id> --json
 ```
 
 One call answers it, and no list is needed.
@@ -66,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.17.0 learning containers list --json
+npx --prefer-offline --yes copilotkit@4.19.0 learning containers list --json
 ```
 
 One call returns at most 500 containers. When `nextCursor` in the result is not null, read
@@ -77,7 +82,7 @@ second container for work the first one already covers.
 Report what the read found before asking anyone anything:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase container-surveyed
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase container-surveyed
 ```
 
 Everything after this waits on a person, so a run that stops past this point stopped on a
@@ -98,7 +103,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.17.0 learning containers default-id --json
+npx --prefer-offline --yes copilotkit@4.19.0 learning containers default-id --json
 ```
 
 It derives the project-scoped id from the selected project's slug, reads the local project
@@ -112,7 +117,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.17.0 learning containers create --id <id> --name <name> --json
+npx --prefer-offline --yes copilotkit@4.19.0 learning containers create --id <id> --name <name> --json
 ```
 
 An id already in use answers `LEARNING_CONTAINER_ALREADY_EXISTS`. That is a container to
@@ -127,7 +132,7 @@ or a guessed id.
 Then report that the container is settled, before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard checkpoint --phase container-settled
+npx --prefer-offline --yes copilotkit@4.19.0 onboard checkpoint --phase container-settled
 ```
 
 Everything above happens between two prompts, so a run that stopped on a developer who could
@@ -148,13 +153,13 @@ non-zero on an app that is working. Pass what `identifyUser` reads with a repeat
 It is not a defect to repair.
 
 Run focused tests and
-`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 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.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
@@ -173,7 +178,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
@@ -185,7 +190,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
@@ -196,7 +201,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
@@ -210,17 +215,17 @@ 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.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/learning/proof`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/learning/proof`.

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

@@ -7,7 +7,7 @@ Container. Confirm the thread remains associated with the expected user.
 One command decides it:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --expect-learning-container <id> --json
+npx --prefer-offline --yes copilotkit@4.19.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --expect-learning-container <id> --json
 ```
 
 It reads the thread back from the platform, so it answers for any runtime mount, and it
@@ -40,7 +40,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
@@ -52,24 +52,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 a proved Container assignment, `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
@@ -84,9 +84,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/learning/start.md

@@ -4,28 +4,51 @@ Treat Learning as a managed Intelligence feature that assigns real threads to a
 Learning Container. Orchestrate with separate read-only, implementation, and proof
 subagents. Work only inside the target project and preserve its existing agent and chat.
 
-## If you stop in this phase
+## Waits, stops, and subagents
 
-Name the exact command, code, or check that stopped you, then 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.
+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.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.
 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. A run that stopped cannot separate one papercut's cost from the cost of
-the whole run, so the estimate is optional on a stop report and only there. 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.
+--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.
 
-A refusal by the platform is the one exception. It reaches `feature/blocked-by-plan`, which
-reports the ending by itself and says to file nothing further. A stop that routes to
-`feature/stop` also sends no report here: that prompt first asks the developer about one
-scoped fix, and sends the report itself when no fix is approved.
+A refusal by the platform also sends no report here. It reaches `feature/blocked-by-plan`, which
+reports the ending by itself and says to file nothing further.
 
 Ask the platform whether this organization may use Learning before doing any work. The
 read carries the same availability gate as the create, so it answers the entitlement
@@ -43,7 +66,7 @@ status:
   before the capture, the inspection, and any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.17.0 onboard read feature/blocked-by-plan
+npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/blocked-by-plan
 ```
 
 - `LEARNING_AVAILABILITY_UNAVAILABLE` means the platform did not resolve the answer. It is
@@ -64,7 +87,7 @@ again: it has no answer, so it carries the question forward rather than ending o
 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
@@ -78,7 +101,7 @@ test/dev commands. Prove the current 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
@@ -88,7 +111,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:
@@ -120,7 +143,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
@@ -130,7 +153,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/learning/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/learning/implement`.

package/onboarding/prompts/feature/open-generative-ui/implement.md

@@ -16,7 +16,7 @@ validation results without secrets.
 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
@@ -35,7 +35,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
@@ -47,7 +47,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
@@ -58,7 +58,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
@@ -71,17 +71,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/open-generative-ui/proof`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/open-generative-ui/proof`.

package/onboarding/prompts/feature/open-generative-ui/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 a proved generated UI, `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`.
+and `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 outcome actually
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/complete` with the outcome actually
 observed.

package/onboarding/prompts/feature/open-generative-ui/start.md

@@ -3,10 +3,53 @@
 Treat this as a focused OSS enhancement. Orchestrate the work with separate read-only,
 implementation, and proof subagents, all restricted to the target project directory.
 
+## 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, have a research subagent identify the current CopilotKit runtime route,
 provider/chat component, agent id, package versions, existing middleware, sandbox/CSP
 constraints, and normal test/dev commands. Prove the existing app first 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 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.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 sign in, select an Intelligence project, create credentials, change the existing
@@ -54,7 +97,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
@@ -64,7 +107,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/open-generative-ui/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/open-generative-ui/implement`.

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

@@ -17,14 +17,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 tests and
-`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 and 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
@@ -43,7 +43,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
@@ -55,7 +55,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
@@ -66,7 +66,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
@@ -79,17 +79,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/realtime-sync/proof`.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/realtime-sync/proof`.

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

@@ -23,7 +23,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
@@ -35,23 +35,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 two-client sync, `failed` for an attempted proof that failed,
-and `skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.17.0 onboard audit`.
+and `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
@@ -66,8 +66,8 @@ the path and the change the audit reports. Run the audit again after each accept
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.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 outcome.
+`npx --prefer-offline --yes copilotkit@4.19.0 onboard read feature/complete` with the actual outcome.