copilotkit 4.12.0 → 4.13.1

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.12.0 onboard protect
+npx --yes copilotkit@4.13.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.12.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`,
+`npx --yes copilotkit@4.13.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.12.0 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.13.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.12.0 onboard read feature/stop
+npx --yes copilotkit@4.13.1 onboard read feature/stop
 ```
 
 Do not run login, select Intelligence, create a credential, read a credential value, or
@@ -54,7 +54,7 @@ one.
 After approval, record each approved path before implementation:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.13.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.12.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.12.0 onboard read feature/voice/implement`.
+Then run `npx --yes copilotkit@4.13.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.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.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.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -23,11 +23,13 @@ runtime setup.
 These pages use the root documentation scope. Do not add a framework path segment to
 their URLs. Use the tool-based generative UI page for this built-in route.
 
+Connect the Copilot Runtime with `BuiltInAgent` from `@copilotkit/runtime/v2`.
+
 Record the selected framework, vendor, model, required credential variable names, and
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.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.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.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.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.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.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -25,11 +25,14 @@ agent-app-context setup. If the requested work needs it, run the unsupported rou
 A2UI is not on this path. If the developer asks for it, say first that its backend example
 is Python-only, so a TypeScript project has nothing to follow.
 
+Connect the Copilot Runtime with `LangGraphAgent` from `@copilotkit/runtime/langgraph`
+on the Deep Agent path, or `HttpAgent` from `@ag-ui/client` on the FastAPI path.
+
 Record the selected framework, language, vendor, model, required credential variable
 names, these URLs, and each documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -24,11 +24,13 @@ that missing page as a documentation gap. Do not read the built-in-agent context
 in its place: that page states no backend work is needed, which holds for the built-in
 agent and not for ADK.
 
+Connect the Copilot Runtime with `HttpAgent` from `@ag-ui/client`.
+
 Record the selected framework, vendor, model, required credential variable names, and
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -17,14 +17,15 @@ The FastAPI graph must have a checkpointer.
 Keep the existing checkpointer. For a new local agent, use `MemorySaver` only for
 development.
 Use `add_langgraph_fastapi_endpoint` for the FastAPI agent endpoint.
-Use `LangGraphHttpAgent` in the Copilot Runtime.
+Connect the Copilot Runtime with `HttpAgent` from `@ag-ui/client`.
+`LangGraphHttpAgent` is deprecated. Do not use it.
 Do not copy the LangSmith path, its no-checkpointer rule, or its `LangGraphAgent` adapter.
 
 Record the selected framework, vendor, model, required credential variable names, and
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -11,11 +11,15 @@ name its credential variables and setup steps.
 - https://docs.copilotkit.ai/langgraph-python/generative-ui/tool-based.md
 - https://docs.copilotkit.ai/langgraph-python/agent-app-context.md
 
+Connect the Copilot Runtime with `LangGraphAgent` from `@copilotkit/runtime/langgraph`
+on the LangSmith path, or `HttpAgent` from `@ag-ui/client` on the FastAPI path.
+`LangGraphHttpAgent` is deprecated. Do not use it.
+
 Record the selected framework, vendor, model, required credential variable names, and
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -11,11 +11,15 @@ name its credential variables and setup steps.
 - https://docs.copilotkit.ai/langgraph-typescript/generative-ui/tool-based.md
 - https://docs.copilotkit.ai/langgraph-typescript/agent-app-context.md
 
+Connect the Copilot Runtime with `LangGraphAgent` from `@copilotkit/runtime/langgraph`
+on the LangSmith path, or `HttpAgent` from `@ag-ui/client` on the FastAPI path.
+`LangGraphHttpAgent` is deprecated. Do not use it.
+
 Record the selected framework, vendor, model, required credential variable names, and
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/framework/mastra.md

@@ -41,11 +41,13 @@ what the developer had.
 - https://docs.copilotkit.ai/mastra/generative-ui/tool-based.md
 - https://docs.copilotkit.ai/mastra/agent-app-context.md
 
+Connect the Copilot Runtime with `MastraAgent` from `@ag-ui/mastra`.
+
 Record the selected framework, vendor, model, required credential variable names, and
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -30,11 +30,13 @@ Use `Microsoft.Agents.AI.Hosting.AGUI.AspNetCore` from the Learn guide. Register
 with `AddAGUIServer`. Map the existing `AIAgent` with `MapAGUIServer`. The endpoint accepts
 `RunAgentInput` requests and streams AG-UI events with server-sent events.
 
+Connect the Copilot Runtime with `HttpAgent` from `@ag-ui/client`.
+
 Record the selected framework, provider, model, required credential variable names, and
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -24,11 +24,13 @@ byte-identical to the one at `ms-agent-dotnet`: one page serves both languages t
 a `.NET` and `Python` tab group. The scope in the URL does not select the language, so
 read the Python tab. The first code block on the page is the .NET one.
 
+Connect the Copilot Runtime with `HttpAgent` from `@ag-ui/client`.
+
 Record the selected framework, vendor, model, required credential variable names, and
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -23,11 +23,13 @@ No Strands agent-app-context Markdown page is available. Do not invent an
 agent-app-context setup. If the requested work needs that missing setup, run the
 unsupported route below.
 
+Connect the Copilot Runtime with `HttpAgent` from `@ag-ui/client`.
+
 Record the selected framework, vendor, model, required credential variable names, these
 URLs, and the context documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

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

@@ -24,11 +24,13 @@ run the unsupported route below.
 A2UI is not on this path. If the developer asks for it, say first that its page has no
 Strands TypeScript backend example, so a TypeScript project has nothing to follow.
 
+Connect the Copilot Runtime with `HttpAgent` from `@ag-ui/client`.
+
 Record the selected framework, vendor, model, required credential variable names, these
 URLs, and the context documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/angular.md

@@ -5,7 +5,7 @@ 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 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.12.0 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read unsupported/no-validated-path`.
+together, run `npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/nextjs.md

@@ -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.12.0 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/plan.md

@@ -1,5 +1,19 @@
 # Select the frontend
 
+## A named Channel decides this node
+
+If the developer already named Slack or Microsoft Teams, use that choice.
+If the copied prompt came from a Slack or Teams docs page, use that page as the named frontend.
+
+Either one is final here. Do not ask the frontend question on that run. Do not let an
+existing frontend take a web route instead: the project keeps the frontend it has, and the
+Channel is what this run adds. Take the Slack or Microsoft Teams route below and name the
+provider to it. A Slack page names Slack. A Teams page names Teams.
+
+Every rule below is for a run that named neither.
+
+## Select the frontend from the findings
+
 Use the repository findings to select the frontend. Ask the developer only for choices
 that the repository does not show. Do not change application code in this phase.
 
@@ -9,9 +23,6 @@ the alternatives short. When the frontend is unknown, use this rule: Ask one fro
 question that lists the recommendation and valid choices. Do not ask a yes-or-no question
 first. Do not ask about the model or project in this step.
 
-If the developer already named Slack or Microsoft Teams, use that choice.
-If the copied prompt came from a Slack or Teams docs page, use that page as the named frontend.
-
 If the project has a frontend, preserve it and use the matching route below. If the project
 needs a frontend, show the valid choices and one recommendation based on repository
 evidence, then ask the developer to choose.
@@ -25,15 +36,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.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`
+1. React SPA: `npx --yes copilotkit@4.13.1 onboard read frontend/react-spa`
+2. Next.js: `npx --yes copilotkit@4.13.1 onboard read frontend/nextjs`
+3. Angular: `npx --yes copilotkit@4.13.1 onboard read frontend/angular`
+4. Vue 3: `npx --yes copilotkit@4.13.1 onboard read frontend/vue`
+5. React Native: `npx --yes copilotkit@4.13.1 onboard read frontend/react-native`
+6. Slack or Microsoft Teams: `npx --yes copilotkit@4.13.1 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.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/finalize-plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.13.1 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -36,6 +36,16 @@ plan said, what you did instead, and why. Carry that record into the closing sum
 which has an item for it. Do not stop for a departure that is the right call, and do not
 leave it unrecorded either.
 
+The existing agent's behavior is never a departure to record and carry on from. It is four
+things: its system prompt and instructions, its tools and what those tools do, its model
+and provider configuration, and its memory or state handling. Repair a failing check on
+the CopilotKit side first -- the frontend rendering, the tool schema, the runtime wiring.
+Where the only fix you can find is a change to the agent's instructions or tools, stop:
+report the failing predicate and the change you propose, and continue only after the
+developer approves it. An approved change is a behavior change, and the closing report
+names it as one. Never call a change to the agent's instructions or tools a repair. If you
+cannot ask, or the developer declines, use the route-out rules below.
+
 ## Authorization requested by the plan
 
 Approving the plan is the developer agreeing to every path it listed under
@@ -43,7 +53,7 @@ Approving the plan is the developer agreeing to every path it listed under
 app directory:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.13.1 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
@@ -60,7 +70,7 @@ No implementation step has run yet, so the change is theirs rather than this run
 consent over it by adding one flag:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>" --with-prior-change
+npx --yes copilotkit@4.13.1 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
@@ -79,7 +89,7 @@ rather than this section.
 Run the audit from the target app directory:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard audit
+npx --yes copilotkit@4.13.1 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -114,14 +124,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.12.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.13.1 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.12.0 onboard protect --accept-credential --path <path>
+npx --yes copilotkit@4.13.1 onboard protect --accept-credential --path <path>
 ```
 
 That route proves no recorded credential was lost, instead of taking the run's word that it
@@ -140,7 +150,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.12.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.13.1 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
@@ -161,7 +171,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.12.0 learning containers create --id <id> --name <name> --json
+npx --yes copilotkit@4.13.1 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
@@ -177,7 +187,7 @@ hold.
 Then report that the container is settled, before any edit:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard checkpoint --phase container-settled
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase container-settled
 ```
 
 Where the plan names a container the platform already held, report the same checkpoint and
@@ -186,11 +196,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.12.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase plan-written
 ```
 
 Spawn one implementation subagent. Tell it to run
-`npx --yes copilotkit@4.12.0 onboard read subagent/implement-and-validate` first and follow
+`npx --yes copilotkit@4.13.1 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
@@ -202,6 +212,14 @@ to implement every step in plan order and run the full validation list. Wait for
 One subagent implements the whole plan. Do not divide the work across concurrent subagents,
 and do not spawn a second subagent to reconcile a split.
 
+All implementation work happens in the run root's own working tree: the target app
+directory this run started in. Never send the subagent to a separate worktree, a branch
+checkout, or a copy of the project, and tell it to work in that directory itself. A
+subagent that worked elsewhere must bring its changes into the run root before it reports.
+The completion step verifies that the changed files exist in this project and refuses a run
+whose tree never changed, so work left in another tree ends the run with nothing in the
+developer's hands.
+
 If the implementation result does not start with `Status: passed`, do not continue to proof.
 Run the protected-path audit after the implementation subagent passes. Decide each path it
 names the same way as above, against the Files changed section that subagent just
@@ -210,11 +228,11 @@ returned. Continue to proof only when that audit passes.
 After the selected implementation path passes, report it:
 
 ```text
-npx --yes copilotkit@4.12.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase build-validated
 ```
 
 Then run
-`npx --yes copilotkit@4.12.0 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.13.1 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -236,9 +254,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.12.0 onboard read stopped/run-failed`.
+`npx --yes copilotkit@4.13.1 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.12.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.