copilotkit 4.22.0 → 4.23.1

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

@@ -20,13 +20,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.22.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -36,7 +36,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.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -66,7 +66,7 @@ status:
   before the capture, the inspection, and any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/blocked-by-plan
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/blocked-by-plan
 ```
 
 - `LEARNING_AVAILABILITY_UNAVAILABLE` means the platform did not resolve the answer. It is
@@ -87,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.22.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -101,50 +101,21 @@ 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.22.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
 ```
 
-Fetch the current official guides before planning:
-https://docs.copilotkit.ai/learning.md
-https://docs.copilotkit.ai/backend/copilot-runtime.md
-https://docs.copilotkit.ai/intelligence/quickstart.md
-https://docs.copilotkit.ai/threads.md
-Use a second retrieval method if needed.
-
-The CLI owns the container. `copilotkit learning containers list --json` reads the ones this
-project already has, and `copilotkit learning containers create --id <id> --name <name>
---json` makes one. So there is no dashboard step and no reason to guess: never invent an id,
-scrape a dashboard, or treat an arbitrary string as a container.
-
-Read the "Assign Threads to Learning Containers" section of that page. The container is
-chosen by `getLearningContainerId` on the `CopilotKitIntelligence` instance, which the
-same page documents; it receives the resolved application user and the run input, and it
-serves web and Channel runs through one API.
-
-Show a concise plan for managed runtime/thread prerequisites, a stable selected container,
-the documented `getLearningContainerId` selector, validation, and a visible assignment
-proof. Ask for approval separately.
-
-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.
-
-After approval, record each approved path before implementation:
+When the inspection proved what this intent needs, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/learning/plan
 ```
 
-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.22.0 onboard read feature/learning/implement`.
+That prompt holds the plan, the developer's approval, and the paths the plan changes.
+Do not write the plan or change project files in this prompt.

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.22.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -71,11 +71,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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard read feature/open-generative-ui/proof`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/open-generative-ui/proof`.

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

@@ -0,0 +1,70 @@
+# Plan Open Generative UI with the developer
+
+The inspection in `feature/open-generative-ui/start` came back and proved what this intent
+needs. This prompt turns it into a plan, asks the developer to approve it, and records the
+protected paths the plan changes. Do not change project files in this prompt.
+
+## Waits and stops
+
+The rules in `feature/open-generative-ui/start` still hold here.
+
+The approval is a wait for the developer. Before you end your turn to wait, report the
+pause:
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 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 arrives, continue from the step that paused. If the developer asks for a
+change, show the changed plan and ask again.
+
+## What this prompt takes from the start
+
+Keep these from `feature/open-generative-ui/start`, and give them to every subagent:
+
+- the protected path list that `onboard protect` printed, and
+- the paths and findings the inspection returned: the runtime route, provider and chat
+  component, agent id, package versions, existing middleware, sandbox and CSP constraints,
+  test and dev commands, and the round trip that `verify` proved.
+
+If you do not hold them, as after `onboard resume` in a new session, get them back before
+you plan. Run `onboard protect` again from the target app directory: on the same run it
+prints the baseline the run already holds.
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
+```
+
+Then have one read-only subagent repeat the inspection for the findings above, and wait
+for it. It changes no files.
+
+## Plan the change
+
+Do not sign in, select an Intelligence project, create credentials, change the existing
+agent, or swap out the chat surface. Open Generative UI is an OSS runtime feature.
+
+Fetch the current official guide before planning:
+https://docs.copilotkit.ai/generative-ui/open-generative-ui.md
+Retry through a second retrieval method if needed. Setup is the documented
+`openGenerativeUI` option on the runtime, which makes `/info` report
+`openGenerativeUIEnabled`. The middleware is what parses tool-call arguments afterwards.
+Show a small plan covering that runtime option, the existing provider's renderer path,
+likely CSP/sandbox implications, tests, and a user-visible generated UI proof. Ask for approval as its own question.
+
+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.
+
+After approval, record each approved path before implementation:
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+```
+
+If an approved path changed after capture and no implementation step has run, add
+`--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
+authorize a path the approved plan did not list.
+
+Then run `npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/open-generative-ui/implement`.

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.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -34,11 +34,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.22.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.23.1 onboard audit`.
 Continue only when it starts with `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -53,9 +53,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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/complete` with the outcome actually
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/complete` with the outcome actually
 observed.

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

@@ -19,13 +19,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.22.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -35,7 +35,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.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -49,7 +49,7 @@ 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.22.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -59,46 +59,27 @@ 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.22.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
 ```
 
-Do not sign in, select an Intelligence project, create credentials, change the existing
-agent, or swap out the chat surface. Open Generative UI is an OSS runtime feature.
-
-Fetch the current official guide before planning:
-https://docs.copilotkit.ai/generative-ui/open-generative-ui.md
-Retry through a second retrieval method if needed. Setup is the documented
-`openGenerativeUI` option on the runtime, which makes `/info` report
-`openGenerativeUIEnabled`; the middleware is what parses tool-call arguments afterwards.
-Show a small plan covering that runtime option, the existing provider's renderer path,
-likely CSP/sandbox implications, tests, and a user-visible generated UI proof. Ask for approval separately.
-
-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.
-
-After approval, record each approved path before implementation:
+When the inspection proved what this intent needs, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/open-generative-ui/plan
 ```
 
-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.22.0 onboard read feature/open-generative-ui/implement`.
+That prompt holds the plan, the developer's approval, and the paths the plan changes.
+Do not write the plan or change project files in this prompt.

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.22.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -79,11 +79,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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard read feature/realtime-sync/proof`.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/realtime-sync/proof`.

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

@@ -0,0 +1,75 @@
+# Plan realtime thread sync with the developer
+
+The inspection in `feature/realtime-sync/start` came back and proved what this intent
+needs. This prompt turns it into a plan, asks the developer to approve it, and records the
+protected paths the plan changes. Do not change project files in this prompt.
+
+## Waits and stops
+
+The rules in `feature/realtime-sync/start` still hold here.
+
+The approval is a wait for the developer. Before you end your turn to wait, report the
+pause:
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 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 arrives, continue from the step that paused. If the developer asks for a
+change, show the changed plan and ask again.
+
+## What this prompt takes from the start
+
+Keep these from `feature/realtime-sync/start`, and give them to every subagent:
+
+- the protected path list that `onboard protect` printed, and
+- the paths and findings the inspection returned: the runtime, provider and chat, agent
+  id, authenticated stable user identity, thread routes, existing Intelligence
+  configuration (presence only), websocket configuration, test and dev commands, and the
+  round trip.
+
+If you do not hold them, as after `onboard resume` in a new session, get them back before
+you plan. Run `onboard protect` again from the target app directory: on the same run it
+prints the baseline the run already holds.
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
+```
+
+Then have one read-only subagent repeat the inspection for the findings above, and wait
+for it. It changes no files.
+
+## Plan the change
+
+Fetch the current official guides before planning:
+https://docs.copilotkit.ai/intelligence/quickstart.md
+https://docs.copilotkit.ai/auth.md
+https://docs.copilotkit.ai/intelligence/threads-explained.md
+https://docs.copilotkit.ai/reference/hooks/useThreads.md
+Retry unavailable pages a second way. Reuse a proven Intelligence project where present. Do
+not sign in or select/create one until the developer approves the plan.
+
+The plan must name the documented managed runtime/thread wiring, identity and catch-all
+thread routes, the existing or documented client realtime connection, tests, and a proof in
+two browser contexts. For self-hosted Intelligence, configure `apiUrl` and `wsUrl` together
+from explicit developer-owned values. Never derive one from the other. The client prepends
+`/api` itself, so an `apiUrl` that already ends in `/api` produces `/api/api/...`. Hosted setup may not
+need a `wsUrl`. Ask for approval as its own question.
+
+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.
+
+After approval, record each approved path before implementation:
+
+```text
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+```
+
+If an approved path changed after capture and no implementation step has run, add
+`--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
+authorize a path the approved plan did not list.
+
+Then run `npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/realtime-sync/implement`.

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.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -36,11 +36,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.22.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.23.1 onboard audit`.
 Continue only when it starts with `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -55,8 +55,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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/complete` with the actual outcome.
+`npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/complete` with the actual outcome.

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

@@ -20,13 +20,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.22.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.23.1 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -36,7 +36,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.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -50,7 +50,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.22.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.23.1 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -65,44 +65,21 @@ 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.22.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.23.1 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.22.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/stop
 ```
 
-Fetch the current official guides before planning:
-https://docs.copilotkit.ai/intelligence/quickstart.md
-https://docs.copilotkit.ai/auth.md
-https://docs.copilotkit.ai/intelligence/threads-explained.md
-https://docs.copilotkit.ai/reference/hooks/useThreads.md
-Retry unavailable pages a second way. Reuse a proven Intelligence project where present; do
-not sign in or select/create one until the developer approves the plan.
-
-The plan must name the documented managed runtime/thread wiring, identity and catch-all
-thread routes, the existing or documented client realtime connection, tests, and a proof in
-two browser contexts. For self-hosted Intelligence, configure `apiUrl` and `wsUrl` together
-from explicit developer-owned values; never derive one from the other. The client prepends
-`/api` itself, so an `apiUrl` that already ends in `/api` produces `/api/api/...`. Hosted setup may not
-need a `wsUrl`. Ask for approval separately.
-
-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.
-
-After approval, record each approved path before implementation:
+When the inspection proved what this intent needs, read the next prompt now, in this turn:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.23.1 onboard read feature/realtime-sync/plan
 ```
 
-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.22.0 onboard read feature/realtime-sync/implement`.
+That prompt holds the plan, the developer's approval, and the paths the plan changes.
+Do not write the plan or change project files in this prompt.