copilotkit 4.9.50 → 4.9.60

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

@@ -1,27 +1,45 @@
 # Prove a real run is assigned to the selected Learning Container
 
 Delegate proof to a fresh subagent. In the real authenticated app, create or use a thread,
-send a normal agent request, and confirm the resulting run is assigned to the selected
-Learning Container through the documented Intelligence/Inspector evidence. Confirm the
-thread remains associated with the expected user and that the managed round-trip check still
-passes.
+send a normal agent request, and confirm the resulting run reached the selected Learning
+Container. Confirm the thread remains associated with the expected user.
+
+One command decides it:
+
+```text
+npx --yes copilotkit@4.9.60 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
+passes only when that thread carries the container this run selected.
+
+Two other signals look like proof and are not. `features.self_learning` is a plan
+entitlement and is already true before any wiring. The `/info` response reports Learning
+from the presence of a callback, not from a single assigned thread. Never report either one
+as evidence.
 
 Do not claim that Insights or Skills are already available: those depend on completed runs
 and later learning processing. Record only the assignment visible now, the request, app URL,
 process IDs, and safe stop commands. Repair changed-file defects and repeat.
 
+Tell the developer what happens next, because a correct run looks like a broken one
+otherwise. Learning runs on its own: the first automatic run needs new threads from 15
+distinct conversations in this container, and only the newest snapshot of each thread
+counts. Threads that already ran before this change are never pulled in, because a thread
+takes its container before its first agent run. So the container starts empty on purpose.
+
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Run
-`npx --yes copilotkit@4.9.50 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
+`npx --yes copilotkit@4.9.60 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
 with the actual surface outcome.

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

@@ -13,7 +13,7 @@ onboarding.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -23,16 +23,20 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.9.60 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/connect-your-runtime.md
 https://docs.copilotkit.ai/threads.md
-Use a second retrieval method if needed. The CLI has no supported command to create or list
-Learning Containers. Do not invent an id, scrape a dashboard, or treat an arbitrary string
-as one.
+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
@@ -46,7 +50,7 @@ proof. Ask for approval separately.
 After approval, report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.9.50 onboard read feature/learning/implement`.
+Then run `npx --yes copilotkit@4.9.60 onboard read feature/learning/implement`.

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

@@ -14,15 +14,15 @@ Run the project's focused validation commands. Start the app and confirm `/info`
 validation results without secrets. When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase build-validated
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, stop
 without further changes:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.9.60 onboard read feature/stop
 ```
 
 Otherwise run
-`npx --yes copilotkit@4.9.50 onboard read feature/open-generative-ui/proof`.
+`npx --yes copilotkit@4.9.60 onboard read feature/open-generative-ui/proof`.

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

@@ -13,15 +13,15 @@ the missing visual proof honestly.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then run
-`npx --yes copilotkit@4.9.50 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
+`npx --yes copilotkit@4.9.60 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
 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 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.9.50 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --yes copilotkit@4.9.60 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.
@@ -14,7 +14,7 @@ generic onboarding path first.
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -24,7 +24,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.9.60 onboard read feature/stop
 ```
 
 Do not sign in, select an Intelligence project, create credentials, change the existing
@@ -41,7 +41,7 @@ likely CSP/sandbox implications, tests, and a user-visible generated UI proof. A
 After approval, report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.9.50 onboard read feature/open-generative-ui/implement`.
+Then run `npx --yes copilotkit@4.9.60 onboard read feature/open-generative-ui/implement`.

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

@@ -17,22 +17,22 @@ 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.9.50 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --yes copilotkit@4.9.60 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 Repair changed-file failures and record changed paths and secret-safe validation
 evidence.
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase build-validated
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, stop
 without further changes:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.9.60 onboard read feature/stop
 ```
 
 Otherwise run
-`npx --yes copilotkit@4.9.50 onboard read feature/realtime-sync/proof`.
+`npx --yes copilotkit@4.9.60 onboard read feature/realtime-sync/proof`.

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

@@ -14,15 +14,15 @@ 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.9.50 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Run
-`npx --yes copilotkit@4.9.50 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
+`npx --yes copilotkit@4.9.60 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
 with the actual outcome.

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

@@ -13,7 +13,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.9.50 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -23,7 +23,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.9.60 onboard read feature/stop
 ```
 
 Fetch the current official guides before planning:
@@ -44,7 +44,7 @@ need a `wsUrl`. Ask for approval separately.
 After approval, report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.9.50 onboard read feature/realtime-sync/implement`.
+Then run `npx --yes copilotkit@4.9.60 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.9.50 login --json` and follow its single streaming session. Then
+`npx --yes copilotkit@4.9.60 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,22 +20,22 @@ 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.9.50 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
+`npx --yes copilotkit@4.9.60 verify --expect-runtime intelligence --round-trip --agent <agent-id> --json`.
 Repair changed-file failures before continuing. Record changed paths and secret-safe
 validation evidence.
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase build-validated
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, stop
 without further changes:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.9.60 onboard read feature/stop
 ```
 
 Otherwise run
-`npx --yes copilotkit@4.9.50 onboard read feature/rich-threads/proof`.
+`npx --yes copilotkit@4.9.60 onboard read feature/rich-threads/proof`.

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

@@ -13,15 +13,15 @@ running.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then run
-`npx --yes copilotkit@4.9.50 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
+`npx --yes copilotkit@4.9.60 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
 with the actual browser outcome.

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

@@ -13,7 +13,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.9.50 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -23,7 +23,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.9.60 onboard read feature/stop
 ```
 
 Fetch the current official guides before planning:
@@ -46,7 +46,7 @@ tests, and a reload/reopen proof. Ask for approval separately.
 After approval, report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.9.50 onboard read feature/rich-threads/implement`.
+Then run `npx --yes copilotkit@4.9.60 onboard read feature/rich-threads/implement`.

package/onboarding/prompts/feature/stop.md

@@ -14,7 +14,7 @@ a `start` with no `--run` reprints the id this stopped run already holds, and on
 covering both reads as one run that did two different things.
 
 ```text
-npx --yes copilotkit@4.9.50 onboard start --run <new-12-character-id>
+npx --yes copilotkit@4.9.60 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 +29,7 @@ Send one short report. Run the feedback command without another developer questi
 CLI telemetry gate decides whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.50 onboard feedback
+npx --yes copilotkit@4.9.60 onboard feedback
 ```
 
 Write the feedback message to the command's standard input, in at most four lines. Send no
@@ -37,5 +37,5 @@ secrets, source code, logs, or command output. The command refuses a report that
 any of those, prints the reason, and exits zero. A refused report is not a failed step.
 Reword it and send it again, or stop without a report. The command prints what it sent.
 This is the channel for a stop. Report friction only from a run that finished, never from
-here. If the CLI says that telemetry is disabled or unavailable, state that the report was
-not sent and stop without another question.
+here. If the CLI says the report was not sent, state what it said and
+stop without another question.

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

@@ -14,15 +14,15 @@ voice proof. Record changed paths and validation results.
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase build-validated
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, stop
 without further changes:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.9.60 onboard read feature/stop
 ```
 
 Otherwise run
-`npx --yes copilotkit@4.9.50 onboard read feature/voice/proof`.
+`npx --yes copilotkit@4.9.60 onboard read feature/voice/proof`.

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

@@ -13,15 +13,15 @@ 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.9.50 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 Then run
-`npx --yes copilotkit@4.9.50 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
+`npx --yes copilotkit@4.9.60 onboard complete --visual-check <performed|skipped-no-browser-tool|failed>`
 with the actual surface outcome.

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

@@ -6,14 +6,14 @@ read-only, implementation, and proof subagents, each restricted to the target pr
 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.9.50 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --yes copilotkit@4.9.60 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.9.50 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase research-returned
 ```
 
 A refused checkpoint prints its reason and leaves onboarding unaffected. It is not a
@@ -23,7 +23,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard read feature/stop
+npx --yes copilotkit@4.9.60 onboard read feature/stop
 ```
 
 Do not run login, select Intelligence, create a credential, read a credential value, or
@@ -39,7 +39,7 @@ tests, and a microphone/canned-transcript proof. Ask for approval separately.
 After approval, report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.9.50 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.9.60 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.9.50 onboard read feature/voice/implement`.
+Then run `npx --yes copilotkit@4.9.60 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.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 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.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 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.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 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.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 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.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 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.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 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.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 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.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.

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

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

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

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

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

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

package/onboarding/prompts/framework/llamaindex.md

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

package/onboarding/prompts/framework/mastra.md

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

package/onboarding/prompts/framework/ms-agent-dotnet.md

@@ -34,7 +34,7 @@ Record the selected framework, provider, model, required credential variable nam
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/ms-agent-harness-dotnet.md

@@ -44,7 +44,7 @@ Record the selected framework, provider, model, required credential variable nam
 URLs, and the quickstart gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/ms-agent-python.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.9.50 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.60 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.50 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.60 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/pydantic-ai.md

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