founder-schema 0.1.0

package/dist/feed.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"feed.d.ts","sourceRoot":"","sources":["../src/feed.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAMxB;;;;GAIG;AACH,eAAO,MAAM,mBAAmB,OAAO,CAAC;AACxC;;;;;;;;GAQG;AACH,eAAO,MAAM,cAAc,KAAK,CAAC;AACjC;;;;;;GAMG;AACH,eAAO,MAAM,UAAU,IAAI,CAAC;AAC5B,eAAO,MAAM,sBAAsB,OAAO,CAAC;AAE3C,eAAO,MAAM,uBAAuB,MAAM,CAAC;AAC3C,eAAO,MAAM,qBAAqB,KAAK,CAAC;AACxC,eAAO,MAAM,gBAAgB,IAAI,CAAC;AAClC,eAAO,MAAM,gBAAgB,IAAI,CAAC;AAClC,iEAAiE;AACjE,eAAO,MAAM,oBAAoB,QAAgB,CAAC;AAClD,eAAe;AACf,eAAO,MAAM,oBAAoB,QAA2B,CAAC;AAI7D;;;;;;;GAOG;AACH,eAAO,MAAM,mBAAmB,2BAA4B,CAAC;AAC7D,eAAO,MAAM,iBAAiB;;;EAA8B,CAAC;AAC7D,MAAM,MAAM,WAAW,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,iBAAiB,CAAC,CAAC;AAE5D;;;;;;GAMG;AACH,eAAO,MAAM,oBAAoB,yDAA0D,CAAC;AAC5F,eAAO,MAAM,kBAAkB;;;;;EAA+B,CAAC;AAC/D,MAAM,MAAM,YAAY,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAAC;AAE9D;;;;;;;GAOG;AACH,eAAO,MAAM,gBAAgB,yBAA0B,CAAC;AACxD,eAAO,MAAM,cAAc;;;EAA2B,CAAC;AACvD,MAAM,MAAM,QAAQ,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,cAAc,CAAC,CAAC;AAEtD;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,oBAAoB;;;;;kCAGhC,CAAC;AACF,MAAM,MAAM,cAAc,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,oBAAoB,CAAC,CAAC;AAIlE;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,gBAAgB;;;;;;iBAU3B,CAAC;AACH,MAAM,MAAM,UAAU,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,gBAAgB,CAAC,CAAC;AAI1D;;;;;;;;GAQG;AACH,eAAO,MAAM,eAAe;;;;;;;iBAQ1B,CAAC;AACH,MAAM,MAAM,SAAS,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,eAAe,CAAC,CAAC;AAExD,eAAO,MAAM,eAAe;;;;;;;iBAU1B,CAAC;AACH,MAAM,MAAM,SAAS,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,eAAe,CAAC,CAAC;AAExD;;;;GAIG;AACH,eAAO,MAAM,eAAe;;;;;;;;;;;;;;2BAAmE,CAAC;AAChG,MAAM,MAAM,SAAS,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,eAAe,CAAC,CAAC;AAIxD;;;;;;;;;GASG;AACH,eAAO,MAAM,iBAAiB;;;;;iBAK5B,CAAC;AACH,MAAM,MAAM,WAAW,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,iBAAiB,CAAC,CAAC;AAI5D;;;;;;;GAOG;AACH,eAAO,MAAM,iBAAiB;;;;;;;;;;;;iBAsB5B,CAAC;AACH,MAAM,MAAM,WAAW,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,iBAAiB,CAAC,CAAC;AAI5D;;;;;;;;;;GAUG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBAuCzB,CAAC;AACH,MAAM,MAAM,QAAQ,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,cAAc,CAAC,CAAC;AAItD;;;;GAIG;AACH,eAAO,MAAM,gBAAgB;;;;iBAQ3B,CAAC;AACH,MAAM,MAAM,UAAU,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,gBAAgB,CAAC,CAAC;AAE1D;;;;;;;GAOG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBAuCzB,CAAC;AACH,MAAM,MAAM,QAAQ,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,cAAc,CAAC,CAAC;AAItD;;;;GAIG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;kCAAwE,CAAC;AACpG,MAAM,MAAM,QAAQ,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,cAAc,CAAC,CAAC;AAItD;;;;GAIG;AACH,eAAO,MAAM,iBAAiB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBAoB5B,CAAC;AACH,MAAM,MAAM,WAAW,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,iBAAiB,CAAC,CAAC;AAI5D;;;;;;GAMG;AACH,eAAO,MAAM,eAAe;;;;;;;;iBAG1B,CAAC;AACH,MAAM,MAAM,SAAS,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,eAAe,CAAC,CAAC;AAExD,eAAO,MAAM,mBAAmB;;;;iBAG9B,CAAC;AACH,MAAM,MAAM,aAAa,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,mBAAmB,CAAC,CAAC;AAIhE;;;;;GAKG;AAEH;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AACH,eAAO,MAAM,oBAAoB,MAAM,CAAC;AAExC;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,qBAAqB,gDAAiD,CAAC;AAEpF,eAAO,MAAM,eAAe,aASgD,CAAC;AAC7E,MAAM,MAAM,SAAS,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,eAAe,CAAC,CAAC;AAExD,eAAO,MAAM,mBAAmB;;;iBAI9B,CAAC;AACH,MAAM,MAAM,aAAa,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,mBAAmB,CAAC,CAAC;AAEhE;;;GAGG;AACH,eAAO,MAAM,oBAAoB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBAW7B,CAAC;AACL,MAAM,MAAM,cAAc,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,oBAAoB,CAAC,CAAC;AAElE;yDACyD;AACzD,eAAO,MAAM,oBAAoB;;iBAE/B,CAAC;AACH,MAAM,MAAM,cAAc,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,oBAAoB,CAAC,CAAC;AAElE,eAAO,MAAM,oBAAoB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBA2B9B,CAAC;AACJ,MAAM,MAAM,cAAc,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,oBAAoB,CAAC,CAAC;AAElE;0CAC0C;AAC1C,eAAO,MAAM,kBAAkB;;iBAW7B,CAAC;AACH,MAAM,MAAM,YAAY,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAAC;AAE9D,eAAO,MAAM,uBAAuB;;;iBAIlC,CAAC;AACH,MAAM,MAAM,iBAAiB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,uBAAuB,CAAC,CAAC;AAExE,eAAO,MAAM,uBAAuB;;iBAElC,CAAC;AACH,MAAM,MAAM,iBAAiB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,uBAAuB,CAAC,CAAC;AAExE,kFAAkF;AAClF,eAAO,MAAM,qBAAqB;;;;;;;iBAEhC,CAAC;AACH,MAAM,MAAM,eAAe,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,qBAAqB,CAAC,CAAC;AAIpE;;;;;GAKG;AACH,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;;;;iBAKpC,CAAC;AACH,MAAM,MAAM,mBAAmB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,yBAAyB,CAAC,CAAC;AAI5E;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,oBAAoB,0FAOvB,CAAC;AACX,eAAO,MAAM,kBAAkB;;;;;;;EAA+B,CAAC;AAC/D,MAAM,MAAM,YAAY,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAAC;AAE9D;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,sBAAsB;;;;;;;;;;iBAGjC,CAAC;AACH,MAAM,MAAM,gBAAgB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,sBAAsB,CAAC,CAAC;AAEtE;;;;;;;;;GASG;AACH,eAAO,MAAM,0BAA0B;;;;;;;iBAIrC,CAAC;AACH,MAAM,MAAM,oBAAoB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,0BAA0B,CAAC,CAAC;AAE9E,6EAA6E;AAC7E,eAAO,MAAM,4BAA4B;;;;;;;iBAIvC,CAAC;AACH,MAAM,MAAM,sBAAsB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,4BAA4B,CAAC,CAAC;AAElF;mEACmE;AACnE,eAAO,MAAM,sBAAsB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iBAEjC,CAAC;AACH,MAAM,MAAM,gBAAgB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,sBAAsB,CAAC,CAAC"}

package/dist/feed.js

@@ -0,0 +1,593 @@
+/**
+ * founder-schema — Feed wire shapes: post, poll, comment, reaction
+ *
+ * ADAPTED FROM `jansathi-community-schema`, NOT DEPENDENT ON IT.
+ *
+ * The user ruled on 2026-09-21 that Founder Circle is a standalone app, so
+ * these shapes are copied and cut down rather than imported. The reason is
+ * worth keeping: `jansathi-community-schema` encodes Jansathi's reach levels,
+ * community designations, official-area kinds and crowdfunding audiences.
+ * Depending on it would put all of that permanently inside our contract for a
+ * feed that has none of those concepts, and would mean a Jansathi publish can
+ * break this product.
+ *
+ * DELIBERATELY NOT PORTED, so nobody "restores" them:
+ *   - the five civic verticals (lost_found, suggestions_complaints,
+ *     donate_item, crowdfunding, event). `contentKind` here is post | poll
+ *     only, and comments and reactions key off that narrower union.
+ *   - official communities, designations, identity verification badges.
+ *   - social score, and the whole area-proximity ranking vocabulary
+ *     (local / district / state / national / global).
+ *   - `areaLineage` as a REQUIRED authorship snapshot. Jansathi gates its
+ *     composer on a declared residence resolving to Indian district level or
+ *     deeper; the user ruled location is never mandatory here, so nothing in
+ *     this file requires one.
+ *   - anonymous posting, which in Jansathi is gated on identity verification
+ *     we do not have. A founders' network is an identified network.
+ *
+ * @module founder-schema/feed
+ */
+import { z } from 'zod';
+import { httpUrlSchema, objectIdSchema, paginationQuerySchema, usernameSchema } from './common.js';
+import { topicSchema } from './onboarding.js';
+// ─── Limits ──────────────────────────────────────────────────────────────────
+/**
+ * Exported because the composer must count down to the SAME number the server
+ * rejects at. A client-side limit that disagrees with the server is a message
+ * a member cannot send and cannot see why.
+ */
+export const POST_MAX_BODY_CHARS = 5000;
+/**
+ * Total attachments on one post, images and videos together.
+ *
+ * ONE cap over ONE ordered list, rather than Jansathi's separate image and
+ * video arrays. A member who posts a screenshot, then a clip, then another
+ * screenshot means that order, and two parallel arrays cannot express it: the
+ * card would show both images and then the video, which is not what was
+ * written.
+ */
+export const POST_MAX_MEDIA = 10;
+/**
+ * Topics per item.
+ *
+ * Capped low on purpose: a post tagged with everything is about nothing, and
+ * one tagged with ten matches every member, which is how a relevance feature
+ * turns back into a chronological one.
+ */
+export const MAX_TOPICS = 3;
+export const COMMENT_MAX_BODY_CHARS = 2000;
+export const POLL_QUESTION_MAX_CHARS = 280;
+export const POLL_OPTION_MAX_CHARS = 80;
+export const POLL_MIN_OPTIONS = 2;
+export const POLL_MAX_OPTIONS = 6;
+/** 5 minutes. Below this a poll closes before anyone sees it. */
+export const POLL_MIN_DURATION_MS = 5 * 60 * 1000;
+/** 30 days. */
+export const POLL_MAX_DURATION_MS = 30 * 24 * 60 * 60 * 1000;
+// ─── Enums ───────────────────────────────────────────────────────────────────
+/**
+ * What can appear in the feed. Two kinds, not seven.
+ *
+ * Engagement is keyed by `(contentKind, contentId)` so one engagement bar
+ * serves both, and comments hang off the same pair. Adding a kind later is
+ * additive; the union is deliberately narrow now so the client never has to
+ * handle a kind this product does not have.
+ */
+export const CONTENT_KIND_VALUES = ['post', 'poll'];
+export const contentKindSchema = z.enum(CONTENT_KIND_VALUES);
+/**
+ * Reactions. Jansathi's `support` is dropped: it exists for reacting to a
+ * civic complaint or a lost-and-found notice, which this feed does not carry.
+ *
+ * ⚠️ These values are stored per reaction row, so removing one orphans data.
+ * Append only.
+ */
+export const REACTION_TYPE_VALUES = ['like', 'celebrate', 'insightful', 'curious'];
+export const reactionTypeSchema = z.enum(REACTION_TYPE_VALUES);
+/**
+ * Feed ordering.
+ *
+ * `new` is the default here, unlike Jansathi where `hot` leads. A hot ranking
+ * needs volume to be meaningful, and a brand-new network ranking a handful of
+ * posts by a blended score mostly hides the newest thing somebody just wrote.
+ * Revisit when there is enough content for `hot` to mean anything.
+ */
+export const FEED_SORT_VALUES = ['new', 'top'];
+export const feedSortSchema = z.enum(FEED_SORT_VALUES);
+/**
+ * Counts keyed by reaction type, e.g. `{ like: 4, celebrate: 1 }`. Only the
+ * reactions an item actually has need appear.
+ *
+ * ⚠️ `partialRecord`, NOT `record`. In Zod 4 an enum-keyed `z.record` is
+ * EXHAUSTIVE: it demands every key, so `{ like: 4 }` fails with three missing
+ * keys and `{}` fails with four. That would force the server to ship a zero for
+ * every reaction on every item, and the day a fifth reaction is added every
+ * previously stored payload and every older client stops parsing.
+ * `partialRecord` keeps the key validation without the exhaustiveness, so an
+ * unknown key like Jansathi's `support` is still refused.
+ */
+export const reactionCountsSchema = z.partialRecord(reactionTypeSchema, z.number().int().nonnegative());
+// ─── Author byline ───────────────────────────────────────────────────────────
+/**
+ * The author as a card renders them.
+ *
+ * Every field here is LIVE, joined against the profile at read time rather
+ * than frozen onto the post at write time. So a renamed handle, a new avatar
+ * or an edited headline updates on old posts, and the byline link always
+ * targets the current username instead of 404ing on a handle that moved.
+ *
+ * Jansathi additionally snapshots `localName` ("where the author was when
+ * posting"). Not ported: location is optional here, so a byline that depends
+ * on one would be blank for anyone who never set it.
+ */
+export const feedAuthorSchema = z.object({
+    userId: z.string(),
+    username: usernameSchema,
+    displayName: z.string(),
+    /** Server-generated or from the login provider, never member-typed, so a
+     *  plain URL check. Same reasoning as `avatarUrl` on the profile. */
+    avatarUrl: z.url().optional(),
+    /** The author's one-line headline, live-joined. Gives a founders' byline
+     *  the context a civic byline got from an area label. */
+    headline: z.string().optional(),
+});
+// ─── Media ───────────────────────────────────────────────────────────────────
+/**
+ * `width` and `height` are required so a card can reserve the right box before
+ * the image loads. Without them every image arrival shifts the feed under the
+ * reader's thumb.
+ *
+ * URLs here come from our own upload pipeline, so they take a plain `z.url()`
+ * rather than `httpUrlSchema`. ⚠️ If a "paste an image link" path is ever
+ * added, these become member-supplied and must move to `httpUrlSchema`.
+ */
+export const feedImageSchema = z.object({
+    kind: z.literal('image'),
+    url: z.url(),
+    thumbnailUrl: z.url().optional(),
+    width: z.number().int().positive(),
+    height: z.number().int().positive(),
+    /** Author-supplied alt text. Optional, and worth asking for. */
+    alt: z.string().max(280).optional(),
+});
+export const feedVideoSchema = z.object({
+    kind: z.literal('video'),
+    url: z.url(),
+    /** Poster frame, server-extracted. Required: a video with no poster is a
+     *  black rectangle in the feed. */
+    thumbnailUrl: z.url(),
+    width: z.number().int().positive(),
+    height: z.number().int().positive(),
+    /** Seconds. */
+    duration: z.number().positive(),
+});
+/**
+ * One ordered list, discriminated on `kind`, so the carousel renders
+ * attachments in the order they were attached and can switch on the kind
+ * without inspecting fields.
+ */
+export const feedMediaSchema = z.discriminatedUnion('kind', [feedImageSchema, feedVideoSchema]);
+// ─── Link preview ────────────────────────────────────────────────────────────
+/**
+ * Preview for the first link in a post body. Server-derived at write time and
+ * stored, never re-fetched at render: a card that fetches a third-party page
+ * per scroll leaks every reader's address to that site and blocks the feed on
+ * somebody else's latency.
+ *
+ * `url` takes `httpUrlSchema` because it came out of text a member typed.
+ * `imageUrl` is whatever the remote page advertised, so it is not ours either,
+ * and a consumer still treats it as untrusted at render.
+ */
+export const linkPreviewSchema = z.object({
+    url: httpUrlSchema,
+    title: z.string().max(200).optional(),
+    description: z.string().max(500).optional(),
+    imageUrl: httpUrlSchema.optional(),
+});
+// ─── Viewer state ────────────────────────────────────────────────────────────
+/**
+ * What THIS viewer has done to this item, computed per request.
+ *
+ * Optional as a block, because an unauthenticated or server-rendered read has
+ * no viewer. ⚠️ A client must treat an absent `viewer` as "no state known",
+ * never as "has not reacted": rendering an empty reaction button off a missing
+ * block is how a member sees their own reaction disappear on reload.
+ */
+export const viewerStateSchema = z.object({
+    reaction: reactionTypeSchema.nullable(),
+    bookmarked: z.boolean(),
+    isAuthor: z.boolean(),
+    /**
+     * What this viewer may DO, decided by the server and sent as plain answers.
+     *
+     * Not role data for the client to reason about. The moment a client derives
+     * "can I edit this" from roles and ownership, that derivation is a second
+     * implementation of the rule, it drifts from the server's, and the drift is
+     * invisible until the two disagree: either a button that 403s or a button
+     * that should not have been there. `isAuthor` stays because the byline reads
+     * differently for your own post, not because the client should compute rights
+     * from it.
+     *
+     * `canEdit` is false once the edit window closes, so it is not simply
+     * `isAuthor`.
+     */
+    canEdit: z.boolean(),
+    canDelete: z.boolean(),
+    canReport: z.boolean(),
+});
+// ─── Post ────────────────────────────────────────────────────────────────────
+/**
+ * A post as the feed and the single-post page receive it.
+ *
+ * Counts are denormalised onto the row so one document serves a whole card.
+ *
+ * No `score` and no up/down vote. Jansathi's signed score exists to rank civic
+ * content by community judgement, and a downvote arrow on a founder's first
+ * post is a different product. Reactions and comments are the engagement axes
+ * here. Adding a score later is additive; removing a visible downvote after
+ * members have used it is not.
+ */
+export const feedPostSchema = z.object({
+    id: objectIdSchema,
+    contentKind: z.literal('post'),
+    author: feedAuthorSchema,
+    /**
+     * The WHOLE body, never a server-side truncation.
+     *
+     * So there is no "was this shortened" flag and no second fetch to read the
+     * rest: the card clamps visually and expands in place. At a 5,000 character
+     * cap a page of twenty posts is small enough that trimming would cost a round
+     * trip to save nothing. If that ever stops being true, a truncation flag is
+     * an additive change; a client that has been guessing is not.
+     */
+    text: z.string().max(POST_MAX_BODY_CHARS),
+    /** Ordered as the author attached them. */
+    media: z.array(feedMediaSchema).max(POST_MAX_MEDIA),
+    /** Present only when the body had an embeddable link. */
+    linkPreview: linkPreviewSchema.optional(),
+    /**
+     * What this post is ABOUT, from the same vocabulary a member picks as their
+     * interests. This is the whole mechanism behind a relevant feed: matching is
+     * an intersection of two lists drawn from one enum, not a guess from who
+     * wrote it.
+     *
+     * ⚠️ An EMPTY array is allowed and means the post is untagged, so interest
+     * matching cannot reach it. That is a real consequence, not a nuance: an
+     * untagged post is only ever found chronologically.
+     */
+    topics: z.array(topicSchema).max(MAX_TOPICS),
+    commentCount: z.number().int().nonnegative(),
+    reactionCounts: reactionCountsSchema,
+    createdAt: z.iso.datetime(),
+    /** Null when never edited. The edit window is the server's to enforce. */
+    editedAt: z.iso.datetime().nullable(),
+    viewer: viewerStateSchema.optional(),
+});
+// ─── Poll ────────────────────────────────────────────────────────────────────
+/**
+ * One choice. `index` is the identifier a vote refers to, not the label:
+ * sending indices avoids ambiguity between two options whose labels differ
+ * only by case, spacing or an invisible character.
+ */
+export const pollOptionSchema = z.object({
+    index: z
+        .number()
+        .int()
+        .min(0)
+        .max(POLL_MAX_OPTIONS - 1),
+    label: z.string().min(1).max(POLL_OPTION_MAX_CHARS),
+    voteCount: z.number().int().nonnegative(),
+});
+/**
+ * A poll. Its own kind, not a post with extra fields, because votes are their
+ * own records keyed by (poll, voter) and a post has nothing equivalent.
+ *
+ * Polls are not editable. Changing a question or an option after a vote has
+ * been cast silently re-purposes that vote. Closing early is allowed; editing
+ * is not.
+ */
+export const feedPollSchema = z.object({
+    id: objectIdSchema,
+    contentKind: z.literal('poll'),
+    author: feedAuthorSchema,
+    question: z.string().min(1).max(POLL_QUESTION_MAX_CHARS),
+    options: z.array(pollOptionSchema).min(POLL_MIN_OPTIONS).max(POLL_MAX_OPTIONS),
+    /** Unique voters, not votes: with multi-select the two differ. */
+    totalVoters: z.number().int().nonnegative(),
+    allowsMultipleChoices: z.boolean(),
+    closesAt: z.iso.datetime(),
+    /**
+     * Whether the poll is closed, decided by the SERVER's clock.
+     *
+     * Derivable from `closesAt`, and deliberately sent anyway: a device with a
+     * wrong clock would otherwise show a live poll as finished, or offer a vote
+     * the server then rejects, and the member sees a control that lies. `closesAt`
+     * stays for rendering "closes in 2 days"; this is what gates the control.
+     */
+    isClosed: z.boolean(),
+    /** As on a post. A poll is feed content and is matched the same way. */
+    topics: z.array(topicSchema).max(MAX_TOPICS),
+    commentCount: z.number().int().nonnegative(),
+    reactionCounts: reactionCountsSchema,
+    createdAt: z.iso.datetime(),
+    /** Always null. Kept so one byline component renders both kinds. */
+    editedAt: z.iso.datetime().nullable(),
+    viewer: viewerStateSchema
+        .extend({
+        /** Indices this viewer chose. Empty means not voted yet, and it is
+         *  always populated for the viewer: a voter can always see their own
+         *  answer even where others' results are hidden. */
+        votedOptionIndices: z.array(z.number().int().nonnegative()),
+    })
+        .optional(),
+});
+// ─── The feed item union ─────────────────────────────────────────────────────
+/**
+ * Discriminated on `contentKind`, so a client narrows with a switch and the
+ * compiler catches an unhandled kind the day one is added. A plain union would
+ * need every field checked by hand and would silently accept a hybrid.
+ */
+export const feedItemSchema = z.discriminatedUnion('contentKind', [feedPostSchema, feedPollSchema]);
+// ─── Comments ────────────────────────────────────────────────────────────────
+/**
+ * A comment, one level of nesting only: a reply to a comment is allowed, a
+ * reply to a reply is not. Two levels stay readable on a phone; three do not,
+ * and the server is what enforces it.
+ */
+export const feedCommentSchema = z.object({
+    id: objectIdSchema,
+    contentKind: contentKindSchema,
+    contentId: objectIdSchema,
+    /** Null for a top-level comment. A non-null value may only name a top-level
+     *  comment, never a reply. */
+    parentCommentId: objectIdSchema.nullable(),
+    author: feedAuthorSchema,
+    text: z.string().max(COMMENT_MAX_BODY_CHARS),
+    /** Meaningful only on a top-level comment; always 0 on a reply. */
+    replyCount: z.number().int().nonnegative(),
+    reactionCounts: reactionCountsSchema,
+    createdAt: z.iso.datetime(),
+    editedAt: z.iso.datetime().nullable(),
+    /** No `bookmarked`: the post is the right thing to save, not a comment. */
+    viewer: viewerStateSchema.omit({ bookmarked: true }).optional(),
+});
+// ─── Queries ─────────────────────────────────────────────────────────────────
+/**
+ * The feed query. Inherits `limit` and `cursor`, which already tolerate an
+ * emptied control rather than answering 400.
+ *
+ * `authorId` powers "posts by this founder" on a profile page, so the profile
+ * feed and the main feed are the same endpoint and cannot drift apart.
+ */
+export const feedQuerySchema = paginationQuerySchema.extend({
+    sort: feedSortSchema.default('new'),
+    authorId: objectIdSchema.optional(),
+});
+export const commentsQuerySchema = paginationQuerySchema.extend({
+    /** Omitted lists top-level comments; set, it lists that comment's replies. */
+    parentCommentId: objectIdSchema.optional(),
+});
+// ─── Write bodies ────────────────────────────────────────────────────────────
+/**
+ * ⚠️ Every write body below is its own object with NO defaults, and none of
+ * them is built with `.pick().partial()`. `.partial()` does not switch off
+ * `.default()`, so a patch body built that way rewrites defaulted fields on
+ * every request. See `updateFounderProfileBodySchema` for the incident.
+ */
+/**
+ * An attachment on the way IN: a reference to something already uploaded, and
+ * deliberately not a URL.
+ *
+ * Upload happens first, straight to storage, and the composer sends back the
+ * key it was given. The server resolves that key to the URL, dimensions and
+ * poster frame it already knows, and those become the read shape.
+ *
+ * ⚠️ The first draft of this took the full read shape, URL included. That is
+ * the same hole that was closed on the profile: a URL in a write body is a
+ * member-supplied URL, so a post could have carried `javascript:` in an image
+ * source, and nothing downstream re-checks a value the server itself stored.
+ * Taking a key instead removes the question rather than validating it, and it
+ * also stops a member pointing a post at somebody else's file.
+ *
+ * `width`, `height` and `duration` are NOT accepted here either. They are
+ * properties of the uploaded object, so the server reads them from the object;
+ * taking them from the client would let a caller claim a 1x1 image and collapse
+ * the card.
+ *
+ * FORMAT, set by the backend (hary, 2026-09-21), minted server-side and never
+ * by a client:
+ *
+ *     media/<userId>/<uuid>.<ext>
+ *
+ * ⚠️ THIS SCHEMA IS THE FIRST OF THREE CHECKS AND THE WEAKEST. It proves the
+ * key is well FORMED. It cannot prove the two things that actually matter, and
+ * nobody should read a green parse as though it had:
+ *
+ *   1. OWNERSHIP. The `userId` segment is what makes "is this your object"
+ *      checkable, and the backend compares it against the authenticated caller.
+ *      A pattern happily accepts a perfectly well-formed key belonging to
+ *      somebody else, which is the exact attack taking a key was meant to stop.
+ *   2. EXISTENCE. The backend calls HeadObject before writing the post, so a
+ *      key for an object nobody uploaded cannot be committed.
+ *
+ * The length ceiling and the traversal refusal below are redundant against this
+ * pattern, which is anchored and admits no dots outside the extension. They are
+ * kept on purpose: they are what still holds if this pattern is ever loosened.
+ */
+export const UPLOAD_KEY_MAX_CHARS = 300;
+/**
+ * ⚠️ IMAGES ONLY, and that is now a product decision rather than an oversight.
+ *
+ * The asymmetry was real and was raised: `feedVideoSchema` is in the read union
+ * and a card can render a video, while nothing could ever upload one. The user
+ * settled it on 2026-09-21: members upload images, and share video by putting a
+ * link in the post text, which the client renders inline. So the minter stays
+ * images-only by intent.
+ *
+ * `feedVideoSchema` is deliberately KEPT. Widening the write path later is
+ * additive; removing video from the read union once a client handles it is not.
+ * A test named for refusing a video key holds this visible, so whoever adds
+ * video uploads has to delete a test that says out loud why it exists.
+ */
+export const UPLOAD_KEY_EXTENSIONS = ['jpg', 'jpeg', 'png', 'webp', 'gif'];
+export const uploadKeySchema = z
+    .string()
+    .trim()
+    .min(1)
+    .max(UPLOAD_KEY_MAX_CHARS)
+    .regex(/^media\/[0-9a-f]{24}\/[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}\.(jpg|jpeg|png|webp|gif)$/, 'Invalid upload reference')
+    .refine((k) => !k.includes('..'), { message: 'Invalid upload reference' });
+export const attachedMediaSchema = z.object({
+    uploadKey: uploadKeySchema,
+    /** Author-supplied alt text, the one media field a member does write. */
+    alt: z.string().trim().max(280).optional(),
+});
+/**
+ * A post must carry something. Text alone, media alone, or both; empty is
+ * refused here rather than reaching the feed as a blank card.
+ */
+export const createPostBodySchema = z
+    .object({
+    text: z.string().trim().max(POST_MAX_BODY_CHARS).optional(),
+    /** Already uploaded. See `attachedMediaSchema`. Order is preserved. */
+    media: z.array(attachedMediaSchema).max(POST_MAX_MEDIA).optional(),
+    /** Absent means untagged, which means interest matching cannot find it. */
+    topics: z.array(topicSchema).max(MAX_TOPICS).optional(),
+})
+    .refine((b) => Boolean(b.text?.length) || Boolean(b.media?.length), {
+    message: 'Write something or add a photo',
+    path: ['text'],
+});
+/** Only the text is editable. Changing media after the fact makes every
+ *  earlier reply look like a reply to something else. */
+export const updatePostBodySchema = z.object({
+    text: z.string().trim().min(1).max(POST_MAX_BODY_CHARS),
+});
+export const createPollBodySchema = z
+    .object({
+    question: z.string().trim().min(1).max(POLL_QUESTION_MAX_CHARS),
+    options: z
+        .array(z.object({ label: z.string().trim().min(1).max(POLL_OPTION_MAX_CHARS) }))
+        .min(POLL_MIN_OPTIONS)
+        .max(POLL_MAX_OPTIONS),
+    /**
+     * Duration from now, NOT an absolute closing time. A client whose clock is
+     * wrong would otherwise open a poll that is already closed, and the member
+     * would have no way to tell why.
+     */
+    durationMs: z.number().int().min(POLL_MIN_DURATION_MS).max(POLL_MAX_DURATION_MS),
+    allowsMultipleChoices: z.boolean(),
+    topics: z.array(topicSchema).max(MAX_TOPICS).optional(),
+})
+    .refine((b) => {
+    const seen = new Set();
+    for (const o of b.options) {
+        const key = o.label.trim().toLowerCase();
+        if (seen.has(key))
+            return false;
+        seen.add(key);
+    }
+    return true;
+}, { message: 'Poll options must be different from each other', path: ['options'] });
+/** Cast or change a vote. The server upserts on (poll, voter), so voting
+ *  twice replaces rather than doubles. */
+export const castVoteBodySchema = z.object({
+    optionIndices: z
+        .array(z
+        .number()
+        .int()
+        .min(0)
+        .max(POLL_MAX_OPTIONS - 1))
+        .min(1)
+        .max(POLL_MAX_OPTIONS),
+});
+export const createCommentBodySchema = z.object({
+    text: z.string().trim().min(1).max(COMMENT_MAX_BODY_CHARS),
+    /** Null for a top-level comment. */
+    parentCommentId: objectIdSchema.nullable(),
+});
+export const updateCommentBodySchema = z.object({
+    text: z.string().trim().min(1).max(COMMENT_MAX_BODY_CHARS),
+});
+/** Set or clear a reaction. `null` clears it; at most one per viewer per item. */
+export const setReactionBodySchema = z.object({
+    reaction: reactionTypeSchema.nullable(),
+});
+// ─── Engagement responses ────────────────────────────────────────────────────
+/**
+ * Returned by the reaction endpoint so the card can render the authoritative
+ * result without a follow-up read. Without the fresh counts a client has to
+ * guess the new total, and two quick taps leave it showing a number the server
+ * never had.
+ */
+export const setReactionResponseSchema = z.object({
+    contentKind: contentKindSchema,
+    contentId: objectIdSchema,
+    reaction: reactionTypeSchema.nullable(),
+    reactionCounts: reactionCountsSchema,
+});
+// ─── Reporting ───────────────────────────────────────────────────────────────
+/**
+ * Why a member reported something.
+ *
+ * ⚠️ Stored on every report row, so this is data, not a label: removing a value
+ * orphans reports already filed under it, and the counts nobody can recover are
+ * exactly the ones a moderation review needs. Append only.
+ *
+ * ⚠️ A REASON THAT IS MISSING DOES NOT DISAPPEAR, it lands in `other`. Whatever
+ * is not named here becomes an undifferentiated pile that no aggregate can see
+ * a pattern in, which is the one thing report categories exist for. Worth being
+ * deliberate about the absences rather than discovering them later.
+ */
+export const REPORT_REASON_VALUES = [
+    'spam',
+    'harassment',
+    'misinformation',
+    'off_topic',
+    'impersonation',
+    'other',
+];
+export const reportReasonSchema = z.enum(REPORT_REASON_VALUES);
+/**
+ * What a member sends to report a post, poll or comment.
+ *
+ * The target is the URL's, not the body's: a report is filed against a specific
+ * thing at a specific address, and taking the target from the body would let a
+ * caller report one item while the route thinks it is another.
+ *
+ * `note` is free text and optional, which is the pressure valve for everything
+ * the enum does not name. ⚠️ It is written by a member, so it is untrusted at
+ * render: a moderation queue displays it, and a moderation queue is a screen
+ * staff read quickly.
+ */
+export const createReportBodySchema = z.object({
+    reason: reportReasonSchema,
+    note: z.string().trim().max(1000).optional(),
+});
+/**
+ * The answer to filing one.
+ *
+ * `alreadyReported` distinguishes "we have taken this" from "you already told
+ * us", because one report per member per target means a second press is a
+ * no-op, and a silent no-op reads as a failure to somebody who pressed twice
+ * deliberately. It is NOT a count: how many OTHER people reported an item is
+ * moderation's business and telling a reporter would turn the count into a
+ * score anyone could farm.
+ */
+export const createReportResponseSchema = z.object({
+    contentKind: contentKindSchema,
+    contentId: objectIdSchema,
+    alreadyReported: z.boolean(),
+});
+/** The bookmark endpoint is a toggle and returns the state it settled on. */
+export const toggleBookmarkResponseSchema = z.object({
+    contentKind: contentKindSchema,
+    contentId: objectIdSchema,
+    bookmarked: z.boolean(),
+});
+/** A vote returns the whole poll: counts, totals and the viewer's own choices
+ *  all move together, and reassembling them client-side drifts. */
+export const castVoteResponseSchema = z.object({
+    poll: feedPollSchema,
+});
+//# sourceMappingURL=feed.js.map