copilotkit 4.10.0 → 4.11.0

package/onboarding/prompts/authenticate/start.md

@@ -5,7 +5,7 @@
 Run this before anything else in this prompt, including the welcome message below:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard identify --coding-agent <coding-agent-slug>
+npx --yes copilotkit@4.11.0 onboard identify --coding-agent <coding-agent-slug>
 ```
 
 Report your own product with one short slug, such as `codex` or `claude-code`.
@@ -37,7 +37,7 @@ Every later command must run from the directory this run started in. A command r
 somewhere else, such as a sibling of that directory, is refused rather than answered,
 because the run it belongs to cannot be found from there. That refusal is a step to take,
 not a stop to report: run
-`npx --yes copilotkit@4.10.0 onboard start --run <onboarding_run_id>` in the directory
+`npx --yes copilotkit@4.11.0 onboard start --run <onboarding_run_id>` in the directory
 you are now in, which binds it to the same run, then run the refused command again. Do not
 start a run without that id. A run started without it is a second run, and the work already
 done stops counting toward the first.
@@ -48,12 +48,18 @@ question from the documentation this graph gives you. Another checkout on this m
 not a source. The developer running this has none, so an answer taken from one is an
 answer they cannot get, and it hides the documentation gap that blocks them.
 
+Say `CopilotKit Intelligence` in full the first time you name the platform, and never the
+bare word `Intelligence`: it names nothing a developer has met yet. In a question, leave
+the product name out and say what they get. This governs what you say, not the flags you
+pass.
+
 Send this exact message once, as your first message in this onboarding run, before
 anything else:
 
 Welcome to CopilotKit. By the end of this run your own application talks to an AI agent,
 and its chat history stays. A user can close the tab, come back, and reopen any past
-conversation in full. The managed Intelligence platform is what keeps them. I prove that
+conversation in full. The managed CopilotKit Intelligence platform is what keeps them. I
+prove that
 round trip in the running app before I call it done. You finish with working software and
 the evidence that it works.
 
@@ -74,15 +80,27 @@ first send, and a developer who reads it repeatedly learns to skim the region it
 Do not ask for separate feedback consent. The feedback commands enforce the developer's
 CLI telemetry setting when a later step tries to send a report.
 
+## Where commands run
+
+Run every command from the directory this run started in. That directory is the run root,
+and every `--path` argument is read against it rather than against wherever you are
+standing, so one path names one file from anywhere in the project.
+
+One command is deliberately different. `project select` writes the credential into the
+`.env` beside the directory it runs in, because that is the file the application process
+loads. Run it from the directory whose application reads that file. It hoists the project
+record to the repository root by itself and prints where it put it.
+
 ## Report a stop, wherever it happens
 
 This run reports its own stops. If you stop this run at any point, send one short report
 before you stop. That covers a stop this prompt names, a stop a later prompt names, and a
-stop no prompt anticipated, including one your own harness causes. Run the friction command without another developer question. The CLI telemetry gate decides whether the report is
-sent.
+stop no prompt anticipated, including one your own harness causes. Run the friction
+command without another developer question. Do not ask the developer about telemetry: the
+command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.11.0 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -97,13 +115,9 @@ Reporting a stop is not a route change. It does not resume the run, it is not a
 for the developer, and it does not replace whatever the rule that stopped you says to do
 next: send the report, then stop.
 
-Until now the route out of an unsupported path was the only place that asked for a report,
-so a stop anywhere else left no trace at all. A stop nobody hears about is a stop this
-graph cannot fix.
-
 ## Check sign-in
 
-Run `npx --yes copilotkit@4.10.0 login --json` before any project work. This command
+Run `npx --yes copilotkit@4.11.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.
 
@@ -139,8 +153,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.10.0 onboard read research/gather`.
+`npx --yes copilotkit@4.11.0 onboard read research/gather`.
 
 If sign-in stops onboarding, run
-`npx --yes copilotkit@4.10.0 onboard read stopped/run-failed`. It says nothing about
+`npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.0 verify --round-trip`, which sends a
+fifth item is proved by `npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.0 onboard read credentials/finalize-plan`.
+Then run `npx --yes copilotkit@4.11.0 onboard read credentials/finalize-plan`.
 
 If a selected page does not load after the second method, run
-`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.

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

@@ -9,21 +9,21 @@ a secret value.
 
 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
-the alternatives short. When project selection is unknown, ask only which Intelligence
-project to use. Keep final plan approval as its own later question.
+the alternatives short. When project selection is unknown, ask only which project to
+use. Keep final plan approval as its own later question.
 
 ## If you stop in this phase
 
 Several rules below stop onboarding: a refused classification value, a project selection
 that reports a false field, a failed credential check, a model credential nobody can
-place. Each one ends a run that reached project selection and never got a plan, and more
-runs stop here than anywhere else. Name the exact file, value, or check that stopped you:
-a report that names only the step cannot be acted on. Send one short report before you
-stop. Run the friction command without another developer question. The CLI telemetry gate
-decides whether the report is sent.
+place. Each one ends a run that reached project selection and never got a plan. Name the
+exact file, value, or check that stopped you: a report that names only the step cannot be
+acted on. Send one short report before you stop. Run the friction command without another
+developer question. Do not ask the developer about telemetry: the command applies the
+setting they already have.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.11.0 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.10.0 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
+npx --yes copilotkit@4.11.0 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
@@ -131,11 +131,14 @@ way to finish.
 ### Create a project for this directory
 
 No project is bound to this directory, so creating a project for this directory is the
-default. Take the name from the directory that holds the expected project-record path. If
-that directory name is generic -- `project`, `app`, `apps`, `src`, `web`, `frontend`,
-`backend`, `server`, `packages`, `repo` -- use the nearest enclosing directory whose name
-is not. A generic name tells the developer nothing later, and every run that derives it
-collides on it.
+default. Take the name from the directory that holds the expected project-record path.
+
+The CLI refuses a name that says nothing: a layer word from `project`, `app`, `apps`,
+`src`, `web`, `frontend`, `backend`, `server`, `packages`, `repo`, a scratch name such as
+`run-a`, `test-2`, or `tmp`, and anything under three characters. When the directory name
+is one of those, use the nearest enclosing directory whose name is not. Ask when no
+enclosing directory passes either: the parent of a scratch directory is usually another
+one, and a second derived guess collides with the first.
 
 Ask one question: confirm that name, give another, or ask to use a project they already
 have. Name that third answer, so a developer who has one is not asked to guess
@@ -149,12 +152,16 @@ a project from a listing without an answer that names it. A project another run
 minutes ago reads exactly like this directory's own, and every check after the selection
 passes against the wrong one.
 
-Create it, from the target directory:
+Create it, from the target directory, passing the port research settled:
 
 ```text
-npx --yes copilotkit@4.10.0 project select --create <name> --json
+npx --yes copilotkit@4.11.0 project select --create <name> \
+  --runtime-url http://localhost:<port>/api/copilotkit --json
 ```
 
+`--runtime-url` is the only place the settled port is written down. Give the URL the
+application serves on, mount path included.
+
 If the command fails as a duplicate, the organization already holds that display name and
 the refusal names the colliding slug. Do not select the colliding project. Ask whether that
 project is this app's. If no developer answers, run the command again with the next free
@@ -166,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.10.0 project list --json
+npx --yes copilotkit@4.11.0 project list --json
 ```
 
 Narrow them:
 
 ```text
-npx --yes copilotkit@4.10.0 project list --search <query> --json
+npx --yes copilotkit@4.11.0 project list --search <query> --json
 ```
 
 With `--json` the payload is the only thing on standard output, so it is safe to parse. Do
@@ -181,10 +188,12 @@ more. Do not order the projects by creation time: the newest project in the orga
 the one another run created while this one was working, and it is the least likely to be
 this directory's.
 
-Then record the project they name, from the target directory:
+Then record the project they name, from the target directory, with the same
+`--runtime-url`:
 
 ```text
-npx --yes copilotkit@4.10.0 project select --project <slug-or-id> --json
+npx --yes copilotkit@4.11.0 project select --project <slug-or-id> \
+  --runtime-url http://localhost:<port>/api/copilotkit --json
 ```
 
 The two flags cannot be combined. A slug that does not exist fails and lists the real ones,
@@ -226,4 +235,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.10.0 onboard read credentials/settle-credentials`.
+`npx --yes copilotkit@4.11.0 onboard read credentials/settle-credentials`.

package/onboarding/prompts/credentials/plan.md

@@ -68,26 +68,26 @@ another framework. Do not show the internal route.
 
 Use exactly one matching internal route:
 
-1. AG2: `npx --yes copilotkit@4.10.0 onboard read framework/ag2`
-2. Agno: `npx --yes copilotkit@4.10.0 onboard read framework/agno`
-3. Built-in CopilotKit agent: `npx --yes copilotkit@4.10.0 onboard read framework/built-in`
-4. Claude Agent SDK Python: `npx --yes copilotkit@4.10.0 onboard read framework/claude-sdk-python`
-5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.10.0 onboard read framework/claude-sdk-typescript`
-6. CrewAI Flows: `npx --yes copilotkit@4.10.0 onboard read framework/crewai-flows`
-7. Deep Agents: `npx --yes copilotkit@4.10.0 onboard read framework/deep-agents`
-8. LangGraph Python: `npx --yes copilotkit@4.10.0 onboard read framework/langgraph-python`
-9. LangGraph FastAPI: `npx --yes copilotkit@4.10.0 onboard read framework/langgraph-fastapi`
-10. LangGraph TypeScript: `npx --yes copilotkit@4.10.0 onboard read framework/langgraph-typescript`
-11. LlamaIndex: `npx --yes copilotkit@4.10.0 onboard read framework/llamaindex`
-12. ADK: `npx --yes copilotkit@4.10.0 onboard read framework/google-adk`
-13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.10.0 onboard read framework/ms-agent-python`
-14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.10.0 onboard read framework/ms-agent-dotnet`
-15. Mastra: `npx --yes copilotkit@4.10.0 onboard read framework/mastra`
-16. MS Agent Harness .NET: `npx --yes copilotkit@4.10.0 onboard read framework/ms-agent-harness-dotnet`
-17. Pydantic AI: `npx --yes copilotkit@4.10.0 onboard read framework/pydantic-ai`
-18. Strands Agents Python: `npx --yes copilotkit@4.10.0 onboard read framework/strands-python`
-19. Strands Agents TypeScript: `npx --yes copilotkit@4.10.0 onboard read framework/strands-typescript`
+1. AG2: `npx --yes copilotkit@4.11.0 onboard read framework/ag2`
+2. Agno: `npx --yes copilotkit@4.11.0 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --yes copilotkit@4.11.0 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --yes copilotkit@4.11.0 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.11.0 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --yes copilotkit@4.11.0 onboard read framework/crewai-flows`
+7. Deep Agents: `npx --yes copilotkit@4.11.0 onboard read framework/deep-agents`
+8. LangGraph Python: `npx --yes copilotkit@4.11.0 onboard read framework/langgraph-python`
+9. LangGraph FastAPI: `npx --yes copilotkit@4.11.0 onboard read framework/langgraph-fastapi`
+10. LangGraph TypeScript: `npx --yes copilotkit@4.11.0 onboard read framework/langgraph-typescript`
+11. LlamaIndex: `npx --yes copilotkit@4.11.0 onboard read framework/llamaindex`
+12. ADK: `npx --yes copilotkit@4.11.0 onboard read framework/google-adk`
+13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.11.0 onboard read framework/ms-agent-python`
+14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.11.0 onboard read framework/ms-agent-dotnet`
+15. Mastra: `npx --yes copilotkit@4.11.0 onboard read framework/mastra`
+16. MS Agent Harness .NET: `npx --yes copilotkit@4.11.0 onboard read framework/ms-agent-harness-dotnet`
+17. Pydantic AI: `npx --yes copilotkit@4.11.0 onboard read framework/pydantic-ai`
+18. Strands Agents Python: `npx --yes copilotkit@4.11.0 onboard read framework/strands-python`
+19. Strands Agents TypeScript: `npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.

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

@@ -7,11 +7,11 @@ not read, show, store, or request a secret value.
 ## If you stop in this phase
 
 Name the exact file, value, or check that stopped you, then send one short report. Run the
-friction command without another developer question. The CLI telemetry gate decides whether
-the report is sent.
+friction command without another developer question. Do not ask the developer about
+telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.11.0 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -47,7 +47,7 @@ skip this step and name the skip, rather than inventing a name.
 Then ask the platform about that id, from the target directory:
 
 ```text
-npx --yes copilotkit@4.10.0 learning containers get <id> --json
+npx --yes copilotkit@4.11.0 learning containers get <id> --json
 ```
 
 The read carries the same availability gate as the create, so it answers the entitlement
@@ -72,7 +72,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.10.0 onboard checkpoint --phase container-surveyed
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase container-surveyed
 ```
 
 Carry the derived id into the planning subagent's handoff, with whether the platform
@@ -102,7 +102,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.10.0 onboard protect --path <path>
+npx --yes copilotkit@4.11.0 onboard protect --path <path>
 ```
 
 Pass one `--path` for each. The command captures a digest for each path and never re-reads
@@ -116,7 +116,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.10.0 onboard protect --rebaseline --path <path>
+npx --yes copilotkit@4.11.0 onboard protect --rebaseline --path <path>
 ```
 
 From that point they are protected like any other path, so a later step that rewrites
@@ -135,7 +135,7 @@ environment path. The command below is what to run at that point, from the targe
 directory:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard protect --accept-credential --path <environment path>
+npx --yes copilotkit@4.11.0 onboard protect --accept-credential --path <environment path>
 ```
 
 The command compares the variable names the baseline recorded with the names the file holds
@@ -150,4 +150,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.10.0 onboard read credentials/write-plan`.
+`npx --yes copilotkit@4.11.0 onboard read credentials/write-plan`.

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

@@ -7,11 +7,11 @@ the run needs from them.
 ## If you stop in this phase
 
 Name the exact file, value, or check that stopped you, then send one short report. Run the
-friction command without another developer question. The CLI telemetry gate decides whether
-the report is sent.
+friction command without another developer question. Do not ask the developer about
+telemetry: the command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.11.0 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.10.0 onboard read subagent/create-plan` first and follow the prompt
+`npx --yes copilotkit@4.11.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
@@ -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.10.0 onboard read stopped/run-failed`. A plan this run cannot
+`npx --yes copilotkit@4.11.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. Do not show or
 ask for approval of a non-pass plan.
 
@@ -87,7 +87,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.10.0 onboard read implementation/build-and-validate`.
+`npx --yes copilotkit@4.11.0 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --yes copilotkit@4.10.0 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.11.0 onboard read unsupported/no-validated-path`.

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

@@ -9,11 +9,12 @@ This fallback contains unproved steps. Use the approved plan in step order.
 
 Several rules below stop onboarding: a blocked or third failed implementation result, a
 changed protected path, a blocked or third failed proof, a fix that needs changes to the
-existing agent or frontend. Send one short report before you stop. Run the friction command without another developer question. The CLI telemetry gate decides whether the
-report is sent.
+existing agent or frontend. Send one short report before you stop. Run the friction
+command without another developer question. Do not ask the developer about telemetry: the
+command applies the setting they already have.
 
 ```text
-npx --yes copilotkit@4.10.0 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.11.0 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.
@@ -59,13 +60,13 @@ stop.
 
 Use these rules for every protected-path check in this fallback:
 
-- Run `npx --yes copilotkit@4.10.0 onboard audit` from the target app directory.
+- Run `npx --yes copilotkit@4.11.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 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.10.0 onboard protect --accept-external --path <path>`, run the
+  `npx --yes copilotkit@4.11.0 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
@@ -118,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.10.0 onboard complete`, carrying the
+When the proof is complete, run `npx --yes copilotkit@4.11.0 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.10.0 onboard complete --visual-check <outcome>
-npx --yes copilotkit@4.10.0 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.11.0 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.11.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.
 After validation and each repair, run:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard audit
+npx --yes copilotkit@4.11.0 onboard audit
 ```
 
 Continue only when it starts with `Status: passed`. A path under `Authorized to change:` 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.10.0 onboard protect --accept-external --path <path>
+npx --yes copilotkit@4.11.0 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.10.0 onboard protect --authorize --unplanned --path <path> --reason "<what the developer said>"
+npx --yes copilotkit@4.11.0 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.10.0 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When implementation validation passes, report it:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase build-validated
+npx --yes copilotkit@4.11.0 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.10.0 onboard read feature/a2ui/proof`.
+`npx --yes copilotkit@4.11.0 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.10.0 onboard checkpoint --phase journey-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase journey-attempted --attempt 1
 ```
 
 Report each repair cycle the same way, counting from one:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard checkpoint --phase repair-attempted --attempt 1
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase repair-attempted --attempt 1
 ```
 
 After the final attempt, report the gate exactly once:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard proof --step round-trip --outcome <passed|failed|skipped>
+npx --yes copilotkit@4.11.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 --yes copilotkit@4.10.0 onboard audit`.
+and `skipped` when the proof could not run. Then run `npx --yes copilotkit@4.11.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
@@ -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.10.0 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 When the audit passes, run
-`npx --yes copilotkit@4.10.0 onboard read feature/complete` with the actual browser-proof
+`npx --yes copilotkit@4.11.0 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.10.0 onboard protect
+npx --yes copilotkit@4.11.0 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.10.0 verify --expect-runtime oss --round-trip --agent <agent-id> --json`.
+`npx --yes copilotkit@4.11.0 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.10.0 onboard checkpoint --phase research-returned
+npx --yes copilotkit@4.11.0 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.10.0 onboard read feature/stop
+npx --yes copilotkit@4.11.0 onboard read feature/stop
 ```
 
 Do not run `login`, select an Intelligence project, add an Intelligence client, mint a
@@ -62,7 +62,7 @@ with one sentence explaining why. Write `None` when it needs none.
 After approval, record each approved path before implementation:
 
 ```text
-npx --yes copilotkit@4.10.0 onboard protect --authorize --path <path> --reason "<the plan's sentence>"
+npx --yes copilotkit@4.11.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
@@ -72,7 +72,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.10.0 onboard checkpoint --phase plan-written
+npx --yes copilotkit@4.11.0 onboard checkpoint --phase plan-written
 ```
 
-Then run `npx --yes copilotkit@4.10.0 onboard read feature/a2ui/implement`.
+Then run `npx --yes copilotkit@4.11.0 onboard read feature/a2ui/implement`.

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

@@ -0,0 +1,70 @@
+# Implement a managed Channel without rewriting a working agent
+
+Delegate implementation to one subagent with the approved plan and fetched official
+Channels guide. Use the already chosen Slack or Teams adapter only as
+`channels add --adapter slack|teams`. Never read, print, synthesize, or add a secret.
+If a required credential variable is missing, stop with that specific setup
+requirement.
+
+If the folder was empty, clone OpenTag from https://github.com/CopilotKit/OpenTag.git
+and do not rewrite it. Point the subagent at the existing OpenTag agent and runtime
+to verify and run. If the project already has an agent or app, do not clone. Keep
+that code and wire a managed Channel.
+
+On Teams, skip Slack-only tools and the Slack e2e harness. Do not add a CopilotKit
+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, give
+the developer `login` to run, wait, then list projects and select or create one only
+after they choose. Require the secret-safe project/key provisioning summary before
+wiring the Channel. Never display a key.
+
+Run `channels add` until it reports completed. Run the focused type/test command and
+start the long-running runtime. Confirm `/info` can return HTTP 200, but treat that
+as capability evidence rather than completed Channel proof. Record changed paths
+and validation results.
+
+After validation and each repair, run:
+
+```text
+npx --yes copilotkit@4.11.0 onboard audit
+```
+
+Continue only when it starts with `Status: passed`. A path under `Authorized to change:` is
+not a finding. Carry it into the final summary with its reason.
+
+If the audit fails, never repair, reset, or revert a protected path. Compare each named path
+with the implementation subagent's `Files changed` section. If that section does not name
+the path, accept the developer's external change:
+
+```text
+npx --yes copilotkit@4.11.0 onboard protect --accept-external --path <path>
+```
+
+For an env file where the developer placed a requested credential, use
+`onboard protect --accept-credential --path <path>` instead. If the subagent names the path,
+or its report does not settle who changed it, ask the developer to allow the unplanned
+change. Only after they agree, record their answer:
+
+```text
+npx --yes copilotkit@4.11.0 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.11.0 onboard read feature/stop
+```
+
+When implementation validation passes, report it:
+
+```text
+npx --yes copilotkit@4.11.0 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.11.0 onboard read feature/channels/proof`.