@agent-native/core 0.119.3 → 0.119.5

package/corpus/templates/slides/app/components/editor/EditorSidebar.tsx

@@ -36,6 +36,7 @@ import {
 } from "@/components/ui/tooltip";
 import type { Slide } from "@/context/DeckContext";
 import { useAgentGenerating } from "@/hooks/use-agent-generating";
+import { addSlideAgentMessage } from "@/lib/agent-visible-message";
 import type { AspectRatio } from "@/lib/aspect-ratios";
 
 interface EditorSidebarProps {
@@ -413,17 +414,15 @@ function AddSlidePopover({
       }
 
       const trimmedText = text.trim();
-      const description = [trimmedText || "a new slide", googleDocContext]
-        .filter(Boolean)
-        .join("\n\n");
-      const sourceForContext = truncateSourceForContext(description);
+      const googleDocSourceForContext =
+        truncateSourceForContext(googleDocContext);
       const fileContext = describeUploadedFilesForAgent(uploaded, deckId);
       const context = [
         `Add a new slide to deck "${deckTitle}" (id: ${deckId}).`,
         `Insert after slide ${activeSlideIndex + 1} of ${slideCount} (active slide id: ${activeSlideId}).`,
-        "The text below is the user's request and/or pasted source material for the new slide(s). Treat pasted memo content as source material even if the user did not explicitly say they are pasting it.",
-        `User request / source material:\n${sourceForContext.text}`,
-        sourceForContext.truncated
+        "The visible user message above contains the user's request and/or pasted source material for the new slide(s). Treat pasted memo content as source material even if the user did not explicitly say they are pasting it.",
+        googleDocSourceForContext.text,
+        googleDocSourceForContext.truncated
           ? `The pasted source was longer than ${MAX_SOURCE_CONTEXT_CHARS} characters, so only the first ${MAX_SOURCE_CONTEXT_CHARS} characters were included to keep the agent request reliable.`
           : "",
         fileContext,
@@ -438,10 +437,7 @@ function AddSlidePopover({
         "For larger requests, keep adding slides sequentially: wait for each add-slide result, then call add-slide for the next slide. Start slide 1 immediately; do not wait to design the entire sequence before adding it.",
       ].join("\n");
 
-      agentSubmit(
-        `Add slide: ${summarizePromptForChat(trimmedText || "a new slide")}`,
-        context,
-      );
+      agentSubmit(addSlideAgentMessage(trimmedText), context);
       onOpenChange(false);
     },
     [
@@ -539,13 +535,6 @@ function AddSlidePopover({
   );
 }
 
-function summarizePromptForChat(prompt: string): string {
-  const singleLine = prompt.trim().replace(/\s+/g, " ");
-  if (!singleLine) return "a new slide";
-  if (singleLine.length <= 180) return singleLine;
-  return `${singleLine.slice(0, 177)}...`;
-}
-
 export default function EditorSidebar({
   slides,
   activeSlideId,

package/corpus/templates/slides/app/lib/agent-visible-message.ts

@@ -0,0 +1,28 @@
+export const MAX_AGENT_VISIBLE_MESSAGE_CHARS = 60_000;
+
+function formatVisibleAgentMessage(
+  action: string,
+  prompt: string,
+  fallback: string,
+): string {
+  const prefix = `${action}: `;
+  const trimmedPrompt = prompt.trim() || fallback;
+  if (prefix.length + trimmedPrompt.length <= MAX_AGENT_VISIBLE_MESSAGE_CHARS) {
+    return `${prefix}${trimmedPrompt}`;
+  }
+
+  const suffix = "\n\n[Prompt truncated for reliability]";
+  const maxPromptChars = Math.max(
+    0,
+    MAX_AGENT_VISIBLE_MESSAGE_CHARS - prefix.length - suffix.length,
+  );
+  return `${prefix}${trimmedPrompt.slice(0, maxPromptChars)}${suffix}`;
+}
+
+export function createDeckAgentMessage(prompt: string): string {
+  return formatVisibleAgentMessage("Create deck", prompt, "new deck");
+}
+
+export function addSlideAgentMessage(prompt: string): string {
+  return formatVisibleAgentMessage("Add slide", prompt, "a new slide");
+}

package/corpus/templates/slides/app/pages/Index.tsx

@@ -44,9 +44,9 @@ import { ToggleGroup, ToggleGroupItem } from "@/components/ui/toggle-group";
 import { useDecks } from "@/context/DeckContext";
 import { useAgentGenerating } from "@/hooks/use-agent-generating";
 import { useDesignSystems } from "@/hooks/use-design-systems";
+import { createDeckAgentMessage } from "@/lib/agent-visible-message";
 import { savePromptToComposerDraft } from "@/lib/composer-draft";
 
-const MAX_SOURCE_CONTEXT_CHARS = 60_000;
 const NEW_DECK_DRAFT_SCOPE = "slides-new-deck";
 const PENDING_PROMPT_KEY = "slides:pending-deck-prompt";
 
@@ -84,26 +84,6 @@ function mergeUploadedFilesForRetry(
   });
 }
 
-function summarizePromptForChat(prompt: string): string {
-  const singleLine = prompt.trim().replace(/\s+/g, " ");
-  if (!singleLine) return "new deck";
-  if (singleLine.length <= 180) return singleLine;
-  return `${singleLine.slice(0, 177)}...`;
-}
-
-function truncateSourceForContext(prompt: string): {
-  text: string;
-  truncated: boolean;
-} {
-  if (prompt.length <= MAX_SOURCE_CONTEXT_CHARS) {
-    return { text: prompt, truncated: false };
-  }
-  return {
-    text: prompt.slice(0, MAX_SOURCE_CONTEXT_CHARS),
-    truncated: true,
-  };
-}
-
 interface DesignSystemGenerationContextResult {
   title?: string;
   agentContext?: string;
@@ -386,7 +366,6 @@ export default function Index() {
         : "";
 
     const trimmedPrompt = prompt.trim();
-    const sourceForContext = truncateSourceForContext(trimmedPrompt);
     const hasImportedGoogleDocContext = trimmedPrompt.includes("<google-doc ");
     const googleDocUrls = hasImportedGoogleDocContext
       ? []
@@ -426,13 +405,7 @@ export default function Index() {
 
     const context = [
       `The user just created a new empty deck (id: "${deck.id}") and wants to create a presentation or standalone visual.`,
-      "The text below is the user's request and/or pasted source material for the deck. Treat pasted memo content as source material even if the user did not explicitly say they are pasting it.",
-      trimmedPrompt
-        ? `User request / source material:\n${sourceForContext.text}`
-        : "User request / source material: create a new deck.",
-      sourceForContext.truncated
-        ? `The pasted source was longer than ${MAX_SOURCE_CONTEXT_CHARS} characters, so only the first ${MAX_SOURCE_CONTEXT_CHARS} characters were included to keep the agent request reliable.`
-        : "",
+      "The visible user message above contains the user's request and/or pasted source material for the deck. Treat pasted memo content as source material even if the user did not explicitly say they are pasting it.",
       googleDocContext,
       fileContext,
       designSystemContext,
@@ -466,11 +439,10 @@ export default function Index() {
     clearPendingPromptForRetry();
     setNewDeckInitialPrompt(null);
     setNewDeckRetryFiles([]);
-    agentSubmit(
-      `Create deck: ${summarizePromptForChat(trimmedPrompt)}`,
-      context,
-      { newTab: true, openSidebar: true },
-    );
+    agentSubmit(createDeckAgentMessage(trimmedPrompt), context, {
+      newTab: true,
+      openSidebar: true,
+    });
     navigate(`/deck/${deck.id}?generating=1`);
   };
 

package/corpus/templates/slides/changelog/2026-07-23-full-prompts-stay-visible-in-chat-when-creating-decks-or-add.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-07-23
+---
+
+Full prompts stay visible in chat when creating decks or adding slides.

package/corpus/templates/slides/changelog/2026-07-23-opening-or-refining-a-deck-no-longer-crashes-with-a-blank-er.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-07-23
+---
+
+Opening or refining a deck no longer crashes with a blank error screen when the deck has an unrecognized aspect ratio

package/corpus/templates/slides/shared/aspect-ratios.ts

@@ -30,5 +30,8 @@ export const ASPECT_RATIO_VALUES = ["16:9", "1:1", "9:16", "4:5"] as const;
 export const DEFAULT_ASPECT_RATIO: AspectRatio = "16:9";
 
 export function getAspectRatioDims(ratio: AspectRatio | undefined | null) {
-  return ASPECT_RATIOS[ratio ?? DEFAULT_ASPECT_RATIO];
+  if (ratio && Object.prototype.hasOwnProperty.call(ASPECT_RATIOS, ratio)) {
+    return ASPECT_RATIOS[ratio];
+  }
+  return ASPECT_RATIOS[DEFAULT_ASPECT_RATIO];
 }

package/corpus/templates/tasks/.oxfmtrc.json

@@ -0,0 +1,8 @@
+{
+  "tabWidth": 2,
+  "useTabs": false,
+  "printWidth": 80,
+  "trailingComma": "all",
+  "proseWrap": "preserve",
+  "sortImports": true
+}

package/corpus/templates/tasks/AGENTS.md

@@ -7,6 +7,11 @@ inventory existing public kits and installed package seams. Use
 `customizing-agent-native` for the configure → compose → eject → propose seam
 ladder.
 
+## Authoritative References
+
+- [Feature docs](./docs/features/README.md) define product behavior and feature status.
+- [Action definitions](./actions/) contain the canonical tool descriptions, input schemas, and implementations.
+
 ## Core Rules
 
 - Never hardcode API keys, tokens, webhook URLs, signing secrets, private Builder/internal data, customer data, or credential-looking literals. Use secrets/OAuth/runtime configuration and obvious placeholders in examples.
@@ -16,34 +21,38 @@ ladder.
 - Keep the action surface small: task CRUD actions plus `reorder-tasks`, `view-screen`, and `navigate`.
 - Do not use `db-query` for normal task operations.
 - Call `view-screen` first when the user's visible task context matters (especially on `/tasks`).
+- Tasks are private to each user. Preserve `ownerEmail` scoping unless intentionally implementing sharing.
+- The task detail panel exposes `tasks.task-detail.bottom` as an `ExtensionSlot` with `slotContext` containing `taskId`, `title`, `done`, and `fieldValues`.
 
 ## Actions
 
-| Action                       | Method | Purpose                                                                                      |
-| ---------------------------- | ------ | -------------------------------------------------------------------------------------------- |
-| `list-tasks`                 | GET    | List current user's tasks; `includeDone` and `includeFields` default to false                |
-| `create-task`                | POST   | Create a task with `title`                                                                   |
-| `update-task`                | POST   | Patch `title`, `done`, and/or `fieldValues` by `taskId`                                      |
-| `delete-task`                | POST   | Delete a task by `taskId` (confirm with user first)                                          |
-| `bulk-update-tasks`          | POST   | Patch `title` and/or `done` on multiple tasks by id                                          |
-| `bulk-delete-tasks`          | POST   | Delete multiple tasks by id (confirm with user first)                                        |
-| `reorder-tasks`              | POST   | Reorder visible tasks by id list top-to-bottom                                               |
-| `list-inbox-items`           | GET    | List current user's inbox items                                                              |
-| `create-inbox-item`          | POST   | Create a not-ready inbox item with `title` (default chat capture)                            |
-| `update-inbox-item`          | POST   | Patch inbox item `title` by `inboxItemId`                                                    |
-| `delete-inbox-item`          | POST   | Delete an inbox item (confirm with user first)                                               |
-| `mark-inbox-item-ready`      | POST   | Promote inbox item to an incomplete task                                                     |
-| `reorder-inbox-items`        | POST   | Reorder inbox items by id list top-to-bottom                                                 |
-| `list-custom-fields`         | GET    | List custom field definitions                                                                |
-| `create-custom-field`        | POST   | Create a custom field definition with `title`, `type`, and optional `config`                 |
-| `update-custom-field`        | POST   | Patch a field definition `title` and/or type-compatible `config`; type is immutable          |
-| `delete-custom-field`        | POST   | Delete a field definition and its values on every task (confirm with user first)             |
-| `reorder-custom-fields`      | POST   | Reorder custom field definitions by id list top-to-bottom                                    |
-| `list-visible-task-fields`   | GET    | List custom field ids shown on task cards for the current user                               |
-| `update-visible-task-fields` | POST   | Replace which custom fields appear on task cards (max 3)                                     |
-| `view-screen`                | —      | Read navigation, UI bulk selection, visible tasks, and inbox snapshot                        |
-| `navigate`                   | —      | Move UI to a view: `tasks`, `inbox`, `fields`, `extensions`, `team` (`home`/`ask` → `tasks`) |
-| `render-task-list-inline`    | —      | Render an interactive task-list widget inline in chat without leaving the current view       |
+| Action                        | Method | Purpose                                                                                      |
+| ----------------------------- | ------ | -------------------------------------------------------------------------------------------- |
+| `list-tasks`                  | GET    | List current user's tasks; `includeDone` and `includeFields` default to false                |
+| `create-task`                 | POST   | Create a task with `title`                                                                   |
+| `update-task`                 | POST   | Patch `title`, `done`, and/or `fieldValues` by `taskId`                                      |
+| `delete-task`                 | POST   | Delete a task by `taskId` (confirm with user first)                                          |
+| `bulk-update-tasks`           | POST   | Patch `title` and/or `done` on multiple tasks by id                                          |
+| `bulk-delete-tasks`           | POST   | Delete multiple tasks by id (confirm with user first)                                        |
+| `reorder-tasks`               | POST   | Reorder visible tasks by id list top-to-bottom                                               |
+| `list-inbox-items`            | GET    | List current user's inbox items                                                              |
+| `create-inbox-item`           | POST   | Create a not-ready inbox item with `title` (default chat capture)                            |
+| `update-inbox-item`           | POST   | Patch inbox item `title` by `inboxItemId`                                                    |
+| `delete-inbox-item`           | POST   | Delete an inbox item (confirm with user first)                                               |
+| `bulk-delete-inbox-items`     | POST   | Delete multiple inbox items by id (confirm with user first)                                  |
+| `mark-inbox-item-ready`       | POST   | Promote inbox item to an incomplete task                                                     |
+| `bulk-mark-inbox-items-ready` | POST   | Promote multiple inbox items to incomplete tasks by id                                       |
+| `reorder-inbox-items`         | POST   | Reorder inbox items by id list top-to-bottom                                                 |
+| `list-custom-fields`          | GET    | List custom field definitions                                                                |
+| `create-custom-field`         | POST   | Create a custom field definition with `title`, `type`, and optional `config`                 |
+| `update-custom-field`         | POST   | Patch a field definition `title` and/or type-compatible `config`; type is immutable          |
+| `delete-custom-field`         | POST   | Delete a field definition and its values on every task (confirm with user first)             |
+| `reorder-custom-fields`       | POST   | Reorder custom field definitions by id list top-to-bottom                                    |
+| `list-visible-task-fields`    | GET    | List custom field ids shown on task cards for the current user                               |
+| `update-visible-task-fields`  | POST   | Replace which custom fields appear on task cards (max 3)                                     |
+| `view-screen`                 | —      | Read navigation, UI bulk selection, visible tasks, and inbox snapshot                        |
+| `navigate`                    | —      | Move UI to a view: `tasks`, `inbox`, `fields`, `extensions`, `team` (`home`/`ask` → `tasks`) |
+| `render-task-list-inline`     | —      | Render an interactive task-list widget inline in chat without leaving the current view       |
 
 ## Store Functions And Transactions
 
@@ -80,22 +89,6 @@ export type DbHandle = Pick<
 
 ## Commit Message Conventions
 
-- Never include `Made-with: Cursor` in commit messages. Remove it if it appears
-  in a generated message.
-- Use one of these prefixes:
-  - `feature: ...` or `feature(PROJECT): ...`
-  - `fix: ...` or `fix(PROJECT): ...`
-  - `refactor: ...` or `refactor(PROJECT): ...`
-  - `technical: ...` or `technical(PROJECT): ...`
-  - `chore: ...` or `chore(PROJECT): ...`
-- `PROJECT` is optional. If provided, it must be one of `generator` or `web`.
-- Before creating any commit, always:
-  - ask for confirmation,
-  - show the proposed commit message first,
-  - commit only after explicit user approval.
-
-## Commit Message Conventions
-
 - Never include `Made-with: Cursor` in commit messages. Remove it if it appears
   in a generated message.
 - Use one of these prefixes:

package/corpus/templates/tasks/README.md

@@ -4,13 +4,20 @@ Task-list-first agent-native app. Default home is `/tasks`; chat handles capture
 
 ## TODO
 
-- [ ] **i18n** — Add `app/i18n/` catalogs (`en-US` + locale mirrors) and migrate UI copy from raw literals to `useT()`. Remove tasks strings from `scripts/i18n-raw-literal-baseline.txt` once migrated.
-- [ ] **Delete dialog wiring** — `TaskList` and `InboxList` duplicate single/bulk delete dialog state (`pendingDeleteId`, `bulkDeleteOpen`, confirm handlers, toast on bulk success). Extract a shared hook or composer helper (e.g. `useDeleteDialogs`) that owns pending id, open state, and confirm wiring while composers pass entity labels and delete mutations.
-- [ ] Extract shared action schema helpers (e.g. `taskId` field, title patch) once the action surface grows beyond MVP.
-- [ ] Add route-level `ErrorBoundary` and `Suspense` around task list loading (align with other agent-native templates).
+- [ ] **Runtime action discovery filtering** — Update `@agent-native/core` development action discovery to exclude colocated `*.test.*`, `*.spec.*`, and helper-only modules so they are never exposed as agent tools or HTTP action routes.
+- [ ] **Optional event-triggered automations** — If Tasks needs workflows such as “when a task is completed, notify another system,” register stable domain events in `server/plugins/agent-chat.ts` and emit owner-scoped payloads from the successful write paths. Add event discovery, payload-validation, transition, and failure-isolation tests before exposing the events as a public automation contract.
 - [ ] **`view-screen` agent snapshot** — Revisit `AGENT_TASKS_LIST_CAP` in `actions/view-screen.ts`: it caps the agent tool payload (token budget), not the UI list. Confirm whether `list` / `selectedItem` / `inListSnapshot` correctly represent what the user sees, tune or document the cap, and align with UI limits if needed. Also review Zod parsing of `navigation` / app-state selection keys for strictness vs backward compatibility.
-- [ ] **Selection context** — Revisit prop drilling through `TaskList` → header/bar/rows once the composer stabilizes; a narrow context for `{ state, actions }` would trim wiring but must not blur the `dnd/` ↔ `selection/` boundary.
 - [ ] **`TaskList` optimistic state** — Refactor manual `allTasks` buffer in `app/components/tasks/TaskList.tsx` to TanStack Query `onMutate` once exit animations and reorder rollback can share one cache strategy.
 - [ ] **Exit-animation list reconcile** — Move exit-animation reconcile / `exitingIdsRef` out of `app/components/tasks/TaskList.tsx` into a neutral list helper (e.g. `use-ordered-tasks-with-exit-animation.ts`). That logic keeps completed rows visible during CSS exit when Show all is off; it is not DnD. `TaskList` should pass an ordered list into generic `SortableList`.
-- Shared `ListRowPreview` (`app/components/shared/dnd/ListRowPreview.tsx`) still duplicates row chrome; render the live row in the overlay when `SortableList` can mount previews safely (see TODO in that file).
 - [ ] **`move-tasks` / relative reorder (try on a separate branch)** — Today DnD persistence is FE-heavy: `SortableList` runs `reorderMovingItems` (`app/components/dnd/reorder-moving-items.ts`) to compute the **full visible id list**, then `TaskList` calls `reorder-tasks` with every id top-to-bottom. The BE already persists order via `server/tasks/store.ts` `reorderTasks` — no separate `bulkReorder` needed, but the **drop → order** translation is brittle (multi-select before/after/top/bottom edge cases). **Proposal:** add a relative move action, e.g. `move-tasks` with `{ taskIds, beforeId? | afterId?, includeDone? }` (or extend `reorder-tasks` with a relative mode). BE applies the block move, validates visible list / ownership, rewrites `sortOrder`, returns updated tasks. Keep **absolute** full-list `taskIds[]` as an escape hatch for agent/import flows. **FE after refactor:** dnd-kit still handles overlay/collision/optimistic UI, but on drop only derives `{ selected ids, anchor id, before | after }` from `over` + drag direction — delete most of `computeBlockInsertIndex`. **Prefer `beforeId`/`afterId` over `toIndex`** — matches user/agent language (“put these after task Z”) and avoids index ambiguity with `includeDone` / hidden rows. **Touch:** new `actions/move-tasks.ts`, `server/tasks/store.ts`, `use-tasks.ts`, `TaskList.tsx` / `InboxList.tsx`, agent prompt in `server/plugins/agent-chat.ts`, unit tests on store + thin FE mapping tests; keep `reorder-tasks` until callers migrate.
+- [ ] **List pagination + virtualization (when volume warrants)** — `listStoredItems` is unbounded and rows render unvirtualized. Fine at personal-list volumes; if lists grow, adopt mail's pattern (`useInfiniteQuery` with page size 25 + `@tanstack/react-virtual` in `EmailList.tsx`). Parked by the 2026-07-17 sibling-parity review as a latent scaling concern, not an active bug.
+
+## Optional improvements
+
+Reviewed against sibling templates (starter, mail, content, calendar, plan): none of these has an established cross-template convention to adopt, so they are optional polish rather than alignment work.
+
+- [ ] **Delete dialog wiring** — `TaskList` and `InboxList` duplicate single/bulk delete dialog state (`pendingDeleteId`, `bulkDeleteOpen`, confirm handlers, toast on bulk success); a shared `useDeleteDialogs` hook could own that wiring. Siblings: no template has a shared delete-confirm hook — each inlines shadcn `AlertDialog` per call site (calendar's `DeleteEventDialog` is feature-specific). tasks' shared `DeleteItemDialog`/`BulkDeleteDialog` components already lead here; this would be a net-new pattern, not adoption.
+- [ ] **Shared action schema helpers** — Extract shared helpers (e.g. `taskId` field, title patch) if duplication grows. Siblings: no template has generic schema helpers — every action inlines `z.object({...})` in `defineAction`; the only shared primitives are feature-specific (clips' `booleanParam`, tasks' own `boolean-query-param`). Wait for a concrete third duplication before abstracting.
+- [ ] **Custom `ErrorBoundary` copy** — tasks already exports the root-level `ErrorBoundary` (re-export from `@agent-native/core/client`), which is full boundary parity: no template has per-route boundaries, and `Suspense` only wraps `lazy()` components — data loads through react-query, not loaders. The only optional delta: mail and content (2 of 4) replace the re-export with custom copy plus `ErrorReportActions` (send feedback / open issue).
+- [ ] **Task attachments** — no `@agent-native/core/file-upload` usage anywhere, though `.gitignore` already carries the standard `data/uploads/` entry. mail/content/plan use the framework file-upload module. A product decision, not an alignment gap.
+- [ ] **Selection context** — Revisit prop drilling through `TaskList` → header/bar/rows; a narrow `{ state, actions }` context would trim wiring but must not blur the `dnd/` ↔ `selection/` boundary. Siblings: no template uses a React context for list multi-select — the universal pattern is a `useState<Set<string>>` hook plus prop drilling (mail's `EmailList` passes `selectedIds` down as props), and tasks' `use-list-selection.ts` is already the most generalized version of it.

package/corpus/templates/tasks/actions/bulk-delete-inbox-items.ts

@@ -4,16 +4,18 @@ import { z } from "zod";
 import { deleteInboxItems, requireUserEmail } from "../server/inbox/store.js";
 import { BULK_ID_LIMIT } from "../shared/bulk-limits.js";
 
+export const bulkDeleteInboxItemsSchema = z.object({
+  inboxItemIds: z
+    .array(z.string())
+    .min(1)
+    .max(BULK_ID_LIMIT)
+    .describe("Inbox item ids to delete"),
+});
+
 export default defineAction({
   description:
-    "Delete multiple inbox items permanently. Ask the user to confirm before calling.",
-  schema: z.object({
-    inboxItemIds: z
-      .array(z.string())
-      .min(1)
-      .max(BULK_ID_LIMIT)
-      .describe("Inbox item ids to delete"),
-  }),
+    "Delete multiple inbox items permanently. Use delete-inbox-item for one item. Ask the user to confirm before calling.",
+  schema: bulkDeleteInboxItemsSchema,
   run: async (args, ctx) => {
     const ownerEmail = requireUserEmail(ctx?.userEmail);
     return deleteInboxItems({

package/corpus/templates/tasks/actions/bulk-delete-tasks.ts

@@ -4,16 +4,18 @@ import { z } from "zod";
 import { deleteTasks, requireUserEmail } from "../server/tasks/store.js";
 import { BULK_ID_LIMIT } from "../shared/bulk-limits.js";
 
+export const bulkDeleteTasksSchema = z.object({
+  taskIds: z
+    .array(z.string())
+    .min(1)
+    .max(BULK_ID_LIMIT)
+    .describe("Task ids to delete"),
+});
+
 export default defineAction({
   description:
-    "Delete multiple tasks permanently. Ask the user to confirm before calling.",
-  schema: z.object({
-    taskIds: z
-      .array(z.string())
-      .min(1)
-      .max(BULK_ID_LIMIT)
-      .describe("Task ids to delete"),
-  }),
+    "Delete multiple tasks permanently. Use delete-task for one task. Ask the user to confirm before calling.",
+  schema: bulkDeleteTasksSchema,
   run: async (args, ctx) => {
     const ownerEmail = requireUserEmail(ctx?.userEmail);
     return deleteTasks({ ownerEmail, ids: args.taskIds });

package/corpus/templates/tasks/actions/bulk-mark-inbox-items-ready.ts

@@ -9,7 +9,7 @@ import { BULK_ID_LIMIT } from "../shared/bulk-limits.js";
 
 export default defineAction({
   description:
-    "Promote multiple inbox items to incomplete tasks in one atomic batch.",
+    "Promote multiple inbox items to incomplete tasks in one atomic batch, preserving their ids. Use mark-inbox-item-ready for one item.",
   schema: z.object({
     inboxItemIds: z
       .array(z.string())

package/corpus/templates/tasks/actions/bulk-update-tasks.ts

@@ -5,18 +5,20 @@ import { UserInputError } from "../server/errors.js";
 import { requireUserEmail, updateTasks } from "../server/tasks/store.js";
 import { BULK_ID_LIMIT } from "../shared/bulk-limits.js";
 
+export const bulkUpdateTasksSchema = z.object({
+  taskIds: z
+    .array(z.string())
+    .min(1)
+    .max(BULK_ID_LIMIT)
+    .describe("Task ids to update"),
+  title: z.string().min(1).optional().describe("New title for every task"),
+  done: z.boolean().optional().describe("Completion state for every task"),
+});
+
 export default defineAction({
   description:
-    "Update multiple tasks with the same title and/or completion patch.",
-  schema: z.object({
-    taskIds: z
-      .array(z.string())
-      .min(1)
-      .max(BULK_ID_LIMIT)
-      .describe("Task ids to update"),
-    title: z.string().min(1).optional().describe("New title for every task"),
-    done: z.boolean().optional().describe("Completion state for every task"),
-  }),
+    "Apply the same title and/or completion state to multiple tasks. Use update-task for one task or custom field values.",
+  schema: bulkUpdateTasksSchema,
   run: async (args, ctx) => {
     const ownerEmail = requireUserEmail(ctx?.userEmail);
     if (args.title === undefined && args.done === undefined) {

package/corpus/templates/tasks/actions/create-inbox-item.ts

@@ -5,11 +5,14 @@ import { z } from "zod";
 import { createInboxItem, requireUserEmail } from "../server/inbox/store.js";
 import type { InboxItem } from "../server/inbox/store.js";
 
+export const createInboxItemSchema = z.object({
+  title: z.string().min(1).describe("Inbox item title"),
+});
+
 export default defineAction({
-  description: "Create a not-ready inbox item with a title.",
-  schema: z.object({
-    title: z.string().min(1).describe("Inbox item title"),
-  }),
+  description:
+    "Create a not-ready inbox item for later triage. Use create-task when the user explicitly wants it added directly to the task list.",
+  schema: createInboxItemSchema,
   run: async (args, ctx) => {
     const ownerEmail = requireUserEmail(ctx?.userEmail);
     const item = await createInboxItem({ ownerEmail, title: args.title });

package/corpus/templates/tasks/actions/create-task.ts

@@ -9,7 +9,8 @@ import {
 } from "../server/tasks/store.js";
 
 export default defineAction({
-  description: "Create a new task with a title.",
+  description:
+    "Create an incomplete task directly on the task list. Use create-inbox-item for a quick capture to triage later.",
   schema: z.object({
     title: z.string().min(1).describe("Task title"),
   }),

package/corpus/templates/tasks/actions/delete-inbox-item.ts

@@ -3,12 +3,14 @@ import { z } from "zod";
 
 import { deleteInboxItem, requireUserEmail } from "../server/inbox/store.js";
 
+export const deleteInboxItemSchema = z.object({
+  inboxItemId: z.string().describe("Inbox item id"),
+});
+
 export default defineAction({
   description:
-    "Delete an inbox item permanently. Ask the user to confirm before calling.",
-  schema: z.object({
-    inboxItemId: z.string().describe("Inbox item id"),
-  }),
+    "Delete one inbox item permanently. Use bulk-delete-inbox-items for multiple items. Ask the user to confirm before calling.",
+  schema: deleteInboxItemSchema,
   run: async (args, ctx) => {
     const ownerEmail = requireUserEmail(ctx?.userEmail);
     await deleteInboxItem({ ownerEmail, id: args.inboxItemId });

package/corpus/templates/tasks/actions/delete-task.ts

@@ -5,7 +5,7 @@ import { deleteTask, requireUserEmail } from "../server/tasks/store.js";
 
 export default defineAction({
   description:
-    "Delete a task permanently. Ask the user to confirm before calling.",
+    "Delete one task permanently. Use bulk-delete-tasks for multiple tasks. Ask the user to confirm before calling.",
   schema: z.object({
     taskId: z.string().describe("Task id"),
   }),

package/corpus/templates/tasks/actions/list-inbox-items.ts

@@ -3,9 +3,11 @@ import { z } from "zod";
 
 import { listInboxItems, requireUserEmail } from "../server/inbox/store.js";
 
+export const listInboxItemsSchema = z.object({});
+
 export default defineAction({
-  description: "List inbox items for the current user (not-ready capture).",
-  schema: z.object({}),
+  description: "List not-ready inbox items awaiting triage.",
+  schema: listInboxItemsSchema,
   http: { method: "GET" },
   readOnly: true,
   run: async (_args, ctx) => {

package/corpus/templates/tasks/actions/list-visible-task-fields.ts

@@ -4,10 +4,12 @@ import { z } from "zod";
 import { requireUserEmail } from "../server/custom-fields/store.js";
 import { getTaskCardFieldIds } from "../server/user-config/store.js";
 
+export const listVisibleTaskFieldsSchema = z.object({});
+
 export default defineAction({
   description:
     "List custom field ids currently shown on task cards for the current user.",
-  schema: z.object({}),
+  schema: listVisibleTaskFieldsSchema,
   http: { method: "GET" },
   readOnly: true,
   run: async (_args, ctx) => {

package/corpus/templates/tasks/actions/mark-inbox-item-ready.ts

@@ -5,12 +5,14 @@ import { z } from "zod";
 import { markInboxItemReady, requireUserEmail } from "../server/inbox/store.js";
 import type { Task } from "../server/tasks/store.js";
 
+export const markInboxItemReadySchema = z.object({
+  inboxItemId: z.string().describe("Inbox item id"),
+});
+
 export default defineAction({
   description:
-    "Mark an inbox item ready: promotes the inbox item to an incomplete task (same id).",
-  schema: z.object({
-    inboxItemId: z.string().describe("Inbox item id"),
-  }),
+    "Promote one inbox item to an incomplete task, preserving its id. Use bulk-mark-inbox-items-ready for multiple items.",
+  schema: markInboxItemReadySchema,
   run: async (args, ctx) => {
     const ownerEmail = requireUserEmail(ctx?.userEmail);
     return markInboxItemReady({ ownerEmail, id: args.inboxItemId });

package/corpus/templates/tasks/actions/navigate.ts

@@ -21,22 +21,24 @@ import { optionalBooleanQueryParam } from "./lib/boolean-query-param.js";
 
 const viewSchema = z.enum(NAV_VIEW_INPUTS);
 
+export const navigateSchema = z.object({
+  view: viewSchema.describe(
+    "View name to navigate to; home and ask are aliases for tasks",
+  ),
+  taskId: z.string().optional().describe("Selected task id on /tasks"),
+  fieldId: z
+    .string()
+    .optional()
+    .describe("Selected custom field id on /fields"),
+  includeDone: optionalBooleanQueryParam().describe(
+    "When true, show completed tasks on /tasks",
+  ),
+});
+
 export default defineAction({
   description:
-    "Navigate the UI to a specific view. Writes a navigate command to application state which the UI reads and auto-deletes.",
-  schema: z.object({
-    view: viewSchema.describe(
-      "View name to navigate to; home and ask are aliases for tasks",
-    ),
-    taskId: z.string().optional().describe("Selected task id on /tasks"),
-    fieldId: z
-      .string()
-      .optional()
-      .describe("Selected custom field id on /fields"),
-    includeDone: optionalBooleanQueryParam().describe(
-      "When true, show completed tasks on /tasks",
-    ),
-  }),
+    "Navigate the Tasks UI to a view, optionally selecting a task or custom field.",
+  schema: navigateSchema,
   http: false,
   run: async (args) => {
     const view = resolveNavView(args.view);

package/corpus/templates/tasks/actions/reorder-inbox-items.ts

@@ -4,16 +4,18 @@ import { z } from "zod";
 import { reorderInboxItems, requireUserEmail } from "../server/inbox/store.js";
 import { BULK_ID_LIMIT } from "../shared/bulk-limits.js";
 
+export const reorderInboxItemsSchema = z.object({
+  inboxItemIds: z
+    .array(z.string())
+    .min(1)
+    .max(BULK_ID_LIMIT)
+    .describe("Inbox item ids in the desired order from top to bottom."),
+});
+
 export default defineAction({
   description:
     "Reorder the inbox list by passing inbox item ids top-to-bottom.",
-  schema: z.object({
-    inboxItemIds: z
-      .array(z.string())
-      .min(1)
-      .max(BULK_ID_LIMIT)
-      .describe("Inbox item ids in the desired order from top to bottom."),
-  }),
+  schema: reorderInboxItemsSchema,
   run: async (args, ctx) => {
     const ownerEmail = requireUserEmail(ctx?.userEmail);
     return reorderInboxItems({