copilotkit 4.21.0 → 4.22.0

package/onboarding/index.json

@@ -1,5 +1,5 @@
 {
-  "graphTree": "da1c6185427d9e627b0d6a6b6abda10dea05e09a",
+  "graphTree": "035f29b6ead15504507183ff485278d0c9ef6759",
   "intentRoots": {
     "add-a2ui": "feature/a2ui/start",
     "add-chat-suggestions": "feature/chat-suggestions/start",
@@ -43,6 +43,7 @@
         "framework/claude-sdk-python",
         "framework/claude-sdk-typescript",
         "framework/crewai-flows",
+        "framework/custom-ag-ui",
         "framework/deep-agents",
         "framework/langgraph-python",
         "framework/langgraph-fastapi",
@@ -340,6 +341,14 @@
       "milestone": "framework",
       "name": "framework/crewai-flows"
     },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/custom-ag-ui"
+    },
     {
       "edges": [
         "frontend/plan",

package/onboarding/prompts/authenticate/start.md

@@ -14,7 +14,7 @@ does is hidden from the developer.
 
 Run each CLI call exactly as written, as its own command: no pipe, `tee`, `&&`, redirect,
 or variable prefix. Every CLI call in this run matches the prefix rule
-`["npx", "--prefer-offline", "--yes", "copilotkit@4.21.0"]`. If a command can request
+`["npx", "--prefer-offline", "--yes", "copilotkit@4.22.0"]`. If a command can request
 escalation with a prefix rule, request this one on the `onboard identify` call. If your
 harness asks the developer to approve commands, tell them one approval of that prefix covers
 every CLI call. Say then that the install, the dev servers, `curl` to the local app, and
@@ -33,7 +33,7 @@ That refusal is a pause, not a stop.
 Run this before anything else in this prompt, including the welcome message below:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
+npx --prefer-offline --yes copilotkit@4.22.0 onboard identify --coding-agent <coding-agent-slug> --model <model-id> --model-family <model-family>
 ```
 
 Report your own product with one short slug, such as `codex` or `claude-code`.
@@ -62,10 +62,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 --prefer-offline --yes copilotkit@4.21.0 onboard start --run <onboarding_run_id>` where you are
+`npx --prefer-offline --yes copilotkit@4.22.0 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 --prefer-offline --yes copilotkit@4.21.0 onboard start` in the
+If you no longer hold the id, run `npx --prefer-offline --yes copilotkit@4.22.0 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.
@@ -95,15 +95,9 @@ round trip, and leave the app running with its URLs. You finish with working sof
 the evidence that it works.
 
 Everything I need from you comes before that approval: sign-in, a few short setup questions,
-and the plan itself. After you approve it, you can walk away. Building and proving the
-integration is the long part of this run, and I work through it without you. You hear from
-me next when the app is running and I hand you its URLs, or when something stops me and I
-tell you what it was.
-
-If your harness makes the developer approve commands before they run, replace "you can walk
-away" through "without you." with: "I will ask you to approve some commands while I build.
-Keep this window open until the app runs." Decide this from your own approval policy, not
-from your coding-agent slug.
+and the plan itself. After you approve it, I build and prove the integration, which is the
+long part of this run. If I need you to approve a command, or something blocks me, I will ask
+you here. Otherwise you hear from me next when the app is running and I hand you its URLs.
 
 That message belongs to the run, not to this prompt. If you already sent it in this run, do
 not send it again, including on a second read of this prompt.
@@ -132,7 +126,7 @@ the run waits is a pause, not a stop, even when your harness ends it. A terminal
 the report itself, or says to file none, overrides this.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -147,7 +141,7 @@ rule that stopped you says next: send the report, then stop.
 
 ## Check sign-in
 
-Run `npx --prefer-offline --yes copilotkit@4.21.0 login --json` before any project work. This command
+Run `npx --prefer-offline --yes copilotkit@4.22.0 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.
 
@@ -188,8 +182,8 @@ Do not use `whoami` for this check. Do not put account tokens or credentials in
 conversation.
 
 When sign-in is settled, run
-`npx --prefer-offline --yes copilotkit@4.21.0 onboard read research/gather`.
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read research/gather`.
 
 If sign-in stops onboarding, run
-`npx --prefer-offline --yes copilotkit@4.21.0 onboard read stopped/run-failed`. It says nothing about
+`npx --prefer-offline --yes copilotkit@4.22.0 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 --prefer-offline --yes copilotkit@4.21.0 verify --round-trip`, which sends a
+fifth item is proved by `npx --prefer-offline --yes copilotkit@4.22.0 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 --prefer-offline --yes copilotkit@4.21.0 onboard read credentials/finalize-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.22.0 onboard read credentials/finalize-plan`.
 
 If a selected page does not load after the second method, run
-`npx --prefer-offline --yes copilotkit@4.21.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.

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

@@ -24,7 +24,7 @@ Choose the starting state from the repository findings:
 A run served `proof/oss-baseline` records one of the last two.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
+npx --prefer-offline --yes copilotkit@4.22.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
 ```
 
 If a value is refused, fix it from the choices the earlier prompts gave, and run the
@@ -37,7 +37,7 @@ runtime `.env` file, that directory is the target, not the repository root. Do n
 the developer to another terminal.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard credentials --json
+npx --prefer-offline --yes copilotkit@4.22.0 onboard credentials --json
 ```
 
 Every credential this run writes goes to the target's `.env`, the environment path. The
@@ -67,9 +67,9 @@ project from a listing without an answer that names it.
 `--runtime-url` is the URL port research settled, mount path included:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard credentials --create <name> \
+npx --prefer-offline --yes copilotkit@4.22.0 onboard credentials --create <name> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
-npx --prefer-offline --yes copilotkit@4.21.0 onboard credentials --project <slug-or-id> \
+npx --prefer-offline --yes copilotkit@4.22.0 onboard credentials --project <slug-or-id> \
   --runtime-url http://localhost:<port>/api/copilotkit --json
 ```
 
@@ -79,8 +79,8 @@ command unless the developer asks to see their projects, or `notFound` is presen
 show only what they asked for, and do not order it by creation time:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 project list --json
-npx --prefer-offline --yes copilotkit@4.21.0 project list --search <query> --json
+npx --prefer-offline --yes copilotkit@4.22.0 project list --json
+npx --prefer-offline --yes copilotkit@4.22.0 project list --search <query> --json
 ```
 
 `app-directory` means that the key landed where no app reads it. Pick the directory in
@@ -95,4 +95,4 @@ the `--project` command from there with `project.slug`. Do not copy or link the
   reused. The round-trip proof later runs the authenticated Intelligence checks, so record
   the reused project credentials as unverified in the plan until those checks pass.
 
-Then run `npx --prefer-offline --yes copilotkit@4.21.0 onboard read credentials/settle-credentials`.
+Then run `npx --prefer-offline --yes copilotkit@4.22.0 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 --prefer-offline --yes copilotkit@4.21.0 onboard read frontend/plan`.
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read frontend/plan`.
 
 ## Frameworks this machine cannot run yet
 
@@ -42,7 +42,7 @@ things in one message:
 2. That the coding agent's shell reads PATH when it starts, so it cannot see the new
    toolchain until the developer restarts the coding agent.
 3. That the run resumes after the restart with
-   `npx --prefer-offline --yes copilotkit@4.21.0 onboard start --run <onboarding_run_id>`.
+   `npx --prefer-offline --yes copilotkit@4.22.0 onboard start --run <onboarding_run_id>`.
 
 Then end your turn and wait for the developer. That restart is a step here, not an error.
 
@@ -65,6 +65,7 @@ These are the agent frameworks and their default vendors:
 | Claude Agent SDK (Python)          | Anthropic       |
 | Claude Agent SDK (TypeScript)      | Anthropic       |
 | CrewAI Flows                       | Project-defined |
+| Existing AG-UI agent               | The agent's own |
 | Deep Agents                        | OpenAI          |
 | LangGraph FastAPI                  | OpenAI          |
 | LangGraph Python                   | OpenAI          |
@@ -83,9 +84,18 @@ the vendor with the developer: it keeps the one the repository already uses, and
 single question when the repository shows none. Do not read it as a framework this release
 cannot onboard.
 
+"The agent's own" means that the route keeps the vendor the existing agent already uses.
+Ask no vendor question for it.
+
 If the project already has an agent in a listed framework, preserve that framework and
 its model setup. Ask only about choices that remain unknown.
 
+An existing agent that speaks AG-UI, but is none of the other frameworks above, takes the
+Existing AG-UI agent route. For example, an `AbstractAgent` subclass that the project
+wrote, or a service behind AG-UI middleware. Select it only for an agent that the
+repository already has, and only when the findings prove that it speaks AG-UI. Do not
+offer it for a new agent.
+
 If the project needs an agent, show the options and one recommendation based on repository
 evidence. Match the language the repository already uses. Ask the developer to choose.
 
@@ -101,26 +111,27 @@ developer's words instead.
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/ag2`
-2. Agno: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/crewai-flows`
-7. Deep Agents: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/deep-agents`
-8. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/langgraph-python`
-9. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/langgraph-fastapi`
-10. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/langgraph-typescript`
-11. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/llamaindex`
-12. ADK: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/google-adk`
-13. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/ms-agent-python`
-14. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/ms-agent-dotnet`
-15. Mastra: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/mastra`
-16. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/ms-agent-harness-dotnet`
-17. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/pydantic-ai`
-18. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.21.0 onboard read framework/strands-python`
-19. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.21.0 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 --prefer-offline --yes copilotkit@4.21.0 onboard read unsupported/no-validated-path`.
+1. AG2: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/ag2`
+2. Agno: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/crewai-flows`
+7. Existing AG-UI agent: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/custom-ag-ui`
+8. Deep Agents: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/deep-agents`
+9. LangGraph Python: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/langgraph-python`
+10. LangGraph FastAPI: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/langgraph-fastapi`
+11. LangGraph TypeScript: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/langgraph-typescript`
+12. LlamaIndex: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/llamaindex`
+13. ADK: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/google-adk`
+14. Microsoft Agent Framework Python: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/ms-agent-python`
+15. Microsoft Agent Framework .NET: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/ms-agent-dotnet`
+16. Mastra: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/mastra`
+17. MS Agent Harness .NET: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/ms-agent-harness-dotnet`
+18. Pydantic AI: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/pydantic-ai`
+19. Strands Agents Python: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/strands-python`
+20. Strands Agents TypeScript: `npx --prefer-offline --yes copilotkit@4.22.0 onboard read framework/strands-typescript`
+
+If the project has an agent in another framework that does not speak AG-UI, or no
+listed framework fits, keep the developer's current agent and run
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.

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

@@ -21,7 +21,7 @@ The plan names the model credential variables. Run this from the directory that
 `environmentPath` in the project step's result, with one `--model-key` for each variable:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard credentials --model-key <variable> --json
+npx --prefer-offline --yes copilotkit@4.22.0 onboard credentials --model-key <variable> --json
 ```
 
 When the framework node names another env file for the credential, add
@@ -37,7 +37,7 @@ never prints a value. When every key settles, it protects the credential paths.
   list the copy under `Files the run writes itself`, not under `Authorization requested`.
   The developer's approval of the plan is their consent to the copy. Copy the key without
   printing it. Then record the copy with
-  `npx --prefer-offline --yes copilotkit@4.21.0 onboard protect --accept-credential --path <env file>`. If the developer declines the copy, the plan has the app read the key from an
+  `npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --accept-credential --path <env file>`. If the developer declines the copy, the plan has the app read the key from an
   environment variable that the developer sets. The plan then says how to set it. Never
   write the outside path into a project file, not even in a config file such as
   `langgraph.json`. A committed file that names a folder in the developer's home directory
@@ -66,4 +66,4 @@ Never read a file outside the project directory to find a credential: a key foun
 bills another project. Asking for a path is not requesting a secret. A path the developer
 names is theirs to give, including one outside the project. A path this run finds is not.
 
-Then run `npx --prefer-offline --yes copilotkit@4.21.0 onboard read credentials/write-plan`.
+Then run `npx --prefer-offline --yes copilotkit@4.22.0 onboard read credentials/write-plan`.

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

@@ -11,7 +11,7 @@ friction command follows the telemetry setting the developer already chose, so i
 separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -72,7 +72,7 @@ page is selected yet, add the one for the frontend selected above to the same li
    Native, so the planner proves the thread with `verify --round-trip` instead.
 
 Spawn one planning subagent. Tell it to run
-`npx --prefer-offline --yes copilotkit@4.21.0 onboard read subagent/create-plan` first and follow the prompt
+`npx --prefer-offline --yes copilotkit@4.22.0 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
@@ -83,7 +83,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 --prefer-offline --yes copilotkit@4.21.0 onboard read stopped/run-failed`. A plan this run cannot
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read stopped/run-failed`. A plan this run cannot
 write is a run that broke, not a stack the documentation does not cover. The exception is
 a blocked result that names `unsupported/no-validated-path`: the planning subagent found
 that no page supports the plan, so take the no-supported-path route at the end of this
@@ -119,22 +119,14 @@ approve rather than in the implementation that follows. Do not upgrade a depende
 developer did not approve.
 
 When you ask for approval, tell the developer in one line that this is the last thing you
-need from them, and, unless your harness makes the developer approve commands before they
-run, that they can leave the run once they approve. That is a fact about this graph rather
-than a reassurance: no step after approval asks the developer a question unless a step
-cannot be built as approved, and the steps
-that follow are the longest ones in the run. A developer who does not know that waits at
-the terminal through all of them for a question that never comes. Say it in the same
-message as the plan, and do not turn it into a second question.
-
-A command-approval prompt from your harness is not a question from this graph, but the
-build still stops at each one until the developer answers. If your harness raises them,
-replace the leave line with this one: "I will ask you to approve some commands while I
-build. Keep this window open until the app runs." Decide from your own approval policy,
-as the welcome did, not from your coding-agent slug.
+need from them, and that if you need them to approve a command, or something blocks you, you
+will ask them here. Do not predict whether that will happen: no step after approval asks the
+developer a question unless a step cannot be built as approved, but a harness can still hold
+a command for approval. Say it in the same message as the plan, and do not turn it into a
+second question.
 
 If the developer approves the plan, run
-`npx --prefer-offline --yes copilotkit@4.21.0 onboard read implementation/build-and-validate`.
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --prefer-offline --yes copilotkit@4.21.0 onboard read unsupported/no-validated-path`.
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read unsupported/no-validated-path`.

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

@@ -16,7 +16,7 @@ you stop. The friction command follows the telemetry setting the developer alrea
 so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -62,19 +62,19 @@ or frontend, stop onboarding.
 
 Use these rules for every protected-path check in this fallback:
 
-- Run `npx --prefer-offline --yes copilotkit@4.21.0 onboard audit` from the target app directory.
+- Run `npx --prefer-offline --yes copilotkit@4.22.0 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 env file, this rule replaces the one above, even when this
   run wrote the file. This run asked the developer to place a
   credential there, so take the credential route rather than the external one. Accept it
-  with `npx --prefer-offline --yes copilotkit@4.21.0 onboard protect --accept-credential --path <path>`,
+  with `npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --accept-credential --path <path>`,
   run the audit again, and name it in the closing report. If the command refuses because
   it names a lost variable, stop onboarding.
 - Before any proof subagent runs, a changed path that no Files changed section from this
   run names came from outside the run. Accept it by name with
-  `npx --prefer-offline --yes copilotkit@4.21.0 onboard protect --accept-external --path <path>`, run the
+  `npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --accept-external --path <path>`, run the
   audit again, and name it in the closing report.
 - After a proof subagent runs, a changed path that no Files changed section from this run
   names is unsettled rather than outside the run, because the proof subagent here returns
@@ -133,16 +133,16 @@ that the selected documentation proved an inferred step.
 Record what the proof returned before you complete:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.22.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
 ```
 
-When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.21.0 onboard complete`, carrying the
+When the proof is complete, run `npx --prefer-offline --yes copilotkit@4.22.0 onboard complete`, carrying the
 surface-check result the proof subagent returned. Pass exactly one of `--visual-check` or
 `--device-check`, matching this journey's surface:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard complete --visual-check <outcome>
-npx --prefer-offline --yes copilotkit@4.21.0 onboard complete --device-check <outcome>
+npx --prefer-offline --yes copilotkit@4.22.0 onboard complete --visual-check <outcome>
+npx --prefer-offline --yes copilotkit@4.22.0 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.
 Before you spawn the implementation subagent, take the authorized list from the CLI:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.22.0 onboard audit
 ```
 
 From its result, copy the paths under `Authorized to modify:`. A passed or failed audit with
@@ -37,7 +37,7 @@ still go on the record. Name the file and why the work needs it, then end your t
 for the developer's answer. If they allow it, record their answer before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -49,7 +49,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.22.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -60,7 +60,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -73,11 +73,11 @@ Run the audit again after each accepted change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/stop
 ```
 
 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 --prefer-offline --yes copilotkit@4.21.0 onboard read feature/a2ui/proof`.
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/a2ui/proof`.

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

@@ -27,7 +27,7 @@ still go on the record. Name the file and why the fix needs it, then end your tu
 for the developer's answer. If they allow it, record their answer before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -40,11 +40,11 @@ Report the outcome of each attempt as it ends, before any repair. The command co
 attempts and the repairs:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --prefer-offline --yes copilotkit@4.22.0 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 --prefer-offline --yes copilotkit@4.21.0 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --prefer-offline --yes copilotkit@4.22.0 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
@@ -59,9 +59,9 @@ the path and the change the audit reports. Run the audit again after each accept
 If the audit still fails, or starts with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --prefer-offline --yes copilotkit@4.21.0 onboard read feature/complete` with the actual browser-proof
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/complete` with the actual browser-proof
 outcome.

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

@@ -21,13 +21,13 @@ carry on. Keep a read-only assignment read-only. If no subagent works at all, re
 once:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard checkpoint --phase delegation-unavailable
+npx --prefer-offline --yes copilotkit@4.22.0 onboard checkpoint --phase delegation-unavailable
 ```
 
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard checkpoint --phase awaiting-developer
+npx --prefer-offline --yes copilotkit@4.22.0 onboard checkpoint --phase awaiting-developer
 ```
 
 A turn that ends while the run waits is a pause, not a stop, even when your harness ends it.
@@ -37,7 +37,7 @@ If you stop this run, send one short report before you stop. The friction comman
 the telemetry setting the developer already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.22.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.
@@ -51,7 +51,7 @@ one scoped fix, and sends the report itself when no fix is approved.
 Before any subagent or project process runs, capture the developer's existing work:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard protect
+npx --prefer-offline --yes copilotkit@4.22.0 onboard protect
 ```
 
 Keep the exact protected path list it prints and give that list to every subagent. No
@@ -66,20 +66,20 @@ 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 --prefer-offline --yes copilotkit@4.21.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`.
+`npx --prefer-offline --yes copilotkit@4.22.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`.
 Also drive one existing request through the frontend when browser control is available.
 
 Wait for the inspection subagent to finish. Then report that the inspection came back:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard checkpoint --phase research-returned
+npx --prefer-offline --yes copilotkit@4.22.0 onboard checkpoint --phase research-returned
 ```
 
 If the inspection did not prove the baseline this intent extends, stop here without
 changing files:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/stop
 ```
 
 Do not run `login`, select an Intelligence project, add an Intelligence client, mint a
@@ -103,11 +103,11 @@ one.
 After approval, record each approved path before implementation:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
 ```
 
 If an approved path changed after capture and no implementation step has run, add
 `--with-prior-change`. Continue only when every result starts with `Status: passed`. Do not
 authorize a path the approved plan did not list.
 
-Then run `npx --prefer-offline --yes copilotkit@4.21.0 onboard read feature/a2ui/implement`.
+Then run `npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/a2ui/implement`.

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

@@ -19,7 +19,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 --prefer-offline --yes copilotkit@4.21.0 login --json`: the same single streaming
+yourself with `npx --prefer-offline --yes copilotkit@4.22.0 login --json`: the same single streaming
 session generic onboarding uses. Read its JSON Lines while the process runs. The CLI opens
 the page itself when it can: with `"browser_opened": false` in `action_required`, show the
 developer the clickable URL and ask them to finish sign-in there. If the record carries
@@ -75,7 +75,7 @@ starter to satisfy this rule, and do not report the page that shows it.
 Before you spawn the implementation subagent, take the authorized list from the CLI:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.22.0 onboard audit
 ```
 
 From its result, copy the paths under `Authorized to modify:`. A passed or failed audit with
@@ -94,7 +94,7 @@ still go on the record. Name the file and why the work needs it, then end your t
 for the developer's answer. If they allow it, record their answer before any edit:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
 ```
 
 Continue only when the result starts with `Status: passed`. Run the audit again, take the
@@ -106,7 +106,7 @@ feature stop route below.
 After validation and each repair, run:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard audit
+npx --prefer-offline --yes copilotkit@4.22.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to modify:` is
@@ -117,7 +117,7 @@ with the implementation subagent's `Files changed` section. If that section does
 the path, accept the developer's external change:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard protect --accept-external --path <path>
+npx --prefer-offline --yes copilotkit@4.22.0 onboard protect --accept-external --path <path>
 ```
 
 For an env file where the developer placed a requested credential, use
@@ -130,7 +130,7 @@ Run the audit again after each accepted change. If it still fails, or starts
 with `Status: blocked`, route out and stop:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.21.0 onboard read feature/stop
+npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/stop
 ```
 
 ## Values this run writes, and the one credential the developer supplies
@@ -167,4 +167,4 @@ If validation cannot pass, or this run needs a prerequisite the app does not hav
 the feature stop route above without further changes.
 
 Otherwise run
-`npx --prefer-offline --yes copilotkit@4.21.0 onboard read feature/channels/proof`.
+`npx --prefer-offline --yes copilotkit@4.22.0 onboard read feature/channels/proof`.