copilotkit 4.13.0 → 4.13.1

package/onboarding/index.json

@@ -1,5 +1,5 @@
 {
-  "graphTree": "4f56a5f7891360d7a7d73ae2fd1d3ed4d6753a8b",
+  "graphTree": "767f6a96e6cd9a52d8ff39bc083fd7dc2e3aa4e4",
   "intentRoots": {
     "add-a2ui": "feature/a2ui/start",
     "add-chat-suggestions": "feature/chat-suggestions/start",

package/onboarding/prompts/authenticate/start.md

@@ -15,7 +15,7 @@ does is hidden from the developer.
 Run this before anything else in this prompt, including the welcome message below:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard identify --coding-agent <coding-agent-slug>
+npx --yes copilotkit@4.13.1 onboard identify --coding-agent <coding-agent-slug>
 ```
 
 Report your own product with one short slug, such as `codex` or `claude-code`.
@@ -42,10 +42,10 @@ printed once.
 Every later command must run from the directory this run started in. A command run
 somewhere else is refused, because the run it belongs to cannot be found from there. That
 refusal is a step, not a stop to report: run
-`npx --yes copilotkit@4.13.0 onboard start --run <onboarding_run_id>` where you are
+`npx --yes copilotkit@4.13.1 onboard start --run <onboarding_run_id>` where you are
 standing, then run the refused command again.
 
-If you no longer hold the id, run `npx --yes copilotkit@4.13.0 onboard start` in the
+If you no longer hold the id, run `npx --yes copilotkit@4.13.1 onboard start` in the
 directory this run started in, with no `--run` and no `--intent`. It reprints the id of the
 run under way and starts nothing. An id this project does not already hold starts a second
 run, and the work already done stops counting toward the first.
@@ -108,7 +108,7 @@ command without another developer question: it applies the telemetry setting the
 already set.
 
 ```text
-npx --yes copilotkit@4.13.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.
@@ -124,7 +124,7 @@ next: send the report, then stop.
 
 ## Check sign-in
 
-Run `npx --yes copilotkit@4.13.0 login --json` before any project work. This command
+Run `npx --yes copilotkit@4.13.1 login --json` before any project work. This command
 checks the current session. It starts sign-in only as needed. Treat this as a long-lived
 streaming process. Do not wait for the command to exit before you read its standard output.
 
@@ -160,8 +160,8 @@ Do not use `whoami` for this check. It has no JSON output and some failures exit
 zero. Do not put account tokens or credentials in the conversation.
 
 When sign-in is settled, run
-`npx --yes copilotkit@4.13.0 onboard read research/gather`.
+`npx --yes copilotkit@4.13.1 onboard read research/gather`.
 
 If sign-in stops onboarding, run
-`npx --yes copilotkit@4.13.0 onboard read stopped/run-failed`. It says nothing about
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`. It says nothing about
 whether this project's stack is supported, which is not yet known at this point.

package/onboarding/prompts/conversion/plan.md

@@ -100,7 +100,7 @@ of this journey, and a drawer that lists nothing is not a reason to mint one. Li
 tokens stay a self-hosted concern.
 
 Where this journey's frontend framework ships no threads drawer -- React Native --, the
-fifth item is proved by `npx --yes copilotkit@4.13.0 verify --round-trip`, which sends a
+fifth item is proved by `npx --yes copilotkit@4.13.1 verify --round-trip`, which sends a
 real request and reads the answer back off the thread it landed on. The run says which of
 the two it proved. Do not send a run to the managed Intelligence dashboard to prove this.
 An authenticated browser session at a hosted dashboard is the one thing an agent-driven run
@@ -116,7 +116,7 @@ and passed -- so a run scored on either one was scored on the same fact. Every r
 resolves that condition from, while `licenseStatus` is a compatibility projection of it
 for older thread surfaces and outlives them only until those surfaces go.
 
-Then run `npx --yes copilotkit@4.13.0 onboard read credentials/finalize-plan`.
+Then run `npx --yes copilotkit@4.13.1 onboard read credentials/finalize-plan`.
 
 If a selected page does not load after the second method, run
-`npx --yes copilotkit@4.13.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/credentials/finalize-plan.md

@@ -23,7 +23,7 @@ developer question. Do not ask the developer about telemetry: the command applie
 setting they already have.
 
 ```text
-npx --yes copilotkit@4.13.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.
@@ -58,7 +58,7 @@ the command refuses one of them from a run that was served that node.
 Run this command with the exact selected slugs:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
+npx --yes copilotkit@4.13.1 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
 ```
 
 Do not continue if a value is refused. Fix the value from the choices that the earlier
@@ -155,7 +155,7 @@ passes against the wrong one.
 Create it, from the target directory, passing the port research settled:
 
 ```text
-npx --yes copilotkit@4.13.0 project select --create <name> \
+npx --yes copilotkit@4.13.1 project select --create <name> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
 ```
 
@@ -173,13 +173,13 @@ Take this branch only when the developer asks for an existing project, or asks t
 projects they have. Read the choices:
 
 ```text
-npx --yes copilotkit@4.13.0 project list --json
+npx --yes copilotkit@4.13.1 project list --json
 ```
 
 Narrow them:
 
 ```text
-npx --yes copilotkit@4.13.0 project list --search <query> --json
+npx --yes copilotkit@4.13.1 project list --search <query> --json
 ```
 
 With `--json` the payload is the only thing on standard output, so it is safe to parse. Do
@@ -192,7 +192,7 @@ Then record the project they name, from the target directory, with the same
 `--runtime-url`:
 
 ```text
-npx --yes copilotkit@4.13.0 project select --project <slug-or-id> \
+npx --yes copilotkit@4.13.1 project select --project <slug-or-id> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
 ```
 
@@ -222,7 +222,8 @@ After project reuse or a warning-free selection result, send the environment
 research subagent a focused follow-up check. Give it the exact target app directory and both
 credential paths. Require it to report these facts without values:
 
-- The project-record path has non-empty `projectId`, `projectSlug`, and `clerkOrgId` fields.
+- The project-record path has non-empty `projectId` and `projectSlug` fields. Unless
+  `COPILOTKIT_DEPLOYMENT` is `self-hosted`, it also has a non-empty `clerkOrgId` field.
 - The environment path has a non-empty `CPK_INTELLIGENCE_API_KEY` entry.
 - If project selection ran, its selected slug matches `projectSlug`.
 - If project selection ran, the `.env` file was created or its modification time advanced.
@@ -236,4 +237,4 @@ project-record path and environment path as the credential setup path list. Do n
 to the baseline yet.
 
 When project selection is settled, run
-`npx --yes copilotkit@4.13.0 onboard read credentials/settle-credentials`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/settle-credentials`.

package/onboarding/prompts/credentials/plan.md

@@ -20,7 +20,7 @@ If the target directory holds no project and the copied prompt came from the Sla
 Microsoft Teams docs page, do not ask the framework question. The Channel starter brings
 its own agent, so an answer here decides nothing. Tell the developer that the Channel
 starter decides the agent, then run
-`npx --yes copilotkit@4.13.0 onboard read frontend/plan`.
+`npx --yes copilotkit@4.13.1 onboard read frontend/plan`.
 
 Use a gentle wizard. Ask one short question at a time. Do not combine separate choices in
 one question. Put the recommendation first, give its evidence in one sentence, and keep
@@ -74,26 +74,26 @@ another framework. Do not show the internal route.
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --yes copilotkit@4.13.0 onboard read framework/ag2`
-2. Agno: `npx --yes copilotkit@4.13.0 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --yes copilotkit@4.13.0 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --yes copilotkit@4.13.0 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.13.0 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --yes copilotkit@4.13.0 onboard read framework/crewai-flows`
-7. Deep Agents: `npx --yes copilotkit@4.13.0 onboard read framework/deep-agents`
-8. LangGraph Python: `npx --yes copilotkit@4.13.0 onboard read framework/langgraph-python`
-9. LangGraph FastAPI: `npx --yes copilotkit@4.13.0 onboard read framework/langgraph-fastapi`
-10. LangGraph TypeScript: `npx --yes copilotkit@4.13.0 onboard read framework/langgraph-typescript`
-11. LlamaIndex: `npx --yes copilotkit@4.13.0 onboard read framework/llamaindex`
-12. ADK: `npx --yes copilotkit@4.13.0 onboard read framework/google-adk`
-13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.13.0 onboard read framework/ms-agent-python`
-14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.13.0 onboard read framework/ms-agent-dotnet`
-15. Mastra: `npx --yes copilotkit@4.13.0 onboard read framework/mastra`
-16. MS Agent Harness .NET: `npx --yes copilotkit@4.13.0 onboard read framework/ms-agent-harness-dotnet`
-17. Pydantic AI: `npx --yes copilotkit@4.13.0 onboard read framework/pydantic-ai`
-18. Strands Agents Python: `npx --yes copilotkit@4.13.0 onboard read framework/strands-python`
-19. Strands Agents TypeScript: `npx --yes copilotkit@4.13.0 onboard read framework/strands-typescript`
+1. AG2: `npx --yes copilotkit@4.13.1 onboard read framework/ag2`
+2. Agno: `npx --yes copilotkit@4.13.1 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --yes copilotkit@4.13.1 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --yes copilotkit@4.13.1 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.13.1 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --yes copilotkit@4.13.1 onboard read framework/crewai-flows`
+7. Deep Agents: `npx --yes copilotkit@4.13.1 onboard read framework/deep-agents`
+8. LangGraph Python: `npx --yes copilotkit@4.13.1 onboard read framework/langgraph-python`
+9. LangGraph FastAPI: `npx --yes copilotkit@4.13.1 onboard read framework/langgraph-fastapi`
+10. LangGraph TypeScript: `npx --yes copilotkit@4.13.1 onboard read framework/langgraph-typescript`
+11. LlamaIndex: `npx --yes copilotkit@4.13.1 onboard read framework/llamaindex`
+12. ADK: `npx --yes copilotkit@4.13.1 onboard read framework/google-adk`
+13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.13.1 onboard read framework/ms-agent-python`
+14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.13.1 onboard read framework/ms-agent-dotnet`
+15. Mastra: `npx --yes copilotkit@4.13.1 onboard read framework/mastra`
+16. MS Agent Harness .NET: `npx --yes copilotkit@4.13.1 onboard read framework/ms-agent-harness-dotnet`
+17. Pydantic AI: `npx --yes copilotkit@4.13.1 onboard read framework/pydantic-ai`
+18. Strands Agents Python: `npx --yes copilotkit@4.13.1 onboard read framework/strands-python`
+19. Strands Agents TypeScript: `npx --yes copilotkit@4.13.1 onboard read framework/strands-typescript`
 
 If the project has an agent in another framework, or no listed framework fits, keep the
 developer's current agent and run
-`npx --yes copilotkit@4.13.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/credentials/settle-credentials.md

@@ -11,7 +11,7 @@ friction command without another developer question. Do not ask the developer ab
 telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.13.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.
@@ -60,7 +60,7 @@ One container for this project is the default scope, so the id comes from the se
 project slug. Ask the CLI for it, from the target directory:
 
 ```text
-npx --yes copilotkit@4.13.0 learning containers default-id --json
+npx --yes copilotkit@4.13.1 learning containers default-id --json
 ```
 
 The command reads the local project record. It needs no credential and makes no network
@@ -79,7 +79,7 @@ happened.
 Then ask the platform about that id, from the target directory:
 
 ```text
-npx --yes copilotkit@4.13.0 learning containers get <id> --json
+npx --yes copilotkit@4.13.1 learning containers get <id> --json
 ```
 
 The read carries the same availability gate as the create, so it answers the entitlement
@@ -104,7 +104,7 @@ Never invent an id, scrape a dashboard, or treat an arbitrary string as a contai
 Report what the read found, before anything is planned:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase container-surveyed
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase container-surveyed
 ```
 
 Carry the derived id into the planning subagent's handoff, with whether the platform
@@ -134,7 +134,7 @@ protected path list. Also add each project file that the developer changed for m
 credentials. Record them in the baseline from the target app directory:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard protect --path <path>
+npx --yes copilotkit@4.13.1 onboard protect --path <path>
 ```
 
 Pass one `--path` for each. The command captures a digest for each path and never re-reads
@@ -148,7 +148,7 @@ Then re-capture the files this graph wrote itself. For each path the first captu
 as `deferred` that this run has now written, run:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard protect --rebaseline --path <path>
+npx --yes copilotkit@4.13.1 onboard protect --rebaseline --path <path>
 ```
 
 From that point they are protected like any other path, so a later step that rewrites
@@ -167,7 +167,7 @@ environment path. The command below is what to run at that point, from the targe
 directory:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard protect --accept-credential --path <environment path>
+npx --yes copilotkit@4.13.1 onboard protect --accept-credential --path <environment path>
 ```
 
 The command compares the variable names the baseline recorded with the names the file holds
@@ -182,4 +182,4 @@ now. Read its result:
   is not a failed step. It answers the question and the run carries on.
 
 When the credential question is answered, run
-`npx --yes copilotkit@4.13.0 onboard read credentials/write-plan`.
+`npx --yes copilotkit@4.13.1 onboard read credentials/write-plan`.

package/onboarding/prompts/credentials/write-plan.md

@@ -11,7 +11,7 @@ friction command without another developer question. Do not ask the developer ab
 telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.13.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.
@@ -52,7 +52,7 @@ proof subagents:
 Fetch them together with the pages already selected rather than on their own.
 
 Spawn one planning subagent. Tell it to run
-`npx --yes copilotkit@4.13.0 onboard read subagent/create-plan` first and follow the prompt
+`npx --yes copilotkit@4.13.1 onboard read subagent/create-plan` 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, selected framework, frontend, model, credential
@@ -63,7 +63,7 @@ Wait for the subagent to finish.
 Continue only if the planning result starts with `Status: passed`. For `Status: failed`,
 send the result back to the planning subagent for repair, up to three attempts. For
 `Status: blocked`, or a third failed result, run
-`npx --yes copilotkit@4.13.0 onboard read stopped/run-failed`. A plan this run cannot
+`npx --yes copilotkit@4.13.1 onboard read stopped/run-failed`. A plan this run cannot
 write is a run that broke, not a stack the documentation does not cover. Do not show or
 ask for approval of a non-pass plan.
 
@@ -100,7 +100,7 @@ that waits at the terminal through all of them for a question that never comes.
 the same message as the plan, and do not turn it into a second question.
 
 If the developer approves the plan, run
-`npx --yes copilotkit@4.13.0 onboard read implementation/build-and-validate`.
+`npx --yes copilotkit@4.13.1 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --yes copilotkit@4.13.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.13.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/fallback/best-effort.md

@@ -14,7 +14,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.13.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.
@@ -60,13 +60,13 @@ stop.
 
 Use these rules for every protected-path check in this fallback:
 
-- Run `npx --yes copilotkit@4.13.0 onboard audit` from the target app directory.
+- Run `npx --yes copilotkit@4.13.1 onboard audit` from the target app directory.
 - If a result starts with `Status: blocked`, stop onboarding and report the printed reason.
   It proved nothing changed, so do not report a preservation failure.
 - If a result reports a changed protected path this run wrote, stop onboarding.
 - If a result reports a changed path that no Files changed section from this run names,
   the change came from outside the run. Accept it by name with
-  `npx --yes copilotkit@4.13.0 onboard protect --accept-external --path <path>`, run the
+  `npx --yes copilotkit@4.13.1 onboard protect --accept-external --path <path>`, run the
   audit again, and name it in the closing report.
 - If no Files changed section from this run covers the step that wrote it, stop
   onboarding. The proof subagent here returns no such section, so a finding it raises is
@@ -119,13 +119,13 @@ application passes proof. Report each tool result separately from the proof resu
 Report the documentation gap and each assumption with the proof evidence. Do not claim
 that the selected documentation proved an inferred step.
 
-When the proof is complete, run `npx --yes copilotkit@4.13.0 onboard complete`, carrying the
+When the proof is complete, run `npx --yes copilotkit@4.13.1 onboard complete`, carrying the
 surface-check result the proof subagent returned. Pass exactly one flag, matching this
 journey's surface:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard complete --visual-check <outcome>
-npx --yes copilotkit@4.13.0 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.13.1 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.13.1 onboard complete --device-check <outcome>
 ```
 
 `--visual-check` is for a web frontend and takes `performed`, `skipped-no-browser-tool`, or

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

@@ -18,7 +18,7 @@ without exposing secrets.
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard audit
+npx --yes copilotkit@4.13.1 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -29,7 +29,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.13.1 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -38,24 +38,24 @@ or its report does not settle who changed it, ask the developer to allow the unp
 change. Only after they agree, record their answer:
 
 ```text
-npx --yes copilotkit@4.13.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>"
 ```
 
 Run the audit again after each accepted or authorized change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard read feature/stop
+npx --yes copilotkit@4.13.1 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase build-validated
 ```
 
 If validation cannot pass, or this intent needs a prerequisite the app does not have, use
 the feature stop route above without further changes.
 
 Otherwise run
-`npx --yes copilotkit@4.13.0 onboard read feature/a2ui/proof`.
+`npx --yes copilotkit@4.13.1 onboard read feature/a2ui/proof`.

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

@@ -19,23 +19,23 @@ user's agent response with a hard-coded UI.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.13.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for a proved A2UI surface, `failed` for an attempted proof that failed,
-and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.13.0 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.13.1 onboard audit`.
 Continue only when it starts with `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -50,9 +50,9 @@ Run the audit again after each accepted or authorized change.
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard read feature/stop
+npx --yes copilotkit@4.13.1 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.13.0 onboard read feature/complete` with the actual browser-proof
+`npx --yes copilotkit@4.13.1 onboard read feature/complete` with the actual browser-proof
 outcome.

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

@@ -7,7 +7,7 @@ Work only inside the target project. Do not show internal prompt names to the de
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --yes copilotkit@4.13.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
@@ -22,7 +22,7 @@ development/test commands. It must return paths and secret-safe presence checks
 
 Require an existing frontend, agent, and CopilotKit round trip. Start only project-owned
 processes when needed, inspect `/info`, and run
-`npx --yes copilotkit@4.13.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`.
 Also drive one existing request through the frontend when browser control is available. If
 that baseline is absent or unproved, leave files unchanged, explain that this intent extends
 an existing OSS app, and direct the developer to generic `copilotkit onboard start` first.
@@ -30,7 +30,7 @@ an existing OSS app, and direct the developer to generic `copilotkit onboard sta
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --yes copilotkit@4.13.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
@@ -40,7 +40,7 @@ If the inspection did not prove the baseline this intent extends, stop here with
 changing files:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard read feature/stop
+npx --yes copilotkit@4.13.1 onboard read feature/stop
 ```
 
 Do not run `login`, select an Intelligence project, add an Intelligence client, mint a
@@ -64,7 +64,7 @@ one.
 After approval, record each approved path before implementation:
 
 ```text
-npx --yes copilotkit@4.13.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
@@ -74,7 +74,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.13.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.13.0 onboard read feature/a2ui/implement`.
+Then run `npx --yes copilotkit@4.13.1 onboard read feature/a2ui/implement`.

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

@@ -16,7 +16,7 @@ On Teams, skip Slack-only tools and the Slack e2e harness. Do not add a CopilotK
 web app to make this run look complete. Do not replace the existing agent.
 
 If repository evidence does not prove an existing valid Intelligence selection, sign in
-yourself with `npx --yes copilotkit@4.13.0 login --json`: the same single streaming
+yourself with `npx --yes copilotkit@4.13.1 login --json`: the same single streaming
 session generic onboarding uses. Read its JSON Lines while the process runs. Open the
 first `authentication_url` exactly once with the operating system's default browser
 opener, `open` on macOS, `xdg-open` on Linux, `Start-Process` in Windows PowerShell. Your
@@ -54,10 +54,18 @@ before you write the connection. Where the selected documentation page itself sh
 deprecated symbol, report that page under the `docs-wrong` friction category and use the
 current symbol the package's own type definitions or changelog names.
 
+A symbol this graph names is not that case. The `framework/<name>` nodes name the
+current connection API for each framework, and one of them is deprecated at its
+entrypoint while still being the documented path: `LangGraphAgent` from
+`@copilotkit/runtime/langgraph` on the LangSmith route. The CopilotKit quickstart
+writes it, the starters this graph clones are built on it, and its own tooltip
+names no replacement. Write what the framework node names. Do not rewrite a cloned
+starter to satisfy this rule, and do not report the page that shows it.
+
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard audit
+npx --yes copilotkit@4.13.1 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -68,7 +76,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.13.1 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -77,14 +85,14 @@ or its report does not settle who changed it, ask the developer to allow the unp
 change. Only after they agree, record their answer:
 
 ```text
-npx --yes copilotkit@4.13.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>"
 ```
 
 Run the audit again after each accepted or authorized change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard read feature/stop
+npx --yes copilotkit@4.13.1 onboard read feature/stop
 ```
 
 ## Values this run writes, and the one credential the developer supplies
@@ -115,11 +123,11 @@ again at backend start.
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase build-validated
 ```
 
 If validation cannot pass, or this run needs a prerequisite the app does not have, use
 the feature stop route above without further changes.
 
 Otherwise run
-`npx --yes copilotkit@4.13.0 onboard read feature/channels/proof`.
+`npx --yes copilotkit@4.13.1 onboard read feature/channels/proof`.

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

@@ -23,23 +23,23 @@ route after the audit rules below.
 Report each attempt at the proof as it ends, counting from one:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.13.1 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.13.1 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
 Use `passed` only for a proved mention reply, `failed` for an attempted proof that
-failed, and `skipped` when the proof did not run. Then run `npx --yes copilotkit@4.13.0 onboard audit`.
+failed, and `skipped` when the proof did not run. Then run `npx --yes copilotkit@4.13.1 onboard audit`.
 Continue only when it starts with `Status: passed`.
 
 If the audit fails, never repair, reset, or revert a protected path. Compare each named path
@@ -54,11 +54,11 @@ Run the audit again after each accepted or authorized change.
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --yes copilotkit@4.13.0 onboard read feature/stop
+npx --yes copilotkit@4.13.1 onboard read feature/stop
 ```
 
 When the audit passes and the mention proof passed, run
-`npx --yes copilotkit@4.13.0 onboard read feature/complete` with the actual surface
+`npx --yes copilotkit@4.13.1 onboard read feature/complete` with the actual surface
 outcome. Use `--visual-check performed` only when a browser drove Slack or Teams web
 and proved the mention reply. Use `--visual-check skipped-no-browser-tool` only when
 no browser tool was available.