@agent-native/core-corpus 0.209.2-nightly-20261016153022 → 0.209.2

package/corpus/README.md

@@ -32,4 +32,4 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core-corpus/corpu
 
 ## Generated Counts
 
-- template files: 12570
+- template files: 12525

package/corpus/templates/analytics/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/analytics/CHANGELOG.md

@@ -5,19 +5,37 @@ time from the command menu (Cmd+K → "What's new") or from Settings.
 
 ## 2026-10-15
 
+### Added
+
+- Add key dates and data notes from the dashboard's new Annotations menu or a chart's menu, show or hide key-date sets per dashboard, and mark a note fixed or hide it on one chart from its hover card.
+- Data notes shade the days a chart's numbers were affected by an incident or a tracking problem, on the dashboard and in scheduled email reports.
+- Each dashboard save you make pops up with Undo, says whether everyone sees it, and shows how many others have the dashboard open.
+- In Edit mode, check two or more values in a multi-select filter and save them as a named group that everyone can pick in one click.
+
 ### Improved
 
+- Dashboard history now says what each save changed, and the save toast names the change
+- The agent now sees which key dates and data notes a dashboard's charts draw, and confirms which charts a new key date or data note shows on.
 - Collapsed navigation has clearer spacing between its icons
 
 ## 2026-10-14
 
 ### Added
 
+- Dashboard charts can mark key dates, like a launch, with a hoverable badge on the x-axis.
+- Funnel charts can split each stage into completed, skipped, moved on and left the app, so a skipped optional step no longer reads as drop-off.
+- Key-date sets: add launches and product changes once and they show on every time chart of every dashboard and in emailed reports; a dashboard can hide a set.
 - Multi-select dashboard filters can offer presets, named groups of values you pick in one click without changing the other filters.
 - Preview Sigma workbooks in Analytics; SQL import stays blocked until the BigQuery project mapping can be verified.
 
 ### Improved
 
+- Changed dashboard filters now say only you see them, and coming back to a dashboard without a default view reopens the saved view you had open.
+- Dashboard charts stay visible while they refresh or while new filters load, marked as updating, instead of blanking to a skeleton
+- Dashboards open in View mode, so looking around never changes them for everyone; switch to Edit to rearrange, rename, or resize for everyone, and column widths you drag while viewing stay just for you.
+- Dashboards show a Reset filters button whenever a filter differs from the saved view you have open, or from the defaults when no view is open, and it puts every filter back in one click.
+- Key-date markers on charts now show every event of the day in one hover card, accept a time of day and time zone, and appear on combo charts in emailed reports.
+- Dashboard charts below the fold no longer re-run their queries when filters change until you scroll to them, and scrolling a loaded chart away and back never re-runs it
 - Dashboards show a Reset filters button whenever a filter differs from the defaults, and it returns every filter to them in one click.
 - Gong questions use Gong's own search and answer in seconds instead of paging through every call.
 - Start Sigma workbook imports from the dashboard menu, use an Analytics-only connection with direct credentials, or choose a Sigma connection already granted through Dispatch.

package/corpus/templates/assets/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/brain/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/brain/CHANGELOG.md

@@ -3,6 +3,12 @@
 All notable user-facing changes to Agent-Native Brain are documented here. Open it any
 time from the command menu (Cmd+K → "What's new") or from Settings.
 
+## 2026-10-15
+
+### Improved
+
+- Saving a source's settings refreshes the Sources list faster, and the source shows "Updating…" until its new settings appear.
+
 ## 2026-10-13
 
 ### Changed

package/corpus/templates/calendar/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/chat/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/chat/scripts/migrate-production.ts

@@ -1,12 +1,16 @@
 import { closeDbExec, withMigrationRuntime } from "@agent-native/core/db";
 import { loadEnv } from "@agent-native/core/scripts";
-import { runFrameworkReleaseMigrations } from "@agent-native/core/server";
+import {
+  runAppReleaseMigrations,
+  runFrameworkReleaseMigrations,
+} from "@agent-native/core/server";
 
 loadEnv();
 
 async function main(): Promise<void> {
   await withMigrationRuntime(async () => {
     await runFrameworkReleaseMigrations(null);
+    await runAppReleaseMigrations();
   });
 }
 

package/corpus/templates/clips/CHANGELOG.md

@@ -5,6 +5,10 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ## 2026-10-15
 
+### Added
+
+- Step through a paused clip frame by frame with the comma and period keys, and comments keep the exact frame they were left on.
+
 ### Improved
 
 - Clips stays labeled in the menu bar while idle
@@ -12,6 +16,9 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Fixed
 
+- Camera permission denials now show the right recovery guidance
+- The Dictionary scrolls through long lists and stays closed during dictation, Archive and Trash show counts, and selection checkboxes stay visible over dark previews.
+- The Share and copy-link buttons now match in color.
 - Rewind can be enabled from Include last without leaving the recorder.
 - Screen Memory checks privacy exclusions during capture recovery
 - Screen Memory retries capture promptly after audio mode changes fail
@@ -20,6 +27,14 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ## 2026-10-14
 
+### Added
+
+- Add a transcript file to a clip from the transcript panel: WebVTT, SRT, or a timestamped transcript copied from YouTube. Clips keeps its timings, labels it as imported, and automatic transcription never replaces it.
+- Agents connected over MCP can upload a local video file to Clips, choose who can open it, and get its share link back.
+- Extension recordings of Agent-Native apps include what the app did, from 30 seconds before recording started, in the Debug panel and for agents.
+- Record and store your first three clips before connecting your own storage
+- Record three clips before connecting your own storage
+
 ### Improved
 
 - Earlier screen time now follows its clip's normal share rules: adding it no longer makes the clip private, and sharing the clip shares its earlier screen time with it.
@@ -28,6 +43,9 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Fixed
 
+- Captions and the transcript highlight change on cue instead of up to a quarter second late.
+- Clips recognizes existing sign-ins when checking access to free hosted recordings
+- Hosted clips now save reliably to S3-compatible storage, including streamed recordings.
 - Clips keeps the camera preview open while Control Center is active.
 - Clips recording errors without a recovery action now dismiss automatically
 - Dictation cleanup can be undone and the original transcript remains available.

package/corpus/templates/content/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/content/CHANGELOG.md

@@ -3,6 +3,12 @@
 All notable user-facing changes to Agent-Native Content are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
+## 2026-10-12
+
+### Improved
+
+- Pages open faster in a fresh browser
+
 ## 2026-10-11
 
 ### Improved

package/corpus/templates/crm/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/design/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/design/CHANGELOG.md

@@ -3,12 +3,23 @@
 All notable user-facing changes to Design are documented here. Open it any time
 from the command menu (Cmd+K → "What's new") or from Settings.
 
+## 2026-10-16
+
+### Fixed
+
+- Shift-drag keeps selected screens, screen nudges stay with the canvas selection, and Code refreshes when reopened.
+
 ## 2026-10-15
 
 ### Added
 
 - External Design agents can delete screens when you ask them.
 
+### Fixed
+
+- Empty inspector section titles stay compact
+- Fixed local screen, account, and storage setup when route or connection data is unavailable.
+
 ## 2026-10-14
 
 ### Improved
@@ -46,6 +57,9 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Fixed
 
+- Dropping a layer in the empty end of an auto-layout row of buttons keeps it in the row as the last item
+- Layers dropped onto another screen, or beside an auto-layout frame they don't fit, land where they are released instead of the screen's top-left corner
+- Moving a layer in the Layers panel, including from the board into a screen, keeps it where it sits on the canvas
 - Home prompt suggestions stay hidden until AI is connected
 - Undo reliably restores screen positions after repeated keyboard nudges
 - Comment pins no longer show in Interact mode or paint over the editor panels.

package/corpus/templates/dispatch/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/factory/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/forms/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/mail/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/mail/CHANGELOG.md

@@ -7,6 +7,7 @@ time from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Fixed
 
+- Inbox previews show apostrophes, quotes and ampersands as text instead of HTML codes.
 - Allowing automations to send no longer lets them delete mail or change Gmail settings without approval.
 - Automations that add a Gmail label no longer wait for send approval that never arrives.
 

package/corpus/templates/plan/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/slides/.agents/skills/slide-editing/references/animations.md

@@ -14,6 +14,11 @@ simulate reveals. When content and reveals change together, send both fields in
 one `patch-deck` operation. To remove reveals, send `animations: []` with the
 existing content and verify the persisted slide afterward.
 
+By default each entry waits for its own click. Set `trigger: "with-previous"`
+on an entry to play it in the same click as the entry before it, so the objects
+appear together; the first entry always waits for a click. On a `byParagraph`
+entry the trigger applies to its first paragraph only.
+
 Array order is reveal order, and each entry needs a non-empty `id`, a 0-based
 `elementIndex`, and a `type` of `appear`, `fade`, `slide-up`, or `zoom`; the
 schema rejects the operation otherwise. Nothing checks that ids are unique, but

package/corpus/templates/slides/.agents/skills/storing-data/SKILL.md

@@ -44,9 +44,11 @@ second migration owner beside it. The Chat and default starters do not ship that
 Drizzle Kit setup; follow their local instructions and the Database docs for
 the migration path. In Chat, add `server/db/schema.ts`, `server/db/index.ts`
 with `createGetDb(schema)`, and `server/plugins/db.ts` with
-`runMigrations([...], { table })`. `scripts/migrate-production.ts` is framework-only;
-do not create a parallel `runMigrations([...])` list beside a generated Drizzle
-migration owner. Give each handwritten migration a unique, stable `name`
+`runMigrations([...], { table })`. `scripts/migrate-production.ts` applies the
+framework tables and then that plugin (`runAppReleaseMigrations`), because a
+release-owned deploy skips it at boot; a project with a Drizzle config is left to
+`db:migrate`, and do not create a parallel `runMigrations([...])` list beside a
+generated Drizzle migration owner. Give each handwritten migration a unique, stable `name`
 alongside its `version`; append changes instead of renumbering, reusing, or
 editing an applied entry.
 

package/corpus/templates/slides/CHANGELOG.md

@@ -3,14 +3,45 @@
 All notable user-facing changes to Agent-Native Slides are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
+## 2026-10-16
+
+### Added
+
+- Animations can now play with the previous one, so several objects appear together in one click
+
+### Fixed
+
+- Slides keeps the original prompt available if saving a failed generation status does not work.
+
 ## 2026-10-15
 
+### Added
+
+- Advance a presentation with spoken next-slide and previous-slide commands
+
 ### Improved
 
+- Cmd+A selects all the text in a slide text box on the first press, and typing right after a bold, italic or underline toggle keeps the space you type
 - Blank decks and simple follow-ups like adding one empty slide now finish in a single quick step instead of running the full deck-generation process.
 
 ### Fixed
 
+- Backspace clears empty list items, and typed bullet markers match the text size
+- Deck prompts stay visible when generation status checks fail
+- Pasting into slide text keeps lists as lists, keeps bold and italic from other apps, and links bare URLs without leaving stray empty paragraphs
+- Presenter controls preserve Space navigation after mouse clicks and explain microphone recovery.
+- Presenter voice commands now distinguish localized phrases and preserve presentation controls.
+- Text editing in slides behaves like a standard rich text editor: Enter, Backspace and Delete join, split and exit lists, quotes and headings correctly, and Undo no longer breaks after a list toggle
+- Slides can paste the slide you copied into another deck with the keyboard or thumbnail menu.
+- Slides keeps your original request visible when a deck cannot be saved or checked.
+- Slides shows fallback prompts immediately, keeps them disabled until chat setup is ready, and persists generated decks before setup waits.
+- Undo and redo now reliably restore moved images and keep their selection in place
+- Undo and redo now restore moved objects and keep their selection stable.
+- Undo and redo now restore the correct slide change and keep the intended element selected.
+- Undo and redo reliably restore slide edits after saves and layout updates.
+- Undo and redo restore moved images and keep their selection aligned.
+- Undo and redo restore object moves, keep the changed object selected, and surface conflicts while preserving older history.
+- Your original prompt stays available when you reopen a deck after a failed generation
 - Selected slide elements now show a single blue outline.
 - Slides shows fallback prompts immediately and persists generated decks before setup waits.
 - Suggestion chips have more breathing room above the chat field
@@ -19,10 +50,12 @@ time from the command menu (Cmd+K → "What's new").
 
 ### Improved
 
+- The logo now opens an app menu with File, Edit, View, Preferences and Help.
 - Slash command options are easier to distinguish with pointer and keyboard navigation
 
 ### Fixed
 
+- Decks now render in their linked design system's colors, fonts, and canvas for everyone who can open them, even when that design system isn't shared with them or sets no slide default background
 - Backspace removes a leading space in a heading or quote without changing its formatting
 - Chats no longer stop with "result is unknown" after a rejected edit; the agent corrects the call and continues.
 - Fixed retries so the original deck request stays available if generation is delayed.

package/corpus/templates/slides/actions/get-deck.ts

@@ -196,6 +196,8 @@ function compactAnimationSummary(value: unknown, content: string) {
           typeof animation.byParagraph === "boolean"
             ? animation.byParagraph
             : false,
+        trigger:
+          animation.trigger === "with-previous" ? "with-previous" : "on-click",
         type: typeof animation.type === "string" ? animation.type : null,
         targetPreview: targetSummary?.targetPreview ?? null,
         resolvedPath: targetSummary?.resolvedPath ?? null,

package/corpus/templates/slides/actions/patch-deck.ts

@@ -56,6 +56,7 @@ import {
   assertSlideAnimationsResolve,
   type SlideAnimationBaseline,
 } from "../server/lib/validate-slide-animations.js";
+import { ANIMATION_TRIGGERS } from "../shared/api.js";
 import { ASPECT_RATIO_VALUES } from "../shared/aspect-ratios.js";
 import { isRealSlide } from "../shared/blank-slide.js";
 import { stableStringify } from "../shared/deck-content.js";
@@ -141,6 +142,12 @@ const SlideAnimationSchema = z.object({
     .describe(
       "Reveal each paragraph or list item inside this element as its own click step, in document order. A paragraph reveal starts at that paragraph and runs through the rest of its container. With nothing to split it is one step.",
     ),
+  trigger: z
+    .enum(ANIMATION_TRIGGERS)
+    .optional()
+    .describe(
+      "When this step plays. on-click (default) waits for its own click. with-previous plays in the same click as the step before it, so the objects appear together. The first step always waits for a click.",
+    ),
   type: z
     .enum(["appear", "fade", "slide-up", "zoom"])
     .describe(