docs(ai-chat): correct action lifecycle — run() and onTurnComplete do not fire

Three pages still described the pre-May-6 behavior where actions
triggered run() and onTurnComplete. Aligned compaction, reference,
and client-protocol with the actions page: actions fire onAction
(plus hydrateMessages if set) only. If onAction returns a
StreamTextResult, the response auto-pipes — but no run() and no
turn lifecycle hooks fire. Removed the dead `if (trigger === "action")
return;` guard from the compaction code example.

Also fixes a chat.local typing error in the version-upgrades pattern:
chat.local<T> requires T extends Record<string, unknown>, so the
<string> primitive form was wrong. Wrapped in { version: string } and
moved the init from onChatStart to onBoot (matches the canonical
guidance on the chat.local page).

Author: ericallam

docs/ai-chat/client-protocol.mdx

@@ -830,7 +830,7 @@ Custom actions (undo, rollback, edit) ride on the same `.in` channel using `kind
 }
 ```
 
-Actions wake the agent from suspension (same as messages), fire the `onAction` hook, then optionally trigger a normal `run()` turn (when `onAction` returns a `StreamTextResult`). The `action` payload is validated against the agent's `actionSchema`. If the agent didn't register an `actionSchema` (or your `action` payload doesn't match it), validation fails the same way `metadata` does — `.in/append` returns `200 OK`, but the run trace shows `chat turn N [ERROR]` and the wire emits a `turn-complete` control record with no other chunks. See [Actions](/ai-chat/actions) for the agent-side schema setup.
+Actions wake the agent from suspension (same as messages) and fire the `onAction` hook — they are not turns, so `run()` and turn lifecycle hooks do not fire. If `onAction` returns a `StreamTextResult`, the response is auto-piped to the frontend (but still no `run()` or `onTurnComplete`). The `action` payload is validated against the agent's `actionSchema`. If the agent didn't register an `actionSchema` (or your `action` payload doesn't match it), validation fails the same way `metadata` does — `.in/append` returns `200 OK`, but the run trace shows `chat turn N [ERROR]` and the wire emits a `turn-complete` control record with no other chunks. See [Actions](/ai-chat/actions) for the agent-side schema setup.
 
 ### Regenerating the last response
 

docs/ai-chat/compaction.mdx

@@ -247,16 +247,13 @@ export const myChat = chat.agent({
     ]);
   },
 
-  run: async ({ messages, trigger, signal }) => {
-    // Compact action doesn't need an LLM response — just exit.
-    if (trigger === "action") return;
-
+  run: async ({ messages, signal }) => {
     return streamText({ model: anthropic("claude-sonnet-4-5"), messages, abortSignal: signal });
   },
 });
 ```
 
-Actions fire `onAction`, apply any `chat.history.*` mutations, then call `run()`. For compaction there's no new user message to respond to, so `run()` returns early when `trigger === "action"`. `onTurnComplete` still fires with the compacted `uiMessages` — use it to persist the new state.
+Actions fire `onAction` only (plus `hydrateMessages` if set) — `run()` and `onTurnComplete` do not fire for actions. Persist the compacted state directly inside `onAction` after the `chat.history.set` call. See [Actions](/ai-chat/actions) for the full lifecycle.
 
 ### Frontend
 

docs/ai-chat/patterns/version-upgrades.mdx

@@ -128,7 +128,7 @@ export function Chat() {
 ```
 
 ```ts title="trigger/chat.ts"
-const initialAppVersion = chat.local<string>({ id: "appVersion" });
+const initialAppVersion = chat.local<{ version: string }>({ id: "appVersion" });
 
 export const myChat = chat
   .withClientData({
@@ -139,11 +139,11 @@ export const myChat = chat
   })
   .agent({
     id: "my-chat",
-    onChatStart: async ({ clientData }) => {
-      initialAppVersion.init(clientData.appVersion);
+    onBoot: async ({ clientData }) => {
+      initialAppVersion.init({ version: clientData.appVersion });
     },
     onTurnStart: async ({ clientData }) => {
-      if (clientData?.appVersion && clientData.appVersion !== initialAppVersion.value) {
+      if (clientData?.appVersion && clientData.appVersion !== initialAppVersion.version) {
         chat.requestUpgrade();
       }
     },

docs/ai-chat/reference.mdx

@@ -700,7 +700,7 @@ See [Stop generation](/ai-chat/frontend#stop-generation) for full details.
 
 ### transport.sendAction()
 
-Send a custom action to the agent. Actions wake the agent from suspension, fire `onAction`, then trigger a normal `run()` turn.
+Send a custom action to the agent. Actions wake the agent from suspension and fire `onAction`. They are not turns — `run()` and turn lifecycle hooks do not fire. If `onAction` returns a `StreamTextResult`, the response is auto-piped to the frontend.
 
 ```ts
 transport.sendAction(chatId: string, action: unknown): Promise<ReadableStream<UIMessageChunk>>