ad2app-lib 1.10.0 → 1.14.0

package/src/types/scheduling/I_SchedulingPost.ts

@@ -78,11 +78,68 @@ export class SchedulingCreatePostDTO {
 export class SchedulingUpdatePostDTO {
   content?: string;
   scheduledAt?: string;
+  /**
+   * Per-platform targets for the edit patch (C2, AD2-1026) — the backend's
+   * `UpdatePostDTO` intersects this on top locally today; promoted here so
+   * the type ships from the lib instead of a local clone.
+   */
+  platforms?: SchedulingPlatformTargetDTO[];
+  /** Full media array for the edit patch (C2, AD2-1026), same shape as create. */
+  mediaItems?: SchedulingMediaItemDTO[];
 
   constructor(data?: Partial<SchedulingUpdatePostDTO>) {
     if (!data) return;
     this.content = data.content;
     this.scheduledAt = data.scheduledAt;
+    this.platforms = data.platforms;
+    this.mediaItems = data.mediaItems;
+  }
+}
+
+// ── SchedulingPostMediaItemDTO ────────────────────────────────────────────────
+
+/**
+ * One media item on the edit-load response — verbatim from the live Zernio
+ * post's mediaItems (Post.mediaItems → MediaItem, OpenAPI v1.0.4:3223).
+ * Distinct from `SchedulingMediaItemDTO` (the create/update input shape):
+ * every field here is optional and `type` additionally allows `gif`/`document`
+ * to match what a fetched post can actually carry (T022b, AD2-1026).
+ */
+export class SchedulingPostMediaItemDTO {
+  type?: 'image' | 'video' | 'gif' | 'document';
+  url?: string;
+  title?: string;
+
+  constructor(data?: Partial<SchedulingPostMediaItemDTO>) {
+    if (!data) return;
+    this.type = data.type;
+    this.url = data.url;
+    this.title = data.title;
+  }
+}
+
+// ── SchedulingPostTargetDTO ───────────────────────────────────────────────────
+
+/**
+ * One per-platform target on the edit-load response — the request-shape
+ * subset of Zernio's PlatformTarget (OpenAPI v1.0.4:3275): `platform`,
+ * `accountId` (always normalized to the plain string id — Zernio expands it
+ * to an account object on fetched posts, yaml:3282), and
+ * `platformSpecificData` VERBATIM (yaml:3297, additionalProperties: true).
+ * Response-only fields (status, platformPostUrl, errors) are never exposed
+ * here — they already live on platformStatuses/postUrls/platformErrors
+ * (T022b, AD2-1026).
+ */
+export class SchedulingPostTargetDTO {
+  platform: string;
+  accountId?: string;
+  platformSpecificData?: Record<string, unknown>;
+
+  constructor(data?: Partial<SchedulingPostTargetDTO>) {
+    if (!data) return;
+    this.platform = data.platform;
+    this.accountId = data.accountId;
+    this.platformSpecificData = data.platformSpecificData;
   }
 }
 
@@ -104,6 +161,25 @@ export class SchedulingPostDTO {
   contentSnippet?: string;
   createdAt: string;
   updatedAt: string;
+  /**
+   * Media-miniature pass-through fields (C1, AD2-1083) — present only when
+   * the cache row has a stored thumbnail/media URL, absent otherwise (never
+   * an empty string).
+   */
+  thumbnailUrl?: string;
+  mediaUrl?: string;
+  /**
+   * Edit-load fields for compose edit mode (C2, AD2-1026 + T022b):
+   * `content` is the COMPLETE caption (the cache only stores the 280-char
+   * `contentSnippet`); `mediaItems`/`platformTargets` are the full per-post
+   * media array and per-platform accountIds + compose settings. All three
+   * ride the live Zernio fetch: present when it succeeds (arrays may be
+   * possibly-empty = known-empty), ALL absent when it fails, which blocks
+   * edit frontend-side.
+   */
+  content?: string;
+  mediaItems?: SchedulingPostMediaItemDTO[];
+  platformTargets?: SchedulingPostTargetDTO[];
 
   constructor(data: SchedulingPostDTO) {
     this.id = data.id;
@@ -118,6 +194,11 @@ export class SchedulingPostDTO {
     this.contentSnippet = data.contentSnippet;
     this.createdAt = data.createdAt;
     this.updatedAt = data.updatedAt;
+    this.thumbnailUrl = data.thumbnailUrl;
+    this.mediaUrl = data.mediaUrl;
+    this.content = data.content;
+    this.mediaItems = data.mediaItems;
+    this.platformTargets = data.platformTargets;
   }
 }
 

package/CHANGELOG.md

@@ -1,43 +0,0 @@
-# Changelog
-
-All notable changes to `ad2app-lib` are documented here. The analytics taxonomy
-is the single source of truth across all surfaces; the matching spec lives in
-`ad2appus/docs/posthog-implementation.md` (§3).
-
-## 1.9.0
-
-### Added
-
-- Free Tier analytics (epic AD2-887):
-  - `EVENTS.FREE_SKILLS_REQUESTED` (`free_skills_requested`), shape `{ source: string }` — email submitted for the free skills (AD2-889).
-  - `EVENTS.ACCOUNT_CONNECT_BLOCKED` (`account_connect_blocked`), shape `{ platform?: string }` — free user hits the connect wall (AD2-892).
-  - `EVENTS.MCP_POST_BLOCKED_FREE_TIER` (`mcp_post_blocked_free_tier`), shape `{ target_count?: number }` — free user tries to post in the MCP (AD2-898).
-  - `'free_skills'` added to the `LANDING_CTA_CLICKED` location union.
-- Email lifecycle events (Resend webhook -> PostHog, AD2-894):
-  `EVENTS.EMAIL_DELIVERED` / `EMAIL_OPENED` / `EMAIL_CLICKED` / `EMAIL_BOUNCED` /
-  `EMAIL_COMPLAINED`, all sharing `EmailEventProperties` (`{ email_id?, subject?, link? }`).
-
-## 1.8.0
-
-### Added
-
-- `EVENTS.CONNECT_ARTIFACT_COPIED` (`connect_artifact_copied`) with property
-  shape `{ target: 'app' | 'ask' | 'terminal' | 'editor' }` — fired when the
-  `/connect` install snippet is copied.
-- `'ai_connector'` added to the `LANDING_CTA_CLICKED` location union
-  (`hero | pricing | final_cta | nav | ai_connector`).
-
-### Removed
-
-- `EVENTS.TRIAL_STARTED` (`trial_started`) and its `EventProperties` shape.
-- `PERSON_PROPS.TRIAL_ENDS_AT` (`trial_ends_at`).
-- `'trial'` removed from the documented `PLAN` person-property values, which now
-  match the canonical `SchedulingSubscriptionTier` (`free | starter | pro`).
-
-  ad2app is a paid-only product with no trial, so these events never fired.
-  Verified that no consumer (frontend, backend, landing, mcp) referenced them.
-
-> **Semver note:** removing exported symbols is technically breaking. It is
-> released as a minor because no consumer referenced the removed tokens and all
-> consumers pin `^1.7.x`, so they upgrade frictionlessly. If you prefer strict
-> semver, retag as `2.0.0` and bump the consumer ranges deliberately.