@agent-native/core 0.121.2 → 0.122.1

package/corpus/templates/analytics/server/plugins/agent-chat.ts

@@ -73,6 +73,11 @@ export const NON_ANALYTICS_FALLBACK_FINAL_MESSAGE =
 export function analyticsSourceGuidanceOpening(): string {
   return (
     "<data-source-guidance>\n" +
+    // Measured in production: this ran in under 1% of data threads while the
+    // equivalent instruction sat ~7000 words deep. Threads that did call it used
+    // roughly a third the tool calls. Keep it first and keep it imperative.
+    "START HERE — For any question about a metric, cohort, list, count, or trend, your FIRST tool call is `search-analytics-query-catalog`. This is the analytics equivalent of grepping a codebase before writing new code: someone has very likely already built and saved the query you need, and its saved SQL tells you the exact source, table, and column names so you do not have to discover them. Adapt the closest saved query to the requested filters and time window, run it once, and stop. Only fall back to schema discovery or provider catalogs when the catalog search returns nothing usable — and never run more than one schema-discovery pass before querying. " +
+    'ONE BOUNDED CALL — List, filter, count, and cohort questions ("which X, excluding Y") are a single query, not a loop. Express the include filter, the exclude filter, and the aggregation in one SQL statement or one `run-code` script that filters server-side. Never page through a cohort across separate tool calls and never fan out per item to apply a filter; that is what turns a ten-second answer into a twenty-minute one. ' +
     "Apply real-data requirements only when presenting analytics results, source records, or derived metrics. Do not call data-source tools for workflow migration, recurring-job setup, UI/code fixes, settings help, conceptual planning, or other non-data tasks unless the user explicitly asks for data. " +
     NON_ANALYTICS_REQUEST_GUIDANCE +
     BOUNDED_STRUCTURED_LOOKUP_GUIDANCE +
@@ -734,6 +739,11 @@ export default createAgentChatPlugin({
       "Analytics has one user-facing artifact type: dashboards. Dashboards are JSON configs rendered by the built-in dashboard components, and an extension is a dashboard block—not a separate Analytics result. " +
       'If the user\'s requested dashboard, saved analysis/report, visualization, interaction model, custom layout, or bespoke workflow cannot be faithfully represented within the native dashboard components/config fields, do not hand-wave, force an approximate JSON dashboard, or route to source-code changes. In production mode, automatically create a sandboxed extension with `create-extension`, then immediately call `update-dashboard` to embed it as one or more `chartType: "extension"` panels with `config.extensionId`. ' +
       "After creating the dashboard, briefly tell the user that a dashboard block uses an embedded extension because the request needed bespoke UI/code. Never leave a newly created extension standalone, never create a separate saved analysis for the same request, and never direct the user to an Extensions page from Analytics. Legacy analyses may be read or updated only for compatibility with an existing deep link.\n" +
+      // The extension-first default above is deliberate, but it must not swallow
+      // an explicit ask for a code change: without this carve-out the agent
+      // silently substitutes an extension for "open a PR adding a dual-axis
+      // chart type" and the user never learns the handoff exists.
+      "That extension-first default governs what you build on your own initiative. It does not override an explicit request for a source-code change: when the user asks for the capability natively in the product, asks to change app chrome or a shared component, or asks for a PR, branch, or code change in so many words, call `connect-builder` with their request verbatim instead of substituting an extension. When you have just built an extension for something that plainly belongs in the product — a chart type or interaction other dashboards would reuse — add one sentence offering the `connect-builder` handoff, and only call it if they take you up on it.\n" +
       "</analytics-artifact-guidance>";
 
     return `${sourceGuidance}\n\n${artifactGuidance}\n\n${analyticsDataDictionaryRoutingContext()}`;

package/corpus/templates/analytics/server/plugins/auth.ts

@@ -13,7 +13,7 @@ export default createAuthPlugin({
     "/_agent-native/actions/get-public-status-page",
   ],
   marketing: {
-    appName: "Agent-Native Analytics",
+    appName: "Analytics",
     tagline:
       "Your AI agent queries your data sources, builds dashboards, and answers business questions alongside you.",
     features: [

package/corpus/templates/assets/.agents/skills/upgrade-agent-native/SKILL.md

@@ -56,7 +56,29 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    - Runs `skills update scaffold --project`
    - Runs `typecheck` when the project has that script
 
-3. **If upgrade or typecheck fails**
+3. **Pull upstream template changes (optional, separate from the bump)**
+
+   `agent-native upgrade` moves package versions. It never touches files that
+   were copied out of a template at scaffold time, so template fixes and
+   improvements do not arrive with a bump.
+
+   ```bash
+   agent-native template status        # recorded ref vs latest, drift counts
+   agent-native template diff          # what upstream changed, read-only
+   agent-native template sync          # 3-way merge it into the app
+   ```
+
+   `sync` defaults to the ref matching the installed `@agent-native/core`, so
+   run it after `upgrade`. It merges per file against a pristine baseline
+   stored in `refs/agent-native/template-baseline/<app-path>`; files upstream
+   did not touch are left alone, and real collisions get conflict markers.
+   After resolving markers, run `agent-native template accept` — the baseline
+   deliberately does not advance past an unresolved merge.
+
+   Apps scaffolded before provenance existed have no baseline. Create one
+   with `agent-native template baseline` before the first sync.
+
+4. **If upgrade or typecheck fails**
 
    - Read the concrete error
    - Fix **app** source, actions, config, or env — not framework packages
@@ -68,7 +90,7 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    copied component; do not use that path to reproduce framework runtime
    behavior or hide version skew.
 
-4. **Dry-run / partial runs**
+5. **Dry-run / partial runs**
 
    ```bash
    agent-native upgrade --dry-run

package/corpus/templates/assets/app/components/layout/Sidebar.tsx

@@ -17,7 +17,6 @@ import {
   type ChatHistoryItem,
 } from "@agent-native/toolkit/chat-history";
 import {
-  IconHierarchy2,
   IconClipboardList,
   IconLayoutSidebarLeftCollapse,
   IconLayoutSidebarLeftExpand,
@@ -45,7 +44,6 @@ const baseNavItems = [
 ];
 
 const bottomNavItems = [
-  { icon: IconHierarchy2, labelKey: "settings.agentTitle", href: "/agent" },
   { icon: IconSettings, labelKey: "navigation.settings", href: "/settings" },
 ];
 

package/corpus/templates/assets/app/routes/_index.tsx

@@ -35,7 +35,7 @@ const CHAT_STARTERS = [
 ] as const;
 
 const SEO_TITLE =
-  "Agent-Native Assets - Open Source AI asset library for brand-safe images and video";
+  "Assets - Open Source AI asset library for brand-safe images and video";
 const SEO_DESCRIPTION =
   "Open Source asset manager for AI teams to organize brand libraries, search creative work, and generate on-brand images and videos.";
 

package/corpus/templates/assets/changelog/2026-07-25-app-branding-now-uses-the-product-name-without-the-agent-nat.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-25
+---
+
+App branding now uses the product name without the Agent-Native prefix.

package/corpus/templates/assets/changelog/2026-07-25-settings-navigation-now-keeps-manage-agent-as-a-dedicated-li.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-25
+---
+
+Settings navigation now keeps Manage agent as a dedicated linked destination at the bottom.

package/corpus/templates/assets/server/plugins/auth.ts

@@ -2,7 +2,7 @@ import { createAuthPlugin } from "@agent-native/core/server";
 
 export default createAuthPlugin({
   marketing: {
-    appName: "Agent-Native Assets",
+    appName: "Assets",
     tagline:
       "Your AI agent creates, refines, and organizes on-brand assets alongside you.",
     features: [

package/corpus/templates/brain/.agents/skills/upgrade-agent-native/SKILL.md

@@ -56,7 +56,29 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    - Runs `skills update scaffold --project`
    - Runs `typecheck` when the project has that script
 
-3. **If upgrade or typecheck fails**
+3. **Pull upstream template changes (optional, separate from the bump)**
+
+   `agent-native upgrade` moves package versions. It never touches files that
+   were copied out of a template at scaffold time, so template fixes and
+   improvements do not arrive with a bump.
+
+   ```bash
+   agent-native template status        # recorded ref vs latest, drift counts
+   agent-native template diff          # what upstream changed, read-only
+   agent-native template sync          # 3-way merge it into the app
+   ```
+
+   `sync` defaults to the ref matching the installed `@agent-native/core`, so
+   run it after `upgrade`. It merges per file against a pristine baseline
+   stored in `refs/agent-native/template-baseline/<app-path>`; files upstream
+   did not touch are left alone, and real collisions get conflict markers.
+   After resolving markers, run `agent-native template accept` — the baseline
+   deliberately does not advance past an unresolved merge.
+
+   Apps scaffolded before provenance existed have no baseline. Create one
+   with `agent-native template baseline` before the first sync.
+
+4. **If upgrade or typecheck fails**
 
    - Read the concrete error
    - Fix **app** source, actions, config, or env — not framework packages
@@ -68,7 +90,7 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    copied component; do not use that path to reproduce framework runtime
    behavior or hide version skew.
 
-4. **Dry-run / partial runs**
+5. **Dry-run / partial runs**
 
    ```bash
    agent-native upgrade --dry-run

package/corpus/templates/brain/_gitignore

@@ -10,3 +10,4 @@ data/*.db-shm
 data/*.db-wal
 .env
 .env.local
+.agent-native/

package/corpus/templates/brain/app/lib/brain.ts

@@ -1,6 +1,5 @@
 import type { Icon } from "@tabler/icons-react";
 import {
-  IconHierarchy2,
   IconBook2,
   IconChecks,
   IconDatabase,
@@ -1007,12 +1006,6 @@ export const navItems: Array<{
     href: "/settings",
     icon: IconSettings,
   },
-  {
-    view: "agent",
-    label: "Manage agent",
-    href: "/agent",
-    icon: IconHierarchy2,
-  },
 ];
 
 export const defaultSettings: BrainSettings = {

package/corpus/templates/brain/app/routes/_index.tsx

@@ -9,8 +9,7 @@ import { useEffect } from "react";
 import { shouldEnableBrainProviderStatusChecks } from "@/lib/brain-chat-readiness";
 import { TAB_ID } from "@/lib/tab-id";
 
-const SEO_TITLE =
-  "Agent-Native Brain - Open Source company knowledge base for AI agents";
+const SEO_TITLE = "Brain - Open Source company knowledge base for AI agents";
 const SEO_DESCRIPTION =
   "Open Source company knowledge base that turns Slack, meetings, transcripts, docs, and decisions into cited answers for AI agents.";
 

package/corpus/templates/brain/changelog/2026-07-25-app-branding-now-uses-the-product-name-without-the-agent-nat.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-25
+---
+
+App branding now uses the product name without the Agent-Native prefix.

package/corpus/templates/brain/changelog/2026-07-25-settings-navigation-now-keeps-manage-agent-as-a-dedicated-li.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-25
+---
+
+Settings navigation now keeps Manage agent as a dedicated linked destination at the bottom.

package/corpus/templates/brain/package.json

@@ -1,6 +1,6 @@
 {
   "name": "brain",
-  "displayName": "Agent-Native Brain",
+  "displayName": "Brain",
   "private": true,
   "type": "module",
   "scripts": {

package/corpus/templates/brain/public/manifest.json

@@ -1,5 +1,5 @@
 {
-  "name": "Agent-Native Brain",
+  "name": "Brain",
   "short_name": "Brain",
   "start_url": "/",
   "display": "standalone",

package/corpus/templates/brain/server/plugins/auth.ts

@@ -2,7 +2,7 @@ import { createAuthPlugin } from "@agent-native/core/server";
 
 export default createAuthPlugin({
   marketing: {
-    appName: "Agent-Native Brain",
+    appName: "Brain",
     tagline:
       "A company knowledge layer where raw conversations become reviewed, searchable institutional knowledge.",
     features: [

package/corpus/templates/calendar/.agents/skills/upgrade-agent-native/SKILL.md

@@ -56,7 +56,29 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    - Runs `skills update scaffold --project`
    - Runs `typecheck` when the project has that script
 
-3. **If upgrade or typecheck fails**
+3. **Pull upstream template changes (optional, separate from the bump)**
+
+   `agent-native upgrade` moves package versions. It never touches files that
+   were copied out of a template at scaffold time, so template fixes and
+   improvements do not arrive with a bump.
+
+   ```bash
+   agent-native template status        # recorded ref vs latest, drift counts
+   agent-native template diff          # what upstream changed, read-only
+   agent-native template sync          # 3-way merge it into the app
+   ```
+
+   `sync` defaults to the ref matching the installed `@agent-native/core`, so
+   run it after `upgrade`. It merges per file against a pristine baseline
+   stored in `refs/agent-native/template-baseline/<app-path>`; files upstream
+   did not touch are left alone, and real collisions get conflict markers.
+   After resolving markers, run `agent-native template accept` — the baseline
+   deliberately does not advance past an unresolved merge.
+
+   Apps scaffolded before provenance existed have no baseline. Create one
+   with `agent-native template baseline` before the first sync.
+
+4. **If upgrade or typecheck fails**
 
    - Read the concrete error
    - Fix **app** source, actions, config, or env — not framework packages
@@ -68,7 +90,7 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    copied component; do not use that path to reproduce framework runtime
    behavior or hide version skew.
 
-4. **Dry-run / partial runs**
+5. **Dry-run / partial runs**
 
    ```bash
    agent-native upgrade --dry-run

package/corpus/templates/calendar/_gitignore

@@ -37,3 +37,4 @@ data/.sessions.json
 learnings.md
 
 .vercel/
+.agent-native/

package/corpus/templates/calendar/app/components/layout/Sidebar.tsx

@@ -6,7 +6,6 @@ import { OrgSwitcher } from "@agent-native/core/client/org";
 import { FeedbackButton } from "@agent-native/core/client/ui";
 import { SidebarFooterActions } from "@agent-native/toolkit/app-shell";
 import {
-  IconHierarchy2,
   IconCalendar,
   IconSettings,
   IconLink,
@@ -101,11 +100,6 @@ const navItems = [
 ];
 
 const bottomNavItems = [
-  {
-    path: "/agent",
-    labelKey: "settings.agentTitle",
-    icon: IconHierarchy2,
-  },
   { path: "/settings", labelKey: "navigation.settings", icon: IconSettings },
 ];
 

package/corpus/templates/calendar/app/routes/_app._index.tsx

@@ -1,7 +1,7 @@
 import CalendarView from "@/pages/CalendarView";
 
 const SEO_TITLE =
-  "Agent-Native Calendar - Open Source AI scheduling and Google Calendar automation";
+  "Calendar - Open Source AI scheduling and Google Calendar automation";
 const SEO_DESCRIPTION =
   "Open Source AI calendar app for Google Calendar scheduling, booking links, meeting coordination, and agent-managed event updates.";
 

package/corpus/templates/calendar/changelog/2026-07-25-app-branding-now-uses-the-product-name-without-the-agent-nat.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-25
+---
+
+App branding now uses the product name without the Agent-Native prefix.

package/corpus/templates/calendar/changelog/2026-07-25-settings-navigation-now-keeps-manage-agent-as-a-dedicated-li.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-25
+---
+
+Settings navigation now keeps Manage agent as a dedicated linked destination at the bottom.

package/corpus/templates/calendar/package.json

@@ -1,6 +1,6 @@
 {
   "name": "calendar",
-  "displayName": "Agent-Native Calendar",
+  "displayName": "Calendar",
   "private": true,
   "type": "module",
   "scripts": {

package/corpus/templates/calendar/public/manifest.json

@@ -1,5 +1,5 @@
 {
-  "name": "Agent Native Calendar",
+  "name": "Calendar",
   "short_name": "Calendar",
   "description": "Google Calendar integration",
   "start_url": ".",

package/corpus/templates/calendar/server/plugins/auth.ts

@@ -8,7 +8,7 @@ export default createAuthPlugin({
   googleOnly: true,
   mountGoogleOAuthRoutes: false,
   marketing: {
-    appName: "Agent-Native Calendar",
+    appName: "Calendar",
     tagline:
       "Your AI agent schedules, reschedules, and manages your calendar so you never have to.",
     features: [

package/corpus/templates/chat/.agents/skills/upgrade-agent-native/SKILL.md

@@ -56,7 +56,29 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    - Runs `skills update scaffold --project`
    - Runs `typecheck` when the project has that script
 
-3. **If upgrade or typecheck fails**
+3. **Pull upstream template changes (optional, separate from the bump)**
+
+   `agent-native upgrade` moves package versions. It never touches files that
+   were copied out of a template at scaffold time, so template fixes and
+   improvements do not arrive with a bump.
+
+   ```bash
+   agent-native template status        # recorded ref vs latest, drift counts
+   agent-native template diff          # what upstream changed, read-only
+   agent-native template sync          # 3-way merge it into the app
+   ```
+
+   `sync` defaults to the ref matching the installed `@agent-native/core`, so
+   run it after `upgrade`. It merges per file against a pristine baseline
+   stored in `refs/agent-native/template-baseline/<app-path>`; files upstream
+   did not touch are left alone, and real collisions get conflict markers.
+   After resolving markers, run `agent-native template accept` — the baseline
+   deliberately does not advance past an unresolved merge.
+
+   Apps scaffolded before provenance existed have no baseline. Create one
+   with `agent-native template baseline` before the first sync.
+
+4. **If upgrade or typecheck fails**
 
    - Read the concrete error
    - Fix **app** source, actions, config, or env — not framework packages
@@ -68,7 +90,7 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    copied component; do not use that path to reproduce framework runtime
    behavior or hide version skew.
 
-4. **Dry-run / partial runs**
+5. **Dry-run / partial runs**
 
    ```bash
    agent-native upgrade --dry-run

package/corpus/templates/chat/_gitignore

@@ -41,3 +41,4 @@ data/.sessions.json
 learnings.md
 
 .vercel/
+.agent-native/

package/corpus/templates/chat/app/components/layout/Sidebar.tsx

@@ -14,7 +14,6 @@ import {
   type ChatHistoryItem,
 } from "@agent-native/toolkit/chat-history";
 import {
-  IconHierarchy2,
   IconLayoutSidebarLeftCollapse,
   IconLayoutSidebarLeftExpand,
   IconMessageCircle,
@@ -43,12 +42,6 @@ const navItems = [
 ];
 
 const bottomNavItems = [
-  {
-    icon: IconHierarchy2,
-    labelKey: "settings.agentTitle",
-    href: "/agent",
-    view: "agent",
-  },
   {
     icon: IconSettings,
     labelKey: "navigation.settings",

package/corpus/templates/chat/changelog/2026-07-25-settings-navigation-now-keeps-manage-agent-as-a-dedicated-li.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-25
+---
+
+Settings navigation now keeps Manage agent as a dedicated linked destination at the bottom.

package/corpus/templates/clips/.agents/skills/upgrade-agent-native/SKILL.md

@@ -56,7 +56,29 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    - Runs `skills update scaffold --project`
    - Runs `typecheck` when the project has that script
 
-3. **If upgrade or typecheck fails**
+3. **Pull upstream template changes (optional, separate from the bump)**
+
+   `agent-native upgrade` moves package versions. It never touches files that
+   were copied out of a template at scaffold time, so template fixes and
+   improvements do not arrive with a bump.
+
+   ```bash
+   agent-native template status        # recorded ref vs latest, drift counts
+   agent-native template diff          # what upstream changed, read-only
+   agent-native template sync          # 3-way merge it into the app
+   ```
+
+   `sync` defaults to the ref matching the installed `@agent-native/core`, so
+   run it after `upgrade`. It merges per file against a pristine baseline
+   stored in `refs/agent-native/template-baseline/<app-path>`; files upstream
+   did not touch are left alone, and real collisions get conflict markers.
+   After resolving markers, run `agent-native template accept` — the baseline
+   deliberately does not advance past an unresolved merge.
+
+   Apps scaffolded before provenance existed have no baseline. Create one
+   with `agent-native template baseline` before the first sync.
+
+4. **If upgrade or typecheck fails**
 
    - Read the concrete error
    - Fix **app** source, actions, config, or env — not framework packages
@@ -68,7 +90,7 @@ install → refresh scaffold skills → verify, then fix **app** code only.
    copied component; do not use that path to reproduce framework runtime
    behavior or hide version skew.
 
-4. **Dry-run / partial runs**
+5. **Dry-run / partial runs**
 
    ```bash
    agent-native upgrade --dry-run

package/corpus/templates/clips/.agents/skills/video-sharing/SKILL.md

@@ -46,6 +46,7 @@ Read this skill before:
 - **`recordings.visibility`** — framework-managed column from `ownableColumns()`.
 - **`recording_viewers`** + **`recording_events`** — view counting.
 - **`recording_views`** — append-only per-view log (who viewed, when) backing the owner-facing "Viewed by" popover. See "View counting" below.
+- **`recording_agent_views`** — outside agents reading a clip through its public agent APIs, counted separately from humans. See "Agent views" below.
 
 ## Dropping in the share UI
 
@@ -213,6 +214,11 @@ they can fetch only the visual context they need.
 
 ## View counting
 
+Clips counts **human views** and **agent views** separately. The two live in
+different tables and never mix — see "Agent views" below before touching either.
+
+### Human views
+
 A view counts when **any** of these is true:
 
 - The viewer has watched **≥ 5 seconds** of total real playback time
@@ -237,6 +243,34 @@ if (
 
 Events feeding this live in `recording_events`. The `/api/view-event` route receives `view-start`, `watch-progress` (every 5s), `seek`, `pause`, `resume`, `cta-click`, `reaction`. Aggregate into `recording_viewers` on write to keep `get-insights` fast.
 
+### Agent views
+
+An **agent view** is an outside agent reading a clip through its public agent
+APIs — `/api/agent-context.json`, `/api/agent-transcript.json`,
+`/api/agent-frame.jpg`. Those routes are agent-only surfaces (a human watching a
+clip never hits them), so a request on one is the signal.
+
+- **Table:** `recording_agent_views` — one row per `(recordingId, agentKey, viewSessionId)`.
+  `agentKey` is a sha256 of user-agent + request IP, so an agent is countable
+  across polls without ever storing its IP. `agentLabel` is the product name
+  parsed from the user-agent (Claude, ChatGPT, Perplexity, …), falling back to
+  `"Agent"` — never the raw user-agent string.
+- **Where it's written:** `recordAgentView` in `server/lib/agent-views.ts`,
+  called from `loadPublicAgentAccess` — the one choke point all three agent
+  routes share. Owner requests are skipped (they're previews, not views), and the
+  write is best-effort so view accounting can never fail an agent's read.
+- **Dedup:** one agent's burst of context + transcript + frame polls collapses
+  into a single view via a 30-minute window (`AGENT_VIEW_SESSION_MS`), with
+  `requestCount` recording how many polls that view covered.
+- **Reads:** `countRecordingAgentViews` and `listRecordingAgentViewers`. Surfaced
+  as `agentViews` / `agentViewers` on `get-recording-insights` and
+  `agentViewCount` on `get-recording-player-data`, and rendered in the views pill
+  popover (`RecordingViewsBadge`) next to human views.
+
+Keeping this in its own table is deliberate: no human-view query can pick agents
+up by forgetting a filter. Do not add agent rows to `recording_viewers` or
+`recording_views`.
+
 ### Per-viewer view records ("Viewed by")
 
 On top of the aggregate `viewCount` shown in the library and the `views` stat in the insights panel, Clips records **individual view records** — who viewed a clip and when — so the owner can see a timeline, not just a number.

package/corpus/templates/clips/AGENTS.md

@@ -17,7 +17,11 @@ ladder.
 - Store large file/blob payloads in configured file/blob storage, not SQL: no
   base64, `data:` URLs, images, video/audio, PDFs, ZIPs, screenshots,
   thumbnails, or replay chunks in app tables, `application_state`, `settings`,
-  or `resources`; persist URLs, ids, or handles instead.
+  or `resources`; persist URLs, ids, or handles instead. Hosted/shared
+  recording uploads require configured storage — do not preserve video bytes
+  in SQL as a production fallback. The only exception: local SQLite/dev flows
+  may keep scratch chunks while a user connects Builder.io or S3-compatible
+  storage.
 - 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.
 - Use actions for recording metadata, transcripts, cleanup, summaries, chapters,
   comments, spaces/folders, meetings, and sharing. Do not bypass access helpers.
@@ -106,9 +110,6 @@ ladder.
   Anthropic/OpenAI power the agent chat; Gemini powers cleanup, titles, and
   meeting notes; any optional third-party speech provider is limited to
   desktop voice dictation and is not used for recording transcripts.
-- Hosted/shared recording uploads require configured storage. Do not preserve
-  video bytes in SQL as a production fallback; only local SQLite/dev flows may
-  keep scratch chunks while a user connects Builder.io or S3-compatible storage.
 - Use `view-screen` when the active recording, transcript segment, meeting, or
   share context is unclear.
 - Calendar-sourced meeting actions are shortcuts, but do not add raw

package/corpus/templates/clips/_gitignore

@@ -37,3 +37,4 @@ data/.sessions.json
 learnings.md
 
 .vercel/
+.agent-native/

package/corpus/templates/clips/actions/cleanup-transcript.ts

@@ -489,6 +489,11 @@ function buildPrompt({
     "dueDate"?: string              // ISO date if explicitly mentioned
   }>
 }
+Rules for summaryMd:
+- Write it the way the person who made this recording would describe it themselves — plain, direct, and about the subject matter.
+- Never narrate the recording from the outside. Do not write "the speaker", "the presenter", "the narrator", "the author", "the team", "the video", "this recording", "this clip", "this meeting", "the discussion covered", or any equivalent framing.
+- Lead with the topic, decisions, and specifics. Name a person only when who said or owns something actually matters.
+- No praise, no meta commentary about the transcript, no "overall" wrap-up sentence.
 Rules for action items:
 - Attribute each action item to a specific attendee whenever the transcript makes the owner clear (e.g. "I'll send the deck", "Alice will follow up").
 - The "assigneeEmail" MUST be one of the attendee emails listed in the <context> block above — do not invent emails or use display names.