copilotkit 4.11.0 → 4.12.0

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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 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.11.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

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

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

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

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

package/onboarding/prompts/frontend/angular.md

@@ -2,10 +2,10 @@
 
 Preserve an existing Angular frontend. Use the selected page for a new frontend.
 
-Use the starter shortcut only if all these facts are true: the target directory contains
-no entries, its name is a valid `init` project name, and the selected framework is ADK.
+Use the starter shortcut only if all these facts are true: the target directory holds no
+project, its name is a valid `init` project name, and the selected framework is ADK.
 If all three facts are true, record Angular as the selected frontend. Then run
-`npx --yes copilotkit@4.11.0 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.12.0 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -63,7 +63,7 @@ you create or build an Angular project. If the installed version is lower, selec
 supported version first and use it for every later command in this project.
 
 If the pages support the selection, record Angular and these URLs. Then run
-`npx --yes copilotkit@4.11.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.12.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, or the two version lines do not fit
-together, run `npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+together, run `npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/nextjs.md

@@ -2,7 +2,7 @@
 
 Preserve an existing Next.js frontend. Use the selected pages for a new frontend.
 
-Use the starter shortcut only if the target directory contains no entries and its name is
+Use the starter shortcut only if the target directory holds no project and its name is
 a valid `init` project name. The selected framework must also match one of these options.
 
 These Python options have Next.js starters: Agno, Claude Agent SDK Python, CrewAI Flows,
@@ -15,7 +15,7 @@ These TypeScript options have starters: Claude Agent SDK TypeScript, LangGraph T
 Mastra, and Strands Agents TypeScript. The .NET option is Microsoft Agent Framework .NET.
 
 If all shortcut conditions are true, record Next.js as the selected frontend. Then run
-`npx --yes copilotkit@4.11.0 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.12.0 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -27,7 +27,7 @@ agent as the default agent, which is correct only for a project that has no agen
 Do not replace the developer's existing agent with the built-in agent.
 
 If the page supports the selection, record Next.js and this URL. Then run
-`npx --yes copilotkit@4.11.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.12.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/plan.md

@@ -25,15 +25,15 @@ CopilotKit web apps. Then recommend the one the developer names, and say what ea
 
 Use exactly one matching internal route:
 
-1. React SPA: `npx --yes copilotkit@4.11.0 onboard read frontend/react-spa`
-2. Next.js: `npx --yes copilotkit@4.11.0 onboard read frontend/nextjs`
-3. Angular: `npx --yes copilotkit@4.11.0 onboard read frontend/angular`
-4. Vue 3: `npx --yes copilotkit@4.11.0 onboard read frontend/vue`
-5. React Native: `npx --yes copilotkit@4.11.0 onboard read frontend/react-native`
-6. Slack or Microsoft Teams: `npx --yes copilotkit@4.11.0 onboard read feature/channels/start`
+1. React SPA: `npx --yes copilotkit@4.12.0 onboard read frontend/react-spa`
+2. Next.js: `npx --yes copilotkit@4.12.0 onboard read frontend/nextjs`
+3. Angular: `npx --yes copilotkit@4.12.0 onboard read frontend/angular`
+4. Vue 3: `npx --yes copilotkit@4.12.0 onboard read frontend/vue`
+5. React Native: `npx --yes copilotkit@4.12.0 onboard read frontend/react-native`
+6. Slack or Microsoft Teams: `npx --yes copilotkit@4.12.0 onboard read feature/channels/start`
 
 If they chose Slack or Microsoft Teams, tell that node which one they chose so it
 does not ask again.
 
 If no listed frontend fits, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-native.md

@@ -15,7 +15,7 @@ documents `useRenderTool`, which is React Native's own hook for drawing a tool t
 already has. That is a different job and needs a tool in the agent.
 
 If the pages support the selection, record React Native and these URLs. Then run
-`npx --yes copilotkit@4.11.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.12.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-spa.md

@@ -11,7 +11,7 @@ not move the agent into it.
 - https://docs.copilotkit.ai/react-spa.md
 
 If the page supports the selection, record React SPA and this URL. Then run
-`npx --yes copilotkit@4.11.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.12.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/vue.md

@@ -16,7 +16,7 @@ page above. Vue has its own `useComponent`, which is not the React package. Take
 that reference page rather than from a Vue generative-UI guide, which is not published.
 
 If the pages support the selection, record Vue 3 and these URLs. Then run
-`npx --yes copilotkit@4.11.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.12.0 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/implementation/build-and-validate.md

@@ -12,7 +12,7 @@ command without another developer question. Do not ask the developer about telem
 command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.11.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.12.0 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -43,19 +43,24 @@ Approving the plan is the developer agreeing to every path it listed under
 app directory:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.12.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
 ```
 
 Consent has to be on the record before the file moves, so a call made after the change is
 refused. Continue only if every result starts with `Status: passed`. If the plan listed
 nothing there, skip this section.
 
+What you record here covers changing the file. It does not cover removing it. Never delete,
+move, or rename a protected path, whatever the plan says: the audit fails a path that is
+gone even when consent was recorded for it, and no command clears that. If a step cannot
+proceed without removing one, route out and report the path.
+
 If a path the plan listed has already changed, the developer changed it after the capture.
 No implementation step has run yet, so the change is theirs rather than this run's. Record
 consent over it by adding one flag:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>" --with-prior-change
+npx --yes copilotkit@4.12.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>" --with-prior-change
 ```
 
 The flag records their change as drift beside the consent, so the closing report names both
@@ -74,7 +79,7 @@ rather than this section.
 Run the audit from the target app directory:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard audit
+npx --yes copilotkit@4.12.0 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -87,7 +92,7 @@ answers the same.
 
 Decide each path the audit names, one at a time.
 
-A path the audit lists under `Authorized to change:` is not a finding. The developer approved
+A path the audit lists under `Authorized to modify:` is not a finding. The developer approved
 it, the record says why, and the audit reports it rather than failing on it. Carry it into the
 summary with its reason. Nothing else is needed for it.
 
@@ -109,14 +114,14 @@ A path that no Files changed section names changed outside the run, and it is th
 developer's own file. Accept it by name:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.12.0 onboard protect --accept-external --path <path>
 ```
 
 A changed env file is its own case. This run asked the developer to place a credential
 there, so it takes the credential route rather than this one:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard protect --accept-credential --path <path>
+npx --yes copilotkit@4.12.0 onboard protect --accept-credential --path <path>
 ```
 
 That route proves no recorded credential was lost, instead of taking the run's word that it
@@ -135,7 +140,7 @@ neither does a one-line fix. Never repair, reset, or revert it. Ask the develope
 the change, and record the answer they give:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.12.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Use it only for an answer a developer actually gave. It records the consent as taken
@@ -156,7 +161,7 @@ create it now, from the target app directory. The developer approved the id befo
 made, so this is the first point at which it can be created:
 
 ```text
-npx --yes copilotkit@4.11.0 learning containers create --id <id> --name <name> --json
+npx --yes copilotkit@4.12.0 learning containers create --id <id> --name <name> --json
 ```
 
 Pass the id the plan names. Take the name from the selected project's own display name, so
@@ -172,7 +177,7 @@ hold.
 Then report that the container is settled, before any edit:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard checkpoint --phase container-settled
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase container-settled
 ```
 
 Where the plan names a container the platform already held, report the same checkpoint and
@@ -181,11 +186,11 @@ create nothing. Where the plan names no container, skip this section.
 Report the plan this run is about to implement:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase plan-written
 ```
 
 Spawn one implementation subagent. Tell it to run
-`npx --yes copilotkit@4.11.0 onboard read subagent/implement-and-validate` first and follow
+`npx --yes copilotkit@4.12.0 onboard read subagent/implement-and-validate` first and follow
 the prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the plan, selected framework, frontend, model, exact target app
@@ -205,11 +210,11 @@ returned. Continue to proof only when that audit passes.
 After the selected implementation path passes, report it:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.12.0 onboard checkpoint --phase build-validated
 ```
 
 Then run
-`npx --yes copilotkit@4.11.0 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.12.0 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -231,9 +236,9 @@ the same command still fails after three repair attempts, or a result starts wit
 `Status: blocked`. A defect in a package this run installed is not a stack CopilotKit does
 not serve, a command this run cannot get to pass is not one either, and a blocked audit
 proved nothing about the stack. In those cases run
-`npx --yes copilotkit@4.11.0 onboard read stopped/run-failed`.
+`npx --yes copilotkit@4.12.0 onboard read stopped/run-failed`.
 
 A plan with no path to follow takes the unsupported ending: the fix requires changing the
 developer's existing agent or frontend, or the documentation does not support the plan. In
 those cases run
-`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -70,7 +70,7 @@ Name the debugging surface this journey's frontend can reach, rather than the on
 of the documentation leads with. For a web frontend it is the CopilotKit Inspector. For
 React Native there is no Inspector: it is a browser overlay built on a DOM custom element,
 and `@copilotkit/react-native` does not ship it. Give a mobile developer
-`npx --yes copilotkit@4.11.0 verify --round-trip`, the runtime's own log, the AG-UI
+`npx --yes copilotkit@4.12.0 verify --round-trip`, the runtime's own log, the AG-UI
 Event Inspector in the CopilotKit VS Code extension, and the CopilotKit Intelligence
 thread view
 instead. Naming the Inspector to a developer who cannot open it costs them the time it
@@ -79,9 +79,10 @@ takes to conclude their own wiring is broken.
 Where this run settled a Learning Container, 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. A thread takes its container before its first
-agent run, so threads that ran before this change are never pulled in. The container starts
-empty on purpose.
+the newest snapshot of each thread counts. Existing threads can receive their first
+container assignment after prior runs. Their surviving earlier history becomes eligible
+for collection and counts toward the same threshold. Creating a container does not enroll
+existing threads automatically.
 
 Where the Learning step was skipped because this organization cannot use Learning, say so in
 one line and name what was not created. A skip nobody names reads as a container that
@@ -94,7 +95,7 @@ the friction commands without another developer question. Do not ask the develop
 telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.11.0 onboard friction --category <slug> --cost-seconds <seconds>
+npx --yes copilotkit@4.12.0 onboard friction --category <slug> --cost-seconds <seconds>
 ```
 
 Write one or two sentences on the command's standard input. Pick one category from
@@ -106,7 +107,7 @@ Pass --docs-path only for a docs-missing or docs-wrong report, naming the page t
 is about:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
+npx --yes copilotkit@4.12.0 onboard friction --category docs-wrong --cost-seconds 300 --docs-path /docs/threads/drawer
 ```
 
 Give the page's site-relative path or its full URL, with no spaces, query string, or
@@ -123,14 +124,14 @@ Tell the developer when you send a friction report. Do not quote or summarize th
 unless the developer asks. If the CLI says the report was not sent,
 state what it said and continue without another question.
 
-When the evidence is gathered, run `npx --yes copilotkit@4.11.0 onboard complete`, carrying
+When the evidence is gathered, run `npx --yes copilotkit@4.12.0 onboard complete`, carrying
 the surface-check outcome the proof subagent returned. Pass exactly one flag, and pass the
 one that matches this journey's surface.
 
 For a web frontend -- React SPA, Next.js, Angular, Vue:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.12.0 onboard complete --visual-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-browser-tool`, `skipped-cloned-starter`, or
@@ -140,7 +141,7 @@ open no browser. It is the one skip that does not block.
 For React Native:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.12.0 onboard complete --device-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-device`, `skipped-cloned-starter`, or
@@ -153,7 +154,7 @@ browser-origin CORS, so the flag you pass is how this run states which surface i
 For a web frontend, also pass the URL the browser opened:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard complete --visual-check <outcome> \
+npx --yes copilotkit@4.12.0 onboard complete --visual-check <outcome> \
   --frontend-url <the url you opened>
 ```
 
@@ -172,7 +173,7 @@ If the round trip proved and something after it still blocked this run, add `--b
 to the same command:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard complete --visual-check performed --blocked-by <cause>
+npx --yes copilotkit@4.12.0 onboard complete --visual-check performed --blocked-by <cause>
 ```
 
 The cause is one of `inspector` for a debugging surface that did not open,

package/onboarding/prompts/proof/oss-baseline.md

@@ -1,7 +1,7 @@
 # Prove the existing OSS baseline
 
 Do not prove the baseline yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.11.0 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --yes copilotkit@4.12.0 onboard read subagent/prove-oss-baseline` first and follow the
 prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the repository findings and exact CLI package spec.
@@ -17,7 +17,7 @@ Wait for the subagent to finish.
 Record what that proof returned before you route on it:
 
 ```text
-npx --yes copilotkit@4.11.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
+npx --yes copilotkit@4.12.0 onboard proof --step oss-baseline --outcome <passed|failed|skipped> [--predicate <1-6>]
 ```
 
 Report the gate whatever it returned. Pass `passed` when the subagent proved a predicate,
@@ -35,12 +35,12 @@ Do not change project files before this proof ends. Starting existing developmen
 processes and their ignored runtime files is allowed.
 
 If the subagent proves the `both-oss` predicate, keep its evidence with the plan and run
-`npx --yes copilotkit@4.11.0 onboard read conversion/plan`. That project already works.
+`npx --yes copilotkit@4.12.0 onboard read conversion/plan`. That project already works.
 What it needs is the conversion, not a build.
 
 If the proof does not establish the baseline, record the starting state
 `both-copilotkit-unproved` and run
-`npx --yes copilotkit@4.11.0 onboard read credentials/plan`. This prompt is served
+`npx --yes copilotkit@4.12.0 onboard read credentials/plan`. This prompt is served
 whenever a project looks like an OSS integration, so a baseline that did not prove is an
 ordinary starting state rather than a failure. Keep the failing predicate with the plan.
 
@@ -54,5 +54,5 @@ and the plan preserves it rather than repeating it.
 
 If it cannot identify the running process safely, exposes a secret, or finds a baseline
 failure that cannot be classified, run
-`npx --yes copilotkit@4.11.0 onboard read stopped/run-failed`. None of those mean the
+`npx --yes copilotkit@4.12.0 onboard read stopped/run-failed`. None of those mean the
 project is unsupported: they mean this run did not establish what it needed to.