@agent-native/core 0.69.0 → 0.70.1

package/corpus/templates/plan/shared/share-attribution.ts

@@ -0,0 +1,72 @@
+/**
+ * Viral attribution contract for shared/public Plan links.
+ *
+ * Public plan/recap URLs self-attribute so the signup funnel can be measured
+ * even when `document.referrer` is empty (desktop app, Slack, native clients,
+ * etc.). The framework captures first-touch from these params into a cookie and
+ * enriches the `signup` event; Plan's job is to (a) tag the share/public URLs it
+ * mints and (b) emit funnel events when a logged-out visitor views a public plan
+ * and clicks a sign-up CTA.
+ *
+ * Contract strings are centralized here so the minting side (share popover /
+ * copy-link) and the measuring side (public plan view) cannot drift apart. The
+ * framework also derives `plan_share` from public plan paths (`/p/`, `/plan/`,
+ * `/plans/`, `/recaps/`, `/share-plan/`) as a fallback when the param is lost.
+ *
+ * Privacy: `via` must be a non-PII stable id (the owner's user id), never an
+ * email. Omit `via` rather than leak PII into a public URL or event.
+ */
+
+/** Fixed referral source for plan shares. */
+export const PLAN_SHARE_REF = "plan_share";
+
+/** Surface tag included on plan share funnel events. */
+export const PLAN_SHARE_SURFACE = "plan";
+
+/** Query param names that carry attribution. */
+export const REF_PARAM = "ref";
+export const VIA_PARAM = "via";
+
+/**
+ * Append `ref=plan_share` (and `via=<ownerId>` when a non-PII owner id is known)
+ * to an absolute share/public plan URL, preserving any existing query params.
+ * Returns the input unchanged when it isn't a parseable absolute URL.
+ */
+export function withPlanShareAttribution(
+  url: string | undefined,
+  ownerId?: string | null,
+): string | undefined {
+  if (!url) return url;
+  try {
+    const parsed = new URL(url);
+    parsed.searchParams.set(REF_PARAM, PLAN_SHARE_REF);
+    const owner = (ownerId ?? "").trim();
+    if (owner) parsed.searchParams.set(VIA_PARAM, owner);
+    return parsed.toString();
+  } catch {
+    return url;
+  }
+}
+
+export type ShareAttribution = {
+  ref: string | undefined;
+  via: string | undefined;
+};
+
+/**
+ * Read `ref`/`via` from a query string (e.g. `window.location.search`). Falls
+ * back to `ref=plan_share` so downstream attribution stays meaningful even when
+ * the visitor arrived via a link that lost the param. Never throws.
+ */
+export function readPlanShareAttribution(search: string): ShareAttribution {
+  let ref: string | undefined;
+  let via: string | undefined;
+  try {
+    const params = new URLSearchParams(search ?? "");
+    ref = params.get(REF_PARAM) ?? undefined;
+    via = params.get(VIA_PARAM) ?? undefined;
+  } catch {
+    // Ignore malformed query strings — fall through to the default below.
+  }
+  return { ref: ref || PLAN_SHARE_REF, via: via || undefined };
+}

package/corpus/templates/slides/CHANGELOG.md

@@ -0,0 +1,10 @@
+# Changelog
+
+All notable user-facing changes to Agent-Native Slides are documented here. Open it any
+time from the command menu (Cmd+K → "What's new").
+
+## 2026-06-23
+
+### Added
+
+- See what's new right inside Agent-Native Slides — a changelog now lives in the command menu (Cmd+K).

package/corpus/templates/slides/app/root.tsx

@@ -28,6 +28,7 @@ import { useQueryClient } from "@tanstack/react-query";
 import type { LinksFunction } from "react-router";
 import stylesheet from "./global.css?url";
 import { configureTracking } from "@agent-native/core/client";
+import changelog from "../CHANGELOG.md?raw";
 import { getThemeInitScript } from "@agent-native/core/client";
 import { TAB_ID } from "@/lib/tab-id";
 configureTracking({
@@ -162,7 +163,12 @@ function AppContent() {
 
   return (
     <>
-      <CommandMenu open={cmdkOpen} onOpenChange={setCmdkOpen}>
+      <CommandMenu
+        open={cmdkOpen}
+        onOpenChange={setCmdkOpen}
+        changelog={changelog}
+        changelogKey="slides"
+      >
         <CommandMenu.Group heading="Presentations">
           <CommandMenu.Item onSelect={() => {}}>Search decks</CommandMenu.Item>
         </CommandMenu.Group>

package/corpus/templates/videos/CHANGELOG.md

@@ -1,157 +1,10 @@
 # Changelog
 
-## [Unreleased] - 2026-02-28
+All notable user-facing changes to Agent-Native Videos are documented here. Open it any
+time from the command menu (Cmd+K → "What's new").
 
-### Architecture Improvements ✨
-
-- **Extracted Animation Logic to Reusable Pure Function**
-  - Created `app/remotion/animations/useElementAnimations.ts` (202 lines)
-  - Exported `calculateElementAnimations()` - pure function (not hook)
-  - Removed 130 lines of animation logic from InteractiveCardGrid
-  - Centralized all animation calculations in testable function
-  - Can be called inside loops (no Rules of Hooks violations)
-  - Other compositions can now reuse animation system instantly
-  - Reduced InteractiveCardGrid from 400+ to 320 lines
-  - Simpler and faster than hook-based approach
-
-- **Centralized Configuration Constants**
-  - Created `app/config/constants.ts` (204 lines)
-  - Eliminated all magic numbers across codebase
-  - Organized by domain: ANIMATION_CONFIG, CURSOR_CONFIG, CARD_CONFIG, UI_CONFIG, etc.
-  - Type-safe with `as const`
-  - Well-documented with inline comments
-
-- **Code Quality Improvements**
-  - Max function length: 87 lines → 42 lines
-  - Animation logic now testable in isolation
-  - Proper type guards with centralized validation
-  - Cleaner separation of concerns
-
-**Impact**: Architecture grade improved from C+ to A-
+## 2026-06-23
 
 ### Added
 
-- **Color Animation Support**: Background and border color properties for cursor interactions
-  - Added `backgroundColor` and `borderColor` to animation property options
-  - Implemented color interpolation function for smooth color transitions
-  - Color picker UI with native browser color input
-  - Colors animate from each element's base color to target color (preserves multicolor designs)
-
-- **Click Animation Return-to-Hover**: Click animations now properly animate back
-  - Implemented "there-and-back" animation (0→1→0 progress mapping)
-  - Doubles animation duration to accommodate forward and return transitions
-  - Smooth easing applied to both directions
-
-- **Timeline Visual Enhancements**
-  - Changed cursor keyframe click indicator dot from grey/white to yellow (#facc15)
-  - Improved visual distinction for click events in timeline
-
-### Changed
-
-- **Playback Speed System**: Simplified from adaptive to manual control
-  - Removed adaptive playback rate compensation based on FPS measurement
-  - Added manual playback speed dropdown (0.25× to 2×)
-  - Moved speed selector to VideoPlayer bottom controls (next to Frame counter)
-  - Removed playback speed from Timeline component
-
-- **Composition Creation Workflow**: Restored AI-powered generation
-  - Rewrote `NewCompositionPopover` with full agent chat integration
-  - Added file attachment support (images, videos, SVGs via data URLs)
-  - Implemented postMessage API for parent window communication
-  - Added event listener for `builder.agentChat.chatRunning` completion detection
-  - Slug-based URL generation with conflict resolution (`/c/comp-title`, `/c/comp-title-2`)
-  - Navigate to `/c/new` on submission for AI generation
-
-- **Properties Panel Improvements**
-  - Removed composition name input from Properties > Properties section (non-editable)
-  - Hidden "x" unit label to avoid confusion with delete button (kept "px", "deg", etc.)
-  - Moved "Add Property" section above property list (below Motion Curve)
-  - Swapped + button to left side of dropdown
-  - Added Enter key support to add properties from dropdown
-  - Changed focus ring color to red-400 for consistency
-  - Removed hex code display next to color picker (visible in native picker)
-
-- **Animation System Architecture**
-  - Updated `AnimationKeyframe.value` type to support `number | string` for colors
-  - Color animations only apply when `hoverProgress > 0` or `clickProgress > 0`
-  - Each element's base color extracted and used as animation starting point
-  - Hover and click animations support mixed numeric and color properties
-
-### Fixed
-
-- Browser cache issues causing stale code errors
-  - Fixed `ReferenceError: adaptivePlaybackRate is not defined`
-  - Fixed `ReferenceError: onCreateComposition is not defined`
-  - Solution: Dev server restart to clear Vite cache
-
-- Color animation not preserving element colors
-  - Cards were all turning blue when backgroundColor animation added
-  - Fixed by interpolating from each card's unique base color instead of fixed start color
-  - Only applies color animations during active hover/click (preserves idle state)
-
-- Click animations jumping back to hover state
-  - Animations were not tweening back, causing abrupt transitions
-  - Implemented smooth 0→1→0 progress curve with doubled duration
-
-### Technical Details
-
-#### Color Interpolation Implementation
-
-```typescript
-// New function in elementAnimations.ts
-export function interpolateColor(
-  color1: string,
-  color2: string,
-  progress: number,
-): string;
-```
-
-- Parses hex colors to RGB components
-- Linear interpolation per channel
-- Returns hex color string
-
-#### Animation Progress Mapping
-
-```typescript
-// Click animation: 0→1→0 curve
-const rawProgress = framesSinceClick / clickDuration; // 0→2
-clickProgress = rawProgress <= 1 ? rawProgress : 2 - rawProgress; // 0→1→0
-```
-
-#### Files Modified
-
-- `app/components/VideoPlayer.tsx` - Simplified playback rate
-- `app/components/Timeline.tsx` - Removed playback UI, changed dot color
-- `app/pages/CompositionView.tsx` - Playback rate state management
-- `app/components/NewCompositionPopover.tsx` - Complete rewrite for agent chat integration
-- `app/components/Sidebar.tsx` - Updated props, removed name input
-- `app/components/PropsEditor.tsx` - Removed composition name field
-- `app/components/CurrentElementPanel.tsx` - Color properties, UI improvements
-- `app/types/elementAnimations.ts` - Color support, interpolation
-- `app/remotion/compositions/InteractiveCardGrid.tsx` - Color animation logic
-
-#### Files Created
-
-- `app/remotion/animations/useElementAnimations.ts` (209 lines) - **Reusable animation hook**
-- `app/config/constants.ts` (204 lines) - **Centralized configuration**
-- `app/utils/compositionHelpers.ts` (378 lines) - Helper functions library
-- `app/utils/debug.ts` (104 lines) - Production-safe logging utility
-- `scripts/create-composition.ts` (127 lines) - Example composition script
-- `COMPOSITION_GUIDE.md` (787 lines) - Comprehensive API reference
-- `QUICK_START.md` (498 lines) - Beginner-friendly guide
-- `README.md` (209 lines) - Project overview
-- `CHANGELOG.md`, `CODE_REVIEW.md`, `TODO.md`, `PR_DESCRIPTION.md`, `SESSION_SUMMARY.md`
-
-### Developer Experience
-
-- Native `<select>` supports type-to-search for properties
-- Arrow keys navigate property options
-- Enter key adds selected property
-- Color picker shows hex values natively
-- Improved visual hierarchy in properties panel
-
----
-
-## Notes
-
-All changes maintain backward compatibility with existing compositions. Color animation feature is additive and optional.
+- See what's new right inside Agent-Native Videos — a changelog now lives in the command menu (Cmd+K).

package/corpus/templates/videos/app/root.tsx

@@ -20,6 +20,7 @@ import {
   configureTracking,
   getThemeInitScript,
 } from "@agent-native/core/client";
+import changelog from "../CHANGELOG.md?raw";
 configureTracking({
   getDefaultProps: (_name, properties) => ({
     ...properties,
@@ -83,7 +84,12 @@ function AppContent() {
 
   return (
     <>
-      <CommandMenu open={cmdkOpen} onOpenChange={setCmdkOpen}>
+      <CommandMenu
+        open={cmdkOpen}
+        onOpenChange={setCmdkOpen}
+        changelog={changelog}
+        changelogKey="videos"
+      >
         <CommandMenu.Group heading="Videos">
           <CommandMenu.Item onSelect={() => {}}>
             Search compositions

package/dist/action.js

@@ -332,6 +332,92 @@ function zodDefToJsonSchema(def) {
 // ---------------------------------------------------------------------------
 // Runtime validation wrapper
 // ---------------------------------------------------------------------------
+const NO_COERCE = Symbol("no-coerce");
+/**
+ * Coerce a single stringified value to one of the JSON-schema types the field
+ * expects. Returns NO_COERCE when nothing safe applies, so the caller leaves
+ * the original value untouched and the normal validation error still surfaces.
+ */
+function coerceStringToSchemaType(raw, types) {
+    const trimmed = raw.trim();
+    if (types.includes("boolean")) {
+        if (trimmed === "true")
+            return true;
+        if (trimmed === "false")
+            return false;
+    }
+    if ((types.includes("array") &&
+        trimmed.startsWith("[") &&
+        trimmed.endsWith("]")) ||
+        (types.includes("object") &&
+            trimmed.startsWith("{") &&
+            trimmed.endsWith("}"))) {
+        try {
+            const parsed = JSON.parse(trimmed);
+            if (types.includes("array") && Array.isArray(parsed))
+                return parsed;
+            if (types.includes("object") &&
+                parsed &&
+                typeof parsed === "object" &&
+                !Array.isArray(parsed)) {
+                return parsed;
+            }
+        }
+        catch {
+            // fall through — leave the original so validation reports the real error
+        }
+    }
+    if ((types.includes("number") || types.includes("integer")) &&
+        trimmed !== "" &&
+        Number.isFinite(Number(trimmed))) {
+        const n = Number(trimmed);
+        if (types.includes("number") || Number.isInteger(n))
+            return n;
+    }
+    return NO_COERCE;
+}
+/**
+ * Defensively coerce gateway-stringified tool arguments to the types the schema
+ * expects. Some model gateways (notably Builder's Gemini-backed gateway) hand
+ * back structured tool-call arguments as JSON strings — an array param arrives
+ * as `"[{...}]"`, a boolean as `"true"`. Standard Schema (zod) `validate` does
+ * not coerce, so these fail validation and the agent thrashes retrying shapes
+ * (and can hang). We only touch a string value when the schema expects a
+ * non-string type and the string parses cleanly to it; anything ambiguous
+ * (schema also allows string) or unparseable is left as-is. Operates on
+ * top-level properties only — once an array/object param is parsed, its nested
+ * members are already native and validate normally.
+ */
+function coerceGatewayStringifiedArgs(args, parameters) {
+    const properties = parameters?.properties;
+    if (!properties)
+        return args;
+    if (!args || typeof args !== "object" || Array.isArray(args))
+        return args;
+    let out = null;
+    for (const [key, raw] of Object.entries(args)) {
+        if (typeof raw !== "string")
+            continue;
+        const spec = properties[key];
+        if (!spec)
+            continue;
+        const types = Array.isArray(spec.type)
+            ? spec.type
+            : spec.type
+                ? [spec.type]
+                : [];
+        // No declared type, or the field legitimately accepts a string → leave it.
+        if (types.length === 0 || types.includes("string"))
+            continue;
+        const coerced = coerceStringToSchemaType(raw, types);
+        if (coerced === NO_COERCE)
+            continue;
+        if (!out)
+            out = { ...args };
+        out[key] = coerced;
+    }
+    return out ?? args;
+}
 /**
  * Wrap an action's run function with schema validation.
  * Invalid inputs get a clear error message (including what was actually passed)
@@ -339,6 +425,7 @@ function zodDefToJsonSchema(def) {
  */
 function wrapWithValidation(schema, run, toolParameters) {
     return async (args, ctx) => {
+        args = coerceGatewayStringifiedArgs(args, toolParameters);
         const result = await schema["~standard"].validate(args);
         if (result.issues) {
             // Split issues into "missing required field" vs other validation errors