copilotkit 4.9.60 → 4.10.1

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

@@ -73,6 +73,12 @@ started process's output. The project's configuration wins over the table.
 Where this project's runtime runs as a process of its own, the frontend documentation
 puts it on port 8200. Use the runtime URL from step 1 rather than that number.
 
+Read the project's scripts before you start anything. A scaffolded starter serves both the
+agent and the frontend from one `dev` script, which runs them under
+`concurrently --kill-others`. One command starts both, and stopping either one stops the
+other. A second start against a project already running that script collides with a server
+that is up.
+
 Start each server in the background with the project's own script. Then wait for it to
 answer rather than for a fixed number of seconds:
 
@@ -89,8 +95,14 @@ Read the loop's own last line rather than assuming it ended because the server a
 A server that never answered has written the reason to its own output, and reading that
 output is faster than starting it again.
 
+That coupling also turns an ordinary restart into a false failure. Where you stop a server
+to pick up an installed dependency, start both again and wait for both to answer before you
+read the round trip. A check run against a frontend whose agent was stopped with it reports
+a wiring fault this run does not have.
+
 Leave the agent and frontend servers running after proof. Record each process ID and a
-safe command that stops that process. Record the commands that start both servers again.
+safe command that stops that process. Record whether that command stops both. Record the
+commands that start both servers again.
 
 Record the frontend URL the server you started reports, and treat it as provisional. Step 4
 replaces it with the URL the CLI resolves. Do not compose one of your own from a port you
@@ -123,7 +135,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.60 verify --json`. It reads the port from this project, so a
+`npx --yes copilotkit@4.10.1 verify --json`. It reads the port from this project, so a
 non-default port needs no flag. The payload reports `runtimeUrl` and `runtimeUrlSource`. A
 `runtimeUrlSource` of `default` means nothing in the project named a port, so pass
 `--runtime-url` with the URL from step 1 in that case. Read the individual checks rather than
@@ -138,7 +150,7 @@ used the Intelligence credential. `api_key_authenticates` proves only that the k
 will not read. `verify` searches upward for the credential and a framework's env loader
 does not, so a key at the repository root is invisible to an app in a subdirectory. The
 check names the file to write instead. Write the key there, or run
-`npx --yes copilotkit@4.9.60 project select` from the app directory. Do not link,
+`npx --yes copilotkit@4.10.1 project select` from the app directory. Do not link,
 copy, or symlink the file to work around it, and do not treat the credential as missing:
 the check above already reported that it exists.
 
@@ -156,7 +168,7 @@ named no port the CLI can read: keep step 2's URL, and rewrite its host as `loca
 before you use it.
 
 Then run the command once more with the URL you are about to open:
-`npx --yes copilotkit@4.9.60 verify --frontend-url <that url> --json`. The
+`npx --yes copilotkit@4.10.1 verify --frontend-url <that url> --json`. The
 `frontend_assets_served` check asks that server for its page and for one of the page's own
 assets, on that exact host. A `fail` there means the dev server refuses its own static
 assets on the host you were about to use, and the check names the URL to use instead. This
@@ -164,7 +176,7 @@ is the cheapest step that can save the most expensive one, so run it before the
 
 ## Step 5 -- Prove that the agent runs
 
-Run `npx --yes copilotkit@4.9.60 verify --round-trip --json`. It sends one request through
+Run `npx --yes copilotkit@4.10.1 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
@@ -173,6 +185,38 @@ it again, because an auth-gated app refusing an unauthenticated caller is that a
 working. Do not continue until this passes, and never report a round trip proven without
 it.
 
+Where this run settled a Learning Container, add the flag to the call above rather than
+running a second round trip:
+
+```text
+npx --yes copilotkit@4.10.1 verify --round-trip --expect-learning-container <container id> --json
+```
+
+The check reads the thread that this run created, so a second round trip proves a second
+thread and leaves the first unexamined. Add `--agent <id>` here too when the runtime
+declares more than one.
+
+It reads the thread back from the platform, so it answers for every runtime mount,
+including a single-route one. Read the `extraChecks` entry whose `id` is
+`learning_container_assigned`, and route on that entry's own `status` rather than on the
+exit status: the command exits non-zero for any check that is not `pass`, and
+`undetermined` is what a runtime the CLI cannot read reports.
+
+- `pass` proves the assignment. The thread came back carrying the container this run
+  settled.
+- `fail` is a defect. Either the thread carries no container, which means the selector
+  returned nothing, or it carries a different one. A thread cannot move between containers
+  after its first assignment, so start a new thread rather than repairing that one.
+- `undetermined` proves nothing either way. Record it and continue. An auth-gated
+  `identifyUser` produces it on an app that works, and so does a runtime the CLI cannot
+  read.
+
+`features.self_learning` and `/info` are not evidence. The first is a plan entitlement and
+is already true before any wiring. The second reports Learning from the presence of a
+callback rather than from an assigned thread. Never report either one as proof.
+
+Where this run skipped the Learning step, leave the flag off.
+
 ### Step 5a -- Prove that the page's data reaches the model
 
 `verify --round-trip` sends `context: []` and asks a question that needs no context. It
@@ -235,13 +279,13 @@ holds. Streamed text alone is not this step's outcome, whatever it says.
 This is the step that covers realtime delivery, the frontend provider being wired to this
 runtime, and the component actually rendering, and no command-line check reaches any of
 them. It is not optional polish: a run that skips it has proven the agent and not the
-journey, and the graph ends such a run as blocked rather than complete.
+journey, and such a run ends 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 --, prove
-that thread with `npx --yes copilotkit@4.9.60 verify --round-trip`, which reads the
+that thread with `npx --yes copilotkit@4.10.1 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
@@ -269,7 +313,7 @@ request never exercises. Drive it with the browser control step 6 named.
    the page to finish loading. Do not retype the host, and do not substitute a URL a tool
    offers you by default. Where the page loads but its styling is missing or the chat
    control is dead, run
-   `npx --yes copilotkit@4.9.60 verify --frontend-url <the url you opened> --json`
+   `npx --yes copilotkit@4.10.1 verify --frontend-url <the url you opened> --json`
    before you diagnose anything else. A dev server can serve its page and refuse every
    static chunk behind it, and on screen that is indistinguishable from a broken
    integration. The `frontend_assets_served` check tells the two apart.

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

@@ -30,19 +30,22 @@ 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.60 onboard read fallback/best-effort`.
+`npx --yes copilotkit@4.10.1 onboard read fallback/best-effort`.
 
-Send one short report. Run the feedback command without another developer question. The
+Send one short report. Run the friction command without another developer question. The
 CLI telemetry gate decides whether the report is sent.
 
 ```text
-npx --yes copilotkit@4.9.60 onboard feedback
+npx --yes copilotkit@4.10.1 onboard friction --phase stop --category <slug>
 ```
 
-Write the feedback message to the command's standard input, in at most four lines.
+Write one or two sentences to standard input: the step you stopped at and what stopped it.
+Pick the category that fits from docs-missing, docs-wrong, docs-sequential, cli-gap,
+sdk-gap, environment, port-collision, credential, validation-loop, and other. Leave
+--cost-seconds off. A run that stopped cannot separate one papercut's cost from the cost
+of the whole run, so the estimate is optional on a stop report and only there.
 Send no secrets, source code, logs, or command output. The command refuses a report
 that carries any of those, prints the reason, and exits zero. A refused report is not
 a failed step. Reword it and send it again, or stop without a report. The command
-prints what it sent. This is the channel for a stop. Report friction only from a run that
-finished, never from here. If the CLI says the report was not sent,
+prints what it sent. This is the channel for a stop. If the CLI says the report was not sent,
 state what it said and stop without another question.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "copilotkit",
-  "version": "4.9.60",
+  "version": "4.10.1",
   "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 ? "d1584b840f904674b470be5d2b16c4ccca99c4f4" : "main";
+  return true ? "7e6964fc11092b685bbea62bc331d5d177b738c1" : "main";
 }
 
 // apps/cli/src/services/agentcore-config.ts
@@ -15270,13 +15270,49 @@ import * as fs3 from "node:fs";
 import * as path3 from "node:path";
 import * as os from "node:os";
 import { execFileSync } from "node:child_process";
+var PROJECT_DIRECTORY_NAMES = /* @__PURE__ */ new Set([
+  "agent",
+  "api",
+  "app",
+  "components",
+  "lib",
+  "packages",
+  "pages",
+  "server",
+  "src",
+  "web"
+]);
+var PROJECT_MANIFEST_NAMES = /* @__PURE__ */ new Set([
+  "Cargo.toml",
+  "Gemfile",
+  "build.gradle",
+  "composer.json",
+  "go.mod",
+  "package.json",
+  "pom.xml",
+  "pyproject.toml",
+  "requirements.txt"
+]);
+var ENV_TEMPLATE_SUFFIXES = [".example", ".sample", ".template"];
+function isCredentialEnvFile(entry) {
+  if (!entry.startsWith(".env"))
+    return false;
+  if (ENV_TEMPLATE_SUFFIXES.some((suffix) => entry.endsWith(suffix)))
+    return false;
+  return entry === ".env" || entry.startsWith(".env.");
+}
+function entryHoldsProject(entry) {
+  if (isCredentialEnvFile(entry))
+    return true;
+  return PROJECT_DIRECTORY_NAMES.has(entry) || PROJECT_MANIFEST_NAMES.has(entry);
+}
 function isProjectDirOccupied(projectDir) {
-  return fs3.existsSync(projectDir) && fs3.readdirSync(projectDir).length > 0;
+  return fs3.existsSync(projectDir) && fs3.readdirSync(projectDir).some(entryHoldsProject);
 }
 function assertProjectDirAvailable(projectDir) {
   if (isProjectDirOccupied(projectDir)) {
     throw tagError(
-      new Error(`${projectDir} already exists and is not empty`),
+      new Error(`${projectDir} already holds a project`),
       TELEMETRY_ERROR_CODES.PREREQUISITE_MISSING
     );
   }