copilotkit 4.9.17 → 4.9.31

package/onboarding/index.json

@@ -1,5 +1,5 @@
 {
-  "graphTree": "613209959e8d5888a5770391381eeb0055fbe68d",
+  "graphTree": "4d505cf0b83ae312e7331fdaca811ef5959d69c2",
   "root": "authenticate/start",
   "prompts": [
     {

package/onboarding/prompts/authenticate/start.md

@@ -16,7 +16,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.9.17 onboard start --run <onboarding_run_id>` in the directory
+`npx --yes copilotkit@4.9.31 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.
@@ -50,7 +50,7 @@ without another developer question. The CLI telemetry gate decides whether the r
 sent.
 
 ```text
-npx --yes copilotkit@4.9.17 onboard feedback
+npx --yes copilotkit@4.9.31 onboard feedback
 ```
 
 Write at most four lines to the command's standard input: the step you stopped at and what
@@ -67,7 +67,7 @@ Until now the route out of an unsupported path was the only place that asked for
 so a stop anywhere else left no trace at all. A stop nobody hears about is a stop this
 graph cannot fix.
 
-Run `npx --yes copilotkit@4.9.17 login --json` before any project work. This command
+Run `npx --yes copilotkit@4.9.31 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.
 
@@ -84,11 +84,30 @@ Read each JSON Lines record as the running command writes it:
 Do not use `whoami` for this check. It has no JSON output and some failures exit with code
 zero. Do not put account tokens or credentials in the conversation.
 
+## How to wait for a subagent
+
+This rule covers every subagent this run spawns, here and in every later prompt.
+
+Spawning a subagent returns almost at once. That return is the dispatch succeeding, not the
+work finishing: the subagent runs in the background, and its result reaches you as a
+notification. Where your own harness hands you the report from the dispatch itself instead,
+you already hold the result. Either way there is nothing to poll.
+
+After you dispatch, do the work that does not depend on the result -- dispatch the other
+subagent, run the preflight below -- and then stop and wait. Wherever a prompt in this graph
+says to wait for a subagent to finish, that is what it means.
+
+Do not sleep to pass the time. Not `sleep`, not `/bin/sleep`, not a timer under another
+name, and not a loop that re-checks whether a result has arrived. Sleeping tells you nothing
+that waiting for the result does not, and it spends wall clock, which is one of the things
+this journey is measured on. One recorded run spent most of two hours asleep between
+dispatches that had all returned in seconds.
+
 Before you ask the developer any setup question, finish every read-only investigation and
 preflight check in this section.
 
 Prepare two research assignments. Give each research subagent one assignment. Tell it to run
-`npx --yes copilotkit@4.9.17 onboard read subagent/inspect-repository` first and follow the
+`npx --yes copilotkit@4.9.31 onboard read subagent/inspect-repository` 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. Require only its assigned packet.
@@ -171,7 +190,7 @@ both workers return the same one target app directory. Both results must start w
 Before you route on, run this from the target app directory:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard protect
+npx --yes copilotkit@4.9.31 onboard protect
 ```
 
 It reads the working tree itself, records every changed or untracked path with a digest,
@@ -213,7 +232,7 @@ settle these three from your own reading of the project. Each one comes from the
 packets or it is not proved.
 
 If all three are proved, prove the live starting state before any project file changes. Run
-`npx --yes copilotkit@4.9.17 onboard read proof/oss-baseline`.
+`npx --yes copilotkit@4.9.31 onboard read proof/oss-baseline`.
 
 Route there before you ask the developer anything else. The questions after this prompt
 select a framework and a frontend that the findings already name, so a developer who
@@ -226,10 +245,10 @@ developer nor the repository findings prove what the project is for, ask one gui
 question about the user outcome. This asks what the developer wants to build before you
 select a framework. Give two or three short examples and offer a minimal starter. Record
 the answer and give it to each later subagent. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/plan`.
+`npx --yes copilotkit@4.9.31 onboard read credentials/plan`.
 
 Do not ask that question on the route above. A project carrying all three states its
 purpose in the application it already serves.
 
 If authentication or inspection stops onboarding, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/conversion/plan.md

@@ -52,9 +52,9 @@ Then select the drawer page for the frontend the baseline found:
 1. React SPA or Next.js: https://docs.copilotkit.ai/prebuilt-components/copilot-threads-drawer.md
 2. Angular: https://docs.copilotkit.ai/angular/guides/threads-memory-attachments-headless.md
 3. Vue 3: https://docs.copilotkit.ai/vue/guides/threads-and-drawer.md
-4. React Native: select no drawer page, and select the managed Intelligence dashboard as
-   the proof surface instead. No page documents a threads drawer for React Native, and
-   `@copilotkit/react-native` ships no thread components. The closing prompt gives a
+4. React Native: select no drawer page. No page documents a threads drawer for React
+   Native, and `@copilotkit/react-native` ships no thread components, so the fifth
+   criterion below is proved on the command line instead. The closing prompt gives a
    mobile developer a different debugging surface for the same reason.
 
 The next prompt adds the runtime pages and fetches everything in one pass, so do not fetch
@@ -79,25 +79,36 @@ steps unchanged. This conversion succeeded when all five are true:
 1. The same request the OSS baseline made still produces the same kind of user-visible
    result, on the same frontend.
 2. The runtime is constructed with an `intelligence` option rather than a `runner` option.
-3. `verify --json` exits zero with `ok` true and all seven checks passing, including
-   `intelligence_consumed` and `intelligence_thread_routes`.
+3. `verify --json` exits zero with `ok` true and every check passing, including
+   `intelligence_consumed`, `intelligence_thread_routes`, and
+   `api_key_loadable_by_app`.
 4. `/info` now reports `licenseStatus`, which the runtime emits exactly when an
    Intelligence client was constructed and passed.
 5. A thread for that request is persisted and visible to the developer.
 
 The drawer is what makes the fifth item something the developer can see. Before the
-conversion it renders its locked state, because it reads the license context and this
-project has none. After it, it lists the thread the proven request created. That before and
-after is the conversion's whole user-visible result, and it is why a conversion that only
-passes the command-line checks is worth less to the developer than one that does not.
+conversion it lists nothing, because it reads the entitlement the runtime reports and an
+OSS runtime reports none. After it, it lists the thread the proven request created. That
+before and after is the conversion's whole user-visible result, and it is why a conversion
+that only passes the command-line checks is worth less to the developer than one that does
+not.
+
+A managed Intelligence project needs no license token. The entitlement the drawer reads
+comes from the project API key this run already configured, resolved by the runtime
+against the managed platform. Minting a token with `copilotkit license create` is not part
+of this journey, and a drawer that lists nothing is not a reason to mint one. License
+tokens stay a self-hosted concern.
 
 Where this journey's frontend framework ships no threads drawer -- React Native --, the
-fifth item is proved in the managed Intelligence dashboard instead, and the run says which
-of the two it proved.
+fifth item is proved by `npx --yes copilotkit@4.9.31 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
+cannot produce, so a criterion that asks for one can never be met on this route.
 
 Record this criterion as `conversion-v1` for the run report.
 
-Then run `npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+Then run `npx --yes copilotkit@4.9.31 onboard read credentials/finalize-plan`.
 
 If a selected page does not load after the second method, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

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

@@ -14,15 +14,16 @@ 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, an output path that
-overlaps a protected path, 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. Send
-one short report before you stop. Run the feedback command without another developer
-question. The CLI telemetry gate decides whether the report is sent.
+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 feedback command without another developer question. The CLI telemetry gate
+decides whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.17 onboard feedback
+npx --yes copilotkit@4.9.31 onboard feedback
 ```
 
 Write at most four lines to standard input: the step you stopped at and what stopped it.
@@ -45,7 +46,7 @@ starts. Choose one starting state: empty, agent-only, frontend-only, both, both-
 Run this command with the exact selected slugs:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
+npx --yes copilotkit@4.9.31 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
@@ -57,6 +58,36 @@ Use the target app or runtime directory from the repository findings. If a neste
 the runtime `.env` file, do not default to the repository root.
 Set the environment path to `<target>/.env`.
 
+Every credential this run writes goes to the environment path. That covers the project
+key, the model credential, and a license token. Do not write a credential to `.env.local`,
+or to any second env file beside it. A project ignore file usually covers `.env` and not
+`.env.local`, so a credential written there is untracked, visible, and added by the first
+`git add -A`. And a second env file beside `.env` outranks it when a key is read back, so
+the value the run depends on is the one it did not write.
+
+### Prove the environment path is ignored
+
+Do this before the first credential is written. Ask git whether it ignores the environment
+path, from the repository the path lives in:
+
+```text
+git check-ignore -q <environment path>
+```
+
+Ask git rather than reading `.gitignore`. The answer also comes from a parent ignore file,
+a global excludes file, or a pattern the developer already has, and reading one file gets
+each of those wrong.
+
+Exit zero means git ignores the path and nothing more is needed. Exit one means git tracks
+the path, and the credential this run is about to write lands in the first commit. Add the
+missing pattern to the ignore file the developer already keeps, and list that edit in the
+plan with every other file change. Any other exit means there is no work tree here to
+protect. Say so once and carry on.
+
+If the path cannot be made ignored, stop onboarding and report it. Do not write the
+credential and leave the problem in the closing report. A developer who commits before
+reading the last screen has already published the token.
+
 If valid project fields and a non-empty `CPK_INTELLIGENCE_API_KEY` already exist, use this
 rule: Reuse that project without another question. Do not mint another key. The round-trip
 proof later runs the authenticated Intelligence checks. Record the reused project
@@ -64,57 +95,100 @@ credentials as unverified in the plan until those checks pass.
 If you reuse a project, set the project-record path to the exact evidence path from the
 project research subagent.
 
-If the developer needs a project or another project, do the selection yourself from the
-target directory. Do not send the developer to another terminal.
+If the developer needs a project, do the work yourself from the target directory.
+Do not send the developer to another terminal.
+
+Project selection writes the environment path. It updates the nearest project record from
+the target through the repository root. If no project record exists there, it writes one at
+the repository root. If no repository exists, use the target. If the repository root is the
+home directory, use the target.
 
-Read the choices first:
+Before project selection, derive the expected project-record path from the repository
+findings. Compare that path and the environment path with the paths the first capture
+printed as `protected`. Use the path-segment overlap rule. Ignore every path it printed as
+`deferred`. Those are the files project selection exists to write, so the environment path
+always overlaps one of them, and a run that stops on that overlap never reaches the step
+that provisions its key.
+
+If an output path overlaps a `protected` path, do not stop. Name the path, say what
+project selection writes there, list that file in the plan with every other change, and
+carry on. Nothing before project selection ends the run. It is the step that provisions
+this project's key, so a run that stops earlier leaves the developer with no key and no
+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.
+
+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
+that it is available. Do not list the organization's projects as part of the question: a
+menu of projects is what bound one onboarding to another one's project, and a developer who
+wants theirs will say so. If they ask for an existing project, take the branch below.
+
+Do not combine this question with a frontend, framework, model, credential, or
+plan-approval question. If no developer answers, create with the derived name. Never select
+a project from a listing without an answer that names it. A project another run created
+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:
 
 ```text
-npx --yes copilotkit@4.9.17 project list --json
+npx --yes copilotkit@4.9.31 project select --create <name> --json
 ```
 
-With `--json` the payload is the only thing on standard output, so it is safe to parse.
-Show the current selection and the five most recent projects. Sort recency by `createdAt`.
-Offer search, create-new, and list-all options. Do not show every project unless the
-developer asks.
+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
+`-2`, `-3` suffix on the name.
 
-If the developer searches, run:
+### Select an existing project instead
+
+Take this branch only when the developer asks for an existing project, or asks to see the
+projects they have. Read the choices:
 
 ```text
-npx --yes copilotkit@4.9.17 project list --search <query> --json
+npx --yes copilotkit@4.9.31 project list --json
 ```
 
-If the developer asks for all projects, show the result of the first list command. Ask
-which project to use, or ask for a new project name. Do not combine this question with a
-frontend, framework, model, credential, or plan-approval question.
+Narrow them:
 
-Project selection writes the environment path. It updates the nearest project record from
-the target through the repository root. If no project record exists there, it writes one at
-the repository root. If no repository exists, use the target. If the repository root is the
-home directory, use the target.
+```text
+npx --yes copilotkit@4.9.31 project list --search <query> --json
+```
 
-Before project selection, derive the expected project-record path from the repository
-findings. Compare that path and the environment path with the initial protected paths. Use
-the path-segment overlap rule. If either output path overlaps an initial protected path, do
-not run project selection. Report the conflicting path and stop onboarding.
+With `--json` the payload is the only thing on standard output, so it is safe to parse. Do
+not run either list command unless the developer asks. Show what they asked for and nothing
+more. Do not order the projects by creation time: the newest project in the organization is
+the one another run created while this one was working, and it is the least likely to be
+this directory's.
 
-Then record their answer, from the target directory:
+Then record the project they name, from the target directory:
 
 ```text
-npx --yes copilotkit@4.9.17 project select --project <slug-or-id> --json
+npx --yes copilotkit@4.9.31 project select --project <slug-or-id> --json
 ```
 
-Use `--create <name> --json` instead when they want a new project. The two flags cannot be
-combined. A slug that does not exist fails and lists the real ones, so a typo cannot record
-a selection that points at nothing.
+The two flags cannot be combined. A slug that does not exist fails and lists the real ones,
+so a typo cannot record a selection that points at nothing.
 
 Read the JSON result. It reports `selected_project_slug`, `config_path`,
 `api_key_provisioned`, `project_file_written`, and `environment_file_written` at the top
 level. The result does not contain a secret. Report `selected_project_slug` as the project
 slug that the server selected or created. Require `api_key_provisioned`,
-`project_file_written`, and `environment_file_written` to be true. If one is false, report
-the error and stop onboarding. Key provisioning is non-fatal, so the command can persist a
-selection and still exit zero with no key. A scaffold with no key looks finished and is not.
+`project_file_written`, and `environment_file_written` to be true.
+
+A run that wrote the project record without a key exits 75 and reports `"type": "partial"`
+with a `retry_command`. That is the recoverable half: the record is kept, and the failure
+is usually transient. Run the `retry_command` once. If the retry also reports
+`api_key_provisioned` false, report the error and stop onboarding.
+A scaffold with no key looks finished and is not.
 
 After project selection, set the project-record path to the absolute `config_path` from the
 JSON result. If it differs from the expected project-record path, report both paths and stop
@@ -162,7 +236,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.9.17 onboard protect --path <path>
+npx --yes copilotkit@4.9.31 onboard protect --path <path>
 ```
 
 Pass one `--path` for each. The command captures a digest for each path and never re-reads
@@ -172,7 +246,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.9.17 onboard protect --rebaseline --path <path>
+npx --yes copilotkit@4.9.31 onboard protect --rebaseline --path <path>
 ```
 
 From that point they are protected like any other path, so a later step that rewrites
@@ -196,7 +270,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.9.17 onboard read subagent/create-plan` first and follow the prompt
+`npx --yes copilotkit@4.9.31 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
@@ -212,17 +286,17 @@ ask for approval of a non-pass plan.
 Make sure that the plan preserves each part that already exists. The plan must name the
 credential variables, the Intelligence runtime wiring, the application the project asks
 for, implementation steps, validation steps, and proof steps. Where the plan upgrades the
-CopilotKit dependencies, it must name the versions it moves and the revert it falls back
-to. It must not contain secret values.
+CopilotKit dependencies, it must name the versions it moves, every other pin it has to
+move with them, and the revert it falls back to. It must not contain secret values.
 
-Show only the selected framework, frontend, model, planned file changes, the CopilotKit dependency upgrade and the versions it moves, validation commands, and proof steps.
+Show only the selected framework, frontend, model, planned file changes, any ignore-file line this run adds, the CopilotKit dependency upgrade and the versions it moves, every other dependency the upgrade moves and the versions it moves them to, validation commands, and proof steps.
 
 An upgrade to a working install is the developer's call, so it belongs in the plan they
 approve rather than in the implementation that follows. Do not upgrade a dependency the
 developer did not approve.
 
 If the developer approves the plan, run
-`npx --yes copilotkit@4.9.17 onboard read implementation/build-and-validate`.
+`npx --yes copilotkit@4.9.31 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

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

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

@@ -14,7 +14,7 @@ command without another developer question. The CLI telemetry gate decides wheth
 report is sent.
 
 ```text
-npx --yes copilotkit@4.9.17 onboard feedback
+npx --yes copilotkit@4.9.31 onboard feedback
 ```
 
 Write at most four lines to standard input: the step you stopped at and what stopped it.
@@ -40,7 +40,8 @@ from different official pages. Tell it to run every implementation and validatio
 plan order, and to run the full validation list.
 
 Give it this result format: Start with `Status: passed`, `Status: failed`, or
-`Status: blocked`.
+`Status: blocked`. Then require a Files changed section that names every file it touched.
+The protected-path rules below read that section, so a result without it settles nothing.
 
 Wait for the implementation subagent to finish.
 
@@ -55,10 +56,17 @@ stop.
 
 Use these rules for every protected-path check in this fallback:
 
-- Run `npx --yes copilotkit@4.9.17 onboard audit` from the target app directory.
+- Run `npx --yes copilotkit@4.9.31 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, stop onboarding.
+- 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.9.31 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
+  unsettled rather than outside the run.
 - Never repair, reset, or revert a protected path.
 
 Run the protected-path check now. Apply the protected-path rules. Continue only when the
@@ -107,13 +115,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.9.17 onboard complete`, carrying the
+When the proof is complete, run `npx --yes copilotkit@4.9.31 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.9.17 onboard complete --visual-check <outcome>
-npx --yes copilotkit@4.9.17 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.9.31 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.9.31 onboard complete --device-check <outcome>
 ```
 
 `--visual-check` is for a web frontend and takes `performed`, `skipped-no-browser-tool`, or
@@ -122,6 +130,7 @@ or `failed`. Anything but `performed` ends this run as blocked, and the command'
 names the evidence that is missing. Report it that way.
 
 If the proof passed and something after it still blocked this run, add
-`--blocked-by <cause>` to the same command, with one of `hosted-dashboard`, `inspector`,
-`plan-excluded-capability`, or `other`. It ends the run as blocked and names what the
-blocker leaves unverified.
+`--blocked-by <cause>` to the same command, with one of `inspector`, `plan-excluded-capability`,
+or `other`. It ends the run as blocked and names what the blocker leaves unverified. The
+managed Intelligence dashboard is not a cause, because nothing in this graph asks a run to
+open it.

package/onboarding/prompts/framework/ag2.md

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

package/onboarding/prompts/framework/agno.md

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

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

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

package/onboarding/prompts/framework/claude-sdk-python.md

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

package/onboarding/prompts/framework/claude-sdk-typescript.md

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

package/onboarding/prompts/framework/crewai-flows.md

@@ -54,7 +54,7 @@ variable names the repository proves or the developer named, these URLs, the ada
 shared-state limit.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

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

@@ -29,7 +29,7 @@ Record the selected framework, language, vendor, model, required credential vari
 names, these URLs, and each documentation gap.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.

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

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

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

@@ -24,7 +24,7 @@ Record the selected framework, vendor, model, required credential variable names
 these URLs.
 
 If the pages support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read frontend/plan`.
+`npx --yes copilotkit@4.9.31 onboard read frontend/plan`.
 
 If the documentation does not support the selection, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.31 onboard read unsupported/no-validated-path`.