copilotkit 4.13.1 → 4.14.0

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

@@ -13,8 +13,8 @@ The existing agent's behavior is outside every step of this proof. It is four th
 agent's system prompt and instructions, its tools and what those tools do, its model and
 provider configuration, and its memory or state handling. A failing predicate is repaired
 on the CopilotKit side -- the frontend rendering, the tool schema, the runtime wiring.
-Where the only fix you can find is a change to the agent's instructions or tools, stop and
-return the failing predicate with the change you propose, for the developer to approve.
+Where the only fix you can find is a change to the agent's instructions or tools, return
+the failing predicate with the change you propose, for the developer to approve.
 Such a change is a behavior change rather than a repair: it changes how the agent answers
 everywhere, not only in CopilotKit. Never rewrite the agent's prompt to make a component
 render, and never report a round trip proved by a prompt this run rewrote.
@@ -145,7 +145,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.13.1 verify --json`. It reads the port from this project, so a
+`npx --yes copilotkit@4.14.0 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
@@ -179,7 +179,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.13.1 verify --frontend-url <that url> --json`. The
+`npx --yes copilotkit@4.14.0 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
@@ -187,7 +187,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.13.1 verify --round-trip --json`. It sends one request through
+Run `npx --yes copilotkit@4.14.0 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
@@ -200,7 +200,7 @@ Where this run settled a Learning Container, add the flag to the call above rath
 running a second round trip:
 
 ```text
-npx --yes copilotkit@4.13.1 verify --round-trip --expect-learning-container <container id> --json
+npx --yes copilotkit@4.14.0 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
@@ -234,7 +234,7 @@ the credential was written holds an empty key while the file beside it carries t
 one. Run this from the target app directory:
 
 ```text
-npx --yes copilotkit@4.13.1 onboard env-staleness
+npx --yes copilotkit@4.14.0 onboard env-staleness
 ```
 
 A `stale` line names the env file and how long after launch it was written. Report that,
@@ -312,7 +312,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 --yes copilotkit@4.13.1 verify --round-trip`, which reads the
+that thread with `npx --yes copilotkit@4.14.0 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
@@ -340,7 +340,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.13.1 verify --frontend-url <the url you opened> --json`
+   `npx --yes copilotkit@4.14.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.
@@ -489,4 +489,4 @@ standard blocked completion route. Use `Status: failed` for a failed proof step.
 Return the proof or the exact failed step to the main coding agent, together with the
 input, the visible result, the relevant process status, the evidence locations, the
 surface-check outcome, and which surface that outcome speaks for. Do not return secret
-values. Stop after you return the result.
+values. End your turn after you return the result.

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

@@ -30,13 +30,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.13.1 onboard read fallback/best-effort`.
+`npx --yes copilotkit@4.14.0 onboard read fallback/best-effort`.
 
 Send one short report. 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.13.1 onboard friction --phase stop --category <slug>
+npx --yes copilotkit@4.14.0 onboard friction --phase stop --category <slug>
 ```
 
 Write one or two sentences to standard input: the step you stopped at and what stopped it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "copilotkit",
-  "version": "4.13.1",
+  "version": "4.14.0",
   "type": "module",
   "engines": {
     "node": ">=20.9.0"
@@ -16,5 +16,9 @@
   "optionalDependencies": {
     "@microsoft/teams.cli": "3.0.3"
   },
+  "dependencies": {
+    "@mastra/core": "1.48.0",
+    "@mastra/libsql": "1.14.3"
+  },
   "license": "SEE LICENSE IN LICENSE"
 }