@agent-native/core 0.91.1 → 0.92.0

package/corpus/templates/calendar/app/i18n/zh-TW.ts

@@ -123,6 +123,7 @@ const messages = {
   },
   attendees: {
     addAnotherGuest: "新增另一位來賓",
+    clearTimezone: "清除時區",
     contacts: "聯絡人",
     contactsReconnect: "需要重新連線聯絡人或目錄存取權限。",
     directory: "目錄",
@@ -134,6 +135,7 @@ const messages = {
     otherContacts: "其他聯絡人",
     removeAttendee: "移除 {{email}}",
     searchingPeople: "正在搜尋人員",
+    setTimezone: "設定時區…",
   },
   findTime: {
     busy: "忙碌",

package/corpus/templates/calendar/app/i18n-data.ts

@@ -134,6 +134,7 @@ const enUS = {
   },
   attendees: {
     addAnotherGuest: "Add another guest",
+    clearTimezone: "Clear timezone",
     contacts: "Contacts",
     contactsReconnect: "Contacts or directory access needs to be reconnected.",
     directory: "Directory",
@@ -145,6 +146,7 @@ const enUS = {
     otherContacts: "Other contacts",
     removeAttendee: "Remove {{email}}",
     searchingPeople: "Searching people",
+    setTimezone: "Set timezone…",
   },
   findTime: {
     busy: "Busy",
@@ -6123,6 +6125,7 @@ const translatedCalendarRemainingRaw = {
     },
     attendees: {
       addAnotherGuest: "添加另一位来宾",
+      clearTimezone: "清除时区",
       contacts: "联系人",
       contactsReconnect: "需要重新连接联系人或目录访问权限。",
       directory: "目录",
@@ -6134,6 +6137,7 @@ const translatedCalendarRemainingRaw = {
       otherContacts: "其他联系人",
       removeAttendee: "移除 {{email}}",
       searchingPeople: "正在搜索人员",
+      setTimezone: "设置时区…",
     },
     findTime: {
       busy: "忙碌",
@@ -6254,6 +6258,8 @@ const translatedCalendarRemainingRaw = {
       otherContacts: "Otros contactos",
       removeAttendee: "Quitar {{email}}",
       searchingPeople: "Buscando personas",
+      clearTimezone: "Borrar zona horaria",
+      setTimezone: "Establecer zona horaria…",
     },
     findTime: {
       busy: "Ocupado",
@@ -6598,6 +6604,8 @@ const translatedCalendarExactCleanup = {
       otherContacts: "Autres contacts",
       removeAttendee: "Retirer {{email}}",
       searchingPeople: "Recherche de personnes",
+      clearTimezone: "Effacer le fuseau horaire",
+      setTimezone: "Définir le fuseau horaire…",
     },
     findTime: {
       busy: "Occupé",
@@ -6787,6 +6795,8 @@ const translatedCalendarExactCleanup = {
       otherContacts: "Weitere Kontakte",
       removeAttendee: "{{email}} entfernen",
       searchingPeople: "Personen werden gesucht",
+      clearTimezone: "Zeitzone löschen",
+      setTimezone: "Zeitzone festlegen…",
     },
     findTime: {
       busy: "Beschäftigt",
@@ -6966,6 +6976,8 @@ const translatedCalendarExactCleanup = {
       otherContacts: "その他の連絡先",
       removeAttendee: "{{email}} を削除",
       searchingPeople: "ユーザーを検索中",
+      clearTimezone: "タイムゾーンをクリア",
+      setTimezone: "タイムゾーンを設定…",
     },
     findTime: {
       busy: "予定あり",
@@ -7136,6 +7148,8 @@ const translatedCalendarExactCleanup = {
       otherContacts: "기타 연락처",
       removeAttendee: "{{email}} 제거",
       searchingPeople: "사람 검색 중",
+      clearTimezone: "시간대 지우기",
+      setTimezone: "시간대 설정…",
     },
     findTime: {
       busy: "바쁨",
@@ -7315,6 +7329,8 @@ const translatedCalendarExactCleanup = {
       otherContacts: "Outros contatos",
       removeAttendee: "Remover {{email}}",
       searchingPeople: "Pesquisando pessoas",
+      clearTimezone: "Limpar fuso horário",
+      setTimezone: "Definir fuso horário…",
     },
     findTime: {
       busy: "Ocupado",
@@ -7494,6 +7510,8 @@ const translatedCalendarExactCleanup = {
       otherContacts: "अन्य संपर्क",
       removeAttendee: "{{email}} हटाएं",
       searchingPeople: "लोग खोजे जा रहे हैं",
+      clearTimezone: "समय क्षेत्र साफ़ करें",
+      setTimezone: "समय क्षेत्र सेट करें…",
     },
     findTime: {
       busy: "व्यस्त",
@@ -7668,6 +7686,8 @@ const translatedCalendarExactCleanup = {
       otherContacts: "جهات اتصال أخرى",
       removeAttendee: "إزالة {{email}}",
       searchingPeople: "جارٍ البحث عن أشخاص",
+      clearTimezone: "مسح المنطقة الزمنية",
+      setTimezone: "تعيين المنطقة الزمنية…",
     },
     findTime: {
       busy: "مشغول",

package/corpus/templates/calendar/app/lib/attendee-local-time.ts

@@ -0,0 +1,122 @@
+/**
+ * Format and resolve per-attendee local times for an event start.
+ *
+ * Resolution priority for an attendee's IANA timezone:
+ * 1. Self attendee (`attendee.self` or email matches accountEmail) →
+ *    event.startTimeZone, else the browser timezone
+ * 2. Optional `attendee.timeZone` on the attendee object
+ * 3. User-stored override from the `attendee-timezones` setting map
+ *
+ * When no timezone is known, returns null — never invent a zone.
+ */
+
+export type AttendeeTimezoneSource = {
+  email: string;
+  self?: boolean;
+  timeZone?: string;
+};
+
+export type ResolveAttendeeTimezoneInput = {
+  attendee: AttendeeTimezoneSource;
+  accountEmail?: string;
+  eventStartTimeZone?: string;
+  /** email (lowercased) → IANA timezone overrides from user settings */
+  overrides?: Record<string, string>;
+  /** Browser/local fallback for the self attendee when the event has no zone */
+  browserTimeZone?: string;
+};
+
+export function isSelfAttendee(
+  attendee: AttendeeTimezoneSource,
+  accountEmail?: string,
+): boolean {
+  if (attendee.self) return true;
+  if (!accountEmail) return false;
+  return (
+    attendee.email.trim().toLowerCase() === accountEmail.trim().toLowerCase()
+  );
+}
+
+export function isValidIanaTimeZone(
+  timeZone: string | undefined | null,
+): boolean {
+  if (!timeZone?.trim()) return false;
+  try {
+    new Intl.DateTimeFormat("en-US", { timeZone: timeZone.trim() }).format();
+    return true;
+  } catch {
+    return false;
+  }
+}
+
+export function resolveAttendeeTimeZone(
+  input: ResolveAttendeeTimezoneInput,
+): string | null {
+  const {
+    attendee,
+    accountEmail,
+    eventStartTimeZone,
+    overrides,
+    browserTimeZone,
+  } = input;
+
+  if (isSelfAttendee(attendee, accountEmail)) {
+    if (isValidIanaTimeZone(eventStartTimeZone)) {
+      return eventStartTimeZone!.trim();
+    }
+    const browser =
+      browserTimeZone?.trim() ||
+      (typeof Intl !== "undefined"
+        ? Intl.DateTimeFormat().resolvedOptions().timeZone
+        : undefined);
+    return isValidIanaTimeZone(browser) ? browser!.trim() : null;
+  }
+
+  if (isValidIanaTimeZone(attendee.timeZone)) {
+    return attendee.timeZone!.trim();
+  }
+
+  const key = attendee.email.trim().toLowerCase();
+  const override = overrides?.[key];
+  if (isValidIanaTimeZone(override)) {
+    return override!.trim();
+  }
+
+  return null;
+}
+
+/**
+ * Formats an event start instant in a given IANA timezone as a short local
+ * time label, e.g. "6:30 AM EDT".
+ */
+export function formatAttendeeLocalTime(
+  startIso: string,
+  timeZone: string,
+  locale = "en-US",
+): string | null {
+  if (!isValidIanaTimeZone(timeZone)) return null;
+  const date = new Date(startIso);
+  if (Number.isNaN(date.getTime())) return null;
+
+  try {
+    return new Intl.DateTimeFormat(locale, {
+      timeZone: timeZone.trim(),
+      hour: "numeric",
+      minute: "2-digit",
+      timeZoneName: "short",
+    }).format(date);
+  } catch {
+    return null;
+  }
+}
+
+export function getAttendeeLocalTimeLabel(
+  input: ResolveAttendeeTimezoneInput & {
+    startIso: string;
+    locale?: string;
+  },
+): string | null {
+  const timeZone = resolveAttendeeTimeZone(input);
+  if (!timeZone) return null;
+  return formatAttendeeLocalTime(input.startIso, timeZone, input.locale);
+}

package/corpus/templates/calendar/changelog/2026-07-08-event-details-now-support-extension-widgets-and-you-can-see-.md

@@ -0,0 +1,6 @@
+---
+type: added
+date: 2026-07-08
+---
+
+Event details now support extension widgets, and you can see each guest's local time next to their email when their timezone is known.

package/corpus/templates/calendar/changelog/2026-07-08-when-you-invite-guests-to-a-new-event-you-now-appear-in.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-07-08
+---
+
+When you invite guests to a new event, you now appear in the Guests list the same way Google Calendar shows you as the organizer.

package/corpus/templates/calendar/package.json

@@ -69,7 +69,6 @@
     "@types/node": "^24.2.1",
     "@types/react": "catalog:",
     "@types/react-dom": "catalog:",
-    "@typescript/native-preview": "catalog:",
     "@vitejs/plugin-react-swc": "^4.0.0",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
@@ -94,7 +93,8 @@
     "tailwind-merge": "^3.5.0",
     "tailwindcss": "catalog:",
     "tsx": "^4.20.3",
-    "typescript": "^6.0.3",
+    "typescript": "catalog:",
+    "typescript-7": "catalog:",
     "vaul": "^1.1.2",
     "vite": "catalog:",
     "vitest": "catalog:"

package/corpus/templates/calendar/server/handlers/events.ts

@@ -9,6 +9,7 @@ import {
   type H3Event,
 } from "h3";
 
+import { ensureOrganizerInAttendees } from "../../actions/event-action-helpers.js";
 import type { CalendarEvent } from "../../shared/api.js";
 import { getGoogleEventColorHex } from "../../shared/google-event-colors.js";
 import {
@@ -271,6 +272,9 @@ export const createEvent = defineEventHandler(async (event: H3Event) => {
       id: "",
       source: "google",
       accountEmail: acctEmail,
+      // Match Google Calendar UI: when inviting guests, include the
+      // organizer/self email in attendees so they appear in Guests.
+      attendees: ensureOrganizerInAttendees(eventBody.attendees, acctEmail),
       createdAt: new Date().toISOString(),
       updatedAt: new Date().toISOString(),
     };
@@ -302,7 +306,7 @@ export const createEvent = defineEventHandler(async (event: H3Event) => {
           title: calEvent.title || eventBody.title || "",
           startTime: calEvent.start,
           endTime: calEvent.end,
-          attendees: eventBody.attendees ?? [],
+          attendees: calEvent.attendees ?? [],
           createdBy: email,
         },
         { owner: email },

package/corpus/templates/calendar/shared/api.ts

@@ -47,6 +47,12 @@ export interface CalendarEvent {
     self?: boolean;
     /** When true, the attendee is optional (Google Calendar `optional`). */
     optional?: boolean;
+    /**
+     * Optional IANA timezone for this attendee (e.g. America/New_York).
+     * Used to show their local time for the event start when known.
+     * Prefer user overrides via `attendee-timezones` settings when absent.
+     */
+    timeZone?: string;
   }>;
   reminders?: Array<{ method: "popup" | "email"; minutes: number }>;
   /** Whether this event uses the calendar's default reminder policy. */

package/corpus/templates/chat/.agents/skills/self-modifying-code/SKILL.md

@@ -28,7 +28,19 @@ Not all modifications are equal. Use this to decide what level of care is needed
 | 1: Data       | Files in `data/`      | JSON state, generated content, markdown          | Nothing — these are routine       |
 | 2: Source     | App code              | Components, routes, styles, scripts              | Run `pnpm typecheck && pnpm lint` |
 | 3: Config     | Project config        | `package.json`, `tsconfig.json`, `vite.config.*` | Ask for explicit approval first   |
-| 4: Off limits | Secrets and framework | `.env`, `@agent-native/core` internals           | Never modify these                |
+| 4: Off limits | Secrets and framework | `.env`, `@agent-native/*` packages & overrides   | Never modify these                |
+
+Tier 4 includes **all** of the following — not only editing package source:
+
+- Files under `node_modules/@agent-native/*` (core, dispatch, scheduling, …)
+- `pnpm.overrides`, `overrides`, `resolutions`, or `patchedDependencies` that
+  target any `@agent-native/*` package
+- Local patches, vendored copies, or invented "dispatch/core behavior"
+  shims meant to paper over a version skew or failed upgrade
+
+When an older branch needs current packages, use **`agent-native upgrade`**
+(see the `upgrade-agent-native` skill). If upgrade or typecheck fails, fix
+**app** code or stop and ask — do not patch the framework.
 
 ## Git Checkpoint Pattern
 
@@ -74,13 +86,19 @@ inline strings in components.
 ## Don't
 
 - Don't modify `.env` files or files containing secrets
-- Don't modify `@agent-native/core` package internals
+- Don't modify `@agent-native/core`, `@agent-native/dispatch`, or other
+  `@agent-native/*` package internals (including under `node_modules`)
+- Don't add `pnpm.overrides` / `patchedDependencies` / `resolutions` for
+  `@agent-native/*` to "make the app run" after a version bump
+- Don't invent local dispatch/core behavior overrides when upgrade fails —
+  run `npx @agent-native/core@latest upgrade`, then fix app-level errors only
 - Don't modify `.agents/skills/` or `AGENTS.md` unless explicitly requested
 - Don't skip the typecheck/lint step after editing source code
 - Don't make source changes without a git checkpoint to roll back to
 
 ## Related Skills
 
+- **upgrade-agent-native** — supported path to bring an older app/workspace current
 - **storing-data** — Tier 1 modifications (data files) are the safest and most common
 - **actions** — The agent can create or modify actions to add new capabilities
 - **delegate-to-agent** — Self-modification requests come through the agent chat

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

@@ -0,0 +1,87 @@
+---
+name: upgrade-agent-native
+description: >-
+  Bring an older Agent Native app or workspace current. Use when updating
+  @agent-native/core, fixing a broken upgrade, or when tempted to patch or
+  override core/dispatch packages to make an old branch run.
+scope: dev
+metadata:
+  internal: true
+---
+
+# Upgrade Agent Native
+
+## Rule
+
+When an older Agent Native app/branch needs to run on current packages, use
+`agent-native upgrade`. Never "fix" upgrade breakage with
+`pnpm.overrides`, `patchedDependencies`, `resolutions`, local patches, or
+edits under `node_modules/@agent-native/*` — especially not against
+`@agent-native/core` or `@agent-native/dispatch`.
+
+## Why
+
+Agents often respond to a failed core bump by inventing framework patches and
+dispatch behavior overrides. That hides the real app-level break, drifts from
+upstream, and makes the next upgrade worse. The supported path is bump →
+install → refresh scaffold skills → verify, then fix **app** code only.
+
+## How
+
+1. **Doctor first (optional but recommended)**
+
+   ```bash
+   npx @agent-native/core@latest upgrade check
+   ```
+
+   This reports framework overrides/patches and pending `@agent-native/*`
+   bumps. If overrides/patches are present, remove them before continuing.
+
+2. **Run the upgrade**
+
+   ```bash
+   npx @agent-native/core@latest upgrade
+   ```
+
+   Or from an already-installed CLI: `pnpm exec agent-native upgrade` /
+   `agent-native upgrade`.
+
+   What it does:
+
+   - Blocks (unless `--force`) when `@agent-native/*` overrides/patches exist
+   - Rewrites non-local `@agent-native/*` dependency pins to `latest`
+   - Runs the package manager install
+   - Runs `skills update scaffold --project`
+   - Runs `typecheck` when the project has that script
+
+3. **If upgrade or typecheck fails**
+
+   - Read the concrete error
+   - Fix **app** source, actions, config, or env — not framework packages
+   - Re-run `agent-native upgrade` or `pnpm typecheck`
+   - Stop and ask the user if you cannot fix the app-level error
+
+4. **Dry-run / partial runs**
+
+   ```bash
+   agent-native upgrade --dry-run
+   agent-native upgrade --skip-verify
+   agent-native upgrade --skip-install   # package.json bumps only
+   ```
+
+## Don't
+
+- Don't add `pnpm.overrides`, `overrides`, `resolutions`, or
+  `patchedDependencies` for any `@agent-native/*` package
+- Don't edit `node_modules/@agent-native/core` or
+  `node_modules/@agent-native/dispatch`
+- Don't invent local "dispatch behavior" shims to paper over version skew
+- Don't keep iterating with more framework patches after a failed install
+- Don't skip `skills update scaffold --project` after a core bump (the
+  upgrade command does this for you)
+
+## Related Skills
+
+- **self-modifying-code** — Tier 4: framework packages are off limits
+- **agent-native-docs** — version-matched docs after the bump
+- **portability** — keep app code provider-agnostic across upgrades

package/corpus/templates/chat/package.json

@@ -60,7 +60,6 @@
     "@types/node": "^24.2.1",
     "@types/react": "catalog:",
     "@types/react-dom": "catalog:",
-    "@typescript/native-preview": "catalog:",
     "@xterm/addon-fit": "^0.11.0",
     "@xterm/addon-web-links": "^0.12.0",
     "@xterm/xterm": "^6.0.0",
@@ -82,7 +81,8 @@
     "tailwind-merge": "^3.5.0",
     "tailwindcss": "catalog:",
     "tsx": "^4.20.3",
-    "typescript": "^6.0.3",
+    "typescript": "catalog:",
+    "typescript-7": "catalog:",
     "vaul": "^1.1.2",
     "vite": "catalog:",
     "vitest": "catalog:"

package/corpus/templates/clips/.agents/skills/meetings/SKILL.md

@@ -58,7 +58,11 @@ Both fields are set by `start-meeting-recording`. Agents that operate on a recor
 
 ## Calendar reminders
 
-Calendar events fire a desktop notification **5 minutes before** the meeting start (consumer: the desktop tray in `src-tauri/`). The tray polls `list-meetings`, which reads Google Calendar live, so upcoming reminders do not depend on a manual sync or pre-created `meetings` rows. Agents do not need to schedule reminders manually.
+Calendar events fire a desktop notification **1 minute before** the meeting start and keep it visible until **5 minutes after** start unless dismissed (consumer: the desktop tray in `src-tauri/`). The tray polls `list-meetings`, which reads Google Calendar live, so upcoming reminders do not depend on a manual sync or pre-created `meetings` rows. Agents do not need to schedule reminders manually.
+
+## Adhoc Zoom / Teams detection (desktop)
+
+When meetings are enabled, the Clips desktop app also watches for native Zoom (`us.zoom.xos` / `us.zoom.ZoomClips`) and Microsoft Teams (`com.microsoft.teams` / `com.microsoft.teams2`) becoming frontmost. After a short dwell (~9s) it creates an adhoc meeting via `create-meeting` (`source: "adhoc"`) and shows the same Granola-style popup (`type: "adhoc"`, subtitle "Take notes?"). Auto transcription mode also emits `meetings:start-transcription` with reason `adhoc-auto`. Detection skips when a meeting is already being transcribed, when Manual mode has the meeting widget disabled, and soft-skips shortly after a calendar reminder for the same platform.
 
 ## Actions
 
@@ -66,7 +70,7 @@ Calendar events fire a desktop notification **5 minutes before** the meeting sta
 | ------------------------- | --------------------------------------------------------------------- |
 | `list-meetings`           | Upcoming + past, scoped via `accessFilter`; reads connected Google Calendar live |
 | `get-meeting`             | One meeting + participants + segments + notes                         |
-| `create-meeting`          | Internal/escape-hatch meeting row creation; the visible Meetings UI is calendar-sourced |
+| `create-meeting`          | Create a meeting row (`source`: `calendar` / `adhoc` / `manual`); desktop adhoc Zoom/Teams detection passes `source: "adhoc"` |
 | `update-meeting`          | Inline title edit, notes edits                                        |
 | `delete-meeting`          | Soft-delete a meeting from the visible list; linked recordings and calendar events stay intact |
 | `start-meeting-recording` | Begin native macOS transcript stream + create the linked recording   |

package/corpus/templates/clips/.agents/skills/self-modifying-code/SKILL.md

@@ -28,7 +28,19 @@ Not all modifications are equal. Use this to decide what level of care is needed
 | 1: Data       | Files in `data/`      | JSON state, generated content, markdown          | Nothing — these are routine       |
 | 2: Source     | App code              | Components, routes, styles, scripts              | Run `pnpm typecheck && pnpm lint` |
 | 3: Config     | Project config        | `package.json`, `tsconfig.json`, `vite.config.*` | Ask for explicit approval first   |
-| 4: Off limits | Secrets and framework | `.env`, `@agent-native/core` internals           | Never modify these                |
+| 4: Off limits | Secrets and framework | `.env`, `@agent-native/*` packages & overrides   | Never modify these                |
+
+Tier 4 includes **all** of the following — not only editing package source:
+
+- Files under `node_modules/@agent-native/*` (core, dispatch, scheduling, …)
+- `pnpm.overrides`, `overrides`, `resolutions`, or `patchedDependencies` that
+  target any `@agent-native/*` package
+- Local patches, vendored copies, or invented "dispatch/core behavior"
+  shims meant to paper over a version skew or failed upgrade
+
+When an older branch needs current packages, use **`agent-native upgrade`**
+(see the `upgrade-agent-native` skill). If upgrade or typecheck fails, fix
+**app** code or stop and ask — do not patch the framework.
 
 ## Git Checkpoint Pattern
 
@@ -74,13 +86,19 @@ inline strings in components.
 ## Don't
 
 - Don't modify `.env` files or files containing secrets
-- Don't modify `@agent-native/core` package internals
+- Don't modify `@agent-native/core`, `@agent-native/dispatch`, or other
+  `@agent-native/*` package internals (including under `node_modules`)
+- Don't add `pnpm.overrides` / `patchedDependencies` / `resolutions` for
+  `@agent-native/*` to "make the app run" after a version bump
+- Don't invent local dispatch/core behavior overrides when upgrade fails —
+  run `npx @agent-native/core@latest upgrade`, then fix app-level errors only
 - Don't modify `.agents/skills/` or `AGENTS.md` unless explicitly requested
 - Don't skip the typecheck/lint step after editing source code
 - Don't make source changes without a git checkpoint to roll back to
 
 ## Related Skills
 
+- **upgrade-agent-native** — supported path to bring an older app/workspace current
 - **storing-data** — Tier 1 modifications (data files) are the safest and most common
 - **actions** — The agent can create or modify actions to add new capabilities
 - **delegate-to-agent** — Self-modification requests come through the agent chat

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

@@ -0,0 +1,87 @@
+---
+name: upgrade-agent-native
+description: >-
+  Bring an older Agent Native app or workspace current. Use when updating
+  @agent-native/core, fixing a broken upgrade, or when tempted to patch or
+  override core/dispatch packages to make an old branch run.
+scope: dev
+metadata:
+  internal: true
+---
+
+# Upgrade Agent Native
+
+## Rule
+
+When an older Agent Native app/branch needs to run on current packages, use
+`agent-native upgrade`. Never "fix" upgrade breakage with
+`pnpm.overrides`, `patchedDependencies`, `resolutions`, local patches, or
+edits under `node_modules/@agent-native/*` — especially not against
+`@agent-native/core` or `@agent-native/dispatch`.
+
+## Why
+
+Agents often respond to a failed core bump by inventing framework patches and
+dispatch behavior overrides. That hides the real app-level break, drifts from
+upstream, and makes the next upgrade worse. The supported path is bump →
+install → refresh scaffold skills → verify, then fix **app** code only.
+
+## How
+
+1. **Doctor first (optional but recommended)**
+
+   ```bash
+   npx @agent-native/core@latest upgrade check
+   ```
+
+   This reports framework overrides/patches and pending `@agent-native/*`
+   bumps. If overrides/patches are present, remove them before continuing.
+
+2. **Run the upgrade**
+
+   ```bash
+   npx @agent-native/core@latest upgrade
+   ```
+
+   Or from an already-installed CLI: `pnpm exec agent-native upgrade` /
+   `agent-native upgrade`.
+
+   What it does:
+
+   - Blocks (unless `--force`) when `@agent-native/*` overrides/patches exist
+   - Rewrites non-local `@agent-native/*` dependency pins to `latest`
+   - Runs the package manager install
+   - Runs `skills update scaffold --project`
+   - Runs `typecheck` when the project has that script
+
+3. **If upgrade or typecheck fails**
+
+   - Read the concrete error
+   - Fix **app** source, actions, config, or env — not framework packages
+   - Re-run `agent-native upgrade` or `pnpm typecheck`
+   - Stop and ask the user if you cannot fix the app-level error
+
+4. **Dry-run / partial runs**
+
+   ```bash
+   agent-native upgrade --dry-run
+   agent-native upgrade --skip-verify
+   agent-native upgrade --skip-install   # package.json bumps only
+   ```
+
+## Don't
+
+- Don't add `pnpm.overrides`, `overrides`, `resolutions`, or
+  `patchedDependencies` for any `@agent-native/*` package
+- Don't edit `node_modules/@agent-native/core` or
+  `node_modules/@agent-native/dispatch`
+- Don't invent local "dispatch behavior" shims to paper over version skew
+- Don't keep iterating with more framework patches after a failed install
+- Don't skip `skills update scaffold --project` after a core bump (the
+  upgrade command does this for you)
+
+## Related Skills
+
+- **self-modifying-code** — Tier 4: framework packages are off limits
+- **agent-native-docs** — version-matched docs after the bump
+- **portability** — keep app code provider-agnostic across upgrades

package/corpus/templates/clips/actions/create-meeting.ts

@@ -65,6 +65,12 @@ export default defineAction({
         .enum(["private", "org", "public"])
         .optional()
         .describe("Initial visibility — defaults to private"),
+      source: z
+        .enum(["calendar", "adhoc", "manual"])
+        .optional()
+        .describe(
+          "How the meeting was created. Desktop adhoc Zoom/Teams detection passes `adhoc`; omit to infer from title/calendarEventId.",
+        ),
     })
     .refine((v) => v.title || v.calendarEventId, {
       message: "Provide either title or calendarEventId",
@@ -86,9 +92,8 @@ export default defineAction({
       isOrganizer?: boolean;
     }> = args.participants ?? [];
     let calendarEventIdLink: string | null = null;
-    let source: "calendar" | "adhoc" | "manual" = args.title
-      ? "manual"
-      : "adhoc";
+    let source: "calendar" | "adhoc" | "manual" =
+      args.source ?? (args.title ? "manual" : "adhoc");
 
     if (args.calendarEventId) {
       // Verify the user owns the calendar account that hosts this event.