copilotkit 4.29.0 → 4.30.0

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

@@ -86,10 +86,14 @@ about the failure it was spawned to clear.
 
 ## Steps 2 to 5 -- Run the proof checks
 
+Where your handoff holds an `onboard proof-check` result, that is your first run of the
+proof checks. Read it as the result of the command below. Run the command again only after
+a repair, as the rules below say.
+
 Run this from the target app directory:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard proof-check --json
+npx --prefer-offline --yes copilotkit@4.30.0 onboard proof-check --json
 ```
 
 It starts each app's `dev` script unless a server from that app already listens, and
@@ -145,7 +149,7 @@ Otherwise sort `firstFailure`, and run the command again after each repair:
   asking. Read the port from the log, not from the plan, and record it:
 
   ```text
-  npx --prefer-offline --yes copilotkit@4.29.0 onboard runtime-url --url <runtime-url>
+  npx --prefer-offline --yes copilotkit@4.30.0 onboard runtime-url --url <runtime-url>
   ```
 
   `<runtime-url>` is the project's runtime URL, or the plan's, with its port replaced by the
@@ -220,11 +224,20 @@ Never report a round trip proved unless `round-trip:agent_answers` passed.
 
 The checks leave every process they did not start running. If a repair needs a process
 stopped, stop a process only when its directory is inside this project, and stop its children
-before the parent. Never stop a process because its command line matches a name: one
+before the parent. Wait for its listener to exit before rerunning the proof checks, so
+the command starts only one replacement. Reuse a healthy project-owned frontend instead
+of starting another copy. Never stop a process because its command line matches a name: one
 `pkill` pattern reaches every project on the machine. If a local request in Steps 5a and
 5b fails after 0 ms while the port listens, the sandbox blocked it. Request escalation
 with a prefix rule for `curl`, run it again, and do not record a failed predicate.
 
+Next.js allows only one dev server per project directory. A second `next dev` can
+announce port 3001 and print `Ready` before exiting with `Another next dev server is
+already running` or a `.next/dev/lock` error. Changing ports does not fix that collision.
+Do not delete a live server's lock. Identify the project-owned server and reuse it, or
+stop it under the rule above before rerunning the proof checks. Confirm the replacement
+stays running and serves the app before continuing. Leave other projects' processes alone.
+
 ### Step 5a -- Prove that the page's data reaches the model
 
 Where the proof checks needed `--thread`, the app refuses a run that Steps 5a and 5b send,
@@ -252,7 +265,7 @@ shows it. Send the same run
 body twice: once carrying the context entries the page
 publishes, and once carrying the same entries with one value changed. Use the step 1
 request both times. Write each body to a JSON file in `.copilotkit/proof/`, and send it with
-`npx --prefer-offline --yes copilotkit@4.29.0 verify --send-run <file> --agent <agent id> --json`.
+`npx --prefer-offline --yes copilotkit@4.30.0 verify --send-run <file> --agent <agent id> --json`.
 The command sends the body to `<runtime>/agent/<agent id>/run` and reads the events the run
 streams. It writes them to `<file name>.events.jsonl` beside the body, and prints that path
 with the answer text and the tool calls. Do not send a run with `curl` and read its events
@@ -330,7 +343,7 @@ For a recorded `both-oss` starting state, this step has no component to render.
 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 --prefer-offline --yes copilotkit@4.29.0 verify --round-trip`, which reads the
+that thread with `npx --prefer-offline --yes copilotkit@4.30.0 verify --round-trip`, which reads the
 answer back off the thread and needs no browser. Where the proof checks needed `--thread`,
 prove the thread for this request with `verify --thread <id>` instead. Record which of the
 two you proved.
@@ -360,7 +373,7 @@ limit can be ten minutes. You cannot interrupt a call while it runs, so the limi
 what you do after one. If a browser call took longer than 60 seconds to return, the browser
 control is unresponsive. Do not call the browser again in this attempt. A second call to a
 hung tool waits as long as the first one did. Run
-`npx --prefer-offline --yes copilotkit@4.29.0 verify --frontend-url <the frontendUrl the proof checks resolved> --json` once,
+`npx --prefer-offline --yes copilotkit@4.30.0 verify --frontend-url <the frontendUrl the proof checks resolved> --json` once,
 and record the `frontend_assets_served` result. Report the outcome `failed` with the cause
 `browser-control-unresponsive`. The application is not at fault on this evidence: every
 step before the browser proved the runtime without one, and no repair to the project can
@@ -370,7 +383,7 @@ reach the tool.
    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 --prefer-offline --yes copilotkit@4.29.0 verify --frontend-url <the url you opened> --json`
+   `npx --prefer-offline --yes copilotkit@4.30.0 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.
@@ -482,7 +495,7 @@ For every other starting state, record Step 8 as not applicable.
 Before you return, record that you are returning:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase subagent-returned --brief prove-round-trip --result <ok|failed>
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase subagent-returned --brief prove-round-trip --result <ok|failed>
 ```
 
 The Status line of your result decides the value. Pass `ok` only for `Status: passed`.

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

@@ -9,9 +9,9 @@ trip caused the route change. Do not say a path works when this release does not
 If the CLI stopped this run with `## Stop: this run deleted or moved the developer's work`,
 name each path and change it listed, in the words it printed. A report that says only that
 files changed cannot be acted on: nobody reading it can tell which file moved.
-This step prints `## The developer's files` below: relay that report as printed, with its
-restore command. When the report says the run started in an empty folder, relay that one
-line alone: list no files and offer no restore.
+This step prints `## Your files` below: relay that report as printed, with its restore
+command. A run that started in an empty folder prints no such section: list no files and
+offer no restore.
 
 Stop onboarding without making more repository changes by default.
 
@@ -36,17 +36,17 @@ Before you show the best-effort plan, require this complete packet:
 Before you end your turn to wait for the developer, report the pause:
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard checkpoint --phase awaiting-plan-approval
+npx --prefer-offline --yes copilotkit@4.30.0 onboard checkpoint --phase awaiting-plan-approval
 ```
 
 After the developer approves the best-effort plan, run
-`npx --prefer-offline --yes copilotkit@4.29.0 onboard read fallback/best-effort`.
+`npx --prefer-offline --yes copilotkit@4.30.0 onboard read fallback/best-effort`.
 
 Send one short report. The friction command follows the telemetry setting the developer
 already chose, so it needs no separate question.
 
 ```text
-npx --prefer-offline --yes copilotkit@4.29.0 onboard friction --phase stop --category <slug> --message "<sentences>"
+npx --prefer-offline --yes copilotkit@4.30.0 onboard friction --phase stop --category <slug> --message "<sentences>"
 ```
 
 `--message` takes one or two sentences: the step you stopped at and what stopped it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "copilotkit",
-  "version": "4.29.0",
+  "version": "4.30.0",
   "type": "module",
   "engines": {
     "node": ">=20.9.0"
@@ -19,5 +19,8 @@
   "dependencies": {
     "oidc-provider": "9.12.2"
   },
+  "devDependencies": {
+    "@ag-ui/client": "0.0.57"
+  },
   "license": "SEE LICENSE IN LICENSE"
 }