copilotkit 4.9.17 → 4.9.24

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

@@ -27,7 +27,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, 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.24 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.24 onboard read unsupported/no-validated-path`.

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

@@ -28,7 +28,7 @@ Record the selected framework, vendor, model, required credential variable names
 URLs, 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.24 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.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/angular.md

@@ -5,7 +5,7 @@ Preserve an existing Angular frontend. Use the selected page for a new frontend.
 Use the starter shortcut only if all these facts are true: the target directory contains
 no entries, its name is a valid `init` project name, and the selected framework is ADK.
 If all three facts are true, record Angular as the selected frontend. Then run
-`npx --yes copilotkit@4.9.17 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.9.24 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -35,7 +35,7 @@ you create or build an Angular project. If the installed version is lower, selec
 supported version first and use it for every later command in this project.
 
 If the pages support the selection, record Angular and these URLs. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.24 onboard read credentials/finalize-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.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/nextjs.md

@@ -15,7 +15,7 @@ These TypeScript options have starters: Claude Agent SDK TypeScript, LangGraph T
 Mastra, and Strands Agents TypeScript. The .NET option is Microsoft Agent Framework .NET.
 
 If all shortcut conditions are true, record Next.js as the selected frontend. Then run
-`npx --yes copilotkit@4.9.17 onboard read starter/clone` before you fetch documentation.
+`npx --yes copilotkit@4.9.24 onboard read starter/clone` before you fetch documentation.
 
 ## Documentation
 
@@ -27,7 +27,7 @@ agent as the default agent, which is correct only for a project that has no agen
 Do not replace the developer's existing agent with the built-in agent.
 
 If the page supports the selection, record Next.js and this URL. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.24 onboard read credentials/finalize-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.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/plan.md

@@ -24,11 +24,11 @@ process.
 
 Use exactly one matching internal route:
 
-1. React SPA: `npx --yes copilotkit@4.9.17 onboard read frontend/react-spa`
-2. Next.js: `npx --yes copilotkit@4.9.17 onboard read frontend/nextjs`
-3. Angular: `npx --yes copilotkit@4.9.17 onboard read frontend/angular`
-4. Vue 3: `npx --yes copilotkit@4.9.17 onboard read frontend/vue`
-5. React Native: `npx --yes copilotkit@4.9.17 onboard read frontend/react-native`
+1. React SPA: `npx --yes copilotkit@4.9.24 onboard read frontend/react-spa`
+2. Next.js: `npx --yes copilotkit@4.9.24 onboard read frontend/nextjs`
+3. Angular: `npx --yes copilotkit@4.9.24 onboard read frontend/angular`
+4. Vue 3: `npx --yes copilotkit@4.9.24 onboard read frontend/vue`
+5. React Native: `npx --yes copilotkit@4.9.24 onboard read frontend/react-native`
 
 If no listed frontend fits, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-native.md

@@ -15,7 +15,7 @@ documents `useRenderTool`, which is React Native's own hook for drawing a tool t
 already has. That is a different job and needs a tool in the agent.
 
 If the pages support the selection, record React Native and these URLs. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.24 onboard read credentials/finalize-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.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/react-spa.md

@@ -11,7 +11,7 @@ not move the agent into it.
 - https://docs.copilotkit.ai/react-spa.md
 
 If the page supports the selection, record React SPA and this URL. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.24 onboard read credentials/finalize-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.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/frontend/vue.md

@@ -16,7 +16,7 @@ page above. Vue has its own `useComponent`, which is not the React package. Take
 that reference page rather than from a Vue generative-UI guide, which is not published.
 
 If the pages support the selection, record Vue 3 and these URLs. Then run
-`npx --yes copilotkit@4.9.17 onboard read credentials/finalize-plan`.
+`npx --yes copilotkit@4.9.24 onboard read credentials/finalize-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.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/implementation/build-and-validate.md

@@ -7,7 +7,7 @@ Do not implement the plan yourself. Use the step order in the approved plan.
 Run the audit from the target app directory:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard audit
+npx --yes copilotkit@4.9.24 onboard audit
 ```
 
 It compares every protected path with the digest the CLI captured for it. Its result starts
@@ -25,7 +25,7 @@ protected path as changed. Report the printed reason and use the route-out rules
 A non-pass audit never continues the run. Do not send an audit result to a repair worker.
 
 Spawn one implementation subagent. Tell it to run
-`npx --yes copilotkit@4.9.17 onboard read subagent/implement-and-validate` first and follow
+`npx --yes copilotkit@4.9.24 onboard read subagent/implement-and-validate` first and follow
 the prompt it returns. If that read fails because the subagent cannot use the shell, stop that
 subagent. Run the same command yourself, then spawn a fresh subagent with the returned prompt
 and the same handoff. Give it the plan, selected framework, frontend, model, exact target app
@@ -42,7 +42,7 @@ Run the protected-path audit after the implementation subagent passes. If any pr
 changed, use the route-out rules. Continue to proof only when that audit passes.
 
 After the selected implementation path passes, run
-`npx --yes copilotkit@4.9.17 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.9.24 onboard read proof/round-trip`.
 
 ## Repair rules
 
@@ -60,4 +60,4 @@ Route out for `Status: blocked`. Route out only when the failure is not yours to
 failure is in code this run did not write, the fix requires changing the developer's existing
 agent or frontend, the same command still fails after three repair attempts, or the
 documentation does not support the plan. In those cases run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/complete.md

@@ -37,17 +37,30 @@ The handoff must include:
 - The URL of the running app.
 - The command that starts the app in the future.
 - The debugging surface this journey's frontend can reach, named below.
-- How to use https://intelligence.copilotkit.ai to manage the Intelligence installation.
+- How to use https://intelligence.copilotkit.ai to manage the Intelligence
+  installation. Do not open it. This item makes the developer aware the dashboard is
+  there, and it is a sentence to write rather than a check to perform. Nothing in this
+  graph gates on the dashboard, so a dashboard this run never opened is not a finding,
+  not a caveat, and not a blocker.
 - The process IDs and stop commands for the running agent and frontend.
 - The `@copilotkit/*` versions this conversion changed, and what they were before.
 - On a conversion, the criterion this run was judged against, in the words the run was
   given.
+- Any path this run created that git does not ignore, and what to do with each.
+
+A run leaves paths beside the credential file. Tool output such as `.playwright-mcp/` and
+`.langgraph_api/` is regenerable, so the developer normally wants it ignored.
+`.copilotkit/` is not debris: `project.json` and `channels.json` are the project's own
+declared state and belong in the commit, while `.copilotkit/artifacts/` holds regenerable
+manifests and does not. Name each path and say which of the two it is. Do not add an
+ignore line for any of them yourself. None of these carries a secret, unlike the
+credential path, so the developer decides.
 
 Name the debugging surface this journey's frontend can reach, rather than the one the rest
 of the documentation leads with. For a web frontend it is the CopilotKit Inspector. For
 React Native there is no Inspector: it is a browser overlay built on a DOM custom element,
 and `@copilotkit/react-native` does not ship it. Give a mobile developer
-`npx --yes copilotkit@4.9.17 verify --round-trip`, the runtime's own log, the AG-UI
+`npx --yes copilotkit@4.9.24 verify --round-trip`, the runtime's own log, the AG-UI
 Event Inspector in the CopilotKit VS Code extension, and the Intelligence thread view
 instead. Naming the Inspector to a developer who cannot open it costs them the time it
 takes to conclude their own wiring is broken.
@@ -59,7 +72,7 @@ the friction commands without another developer question. The CLI telemetry gate
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.17 onboard friction --category <slug> --cost-seconds <seconds>
+npx --yes copilotkit@4.9.24 onboard friction --category <slug> --cost-seconds <seconds>
 ```
 
 Write one or two sentences on the command's standard input. Pick one category from
@@ -76,14 +89,14 @@ Tell the developer when you send a friction report. Do not quote or summarize th
 unless the developer asks. If the CLI says that telemetry is disabled or unavailable,
 state that the report was not sent and continue without another question.
 
-When the evidence is gathered, run `npx --yes copilotkit@4.9.17 onboard complete`, carrying
+When the evidence is gathered, run `npx --yes copilotkit@4.9.24 onboard complete`, carrying
 the surface-check outcome the proof subagent returned. Pass exactly one flag, and pass the
 one that matches this journey's surface.
 
 For a web frontend -- React SPA, Next.js, Angular, Vue:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.9.24 onboard complete --visual-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
@@ -91,7 +104,7 @@ The outcome is one of `performed`, `skipped-no-browser-tool`, or `failed`.
 For React Native:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard complete --device-check <outcome>
+npx --yes copilotkit@4.9.24 onboard complete --device-check <outcome>
 ```
 
 The outcome is one of `performed`, `skipped-no-device`, or `failed`.
@@ -109,14 +122,18 @@ If the round trip proved and something after it still blocked this run, add `--b
 to the same command:
 
 ```text
-npx --yes copilotkit@4.9.17 onboard complete --visual-check performed --blocked-by <cause>
+npx --yes copilotkit@4.9.24 onboard complete --visual-check performed --blocked-by <cause>
 ```
 
-The cause is one of `hosted-dashboard` for a managed dashboard that did not load or refused
-a sign-in, `inspector` for a debugging surface that did not open, `plan-excluded-capability`
-for a capability the approved plan had already excluded for this framework, and `other` for
-anything else. Pick `other` rather than leaving the flag off. The command ends the run as
-blocked and prints what the blocker leaves unverified.
+The cause is one of `inspector` for a debugging surface that did not open,
+`plan-excluded-capability` for a capability the approved plan had already excluded for this
+framework, and `other` for anything else. Pick `other` rather than leaving the flag off.
+The command ends the run as blocked and prints what the blocker leaves unverified.
+
+The managed Intelligence dashboard is not among these, because nothing in this graph asks a
+run to open it. A run that records a blocker for a surface it was never sent to looks worse
+than an identical run that wrote the same handoff sentence, and the two are then not
+comparable.
 
 This is the flag for a journey that worked. It is not a way to report an unsupported path,
 and a blocked run here is still owed the full handoff above: the URL, the start command,

package/onboarding/prompts/proof/oss-baseline.md

@@ -1,7 +1,7 @@
 # Prove the existing OSS baseline
 
 Do not prove the baseline yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.9.17 onboard read subagent/prove-oss-baseline` first and follow the
+`npx --yes copilotkit@4.9.24 onboard read subagent/prove-oss-baseline` 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 and exact CLI package spec. Wait for the
@@ -11,14 +11,14 @@ Do not change project files before this proof ends. Starting existing developmen
 processes and their ignored runtime files is allowed.
 
 If the subagent proves the `both-oss` predicate, keep its evidence with the plan and run
-`npx --yes copilotkit@4.9.17 onboard read conversion/plan`. That project already works.
+`npx --yes copilotkit@4.9.24 onboard read conversion/plan`. That project already works.
 What it needs is the conversion, not a build.
 
 If it proves another supported starting state, record that state and run
-`npx --yes copilotkit@4.9.17 onboard read credentials/plan`. This prompt is served
+`npx --yes copilotkit@4.9.24 onboard read credentials/plan`. This prompt is served
 whenever a project looks like an OSS integration, so a baseline that did not prove is an
 ordinary starting state rather than a failure.
 
 If it cannot identify the running process safely, exposes a secret, or finds a baseline
 failure that cannot be classified, run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/proof/round-trip.md

@@ -1,7 +1,7 @@
 # Prove the user journey
 
 Do not do the proof work yourself. Spawn one proof subagent. Tell it to run
-`npx --yes copilotkit@4.9.17 onboard read subagent/prove-round-trip` first and follow the
+`npx --yes copilotkit@4.9.24 onboard read subagent/prove-round-trip` 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 selected framework, frontend, model, approved plan, selected
@@ -20,7 +20,7 @@ https://docs.copilotkit.ai/build-with-agents.md
 Wait for the subagent to finish.
 
 For every protected-path audit in this prompt, run
-`npx --yes copilotkit@4.9.17 onboard audit` from the target app directory. If its result
+`npx --yes copilotkit@4.9.24 onboard audit` from the target app directory. If its result
 starts with `Status: blocked`, report the printed reason and use the route-out rules below.
 A blocked audit proved nothing changed and is not a preservation failure. If a
 protected-path audit reports a changed path, use the route-out rules below. Never repair,
@@ -28,16 +28,16 @@ reset, or revert a protected path.
 
 If the proof result starts with `Status: passed`, run the protected-path audit. Continue to
 `proof/complete` only if that audit passes. After the audit passes, run
-`npx --yes copilotkit@4.9.17 onboard read proof/complete`. A performed surface outcome with
+`npx --yes copilotkit@4.9.24 onboard read proof/complete`. A performed surface outcome with
 the full round trip is core success even if a continued-development tool fails. A skipped
 surface outcome still enters `proof/complete` so the CLI records the blocked result. Do not
 describe a skipped surface as proved. Keep the Skills and MCP results separate from the proof
 result.
 
-If the round trip proves and something after it blocks this run anyway -- the managed
-Intelligence dashboard, the debugging surface, or a capability the approved plan already
-excluded for this framework -- read `proof/complete` all the same, with the command above,
-and carry the blocker there with `--blocked-by`.
+If the round trip proves and something after it blocks this run anyway -- the debugging
+surface, or a capability the approved plan already excluded for this framework -- read
+`proof/complete` all the same, with the command above, and carry the blocker there with
+`--blocked-by`.
 The stop terminal is for a journey this release cannot carry. It is
 not for a journey that worked and then hit a wall: routing a proved run there tells the
 developer that a framework and frontend that just worked are unsupported, and hands them a
@@ -95,7 +95,7 @@ and proof cycles.
 
 Route out only when the failure is not yours to fix, when the same proof still fails after
 three attempts, or when no evidence of the round trip can be produced. In those cases run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`. All three are
+`npx --yes copilotkit@4.9.24 onboard read unsupported/no-validated-path`. All three are
 about the round trip itself. A round trip that proved is not one of them, whatever failed
 after it.
 
@@ -105,7 +105,7 @@ Run the feedback command without another developer question. The CLI telemetry g
 whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.17 onboard feedback
+npx --yes copilotkit@4.9.24 onboard feedback
 ```
 
 Write at most four lines to standard input: the step you stopped at and what stopped it.

package/onboarding/prompts/starter/clone.md

@@ -34,11 +34,18 @@ selected pair is not in the table, or the directory name is not valid, stop the
 Do not run `init`. Treat this result as a failed shortcut and follow the final failure
 instruction in this prompt.
 
-If the developer did not name an Intelligence project, list the available projects:
+If the developer did not name an Intelligence project, create one for the app being
+cloned. This directory is new, so no existing project is already its own: take the project
+name from the target directory name derived above, and ask the developer to confirm it or
+give another. Do not list the projects in the organization. If no developer answers, use
+the derived name.
 
-`npx --yes copilotkit@4.9.17 project list --json`
+Only if the developer asks for an existing project, or asks to see the projects they have,
+read the choices:
 
-Ask the developer to select a project or give a name for a new project. If the developer
+`npx --yes copilotkit@4.9.24 project list --json`
+
+Then ask which one to use. Do not order the projects by creation time. If the developer
 already gave this answer, do not ask again. Do not read a secret value. Do not show or
 store a secret value.
 
@@ -46,10 +53,12 @@ Run the command from the parent directory. Do not inspect another entry in the p
 directory. Replace each placeholder with the recorded value. Do not run a placeholder as
 a shell argument.
 
-`npx --yes copilotkit@4.9.17 init --name <project-name> --framework <framework-id> --channel none --no-banner --project <slug-or-id> --install`
+`npx --yes copilotkit@4.9.24 init --name <project-name> --framework <framework-id> --channel none --no-banner --create <name> --install`
 
-If the developer wants a new project, use `--create <name>` instead of
-`--project <slug-or-id>`. If the developer asked to skip the dependency install, use
+Pass the confirmed name to both `--name` and `--create`: the app directory and its
+Intelligence project take the same name here. If the developer names an existing project,
+use `--project <slug-or-id>` instead of `--create <name>`. If the developer asked to skip
+the dependency install, use
 `--no-install` instead of `--install`. Do not wait for an interactive prompt. Pass every
 answer as a flag.
 
@@ -60,8 +69,8 @@ account. The command does not need terminal input.
 If the command succeeds, do not rebuild the starter by hand. Inspect only the generated
 paths inside the target directory. Record the files, install result, project connection,
 and validation commands. Then run
-`npx --yes copilotkit@4.9.17 onboard read proof/round-trip`.
+`npx --yes copilotkit@4.9.24 onboard read proof/round-trip`.
 
 If the command fails, report its exact error and do not claim that the starter is ready.
 Then run
-`npx --yes copilotkit@4.9.17 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.24 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/subagent/create-plan.md

@@ -35,13 +35,18 @@ reference naming hosts that route nothing, and it requires the platform URLs the
 documentation calls optional. A run that reads that reference configures the runtime
 against a dead host, and the failure arrives as an empty-body 404 with no cause named.
 
-If any `@copilotkit/*` dependency is below 1.64.0, plan to upgrade every `@copilotkit/*`
+If any `@copilotkit/*` dependency is below 1.70.0, plan to upgrade every `@copilotkit/*`
 dependency to its latest published version. Packages that share a version line must end
 on the same version. Never force a package onto a version line it does not publish on.
 Resolve each latest version at run time rather than from a remembered version number.
 Where every `@copilotkit/*` dependency already meets that floor, plan no dependency
 change.
 
+The floor is 1.70.0 because the runtime resolves managed Intelligence entitlement
+authority from that version. A runtime below it reports its license from a self-hosted
+token alone. A managed project holds no such token, so the threads drawer this conversion
+adds lists nothing even after every command-line check passes.
+
 Plan the upgrade as its own step before the Intelligence runtime wiring, and plan to
 re-run the recorded baseline checks immediately after it. Name the revert: restore the
 manifest and lockfile to their recorded state and stop, rather than wiring Intelligence
@@ -94,8 +99,9 @@ here is work the developer did not ask for.
 
 Plan the threads drawer itself: add it from the selected drawer page, where this frontend
 does not already render one. Where this journey's frontend framework ships no threads
-drawer -- React Native --, plan that the thread is proved in the managed Intelligence
-dashboard instead.
+drawer -- React Native --, plan that the thread is proved by
+`npx --yes copilotkit@4.9.24 verify --round-trip`, which needs no browser. Do not plan a
+step that opens the managed Intelligence dashboard.
 
 ## Order the plan into steps
 

package/onboarding/prompts/subagent/inspect-repository.md

@@ -38,7 +38,7 @@ from different directories.
 
 For the CopilotKit versions, report the exact installed version of every `@copilotkit/*`
 dependency, read from the lockfile rather than a manifest range, and state whether any of
-them is below 1.64.0. The conversion decides its upgrade from exactly that, and a caret
+them is below 1.70.0. The conversion decides its upgrade from exactly that, and a caret
 range does not answer it.
 
 A project states what it is for in its `README.md`, in its package description, or in

package/onboarding/prompts/subagent/prove-oss-baseline.md

@@ -16,7 +16,7 @@ Prove the live runtime in this order:
 4. Confirm from project files that the runtime constructor passes a `runner` option rather
    than an `intelligence` option. A package, import, project file, or key is not use proof.
 5. Run
-   `npx --yes copilotkit@4.9.17 verify --expect-runtime oss --round-trip --agent <expected-agent-id> --json`,
+   `npx --yes copilotkit@4.9.24 verify --expect-runtime oss --round-trip --agent <expected-agent-id> --json`,
    with the runtime URL or auth header options that this project needs. Require exit zero
    and the JSON `ok` field to be `true`.
 6. Drive one real request through the existing frontend, CopilotKit runtime, and expected

package/onboarding/prompts/subagent/prove-round-trip.md

@@ -90,8 +90,8 @@ A server that never answered has written the reason to its own output, and readi
 output is faster than starting it again.
 
 Leave the agent and frontend servers running after proof. Record each process ID and a
-safe command that stops that process. Record the frontend URL and the commands that start
-both servers again.
+safe command that stops that process. Record the frontend URL, written with `localhost`
+rather than an IP literal, and the commands that start both servers again.
 
 ## Step 3 -- Identify the process that answered
 
@@ -120,7 +120,7 @@ IPv6 only, so an IPv4 literal fails against the correct port.
 ## Step 4 -- Check the wiring
 
 With both running, check the wiring in one command before you open a browser:
-`npx --yes copilotkit@4.9.17 verify --json`. Add `--runtime-url` when the runtime is not at
+`npx --yes copilotkit@4.9.24 verify --json`. Add `--runtime-url` when the runtime is not at
 `http://localhost:3000/api/copilotkit`. Read the individual checks rather than the summary
 alone: a check reported `undetermined` did not run, and that is not a pass. Repair a failed
 check only within the limits above. Otherwise, return the check and its evidence before the
@@ -136,7 +136,7 @@ thread-endpoint state exists, the runtime predates the field. Record that and co
 
 ## Step 5 -- Prove that the agent runs
 
-Run `npx --yes copilotkit@4.9.17 verify --round-trip --json`. It sends one request through
+Run `npx --yes copilotkit@4.9.24 verify --round-trip --json`. It sends one request through
 the runtime and reads the answer back from the thread, so it separates an agent that is
 configured from an agent that works. Use `--agent <id>` when the runtime declares more
 than one. If it reports `user-not-identified`, this project's `identifyUser` reads a
@@ -212,8 +212,9 @@ journey, and the graph ends such a run as blocked rather than complete.
 For a recorded `both-oss` starting state, this step has no component to render. Send the
 same request the baseline recorded, require the same kind of user-visible result the
 baseline produced, and require that the thread for that request is listed in the drawer.
-Where this journey's frontend framework ships no threads drawer -- React Native --, find
-that thread in the managed Intelligence dashboard and record which of the two you proved.
+Where this journey's frontend framework ships no threads drawer -- React Native --, prove
+that thread with `npx --yes copilotkit@4.9.24 verify --round-trip`, which reads the
+answer back off the thread and needs no browser. Record which of the two you proved.
 
 Use the surface control the main coding agent recorded for your environment. It either had
 one already or registered one before this step, so that finding is the answer and there is
@@ -237,6 +238,10 @@ The surface is a browser, and it also covers browser-origin CORS and CSP, which
 request never exercises. Drive it with the browser control step 6 named.
 
 1. Open the frontend URL from step 2 and wait for the page to finish loading.
+   Address it as `localhost` rather than an IP literal, for the reason step 3 gives
+   for the agent. A dev server reached on the IP literal can refuse its own static
+   assets, and a page that loads without them leaves the chat control dead. That
+   reads as a broken integration rather than as the host name you used.
 2. Take one page snapshot. Record whether the CopilotKit surface is on the page. A page
    that renders without it is a wiring failure rather than a proof to retry.
 3. Read the browser console before you type anything, and record every error already
@@ -317,6 +322,12 @@ result. The runtime must now report `licenseStatus`, and the authenticated Intel
 checks must pass. A thread for that request must be persisted and visible. Record both
 before and after evidence, and record that the criterion was `conversion-v1`.
 
+`licenseStatus` reports `unknown` while the runtime entitlement lookup for this project
+has not resolved yet. That value is transient rather than a failure, and the drawer
+renders its locked view for as long as it stands. Re-read `/info` and re-open the drawer
+before you judge either one. Criterion 4 requires `licenseStatus` to be present, and a
+present `unknown` meets it.
+
 For every other starting state, record Step 8 as not applicable.
 
 The application edit ban ends only after Step 8 passes or is recorded as not applicable.

package/onboarding/prompts/unsupported/no-validated-path.md

@@ -26,13 +26,13 @@ Before you show the best-effort plan, require this complete packet:
 - Give the ordered proof rules.
 
 After the developer approves the best-effort plan, run
-`npx --yes copilotkit@4.9.17 onboard read fallback/best-effort`.
+`npx --yes copilotkit@4.9.24 onboard read fallback/best-effort`.
 
 Send one short report. 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.24 onboard feedback
 ```
 
 Write the feedback message to the command's standard input, in at most four lines.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "copilotkit",
-  "version": "4.9.17",
+  "version": "4.9.24",
   "type": "module",
   "repository": {
     "type": "git",

package/release/release-tool.js

@@ -14698,7 +14698,7 @@ import * as path4 from "node:path";
 
 // apps/cli/src/config.ts
 function getTemplateRef() {
-  return true ? "f08f478cf73c46d34e8db03dedcc61f695f9b9b5" : "main";
+  return true ? "2d44d3ff00910e9f3494d5e57aaa7bdd69a82e04" : "main";
 }
 
 // apps/cli/src/services/agentcore-config.ts