@agent-native/core 0.176.0-nightly-20260828040116 → 0.176.1

package/corpus/README.md

@@ -31,4 +31,4 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core/corpus
 
 ## Generated Counts
 
-- template files: 8654
+- template files: 8675

package/corpus/templates/analytics/CHANGELOG.md

@@ -3,6 +3,21 @@
 All notable user-facing changes to Agent-Native Analytics are documented here. Open it any
 time from the command menu (Cmd+K → "What's new") or from Settings.
 
+## 2026-08-27
+
+### Added
+
+- Dashboard owners can archive dashboards from the actions menu.
+- See signup, onboarding, activation, and sharing drop-off in one filterable dashboard.
+
+### Improved
+
+- Show connected Google names and profile photos in analytics
+
+### Fixed
+
+- Analytics exports now show a direct download in chat and reject failed responses
+
 ## 2026-08-26
 
 ### Improved

package/corpus/templates/analytics/docs/schemas/first-party-analytics.md

@@ -117,24 +117,25 @@ event_name = '$ai_sentiment'
 
 Useful query fields live in `properties`:
 
-| Property                                         | Description                                                                                       |
-| ------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
-| `$ai_trace_id`, `run_id`                         | Agent run id                                                                                      |
-| `$ai_session_id`, `thread_id`                    | Chat/thread id, when available                                                                    |
-| `$ai_model`, `model`                             | Model used                                                                                        |
-| `$ai_provider`, `provider`                       | Engine/provider name                                                                              |
-| `$ai_input_tokens`, `input_tokens`               | Input tokens                                                                                      |
-| `$ai_output_tokens`, `output_tokens`             | Output tokens                                                                                     |
-| `cache_read_tokens`, `cache_write_tokens`        | Prompt-cache token counts                                                                         |
-| `$ai_total_cost_usd`, `cost_usd`                 | Estimated run cost in USD                                                                         |
-| `cost_cents_x100`                                | Estimated run cost in centicents                                                                  |
-| `duration_ms`                                    | Run duration in milliseconds                                                                      |
-| `$ai_latency`                                    | Model time in seconds (run duration minus tool time), on `$ai_generation`                         |
-| `tool_calls`, `successful_tools`, `failed_tools` | Complete tool-call counts                                                                         |
-| `tools`, `tools_truncated`                       | First 50 tool names, offsets, durations, statuses, and error classes, including interrupted calls |
-| `delegated`, `delegation_protocol`, `caller_app` | Delegated-run attribution                                                                         |
-| `a2a_task_id`, `parent_run_id`, `parent_turn_id` | Cross-app trace linkage, when available                                                           |
-| `$ai_is_error`, `status`, `$ai_error`            | Error status and message, when applicable                                                         |
+| Property                                         | Description                                                                                                              |
+| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
+| `$ai_trace_id`, `run_id`                         | Agent run id                                                                                                             |
+| `$ai_session_id`, `thread_id`                    | Chat/thread id, when available                                                                                           |
+| `$ai_model`, `model`                             | Model used                                                                                                               |
+| `$ai_provider`, `provider`                       | Engine/provider name                                                                                                     |
+| `$ai_input_tokens`, `input_tokens`               | Input tokens                                                                                                             |
+| `$ai_output_tokens`, `output_tokens`             | Output tokens                                                                                                            |
+| `cache_read_tokens`, `cache_write_tokens`        | Prompt-cache token counts                                                                                                |
+| `$ai_total_cost_usd`, `cost_usd`                 | Estimated run cost in USD                                                                                                |
+| `cost_cents_x100`                                | Estimated run cost in centicents                                                                                         |
+| `duration_ms`                                    | Run duration in milliseconds                                                                                             |
+| `$ai_latency`                                    | Model time in seconds (run duration minus tool time), on `$ai_generation`                                                |
+| `tool_calls`, `successful_tools`, `failed_tools` | Complete tool-call counts                                                                                                |
+| `tools`, `tools_truncated`                       | First 50 tool names, offsets, durations, statuses, and error classes, including interrupted calls                        |
+| `delegated`, `delegation_protocol`, `caller_app` | Delegated-run attribution                                                                                                |
+| `a2a_task_id`, `parent_run_id`, `parent_turn_id` | Cross-app trace linkage, when available                                                                                  |
+| `$ai_is_error`, `status`, `$ai_error`            | Error status and message, when applicable                                                                                |
+| `$ai_http_status`                                | Provider HTTP status: 200 on a completed call, the reported status on a failed one, absent when the failure carried none |
 
 The `tools` array never includes tool arguments, results, or error messages.
 Use `tools_truncated` with the complete `tool_calls` count when a run exceeds

package/corpus/templates/analytics/docs/schemas/tracked-events.md

@@ -28,7 +28,11 @@ Events tracked by application instrumentation and stored in the configured appli
   server-side tracking. Properties include `$ai_trace_id`, `$ai_session_id`,
   `$ai_model`, `$ai_provider`, `$ai_input_tokens`, `$ai_output_tokens`,
   `$ai_latency`, `$ai_total_cost_usd`, `run_id`, `thread_id`,
-  `cost_cents_x100`, `duration_ms`, `tool_calls`, `status`, and error fields.
+  `cost_cents_x100`, `duration_ms`, `tool_calls`, `status`, `$ai_http_status`,
+  and error fields. `$ai_http_status` is 200 on a call that streamed to
+  completion and the provider's status on one that failed; it is absent when
+  the failure carried no status, so an unclassifiable transport drop is never
+  reported as a known rejection.
   `$ai_latency` is model time in seconds; `duration_ms` is the full run in
   milliseconds, and the two differ by the time spent in tools.
   A bounded `tools` array records only tool names, relative start times,

package/corpus/templates/assets/.agents/skills/asset-generation/SKILL.md

@@ -50,13 +50,15 @@ claiming a brand match.
   `generate-image-batch`, `generate-video`, `refresh-generation-run`, and
   `export-asset`.
 - In chat, consume composer `@` references as structured generation inputs:
-  `brand-kit` maps to `libraryId`, `preset` maps to `presetId`, and
+  `brand-kit` maps to `libraryId`, `template` maps to `templateId`, and
   `media-type` chooses image generation versus video generation. If no mention
   is available, use `view-screen`, `list-libraries`, and
-  `list-generation-presets` to choose explicit args.
-- Use generation presets when the user asks for a repeatable output format
-  like social image, blog hero, or diagram. Call `list-generation-presets` for
-  the library and pass `presetId` through generation/refinement actions.
+  `list-templates` to choose explicit args.
+- Use Templates when the user asks for a repeatable output format like social
+  image, blog hero, or diagram. Call `list-templates` and pass `templateId`
+  through generation/refinement actions. Templates may be global or associated
+  with one brand kit; only associated templates can pin images, skeletons, or
+  a canonical logo. `*-generation-preset` actions are deprecated aliases.
 - Use generation sessions when another person needs to continue improving a
   candidate. Sessions carry the brief, preset, active asset, feedback, and run
   IDs without requiring the original chat thread.
@@ -90,7 +92,7 @@ claiming a brand match.
    `generate-image-batch` returns, use its returned `images` / asset fields
    directly; do not call `get-generation-run`, `refresh-generation-run`, or
    regenerate just to verify image runs.
-5. For preset-backed work, pass a mentioned or selected `presetId`; for handoff
+5. For template-backed work, pass a mentioned or selected `templateId`; for handoff
    work, pass `sessionId`.
 6. Let the server choose a small deterministic reference set unless the user
    named exact assets. Canonical style anchors come from

package/corpus/templates/assets/.agents/skills/assets-navigation/SKILL.md

@@ -26,12 +26,15 @@ generation, or embed target is unclear.
   use the right agent sidebar only on non-Create routes with view-transition
   handoff back to `/`.
 
-## Generation preset editor
-
-- Humans can edit an existing generation preset from
-  `/brand-kits/:libraryId/presets/:presetId`. Use `navigate` with
-  `{ view: "preset", libraryId, presetId }` when sending a user to that editor.
-- Preset skeletons are edited from the same route; see `logo-composite` for the
+## Templates
+
+- Humans browse Templates at `/templates` and edit one at
+  `/templates/:templateId`. Use `navigate` with `{ view: "templates" }` or
+  `{ view: "template", templateId }`. Legacy `{ view: "preset", libraryId,
+  presetId }` navigation still resolves for existing conversations.
+- Global templates work with any accessible brand kit. Associated templates are
+  limited to their kit and are required for pinned images, skeletons, and logo
+  compositing. See `logo-composite` for the
   `settings.skeletonSpec` shape and compositing behavior.
 
 ## Context tab

package/corpus/templates/assets/.agents/skills/image-generation/SKILL.md

@@ -58,8 +58,8 @@ evidence, screenshots, or exact logos.
   IDs/URLs; do not follow it with `get-generation-run`,
   `refresh-generation-run`, or more generation unless the user asks for another
   direction or the returned slot has `ok: false`.
-- For repeatable deliverables, honor a `preset` @mention as `presetId` or call
-  `list-generation-presets` when choosing one. Pass the preset through
+- For repeatable deliverables, honor a `template` @mention as `templateId` or
+  call `list-templates` when choosing one. Pass the template through
   `generate-image`, `generate-image-batch`, `refine-image`, or
   `rerun-generation-run`.
 - For designer handoff, preserve `sessionId` and call
@@ -77,40 +77,40 @@ evidence, screenshots, or exact logos.
   `generate-image-batch` / `refine-image`. The design team uses the audit log
   to review quality by app, library, model, prompt, and lineage.
 
-## Composer Mentions And Tagged Presets
+## Composer Mentions And Tagged Templates
 
 - Composer `@` mentions are the source of generation inputs. Map `brand-kit`
-  references to `libraryId`, `preset` references to `presetId`, and `media-type`
+  references to `libraryId`, `template` references to `templateId`, and `media-type`
   references to choosing image (`generate-image` / `generate-image-batch`) or
   video (`generate-video`) generation.
 - The current library view auto-tags its brand kit as a visible removable chip,
-  and the generation preset editor auto-tags both its brand kit and preset.
+  and the template editor auto-tags an associated template with its brand kit.
 - The image model is the only remaining composer-side default; the image-model
   picker writes `imageGenerationModel`, which image generation actions may use
   when `model` is omitted.
-- When a `preset` is tagged, the server embeds that preset's aesthetics and
+- When a `template` is tagged, the server embeds that template's aesthetics and
   creative philosophy (brand style brief, prompt template, text/logo policy,
-  output format) into your message inside a `<tagged-generation-presets>` block.
+  output format) into your message inside a `<tagged-templates>` block.
   Study and internalize that brief before you generate — let it drive
-  composition, mood, lighting, and subject — then pass the `presetId` to
+  composition, mood, lighting, and subject — then pass the `templateId` to
   `generate-image` / `generate-image-batch` so the saved format/model/tier/logo
   apply automatically. Do not restate those as ad-hoc args.
 
-## Preset-first Generation
+## Template-first Generation
 
-- Image requests without a tagged preset are preset-first: the user may not know
-  presets exist. Compare the request against each preset's title, description,
+- Image requests without a tagged template are template-first: the user may not know
+  templates exist. Compare the request against each template's title, description,
   and category, and if one matches the use case (e.g. "livestream poster" -> a
-  Livestream Announcement preset), generate with its `presetId` instead of
-  ad-hoc settings. Only generate presetless when nothing plausibly matches.
+  Livestream Announcement template), generate with its `templateId` instead of
+  ad-hoc settings. Only generate without a template when nothing plausibly matches.
 - Before any ad-hoc generation for a brand kit, call
-  `list-generation-presets` and scan titles/descriptions/categories for a
-  use-case match. A preset encodes the designer's format, model, layout, and
+  `list-templates` and scan titles/descriptions/categories for a use-case match.
+  A template encodes the designer's format, model, layout, and
   reference board; using it is always better than improvising.
-- If one preset clearly matches: use its `presetId`; do not restate its saved
+- If one template clearly matches: use its `templateId`; do not restate its saved
   aspect ratio/size/model/tier. If several plausibly match: pick the best and
   state which one you used; do not ask the user to choose.
-- Match named people/products/backdrops in the request to the preset's
+- Match named people/products/backdrops in the request to the template's
   reference board entry labels in `settings.presetReferences`. Fill required
   variable entries via `presetReferenceFills`: search the library for assets of
   those people first; ask the user for photos only when none exist. Never skip a
@@ -122,8 +122,9 @@ evidence, screenshots, or exact logos.
   optional `textPlacement` to `generate-image` or each `generate-image-batch`
   slot. Keep the general `prompt` for creative direction; the structured text
   fields are what allow the pipeline to render copy instead of suppressing it.
-- If nothing matches: generate ad-hoc, say that no preset fit, and mention a
-  preset could be created for this recurring use case.
+- If nothing matches: generate ad-hoc, say that no template fit, and mention a
+  template could be created for this recurring use case. The deprecated
+  `*-generation-preset` actions remain aliases for existing agent threads.
 
 ## Prompting
 
@@ -131,13 +132,13 @@ evidence, screenshots, or exact logos.
 - Let the server choose references unless the user named exact assets. Automatic
   generation uses up to 6 relevant current references, seeded by canonical
   style anchors; explicit `referenceAssetIds` are preserved.
-- Preset reference boards live on tagged presets as named entries such as a
+- Template reference boards live on tagged templates as named entries such as a
   usual host, product, backdrop, style sample, or per-event speaker. Fixed
   entries attach automatically. Variable entries may be replaced for a run with
   `presetReferenceFills`; each fill REPLACES that entry's pinned images rather
   than appending. Required variable entries block generation until you provide
   at least one image.
-- When a tagged preset brief names required variable references, collect the
+- When a tagged template brief names required variable references, collect the
   needed images from the user's attachments or the library and pass
   `presetReferenceFills: [{ referenceId, assetIds }]` to `generate-image` or
   `generate-image-batch`. Board images are additive to brand style references.

package/corpus/templates/assets/.agents/skills/library-management/SKILL.md

@@ -113,7 +113,7 @@ filtered views.
 
 For a blog-to-brand-kit workflow: inspect the page, pick the strongest image
 URLs, import each URL into the target `libraryId`, then wire the returned
-`assetId`s into generation preset reference fills or call `set-canonical-logo`
+`assetId`s into associated Template reference fills or call `set-canonical-logo`
 for the exact logo. Imported assets are stored as `status: "reference"` with
 `sourceUrl` provenance, so downstream generation, preset boards, and logo
 compositing can use them like uploaded reference assets.

package/corpus/templates/assets/.agents/skills/logo-composite/SKILL.md

@@ -10,24 +10,26 @@ LLMs — including Gemini Pro — degrade complex logos. They smear gradients, d
 ## How it works
 
 1. The library has a `canonicalLogoUrl` (set via `set-canonical-logo --libraryId --assetId`). The asset's role is `logo_reference`.
-2. **Logo compositing is a preset option.** A generation preset carries `includeLogo` (stored in the preset `settings` and surfaced as a first-class field). When a generation resolves to a preset with `includeLogo: true`, `generate-image` composites the logo. A generate call's own `includeLogo` arg, when passed, overrides the preset for that run; when omitted, the preset's value wins.
-3. **Preset skeletons generalize logo compositing.** A preset can also carry `settings.skeletonSpec`: background first, generated subject second, foreground layers last. If the skeleton already has a `foreground` layer with `source: "canonicalLogo"`, `includeLogo` is treated as a no-op for that run so the logo is not stamped twice. If the skeleton does not include the logo and `includeLogo` is true, the existing canonical-logo layer is appended at the default upper-right position during compositing.
+2. **Logo compositing is an associated-template option.** A Template carries `includeLogo` (stored in its `settings` and surfaced as a first-class field). Global templates cannot enable it because a canonical logo belongs to a brand kit. When a generation resolves to an associated template with `includeLogo: true`, `generate-image` composites the logo. A generate call's own `includeLogo` arg, when passed, overrides the template for that run; when omitted, the template's value wins.
+3. **Template skeletons generalize logo compositing.** An associated template can carry `settings.skeletonSpec`: background first, generated subject second, foreground layers last. If the skeleton already has a `foreground` layer with `source: "canonicalLogo"`, `includeLogo` is treated as a no-op for that run so the logo is not stamped twice. If the skeleton does not include the logo and `includeLogo` is true, the existing canonical-logo layer is appended at the default upper-right position during compositing.
 4. When logo compositing is on, the prompt envelope adds:
    > Leave a clean uncluttered area in the upper-right for the real brand logo; do not draw or approximate the logo yourself.
 5. Gemini returns an image with empty space in that corner.
 6. `compositeLogo()` from `server/lib/image-processing.ts` (Sharp) loads the canonical logo PNG / SVG, resizes it to ~16% of the image width with reasonable inset, and composites it onto the generated image. Skeleton runs use `applyPresetSkeleton()` at the same seam.
 7. Output: the image with the actual logo, pixel-perfect, vector-quality if the source is SVG.
 
-Set `includeLogo` via `create-generation-preset` / `update-generation-preset`.
+Set `includeLogo` via `create-template` / `update-template` after associating
+the template with a brand kit. The `*-generation-preset` actions are deprecated
+aliases retained for existing threads.
 `generate-image` / `generate-image-batch` stamp the library's pixel-perfect
-canonical logo onto the result when the resolved preset has it on, and it is a
+canonical logo onto the result when the resolved template has it on, and it is a
 no-op if the library has no canonical logo. The model never draws the logo
 itself.
 
-## Preset skeletons
+## Template skeletons
 
-Preset skeletons live in `settings.skeletonSpec` on generation presets and are
-edited from `/brand-kits/:libraryId/presets/:presetId`. They composite a
+Template skeletons live in `settings.skeletonSpec` on associated templates and
+are edited from `/templates/:templateId`. They composite a
 generated subject onto an uploaded brand background image and optional
 foreground layers.
 
@@ -58,8 +60,8 @@ foreground layers.
 
 ## When to use it
 
-- The user turned on "Composite canonical logo" when creating a generation preset (the preset then stamps the logo on every image made with it).
-- The agent infers the user wants the logo for a one-off (e.g. "make a hero with our brand logo") — pass `includeLogo: true` on that single generate call to override the preset.
+- The user turned on "Composite canonical logo" on an associated template (the template then stamps the logo on every image made with it).
+- The agent infers the user wants the logo for a one-off (e.g. "make a hero with our brand logo") — pass `includeLogo: true` on that single generate call to override the template.
 - The image will appear in a customer-facing context where logo accuracy matters.
 
 ## When NOT to use it

package/corpus/templates/assets/AGENTS.md

@@ -12,9 +12,9 @@ Read the relevant skill in `.agents/skills/` before deeper work:
 - `creative-context` for cross-app source reuse, pinned packs, provenance, and
   context opt-out.
 - `library-management` for kits, collections, access, imports, and duplication.
-- `asset-generation` and `image-generation` for generation paths, presets,
+- `asset-generation` and `image-generation` for generation paths, templates,
   composer mentions, reference boards, and embedded text.
-- `logo-composite` for canonical logo compositing and preset skeletons.
+- `logo-composite` for canonical logo compositing and template skeletons.
 - `assets-navigation` for routes, tabs, chat surfaces, and `navigate` targets.
 - `agent-engines` for model and engine configuration.
 - `a2a-assets` for MCP/A2A callers, skill install paths, and host rendering.
@@ -38,12 +38,15 @@ Read the relevant skill in `.agents/skills/` before deeper work:
 - Preserve provenance and metadata for generated or imported assets.
 - Use `view-screen` when the active library, selected asset, picker, generation,
   or embed target is unclear.
-- Image work is preset-first. Follow the `creative-context` reuse ladder, then
-  check `list-generation-presets` and generate with a matching `presetId`
+- Image work is template-first. Follow the `creative-context` reuse ladder,
+  then check `list-templates` and generate with a matching `templateId`
   instead of ad hoc settings; see `image-generation`.
-- When a `preset` is tagged, the server embeds its brand style brief into your
-  message inside a `<tagged-generation-presets>` block. Internalize that brief,
-  then pass the `presetId` instead of restating its saved settings as args.
+- Templates are global or associated with one brand kit. Only associated
+  templates can pin images, skeleton plates, or a canonical logo.
+- When a `template` is tagged, the server embeds its brief inside a
+  `<tagged-templates>` block. Internalize it, then pass the `templateId`
+  instead of restating saved settings as args. `*-generation-preset` actions
+  are deprecated aliases for existing threads.
 - Keep inline previews and picker outputs lightweight; fetch full asset details
   through actions when needed.
 - Use framework sharing/collaboration primitives for ownable assets.
@@ -55,7 +58,8 @@ Read the relevant skill in `.agents/skills/` before deeper work:
   `{ view: "library", selection: "all" | libraryId, tab, scope, folderId, search }`,
   the embedded picker uses
   `{ view: "picker", mediaType, libraryId, query, prompt, aspectRatio }`, and the
-  preset editor uses `{ view: "preset", libraryId, presetId }`.
+  template gallery uses `{ view: "templates" }`, and an editor uses
+  `{ view: "template", templateId }`. Legacy preset navigation still resolves.
 - `creative-context` holds
   `{ contextMode, selectedContextId, currentPackId, pinnedPackId }`. Respect
   `contextMode: "off"` without silently restoring a pack.
@@ -71,7 +75,7 @@ Uncommon actions stay discoverable through `tool-search`.
 
 | Action | Purpose |
 | --- | --- |
-| `navigate` | Move the UI to a picker, library, generation, asset, preset, or settings surface |
+| `navigate` | Move the UI to a picker, library, template, generation, asset, or settings surface |
 | `view-screen` | Read current navigation, selection, and visible ids |
 | `list-libraries` / `match-library` | Find or disambiguate a brand kit |
 | `duplicate-library` | Make a private copy of a Brand Kit |
@@ -79,8 +83,9 @@ Uncommon actions stay discoverable through `tool-search`.
 | `import-asset-from-url` | Ingest external brand or blog imagery as a reference asset |
 | `import-style-from-url` | Render a website and merge its design.md-style visual language into a library or collection |
 | `set-canonical-logo` | Pin the kit's pixel-perfect logo |
-| `list-generation-presets` | List repeatable output formats before generating |
-| `create-generation-preset` / `update-generation-preset` | Author preset format, references, `includeLogo`, skeleton |
+| `list-templates` / `get-template` | Find accessible reusable generation recipes |
+| `create-template` / `update-template` | Author a global or brand-kit template |
+| `associate-template` / `duplicate-template` | Move a template's scope or copy it into a kit |
 | `generate-image` / `generate-image-batch` | Generate image candidates (synchronous) |
 | `generate-video` | Generate video, then poll `refresh-generation-run` |
 | `refine-image` / `edit-image` / `restyle-image` | Iterate on an existing asset |

package/corpus/templates/assets/CHANGELOG.md

@@ -3,6 +3,12 @@
 All notable user-facing changes to Assets are documented here. Open it any
 time from the command menu (Cmd+K → "What's new") or from Settings.
 
+## 2026-08-26
+
+### Added
+
+- Templates are now their own surface and can be used across brand kits.
+
 ## 2026-08-22
 
 ### Fixed

package/corpus/templates/assets/actions/_helpers.ts

@@ -7,6 +7,7 @@ import type {
   AssetLineageSummary,
   GenerationSessionItemSummary,
   GenerationPresetSummary,
+  TemplateSummary,
   GenerationSessionSummary,
   ImageAssetMetadata,
   StyleBrief,
@@ -196,6 +197,20 @@ export function serializeGenerationPreset(row: any): GenerationPresetSummary {
   };
 }
 
+export function serializeTemplate(row: any): TemplateSummary {
+  const preset = serializeGenerationPreset(row);
+  const libraryId = row.libraryId ?? null;
+  return {
+    ...preset,
+    libraryId,
+    scope: libraryId ? "library" : "global",
+    visibility: row.visibility ?? "private",
+    ownerEmail: row.ownerEmail,
+    accessRole: typeof row.accessRole === "string" ? row.accessRole : undefined,
+    libraryTitle: row.libraryTitle ?? null,
+  };
+}
+
 export function serializeGenerationSession(row: any): GenerationSessionSummary {
   const items = Array.isArray(row.items)
     ? (row.items as GenerationSessionItemSummary[])

package/corpus/templates/assets/actions/_template-access.ts

@@ -0,0 +1,71 @@
+import {
+  accessFilter,
+  assertAccess,
+  resolveAccess,
+  type ShareRole,
+} from "@agent-native/core/sharing";
+import { eq, inArray, or } from "drizzle-orm";
+
+import { getDb, schema } from "../server/db/index.js";
+
+const roleRank: Record<ShareRole | "owner", number> = {
+  viewer: 1,
+  commenter: 2,
+  editor: 3,
+  admin: 4,
+  owner: 5,
+};
+
+export async function resolveTemplateAccess(
+  id: string,
+  minRole: ShareRole | "owner" = "viewer",
+) {
+  // guard:allow-unscoped — this helper combines the template ACL with the
+  // inherited Brand Kit ACL before exposing the row to its callers.
+  const [template] = await getDb()
+    .select()
+    .from(schema.assetTemplates)
+    .where(eq(schema.assetTemplates.id, id))
+    .limit(1);
+  if (!template) throw new Error("Template not found or not accessible.");
+  const ownAccess = await resolveAccess("asset-template", id);
+  const libraryAccess = template.libraryId
+    ? await resolveAccess("asset-library", template.libraryId)
+    : null;
+  const access =
+    libraryAccess &&
+    (!ownAccess || roleRank[libraryAccess.role] > roleRank[ownAccess.role])
+      ? libraryAccess
+      : ownAccess;
+  if (!access) throw new Error("Template not found or not accessible.");
+  if (roleRank[access.role] < roleRank[minRole]) {
+    throw new Error(`Template requires ${minRole} access.`);
+  }
+  return { ...access, resource: template };
+}
+
+export async function assertTemplateTargetLibraryAccess(
+  libraryId: string | null | undefined,
+) {
+  if (libraryId) await assertAccess("asset-library", libraryId, "editor");
+}
+
+export async function accessibleTemplateFilter() {
+  const libraries = await getDb()
+    .select({ id: schema.assetLibraries.id })
+    .from(schema.assetLibraries)
+    .where(accessFilter(schema.assetLibraries, schema.assetLibraryShares));
+  const templateAccess = accessFilter(
+    schema.assetTemplates,
+    schema.assetTemplateShares,
+  );
+  return libraries.length
+    ? or(
+        templateAccess,
+        inArray(
+          schema.assetTemplates.libraryId,
+          libraries.map((library) => library.id),
+        ),
+      )
+    : templateAccess;
+}

package/corpus/templates/assets/actions/_template-input.ts

@@ -0,0 +1,51 @@
+import { z } from "zod";
+
+import {
+  ASPECT_RATIOS,
+  GENERATION_PRESET_REFERENCE_POLICIES,
+  IMAGE_CATEGORIES,
+  IMAGE_MODELS,
+  IMAGE_SIZES,
+} from "../shared/api.js";
+import { generationPresetSettingsSchema } from "./_generation-preset-settings.js";
+
+export const templateFieldsSchema = z.object({
+  libraryId: z.string().nullable().optional(),
+  collectionId: z.string().nullable().optional(),
+  title: z.string().min(1).optional(),
+  description: z.string().nullable().optional(),
+  category: z.enum(IMAGE_CATEGORIES).optional(),
+  promptTemplate: z.string().nullable().optional(),
+  aspectRatio: z.enum(ASPECT_RATIOS).optional(),
+  imageSize: z.enum(IMAGE_SIZES).optional(),
+  model: z.enum(IMAGE_MODELS).optional(),
+  textPolicy: z.string().optional(),
+  referencePolicy: z.enum(GENERATION_PRESET_REFERENCE_POLICIES).optional(),
+  includeLogo: z.coerce.boolean().optional(),
+  settings: generationPresetSettingsSchema.optional(),
+  sortOrder: z.coerce.number().optional(),
+});
+
+export function templateHasPins(settings: Record<string, unknown>) {
+  const refs = Array.isArray(settings.presetReferences)
+    ? settings.presetReferences
+    : [];
+  const pinned = refs.flatMap((reference) => {
+    if (!reference || typeof reference !== "object") return [];
+    const entry = reference as {
+      id?: unknown;
+      label?: unknown;
+      assetIds?: unknown;
+    };
+    if (!Array.isArray(entry.assetIds) || !entry.assetIds.length) return [];
+    const name =
+      typeof entry.label === "string" && entry.label.trim()
+        ? entry.label.trim()
+        : typeof entry.id === "string" && entry.id
+          ? entry.id
+          : "unnamed reference";
+    return [`reference \"${name}\"`];
+  });
+  const skeleton = settings.skeletonSpec ? ["skeletonSpec"] : [];
+  return [...pinned, ...skeleton];
+}

package/corpus/templates/assets/actions/associate-template.ts

@@ -0,0 +1,39 @@
+import { defineAction } from "@agent-native/core/action";
+import { eq } from "drizzle-orm";
+import { z } from "zod";
+
+import { getDb, schema } from "../server/db/index.js";
+import { nowIso, parseJson } from "../server/lib/json.js";
+import { serializeTemplate } from "./_helpers.js";
+import {
+  assertTemplateTargetLibraryAccess,
+  resolveTemplateAccess,
+} from "./_template-access.js";
+import { templateHasPins } from "./_template-input.js";
+
+export default defineAction({
+  description: "Move an asset template between global scope and one Brand Kit.",
+  schema: z.object({ id: z.string(), libraryId: z.string().nullable() }),
+  run: async ({ id, libraryId }) => {
+    const template = (await resolveTemplateAccess(id, "editor")).resource;
+    await assertTemplateTargetLibraryAccess(libraryId);
+    const pins = templateHasPins(
+      parseJson<Record<string, unknown>>(template.settings, {}),
+    );
+    if (libraryId !== template.libraryId && pins.length) {
+      throw new Error(
+        `Clear pinned template settings before changing Brand Kits: ${pins.join(", ")}.`,
+      );
+    }
+    const updates = {
+      libraryId,
+      ...(libraryId !== template.libraryId ? { collectionId: null } : {}),
+      updatedAt: nowIso(),
+    };
+    await getDb()
+      .update(schema.assetTemplates)
+      .set(updates)
+      .where(eq(schema.assetTemplates.id, id));
+    return serializeTemplate({ ...template, ...updates });
+  },
+});