Update chat, desktop, and template surfaces (#2795)

* feat: update chat, desktop, and template surfaces

* docs: align localized file upload provider guidance

* docs: format framework and template documentation

* fix: surface storage and URL parsing failures

* fix: address PR review feedback

* fix: tighten chat history rail hover state

* chore: add toolkit release changeset

* fix: restore macOS Cmd+H hide shortcut

* fix: address follow-up review feedback

* fix: harden form metadata and storage failures

Author: steve8708

.agents/skills/delegate-to-agent/SKILL.md

@@ -49,6 +49,34 @@ sendToAgentChat({
 });
 ```
 
+### Keep user text separate from injected context
+
+Treat the visible `message` as the user's request or the shortest clear
+description of an app-initiated operation. Put context the user did not type —
+IDs, URLs, filenames, current selection or screen state, serialized records,
+upload instructions, and bounded source excerpts — in the `context` field.
+`context` is model input carried through the agent turn; it is stripped from
+the rendered user message, so do not concatenate it into `message` with labels,
+blank-line sections, or `<context>` tags yourself.
+
+Use the related surface for each kind of supporting input:
+
+| Surface | Use for |
+| --- | --- |
+| `message` | User-authored intent or a concise app action description |
+| `context` | Derived metadata and bounded text needed to carry out that intent |
+| `setAgentChatContextItem` | Context staged for a later user-submitted prompt; keep it keyed so updates replace stale context |
+| `images`, `referenceImagePaths`, attachments | Binary or visual inputs; describe only the handling instructions in `context` |
+
+If an app builds a prompt from a form, selection, upload, or editor state, keep
+the visible message short and pass the assembled details as `context`. Preserve
+the user's actual freeform text in `message` when it is the request; do not
+restate it as metadata in `context` unless the agent needs a structured copy.
+
+This boundary applies to auto-submitted turns and prefills. A hidden context
+field is not a license to send unbounded records or secrets: cap excerpts,
+prefer stable IDs and URLs, and use an action or resource lookup for full data.
+
 **From the UI, in the background:**
 
 ```ts

.agents/skills/extensions/SKILL.md

@@ -129,8 +129,12 @@ Extensions have full access to app data via helpers injected into the iframe
   in chat, record passive control/selection output at
   `inline-ui:<extensionId>:output` in application state so the agent can read it
   later with `readAppState`.
-- `agentNative.chat.send(message, opts?)` — send a visible prompt or selected
-  value back into the current agent chat.
+- `agentNative.chat.send(message, opts?)` - send a visible prompt or selected
+  value back into the current agent chat. The extension bridge keeps messages
+  draft-only unless `opts.submit === true`; pass `{ submit: true }` only from a
+  user-triggered Apply or Submit action. Never call it from polling, refresh, or
+  error handlers; use application state or `agentNative.ui.output` for passive
+  results.
 
 For transient inline generative UI, `extensionData` is host-browser
 `localStorage`: the agent cannot read it, it does not sync across devices, it

.agents/skills/extensions/references/api.md

@@ -137,7 +137,7 @@ await dbExec("UPDATE notes SET title = 'Updated Title' WHERE id = 'abc'");
 | `extensionData.get(collection, id, opts?)`       | Get a single item by id                                  | `extensionData.get('todos', 'todo-1')`                                                                           |
 | `extensionData.remove(collection, id, opts?)`    | Delete an item                                           | `extensionData.remove('todos', 'todo-1')`                                                                        |
 | `agentNative.ui.output(value, opts?)`            | Record passive inline UI output in application state     | `agentNative.ui.output({ threshold })`                                                                           |
-| `agentNative.chat.send(message, opts?)`          | Send a visible prompt or selected value back to chat     | `agentNative.chat.send('Use Q2', { context: { q: 2 } })`                                                         |
+| `agentNative.chat.send(message, opts?)`          | Send a visible prompt or selected value back to chat     | `agentNative.chat.send('Use Q2', { submit: true, context: { q: 2 } })`                                           |
 
 ## Persisting Custom Data
 

.agents/skills/generative-ui/SKILL.md

@@ -76,7 +76,9 @@ The stored payload includes `value`, `updatedAt`, `extensionId`, and
 
 Use `agentNative.chat.send(message, opts?)` or `sendToAgentChat(message, opts?)`
 for a visible Apply/Submit button that should send a prompt or selected value
-into the chat.
+into the chat. Pass `{ submit: true }` explicitly for that user-triggered
+action; extension messages are draft-only otherwise. Never call these helpers
+from polling, refresh, or error handlers.
 
 ## App Data And State
 

.changeset/chat-history-rail-hover.md

@@ -0,0 +1,5 @@
+---
+"@agent-native/toolkit": patch
+---
+
+Make chat history rail overflow actions replace timestamps without layout shifts.

.changeset/durable-chat-attachments.md

@@ -0,0 +1,5 @@
+---
+"@agent-native/core": minor
+---
+
+Store chat attachments as durable object-storage references and surface Builder/custom storage setup during onboarding.

.changeset/extension-chat-submit-safety.md

@@ -0,0 +1,5 @@
+---
+"@agent-native/core": patch
+---
+
+Keep sandboxed extension chat messages draft-only unless a user action explicitly submits them.

.changeset/first-class-electron-control-plane.md

@@ -0,0 +1,5 @@
+---
+"@agent-native/dispatch": patch
+---
+
+Render integrations and scheduled work as first-class, chrome-less Electron control-plane pages.

.changeset/fix-auth-utm-callbacks.md

@@ -0,0 +1,5 @@
+---
+"@agent-native/core": patch
+---
+
+Keep email and magic-link callbacks with tracking parameters compatible with Better Auth.

.changeset/hide-chat-from-default-launchers.md

@@ -0,0 +1,5 @@
+---
+"@agent-native/dispatch": patch
+---
+
+Hide the generic Chat starter from Dispatch's default app launchers.