copilotkit 4.10.0 → 4.10.1

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.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.10.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 --yes copilotkit@4.10.0 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.10.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
@@ -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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.0 onboard read feature/complete` with the outcome actually
+`npx --yes copilotkit@4.10.1 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.0 onboard protect
+npx --yes copilotkit@4.10.1 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.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --yes copilotkit@4.10.1 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.0 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 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.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.10.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
@@ -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.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.10.0 onboard read feature/open-generative-ui/implement`.
+Then run `npx --yes copilotkit@4.10.1 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.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --yes copilotkit@4.10.1 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.0 onboard audit
+npx --yes copilotkit@4.10.1 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.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.10.1 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.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/realtime-sync/proof`.
+`npx --yes copilotkit@4.10.1 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.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.10.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 --yes copilotkit@4.10.0 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.10.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
@@ -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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.0 onboard read feature/complete` with the actual outcome.
+`npx --yes copilotkit@4.10.1 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.0 onboard protect
+npx --yes copilotkit@4.10.1 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.0 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 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.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.10.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
@@ -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.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.10.0 onboard read feature/realtime-sync/implement`.
+Then run `npx --yes copilotkit@4.10.1 onboard read feature/realtime-sync/implement`.

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

@@ -2,7 +2,7 @@
 
 Delegate implementation to one subagent with the approved plan and fetched official guides.
 If repository evidence does not prove an existing valid Intelligence selection, run
-`npx --yes copilotkit@4.10.0 login --json` and follow its single streaming session. Then
+`npx --yes copilotkit@4.10.1 login --json` and follow its single streaming session. Then
 list projects, show the developer the current/recent choices, and select or create one only
 after they choose. Require the secret-safe selection summary to confirm the project file,
 environment file, and key provisioning; never display a key. If existing configuration is
@@ -20,14 +20,14 @@ non-zero on an app that is working. Pass what `identifyUser` reads with a repeat
 It is not a defect to repair.
 
 Run focused type/test commands, then start the app and run
-`npx --yes copilotkit@4.10.0 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --yes copilotkit@4.10.1 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 Repair changed-file failures before continuing. Record changed paths and secret-safe
 validation evidence.
 
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard audit
+npx --yes copilotkit@4.10.1 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
@@ -38,7 +38,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.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.10.1 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -47,24 +47,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.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/rich-threads/proof`.
+`npx --yes copilotkit@4.10.1 onboard read feature/rich-threads/proof`.

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

@@ -13,24 +13,24 @@ running.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.10.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for proved persistence and reopen, `failed` for an attempted proof that
 failed, and `skipped` when the proof could not run. Then run
-`npx --yes copilotkit@4.10.0 onboard audit`. Continue only when it starts with
+`npx --yes copilotkit@4.10.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
@@ -45,9 +45,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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.0 onboard read feature/complete` with the actual browser
+`npx --yes copilotkit@4.10.1 onboard read feature/complete` with the actual browser
 outcome.

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

@@ -7,7 +7,7 @@ implementation, and proof to separate subagents within the target project.
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard protect
+npx --yes copilotkit@4.10.1 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -23,7 +23,7 @@ an existing CopilotKit app, leave it unchanged and direct the developer to gener
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 Fetch the current official guides before planning:
@@ -59,7 +59,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.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.10.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
@@ -69,7 +69,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.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.10.0 onboard read feature/rich-threads/implement`.
+Then run `npx --yes copilotkit@4.10.1 onboard read feature/rich-threads/implement`.

package/onboarding/prompts/feature/stop.md

@@ -8,13 +8,19 @@ extends, a documentation page that would not load, a prerequisite the app does n
 validation that would not pass, or a proof that could not be driven. Do not say the feature
 works when this run could not prove it.
 
-If the app has no proven CopilotKit baseline, say so plainly and point the developer at
-generic onboarding, which builds the app this intent needs. Give it a run id of its own:
+For `add-channels`, Slack or Teams is the UI; a CopilotKit web app is not required.
+Do not send this intent to generic onboarding because the project has no web app.
+Name the missing Channel prerequisite or failed mention proof and the next step needed
+to resolve it. Keep the existing agent and runtime, and report friction below.
+
+For other intents, if the app has no proven CopilotKit baseline, say so plainly and point
+the developer at generic onboarding, which builds the app this intent needs. Give it a run
+id of its own:
 a `start` with no `--run` reprints the id this stopped run already holds, and one id
 covering both reads as one run that did two different things.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard start --run <new-12-character-id>
+npx --yes copilotkit@4.10.1 onboard start --run <new-12-character-id>
 ```
 
 Do not read a generic onboarding node from this run. A feature run and a generic run are
@@ -29,7 +35,7 @@ Send one short report. Run the friction command without another developer questi
 CLI telemetry gate decides whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.

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

@@ -14,7 +14,7 @@ voice proof. Record changed paths and validation results.
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard audit
+npx --yes copilotkit@4.10.1 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
@@ -25,7 +25,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.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.10.1 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -34,24 +34,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.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/voice/proof`.
+`npx --yes copilotkit@4.10.1 onboard read feature/voice/proof`.

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

@@ -13,23 +13,23 @@ path, agent response, app URL, and process IDs. Fix changed-file defects and rep
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.10.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for proved voice input, `failed` for an attempted proof that failed, and
-`skipped` when the proof could not run. Then run `npx --yes copilotkit@4.10.0 onboard audit`.
+`skipped` when the proof could not run. Then run `npx --yes copilotkit@4.10.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
@@ -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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.0 onboard read feature/complete` with the actual surface
+`npx --yes copilotkit@4.10.1 onboard read feature/complete` with the actual surface
 outcome.

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

@@ -6,7 +6,7 @@ read-only, implementation, and proof subagents, each restricted to the target pr
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard protect
+npx --yes copilotkit@4.10.1 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -16,14 +16,14 @@ approved authorization before implementation.
 Before edits, inspect the runtime route, CopilotKit provider/chat composer, current agent,
 existing provider credential variable names (presence only), package versions, browser
 permissions approach, and test/dev commands. Prove the existing OSS baseline with `/info`,
-`npx --yes copilotkit@4.10.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --yes copilotkit@4.10.1 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
 and a real UI request when a browser is available. If that baseline is absent, change nothing
 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.0 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.10.1 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.0 onboard read feature/stop
+npx --yes copilotkit@4.10.1 onboard read feature/stop
 ```
 
 Do not run login, select Intelligence, create a credential, read a credential value, or
@@ -52,7 +52,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.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.10.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
@@ -62,7 +62,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.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.10.1 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.10.0 onboard read feature/voice/implement`.
+Then run `npx --yes copilotkit@4.10.1 onboard read feature/voice/implement`.

package/onboarding/prompts/framework/ag2.md

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

package/onboarding/prompts/framework/agno.md

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

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

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

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

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

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

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

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

@@ -54,7 +54,7 @@ variable names the repository proves or the developer named, these URLs, the ada
 shared-state limit.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.10.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.10.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.10.1 onboard read unsupported/no-validated-path`.

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

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

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

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