copilotkit 4.10.1 → 4.11.0

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

@@ -15,7 +15,7 @@ Run focused type/test checks and start the app. Record the changed files and val
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard audit
+npx --yes copilotkit@4.11.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
@@ -26,7 +26,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.11.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -35,24 +35,24 @@ or its report does not settle who changed it, ask the developer to allow the unp
 change. Only after they agree, record their answer:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.11.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Run the audit again after each accepted or authorized change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.1 onboard read feature/chat-suggestions/proof`.
+`npx --yes copilotkit@4.11.0 onboard read feature/chat-suggestions/proof`.

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

@@ -12,23 +12,23 @@ project-owned services running.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.11.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for a proved sent suggestion, `failed` for an attempted proof that failed,
-and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.10.1 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.11.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
@@ -43,9 +43,9 @@ Run the audit again after each accepted or authorized change.
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.1 onboard read feature/complete` with the real browser-proof
+`npx --yes copilotkit@4.11.0 onboard read feature/complete` with the real browser-proof
 outcome.

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

@@ -6,7 +6,7 @@ implementation, and proof to separate subagents and keep all work inside the tar
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect
+npx --yes copilotkit@4.11.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -15,7 +15,7 @@ approved authorization before implementation.
 
 Before edits, identify the current CopilotKit provider, chat component, message lifecycle,
 agent id, package version, and test/dev commands. Prove the existing OSS round trip with
-`/info`, `npx --yes copilotkit@4.10.1 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`/info`, `npx --yes copilotkit@4.11.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and one real frontend request when browser control is available. If there is no proven
 existing CopilotKit chat, leave files unchanged and direct the developer to generic
 onboarding first.
@@ -23,7 +23,7 @@ onboarding first.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -33,7 +33,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 Do not run login, provision Intelligence, request a credential, replace the agent, or alter
@@ -53,7 +53,7 @@ with one sentence explaining why. Write `None` when it needs none.
 After approval, record each approved path before implementation:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.11.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 +63,7 @@ authorize a path the approved plan did not list.
 Then report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.10.1 onboard read feature/chat-suggestions/implement`.
+Then run `npx --yes copilotkit@4.11.0 onboard read feature/chat-suggestions/implement`.

package/onboarding/prompts/feature/complete.md

@@ -3,7 +3,7 @@
 Use the outcome the proof step observed. Run:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>
+npx --yes copilotkit@4.11.0 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>
 ```
 
 Use `performed` only when browser control drove the real user-visible surface. Use

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

@@ -10,7 +10,7 @@ After the project is selected, settle the container from the terminal.
 When the plan or the repository already names an id, ask about that one id and nothing else:
 
 ```text
-npx --yes copilotkit@4.10.1 learning containers get <id> --json
+npx --yes copilotkit@4.11.0 learning containers get <id> --json
 ```
 
 One call answers it, and no list is needed.
@@ -18,7 +18,7 @@ One call answers it, and no list is needed.
 When no id is in hand, survey what the project holds:
 
 ```text
-npx --yes copilotkit@4.10.1 learning containers list --json
+npx --yes copilotkit@4.11.0 learning containers list --json
 ```
 
 One call returns at most 500 containers. When `nextCursor` in the result is not null, read
@@ -29,7 +29,7 @@ second container for work the first one already covers.
 Report what the read found before asking anyone anything:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase container-surveyed
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase container-surveyed
 ```
 
 Everything after this waits on a person, so a run that stops past this point stopped on a
@@ -50,7 +50,7 @@ user, so the callback can return a different id per tier or per customer.
 Use a descriptive lowercase hyphenated id of 1-64 characters:
 
 ```text
-npx --yes copilotkit@4.10.1 learning containers create --id <id> --name <name> --json
+npx --yes copilotkit@4.11.0 learning containers create --id <id> --name <name> --json
 ```
 
 An id already in use answers `LEARNING_CONTAINER_ALREADY_EXISTS`. That is a container to
@@ -65,7 +65,7 @@ or a guessed id.
 Then report that the container is settled, before any edit:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase container-settled
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase container-settled
 ```
 
 Everything above happens between two prompts, so a run that stopped on a developer who could
@@ -86,13 +86,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 --yes copilotkit@4.10.1 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --yes copilotkit@4.11.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 Repair changed-file failures and record secret-safe evidence.
 
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard audit
+npx --yes copilotkit@4.11.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
@@ -103,7 +103,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.11.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -112,24 +112,24 @@ or its report does not settle who changed it, ask the developer to allow the unp
 change. Only after they agree, record their answer:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.11.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Run the audit again after each accepted or authorized change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.1 onboard read feature/learning/proof`.
+`npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.1 verify --expect-runtime intelligence --round-trip --agent <agent-id> --expect-learning-container <id> --json
+npx --yes copilotkit@4.11.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
@@ -31,24 +31,24 @@ takes its container before its first agent run. So the container starts empty on
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.1 onboard audit`. Continue only when it starts with
+`npx --yes copilotkit@4.11.0 onboard audit`. Continue only when it starts with
 `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -63,9 +63,9 @@ Run the audit again after each accepted or authorized change.
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.1 onboard read feature/complete` with the actual surface
+`npx --yes copilotkit@4.11.0 onboard read feature/complete` with the actual surface
 outcome.

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

@@ -7,7 +7,7 @@ subagents. Work only inside the target project and preserve its existing agent a
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect
+npx --yes copilotkit@4.11.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -23,7 +23,7 @@ onboarding.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -33,7 +33,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 Fetch the current official guides before planning:
@@ -63,7 +63,7 @@ with one sentence explaining why. Write `None` when it needs none.
 After approval, record each approved path before implementation:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.11.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
@@ -73,7 +73,7 @@ authorize a path the approved plan did not list.
 Then report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.10.1 onboard read feature/learning/implement`.
+Then run `npx --yes copilotkit@4.11.0 onboard read feature/learning/implement`.

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

@@ -16,7 +16,7 @@ validation results without secrets.
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard audit
+npx --yes copilotkit@4.11.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
@@ -27,7 +27,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.11.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -36,24 +36,24 @@ or its report does not settle who changed it, ask the developer to allow the unp
 change. Only after they agree, record their answer:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.11.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Run the audit again after each accepted or authorized change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.1 onboard read feature/open-generative-ui/proof`.
+`npx --yes copilotkit@4.11.0 onboard read feature/open-generative-ui/proof`.

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

@@ -13,23 +13,23 @@ the missing visual proof honestly.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.1 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.11.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
@@ -44,9 +44,9 @@ Run the audit again after each accepted or authorized change.
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.1 onboard read feature/complete` with the outcome actually
+`npx --yes copilotkit@4.11.0 onboard read feature/complete` with the outcome actually
 observed.

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

@@ -6,7 +6,7 @@ implementation, and proof subagents, all restricted to the target project direct
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect
+npx --yes copilotkit@4.11.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -16,7 +16,7 @@ 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 --yes copilotkit@4.10.1 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --yes copilotkit@4.11.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and a real frontend request when browser control is available. If the app is not an existing
 OSS CopilotKit app with a proven round trip, change nothing and direct the developer to the
 generic onboarding path first.
@@ -24,7 +24,7 @@ generic onboarding path first.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -34,7 +34,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 Do not sign in, select an Intelligence project, create credentials, change the existing
@@ -54,7 +54,7 @@ with one sentence explaining why. Write `None` when it needs none.
 After approval, record each approved path before implementation:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.11.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 +64,7 @@ authorize a path the approved plan did not list.
 Then report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.10.1 onboard read feature/open-generative-ui/implement`.
+Then run `npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.1 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --yes copilotkit@4.11.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 Repair changed-file failures and record changed paths and secret-safe validation
 evidence.
 
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard audit
+npx --yes copilotkit@4.11.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
@@ -35,7 +35,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.11.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -44,24 +44,24 @@ or its report does not settle who changed it, ask the developer to allow the unp
 change. Only after they agree, record their answer:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.11.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Run the audit again after each accepted or authorized change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.1 onboard read feature/realtime-sync/proof`.
+`npx --yes copilotkit@4.11.0 onboard read feature/realtime-sync/proof`.

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

@@ -14,23 +14,23 @@ the missing proof rather than claiming realtime works.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.1 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.11.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
@@ -45,8 +45,8 @@ Run the audit again after each accepted or authorized change.
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.1 onboard read feature/complete` with the actual outcome.
+`npx --yes copilotkit@4.11.0 onboard read feature/complete` with the actual outcome.

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

@@ -7,7 +7,7 @@ two-context proof to subagents within the target project.
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect
+npx --yes copilotkit@4.11.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -23,7 +23,7 @@ unchanged and direct the developer to generic onboarding first.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -33,7 +33,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 Fetch the current official guides before planning:
@@ -57,7 +57,7 @@ with one sentence explaining why. Write `None` when it needs none.
 After approval, record each approved path before implementation:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.11.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
@@ -67,7 +67,7 @@ authorize a path the approved plan did not list.
 Then report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.10.1 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.10.1 onboard read feature/realtime-sync/implement`.
+Then run `npx --yes copilotkit@4.11.0 onboard read feature/realtime-sync/implement`.