@amityco/social-plus-vise 1.2.0 → 1.4.0

package/dist/intake.js

@@ -0,0 +1,117 @@
+import { hasAnswer } from "./outcomes.js";
+import { availableOptionalCapabilityIds, optionalCapabilityChecklist, } from "./capabilities.js";
+import { DESIGN_CONTRACT_CONFIRMATION_ANSWER_ID } from "./tools/design.js";
+export const CLARITY_GATES = [
+    {
+        id: DESIGN_CONTRACT_CONFIRMATION_ANSWER_ID,
+        axis: "design",
+        blocking: true,
+        sufficient: (c) => c.designReview?.status !== "needs-confirmation" ||
+            hasAnswer(c.ctx.answers, DESIGN_CONTRACT_CONFIRMATION_ANSWER_ID),
+        question: (c) => ({
+            id: DESIGN_CONTRACT_CONFIRMATION_ANSWER_ID,
+            question: `Open ${c.designReview?.previewPath} and confirm whether this design preview/contract should be used for the social UI.`,
+            why: "A design contract must be explicitly accepted before Vise can feed it forward or let the agent claim design conformance. If it is wrong, reject it and provide the correct design source.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+            options: ["yes", "no"],
+        }),
+    },
+    {
+        id: "design_source",
+        axis: "design",
+        blocking: true,
+        sufficient: (c) => c.designReview?.status !== "rejected" || hasAnswer(c.ctx.answers, "design_source"),
+        question: () => ({
+            id: "design_source",
+            question: "What design source should replace the rejected preview/contract?",
+            why: "The current design preview was rejected, so Vise must not use it. Provide a prototype, screenshot, theme/token file, or explicitly say to proceed without a design-conformance claim.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+        }),
+    },
+    {
+        id: "design_source",
+        axis: "design",
+        blocking: true,
+        sufficient: (c) => !(c.ctx.mentionsDesign && c.ctx.designSignals.length === 0) || hasAnswer(c.ctx.answers, "design_source"),
+        question: () => ({
+            id: "design_source",
+            question: "Where are the app's design tokens, theme, or reusable UI components defined?",
+            why: "The user asked to match the existing design, and no local design source was detected.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+        }),
+    },
+    {
+        id: "confirm_design_source",
+        axis: "design",
+        blocking: false,
+        sufficient: (c) => !(c.ctx.mentionsDesign && c.ctx.designSignals.length > 0) || hasAnswer(c.ctx.answers, "confirm_design_source"),
+        question: (c) => ({
+            id: "confirm_design_source",
+            question: `Should the social UI use the detected design source(s): ${c.ctx.designSignals.map((signal) => signal.file).join(", ")}?`,
+            why: "Vise found likely design evidence, but the user or host agent should confirm it is the right source before UI edits.",
+            required: true,
+            blocksImplementationWhenMissing: false,
+            options: ["yes", "use another source"],
+        }),
+    },
+    {
+        id: "primary_action_token",
+        axis: "design",
+        blocking: false,
+        sufficient: (c) => !(c.designBrief &&
+            c.designReview?.status === "accepted" &&
+            (c.outcome === "add-feed" || c.outcome === "add-chat") &&
+            !c.designBrief.roles.some((role) => role.role === "primaryAction") &&
+            !hasAnswer(c.ctx.answers, "primary_action_token")),
+        question: () => ({
+            id: "primary_action_token",
+            question: "Which design token (or color value) should be used as the primary action color? No primary-action token was confidently identified in the design contract.",
+            why: "A primary action colour is needed for interactive elements (composer button, own-message bubble). Without a confident token, the agent must guess or omit it.",
+            required: false,
+            blocksImplementationWhenMissing: false,
+        }),
+    },
+    {
+        id: "feed_optional_capabilities",
+        axis: "feature",
+        blocking: false,
+        sufficient: (c) => !(c.outcome === "add-feed" && c.optionalChoices.length > 0 && !hasAnswer(c.ctx.answers, "feed_optional_capabilities")),
+        question: (c) => ({
+            id: "feed_optional_capabilities",
+            question: `Which optional feed capabilities should be in scope on ${c.ctx.platform}: ${c.optionalChoices.map((capability) => capability.id).join(", ")}, or none?`,
+            why: "These capabilities are useful for full feeds, but should become enforceable only after the customer explicitly opts in. Vise only lists capabilities that appear available in the platform SDK surface; unsupported capabilities must be treated as out of scope or confirmed from docs.",
+            required: false,
+            blocksImplementationWhenMissing: false,
+            options: ["none", ...c.optionalChoices.map((capability) => capability.id)],
+        }),
+    },
+];
+export function assembleIntake(args) {
+    const availableOptionalIds = availableOptionalCapabilityIds(args.capabilityAvailability);
+    const optionalChoices = args.outcome === "add-feed" ? optionalCapabilityChecklist(args.outcome, availableOptionalIds) : [];
+    const clarityCtx = {
+        ctx: args.ctx,
+        outcome: args.outcome,
+        designBrief: args.designBrief,
+        designReview: args.designReview,
+        optionalChoices,
+    };
+    const questions = [...args.outcomeQuestions];
+    for (const gate of CLARITY_GATES) {
+        if (args.suppressGateIds?.includes(gate.id)) {
+            continue;
+        }
+        if (!gate.sufficient(clarityCtx)) {
+            questions.push(gate.question(clarityCtx));
+        }
+    }
+    const remainingBlocking = questions.filter((question) => question.blocksImplementationWhenMissing).length;
+    return {
+        questions,
+        remainingBlocking,
+        status: remainingBlocking > 0 ? "needs-clarification" : "ready",
+    };
+}

package/dist/intelligence/placement.js

@@ -3,13 +3,14 @@ import path from "node:path";
 import { fileURLToPath } from "node:url";
 export const SURFACE_REGISTRY = [
     { id: "feed", outcome: "add-feed", label: "Feed and content surface" },
+    { id: "livestream", outcome: "setup-live-data", label: "Live rooms and broadcast" },
     { id: "comments", outcome: "add-comments", label: "Comments and replies" },
     { id: "chat", outcome: "add-chat", label: "Chat inbox and threads" },
     { id: "profile", outcome: "add-follow", label: "Profile and relationship graph" },
     { id: "community", outcome: "add-community", label: "Community management and identity" },
     { id: "notifications", outcome: "add-notifications", label: "Notifications and activation" },
 ];
-const SURFACE_SCAN_ORDER = ["feed", "comments", "chat", "community", "profile", "notifications"];
+const SURFACE_SCAN_ORDER = ["feed", "livestream", "comments", "chat", "community", "profile", "notifications"];
 const outcomeBySurface = new Map(SURFACE_REGISTRY.map((s) => [s.id, s.outcome]));
 const VALID_SURFACES = new Set(SURFACE_REGISTRY.map((s) => s.id));
 function catalogRoot() {

package/dist/outcomes.js

@@ -1,3 +1,4 @@
+import { experienceBundleFor } from "./experience.js";
 export function hasAnswer(answers, id) {
     const value = answers[id];
     return typeof value === "string" && value.trim() !== "";
@@ -28,12 +29,54 @@ const LIVE_PATTERNS = [
     EVENT_REGEX,
     LIVESTREAM_REGEX,
 ];
+export const PLATFORM_FEATURE_GAPS = [
+    {
+        feature: "Scheduled events & RSVP",
+        match: EVENT_REGEX,
+        exclude: /\bevents?\s+(?:listener|listeners|handler|handlers|subscription|subscriptions|emitter|emitters|bus|stream|streams|callback|callbacks)\b|\b(?:real-?time|analytics|tracking|telemetry)\s+events?\b/i,
+        unavailableOn: ["flutter"],
+        availableOn: ["typescript", "ios", "android"],
+        objectIds: ["event", "rsvp"],
+        sdkSource: "social-plus-sdk/social/events/overview",
+        guidance: "The social.plus Flutter SDK does not expose scheduled-event creation, query, management, or RSVP APIs — events are available on the iOS, Android, and TypeScript SDKs. Do not invent an AmityEventRepository / event query in Dart. Choose an alternative: (a) model events as posts in a dedicated community and carry date/RSVP details in post metadata, (b) call the server-side Event REST API (api-reference/event) from your backend and surface results through your own endpoint, or (c) build the event surface on a supported platform (iOS, Android, or TypeScript/web).",
+    },
+    {
+        feature: "Room-based livestreaming (broadcast & room management)",
+        match: LIVESTREAM_REGEX,
+        exclude: /\blive\s+chat\b|\bvideo\s+(?:call|calling|conferenc)\w*\b/i,
+        unavailableOn: ["flutter"],
+        availableOn: ["typescript", "ios", "android"],
+        objectIds: ["livestream"],
+        sdkSource: "use-cases/social/livestream/go-live-and-room-management",
+        guidance: "Room-based livestreaming — broadcasting, going live, and room management (RoomRepository.createRoom / getRoom / getRooms / stopRoom) — is NOT in the social.plus Flutter SDK; it is available on the iOS, Android, and TypeScript/web SDKs. The Flutter SDK exposes only the DEPRECATED legacy Stream API (StreamRepository.getStream) for VIEWING existing stream posts — there is no Room API in Dart, so do not invent RoomRepository / createRoom. Options: (a) build the broadcast/host livestream experience on a supported platform (iOS, Android, or TypeScript/web), (b) on Flutter, render an existing legacy stream post read-only via StreamRepository.getStream(streamId) (deprecated — exposes title/status/isLive only), or (c) embed a web livestream view.",
+    },
+];
+export function platformFeatureGapsFor(request, platform) {
+    return PLATFORM_FEATURE_GAPS.filter((gap) => gap.unavailableOn.includes(platform) &&
+        gap.match.test(request) &&
+        !(gap.exclude && gap.exclude.test(request)));
+}
+export function platformFeatureGapsForObjects(objectIds, platform) {
+    const present = new Set(objectIds);
+    const out = [];
+    for (const gap of PLATFORM_FEATURE_GAPS) {
+        if (!gap.unavailableOn.includes(platform) || !gap.objectIds)
+            continue;
+        const objects = gap.objectIds.filter((id) => present.has(id));
+        if (objects.length > 0)
+            out.push({ gap, objects });
+    }
+    return out;
+}
 const FEED_PATTERNS = [
     /\b(social feature|social features|feed|timeline|post list|news feed|create post|create a post|post creation|compose post)\b/,
 ];
 const COMMENT_PATTERNS = [
     /\b(comment|comments|reply|replies|thread|discussion thread|comment composer)\b/,
 ];
+const REACTION_PATTERNS = [
+    /\b(reaction|reactions|react|like|likes|emoji react|upvote)\b/,
+];
 const MODERATION_OUTCOME_PATTERNS = [
     /\b(moderation|report|flag|block user|mute user|hide content|abuse|review queue|admin queue)\b/,
 ];
@@ -42,25 +85,26 @@ const CHAT_PATTERNS = [
 ];
 const COMMUNITY_PATTERNS = [
     /\b(create|creating|build|building|manage|managing|join|joining|leave|leaving|set ?up)\s+(a\s+|the\s+)?communit/,
-    /\bcommunit\w*\s+(member|membership|role|invit|categor|setting|management|directory|discovery)/,
+    /\bcommunit\w*\s+(member|membership|role|invit|categor|setting|management|directory|discovery|profile|page)/,
     /\bcommunity\s+(creation|management|members?|roles?|invitations?|categories|settings|moderation)\b/,
 ];
 const FOLLOW_PATTERNS = [
     /\b(follow|unfollow|follower|followers|following)\b/,
     /\b(social graph|user relationship|follow request|followers? list|following list)\b/,
+    /\b(?:user'?s?|member|account|my|your|their)\s+profile\b|\buser_profile_page\b/,
     /\bblocked\s+users?\b/,
     /\bmanage\s+blocked\b/,
     /\bblock\s*list\b/,
     /\bunblock\b/,
 ];
 const NOTIFICATION_PATTERNS = [
-    /\b(notification tray|notification cent(?:er|re)|in-?app notification)/,
-    /\bnotification (?:setting|preference)/,
+    /\b(notifications?\s+tray|notifications?\s+cent(?:er|re)|in-?app notifications?)/,
+    /\bnotifications?\s+(?:setting|preference)/,
 ];
 const TROUBLESHOOT_PATTERNS = [/\b(error|broken|crash|not working|fail|timeout|401|403)\b/];
 const VALIDATE_PATTERNS = [/\b(validate|check|correct|setup right|initiali[sz])\b/];
 const SETUP_PATTERNS = [/\b(setup|set up|install|integrate|wire|configure|init sdk|sdk setup|session lifecycle)\b|initialise?s?\b/];
-export const BROAD_SOCIAL_REGEX = /\b(nice|social features|social feature|engagement|community experience)\b|\b(?:feed|post|posts|comments?)\b[\s\S]{0,160}\b(?:chat|messaging|profile|followers?|following|social graph)\b|\b(?:chat|messaging|profile|followers?|following|social graph)\b[\s\S]{0,160}\b(?:feed|post|posts|comments?)\b/i;
+export const BROAD_SOCIAL_REGEX = /\b(nice|social features|social feature|engagement|community experience)\b|\b(?:feeds?|post|posts|comments?)\b[\s\S]{0,160}\b(?:chat|messaging|profile|followers?|following|social graph)\b|\b(?:chat|messaging|profile|followers?|following|social graph)\b[\s\S]{0,160}\b(?:feeds?|post|posts|comments?)\b/i;
 export const DESIGN_REGEX = /\bdesign token|design tokens|theme|same design|design system|brand/i;
 export function classifyOutcome(request) {
     const normalized = request.toLowerCase();
@@ -110,10 +154,11 @@ export function classifyOutcome(request) {
 }
 export function resolveOutcome(request, answers = {}) {
     const selectedSurface = outcomeFromFeatureSurface(answers.feature_surface);
-    if (selectedSurface && BROAD_SOCIAL_REGEX.test(request)) {
+    const bareOutcome = classifyOutcome(request);
+    if (selectedSurface && (BROAD_SOCIAL_REGEX.test(request) || experienceBundleFor(request) !== undefined || bareOutcome === "unknown")) {
         return selectedSurface;
     }
-    return classifyOutcome(request);
+    return bareOutcome;
 }
 function outcomeFromFeatureSurface(answer) {
     const normalized = (answer ?? "").toLowerCase();
@@ -212,7 +257,7 @@ export function liveDataPlatformPath(platform) {
 const setupSdk = {
     id: "setup-sdk",
     patterns: SETUP_PATTERNS,
-    interpretation: "Implement setup-sdk.",
+    interpretation: "Set up the social.plus SDK — client creation with the correct region/endpoint, secure session login, and access-token renewal — the foundation every other social.plus feature builds on.",
     docsQuery: (platform) => `${platform} quick start setup`,
     docs: (platform) => [
         platformQuickStart(platform),
@@ -423,8 +468,11 @@ const setupLiveData = {
         "UI handling for loading, empty, error, insertion, deletion, and modification states",
     ],
     implementationRules: () => [
+        "Gate the live query on a REACTIVE session-readiness signal (observe the session/auth state, seeded synchronously from its current value) so the query (re-)runs when the session becomes active AFTER the view mounts. The consuming surface usually mounts before login resolves; a one-shot readiness check at mount (onAppear / useEffect([]) / initState / onViewCreated) that returns early and never re-fires leaves the surface permanently empty even though it compiles and vise check is green. Render the not-ready and error states as retryable, not a dead end.",
         "Do not replace Live Object or Live Collection observation with polling unless the docs or user explicitly require it.",
         "Always clean up observers/subscriptions when the owning component, screen, ViewModel, or controller is destroyed.",
+        "On iOS/SwiftUI, deinit-based cleanup does NOT run while the owner is retained for the app's lifetime (e.g. a @StateObject view-model in a TabView): for such surfaces prefer .onDisappear / viewWillDisappear so the observer is released when the user leaves the surface, not only when the owner deallocates.",
+        "vise's deterministic events/stories live-collection checks verify reactivity + observer cleanup only and pass on the ABSENCE of a violation (not on positive presence) — independently confirm the surface itself is wired: events need getEvents/getRSVPs + RSVP create/update; stories need getActiveStoriesByTarget + a ring/viewer.",
         "Handle loading and error states from the live data API before rendering data as ready.",
         "For collections, use insertion/deletion/modification changes for targeted UI updates instead of assuming a full list replacement.",
     ],
@@ -441,7 +489,11 @@ const setupLiveData = {
             ],
         },
         {
-            step: "Implement the subscription in the owning lifecycle scope and render loading, empty, error, and data states.",
+            step: "Drive the subscription off a reactive session-readiness signal (observe session/auth state, seeded synchronously from the current value) so the query (re-)runs when the session becomes active — the surface usually mounts before login resolves, and a one-shot readiness check at mount that never re-fires leaves it permanently empty.",
+            evidence: ["social-plus-sdk/getting-started/authentication", liveDataPlatformPath(ctx.platform)],
+        },
+        {
+            step: "Implement the subscription in the owning lifecycle scope and render loading, empty, error, and data states (with not-ready and error states rendered as retryable, not a dead end).",
             evidence: ["requiredInputs.lifecycle owner for subscribe/unsubscribe cleanup", "implementationRules.loading-error-states"],
         },
         {
@@ -489,8 +541,8 @@ const addFeed = {
     docsQuery: (platform) => `${platform} social feed posts`,
     docs: (platform) => [
         {
-            path: "social-plus-sdk/social/posts",
-            reason: "Canonical social post/feed concepts and API entrypoint.",
+            path: "social-plus-sdk/social/content-management/posts/creation/text-post",
+            reason: "Canonical post model and creation API entrypoint; pair with the live-objects/collections docs below for feed querying.",
         },
         {
             path: "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/overview",
@@ -520,7 +572,7 @@ const addFeed = {
         questions.push({
             id: "feed_scope",
             question: "What scope should the first feed use?",
-            why: "Feed APIs and query shape depend on whether the content is global, user-specific, or community-specific.",
+            why: "Feed APIs and query shape depend on whether the content is global, user-specific, or community-specific. A general social feed defaults to global (app-wide); choose community only when the request is explicitly community-scoped — and note a community feed additionally requires the user to be a member before they can post.",
             required: true,
             blocksImplementationWhenMissing: true,
             options: ["global", "user", "community"],
@@ -528,10 +580,10 @@ const addFeed = {
         questions.push({
             id: "feed_target",
             question: "What concrete feed target should reads and post creation use?",
-            why: "A coding agent must not invent community IDs, user timeline targets, or global feed assumptions. If this is a community feed, provide the existing communityId or the flow that lets users select/create one.",
+            why: "Prefer the global (app-wide) feed or the current user's feed for a general social feed — both are ID-free, need no membership to post, and are the safe default. The no-invent rule applies to IDs: never invent a communityId, targetId, or feedId. Choose a community target only when the request names a community-scoped surface, and then source it from route/app state, SDK discovery, user selection, or a create flow.",
             required: true,
             blocksImplementationWhenMissing: true,
-            options: ["existing communityId", "current user's feed", "selected user's feed", "app-defined/global feed", "ask user at runtime"],
+            options: ["app-defined/global feed", "current user's feed", "selected user's feed", "community selected from route/discovery/create flow", "ask user at runtime"],
         });
         questions.push({
             id: "target_screen_or_route",
@@ -564,6 +616,14 @@ const addFeed = {
             blocksImplementationWhenMissing: false,
             options: ["all SDK-available creation types", "text only", "text + media", "text + media + poll", "custom subset"],
         });
+        questions.push({
+            id: "auth_secure_mode",
+            question: "Is this integration production-bound (secure-mode auth with a server-issued token) or dev/testing only (unsecure auth, no token)?",
+            why: "Unsecure (development) auth — login without a server-issued auth token — lets any client impersonate any user. Fine for local testing, but production MUST use secure mode (a server-issued auth token + a renewal handler). `vise check` surfaces a security advisory whenever the code uses unsecure auth, regardless of this answer.",
+            required: false,
+            blocksImplementationWhenMissing: false,
+            options: ["production — secure mode (server-issued auth token)", "dev/testing only — unsecure auth (no token)"],
+        });
         return filterAnswered(ctx.answers, questions);
     },
     requiredInputs: () => [
@@ -571,7 +631,7 @@ const addFeed = {
         "lifecycle owner for subscribe/unsubscribe cleanup",
         "feature choice: feed, comments, profile, community, chat, notifications, or another social surface",
         "feed scope: global, user, or community",
-        "concrete feed target for reads and post creation: existing communityId, selected user target, current user target, or app-defined feed target",
+        "concrete feed target for reads and post creation: app-defined/global feed, current user feed, selected user target, or community selected from route/discovery/create flow",
         "target screen or route for the feed UI",
     ],
     implementationRules: () => [
@@ -601,10 +661,17 @@ const addFeed = {
             {
                 step: "Fetch the canonical social/feed docs and use platform-appropriate live collection patterns.",
                 evidence: [
-                    "social-plus-sdk/social/posts",
+                    "social-plus-sdk/social/content-management/posts/creation/text-post",
                     "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/overview",
                 ],
             },
+            {
+                step: "Drive the feed query off a reactive session-readiness signal (observe session/auth state, seeded synchronously) so it (re-)runs when the session becomes active — the feed screen usually mounts before login resolves, and a one-shot readiness check at mount (onAppear / useEffect([]) / initState) that never re-fires leaves the feed permanently empty even though it compiles and vise check is green. Render the not-ready and error states as retryable, not a dead end.",
+                evidence: [
+                    "social-plus-sdk/getting-started/authentication",
+                    "requiredInputs.target screen or route",
+                ],
+            },
             {
                 step: "Wire feed pagination: after the initial page loads, expose a 'Load more' action (button, scroll trigger, or infinite-query) that calls the collection's next-page method (loadMore() / nextPage() / onNextPage()). Check hasMore / hasNextPage before showing the control so it disappears when the list is exhausted. Use only opaque cursor tokens returned by the SDK — never construct numeric page offsets. On React/TypeScript, useAmityElement with an infinite-query hook is the idiomatic pattern; on Flutter, a ScrollController + loadMore callback; on Android, PagingData with a LazyColumn scroll trigger.",
                 evidence: [
@@ -632,12 +699,16 @@ const addFeed = {
             { step: "Reuse the host app's existing visual system for the social surface.", evidence: designEvidence },
             { step: "Implement loading, empty, error, and data states.", evidence: ["implementationRules.file-specific edits"] },
             {
-                step: "In post card renderers, resolve each media type from the parent post OR its childrenPosts — in a feed the parent is usually dataType 'text' and the image/video/poll/clip/room rides on a child post. Handle at minimum: text, image, video, file, poll, clip, room. Do not render placeholder labels like '[Image post]' or '[Poll post]'; read the SDK data/accessors and render the actual content. Do NOT gate media on the parent's dataType alone (e.g. post.dataType === 'poll') — that never matches a text parent and the content silently never renders. When rendering the text body itself (post or comment), apply @mention highlights if metadata carries mention entries ({ type: 'user', index, length, userId }, length excluding the '@'): wrap each [index, index + length + 1] span in a styled element and resolve userId to a display name, rather than printing raw text. Pass mentionees on create so mentioned users are notified.",
-                evidence: ["social-plus-sdk/social/posts", "intake.feed_post_type_scope", "capabilityAvailability.available"],
+                step: "In post card renderers, render the normal post body/description/caption when it is present. Do not make `postId` the primary visible content, and do not invent a required title model: `post.title`, `metadata.title`, or custom-payload title fields are optional product choices, not requirements for a correct social.plus post renderer.",
+                evidence: ["social-plus-sdk/social/content-management/posts/creation/text-post", "capabilityAvailability.available"],
+            },
+            {
+                step: "In post card renderers, resolve each media type from the parent post OR its childrenPosts — in a feed the parent is usually dataType 'text' and the image/video/poll/clip/room rides on a child post. Handle at minimum: text, image, video, file, poll, clip, room. Do not render placeholder labels like '[Image post]' or '[Poll post]'; read the SDK data/accessors and render the actual content. Do NOT gate media on the parent's dataType alone (e.g. post.dataType === 'poll') — that never matches a text parent and the content silently never renders. Read child media from the RESOLVED children accessor (post.childrenPosts, whose entries are Post objects exposing .dataType / getImageInfo() etc.) — or, if you only have the raw `post.children` array, resolve the child-post IDs first (getPost(childId) / getPostByIds). Do NOT cast `post.children` to post objects and read `.dataType` on it: `post.children` holds child-post ID STRINGS, so `.dataType` is undefined there and attachments silently never render — a resolution bug a presence check (the code merely references children) cannot catch. When rendering the text body itself (post or comment), apply @mention highlights if metadata carries mention entries ({ type: 'user', index, length, userId }, length excluding the '@'): wrap each [index, index + length + 1] span in a styled element and resolve userId to a display name, rather than printing raw text. Pass mentionees on create so mentioned users are notified.",
+                evidence: ["social-plus-sdk/social/content-management/posts/creation/text-post", "intake.feed_post_type_scope", "capabilityAvailability.available"],
             },
             {
                 step: "Read SDK objects through their own typed accessors and types (e.g. post.getImageInfo(), the Amity.* types) instead of casting return values to hand-written shapes like (post.data as { text?: string }). A hand-written cast silences the type-checker, so when an SDK upgrade renames a field your build still compiles and the bug only surfaces at runtime — reading through SDK types lets tsc/analyze flag the breakage.",
-                evidence: ["social-plus-sdk/social/posts"],
+                evidence: ["social-plus-sdk/social/content-management/posts/creation/text-post"],
             },
             {
                 step: "For community and user avatars, use the SDK-provided URL (community.avatar?.fileUrl / community.avatarImage?.getUrl / community.getAvatar()?.getUrl) and fall back to an initial only when the field is absent. Do not derive an initial from the display name as the sole identifier.",
@@ -657,6 +728,15 @@ const addFeed = {
                     evidence: ["social-plus-sdk/social/content-management/comments/creation/text-comment"],
                 },
             ] : []),
+            ...(REACTION_PATTERNS.some((p) => p.test(ctx.request.toLowerCase())) ? [
+                {
+                    step: "If post cards display a reaction/like control, wire it end to end via ReactionRepository — not a static icon. Add on tap with addReaction(referenceType: 'post', referenceId: post.postId, reactionName) and remove with removeReaction(...) on un-tap (reaction names are case-sensitive and app-defined, e.g. 'like'). Source the count and the current user's state from the post's own reaction data (post.reactionsCount / post.myReactions) so the UI reflects optimistic toggles, and use ReactionRepository.getReactions({ referenceId, referenceType: 'post' }) only when you need the per-user breakdown. A heart/like button with no add/remove wiring (or a hardcoded count) is incomplete — users expect the count to update when they react.",
+                    evidence: [
+                        "social-plus-sdk/core-concepts/content-handling/reactions.mdx",
+                        "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/overview",
+                    ],
+                },
+            ] : []),
             ...(/notification|bell|tray|inbox/i.test(ctx.request) ? [
                 {
                     step: "If the design includes a notification bell or notification center, implement it with the notificationTray SDK: getNotificationTrayItems (live collection), markItemsSeen on open, and an unread badge sourced from getNotificationTraySeen.",
@@ -671,12 +751,12 @@ const addFeed = {
                 step: "If the post composer supports poll creation, implement the two-step creation chain: (1) create the poll with the platform SDK poll repository — returns a Poll/pollId; (2) link that poll into a post with the platform post builder, for example `PostRepository.createPost({ targetType, targetId, data: { text: '', pollId } })` on TypeScript/React Native or Android's dedicated `createPollPost(targetType, targetId, pollId, text, ...)` API. Rendering poll answers (votePoll/unvotePoll) is the read-side; without both creation steps the poll composer silently does nothing. Offer a dedicated poll-builder UI (question input + dynamic answer list) so users can author polls inline.",
                 evidence: [
                     "social-plus-sdk/social/content-management/posts/creation/poll-post",
-                    "social-plus-sdk/social/posts",
+                    "social-plus-sdk/social/content-management/posts/creation/text-post",
                 ],
             },
             {
                 step: "In post card headers, show the post's target context when post.targetType === 'community': display 'Author.displayName › Community.displayName' by subscribing to CommunityRepository.getCommunity(post.targetId, cb) for the live community name.",
-                evidence: ["social-plus-sdk/social/communities", "social-plus-sdk/social/posts"],
+                evidence: ["social-plus-sdk/social/communities", "social-plus-sdk/social/content-management/posts/creation/text-post"],
             },
             {
                 step: "For room-type posts, subscribe to RoomRepository.getRoom(roomId, cb) to get the Room object and display room.title (not room.roomId). Show room.status (live/idle/ended) as a badge.",
@@ -684,7 +764,7 @@ const addFeed = {
             },
             {
                 step: "Give each post card an actions menu gated by the viewer's relationship to the post. If the viewer is the author (post.postedUserId === currentUserId), show edit (PostRepository.editPost) and delete (PostRepository.deletePost). For posts the viewer does not own, show report/flag (PostRepository.flagPost). Author-ownership actions and moderator-role actions are distinct — do not show edit/delete to non-authors.",
-                evidence: ["social-plus-sdk/social/posts", "social-plus-sdk/social/moderation"],
+                evidence: ["social-plus-sdk/social/content-management/posts/creation/text-post", "social-plus-sdk/social/moderation"],
             },
             { step: "Run validate_setup and detected command sensors after edits.", evidence: ["validate_setup", "run_sensors"] },
         ];
@@ -699,6 +779,7 @@ const addFeed = {
         "posts.status-filtered",
         "pagination.cursor-opaque",
         "unread.server-synced",
+        "feed.post-body-rendering",
         "feed.rich-post-rendering",
         "feed.rich-post-composer-scope",
         "feed.post-type-scope-explicit",
@@ -710,8 +791,8 @@ const addFeed = {
         "profile.social-counts",
     ],
     stopConditions: (ctx) => filterStops(ctx.answers, [
-        { id: "feed_target", text: "The concrete feed target is unknown; do not invent communityId, targetId, feedId, or global feed assumptions." },
-        { id: "feed_target", text: "If post creation is in scope, the write target must be provided by the user, existing app state, or a customer-owned selection/create flow." },
+        { id: "feed_target", text: "The concrete feed target is unknown; never invent a communityId, targetId, or feedId. For a general social feed, default to the ID-free app-wide global feed or the current user's feed; reserve a specific community/target for an explicitly community-scoped request." },
+        { id: "feed_target", text: "If post creation is in scope, the write target must be a concrete feed — the global or current-user feed (no id, no membership needed), or a community/selected target the user or app state provides (never a hardcoded or invented id)." },
     ]),
     resolvePlan: () => [
         {
@@ -891,7 +972,7 @@ const addModeration = {
         const questions = [
             {
                 id: "moderation_target",
-                question: "What content types need moderation (post, comment, message, user)?",
+                question: "What content types need moderation (posts, comments, messages, users, or all)?",
                 why: "Each content type has different moderation APIs and UI patterns.",
                 required: true,
                 blocksImplementationWhenMissing: true,
@@ -922,7 +1003,7 @@ const addModeration = {
         return filterAnswered(ctx.answers, questions);
     },
     requiredInputs: () => [
-        "moderation target types: post, comment, message, user",
+        "moderation target types: posts, comments, messages, users, or all",
         "moderation action set: report, block, mute, hide, admin queue",
         "post-action rendering policy for blocked/hidden content",
     ],
@@ -1008,9 +1089,16 @@ const addChat = {
             {
                 id: "channel_source",
                 question: "How are channels/conversations created or discovered?",
-                why: "Avoids invented channel IDs. Channels come from user selection, SDK query, or app logic.",
+                why: "For a chat inbox/browse surface, prefer the current user's own channels — queryChannels()/getChannels with membership:'member' is ID-free and needs no channelId. Creating a 1:1 DM needs a recipient userId and a group needs member userIds (createChannel); opening a specific existing channel uses its channelId from the inbox query. The no-invent rule applies to IDs: never invent a channelId or member list.",
                 required: true,
                 blocksImplementationWhenMissing: true,
+                options: [
+                    "my inbox (queryChannels()/getChannels, membership:'member')",
+                    "user/app selection of an existing channel",
+                    "create 1:1 DM (needs recipient userId)",
+                    "create group channel (needs member userIds)",
+                    "ask user at runtime",
+                ],
             },
             {
                 id: "message_capabilities",
@@ -1080,8 +1168,12 @@ const addChat = {
                 step: "Implement channel query/creation and message observation with lifecycle cleanup.",
                 evidence: ["social-plus-sdk/chat/channels", "social-plus-sdk/chat/messages"],
             },
+            {
+                step: "Drive the channel-list (and message) query off a reactive session-readiness signal (observe session/auth state, seeded synchronously) so it (re-)runs when the session becomes active — the inbox/thread usually mounts before login resolves, and a one-shot readiness check at mount (onAppear / useEffect([]) / initState) that never re-fires leaves chat permanently empty even though it compiles and vise check is green. Render the not-ready and error states as retryable, not a dead end.",
+                evidence: ["social-plus-sdk/getting-started/authentication", "social-plus-sdk/chat/channels"],
+            },
             { step: "Reuse the host app's existing visual system for chat UI.", evidence: designEvidence },
-            { step: "Add message send with error handling and auth gate. Observe each message's syncState and surface failed sends (error state) with a retry/delete affordance instead of rendering optimistic success unconditionally; clean up unrecoverable failures (e.g. deleteFailedMessages) on init.", evidence: ["implementationRules.file-specific edits"] },
+            { step: "Add message send with error handling and auth gate. Observe each message's syncState and surface failed sends (error state) with a retry/delete affordance instead of rendering optimistic success unconditionally; clean up unrecoverable failures (e.g. deleteFailedMessages) on init. For a community channel, sending may require joining first (joinChannel) — surface a join affordance so a non-member's send does not silently fail.", evidence: ["implementationRules.file-specific edits"] },
             { step: "Render the chat inbox from SDK channel queries/live collections. Show unread counts/badges from the SDK on channel rows or the chat tab (`channel.getUnreadCount()`, `getSubChannelsUnreadCount()`, or `AmityCoreClient.observeUserUnread()` / `getTotalChannelUnread()`), and declare channel-list sorting explicitly (typically last activity descending) so recency cannot be reversed by UI defaults.", evidence: ["social-plus-sdk/chat/channels", "intake.chat_inbox_scope", "capabilityAvailability.available"] },
             { step: "Declare message order explicitly with `AmityMessageQuerySortOption.FIRST_CREATED` or `LAST_CREATED` so the message thread cannot invert by relying on defaults.", evidence: ["social-plus-sdk/chat/messages"] },
             { step: "Wire read receipts and typing indicators if required — and mark the channel/messages read on open (channel.markAsRead() / message.markRead()) so the server-side unread count actually decrements. Reading the unread count without ever marking read leaves the badge stuck. Note: the MarkerSyncEngine receipt-sync API (startMessageReceiptSync/stopMessageReceiptSync) is deprecated and being sun-set — track read state with the unread count + markRead() instead.", evidence: ["requiredInputs.read receipt and typing indicator requirements"] },
@@ -1163,10 +1255,17 @@ const addCommunity = {
             },
             {
                 id: "community_target",
-                question: "Where does the community ID come from (route param, selection, or a create flow)?",
-                why: "The coding agent must not invent a communityId; it needs a concrete source.",
+                question: "Where do the communities come from — a discovery query, a create flow, user selection, or an app route/detail state?",
+                why: "For a browse/join or create surface this is ID-free: discover communities via getCommunities/searchCommunities/getRecommendedCommunities/getTrendingCommunities (a query, no communityId), or create one with createCommunity (the id is server-generated). A concrete inbound community object/id belongs only to a detail/members or membership-management surface of a specific existing community — source it from route/app state, user selection, discovery, or the create-flow return value. The no-invent rule applies to IDs: never invent a communityId.",
                 required: true,
                 blocksImplementationWhenMissing: true,
+                options: [
+                    "discovery query (getCommunities/searchCommunities/getRecommendedCommunities/getTrendingCommunities)",
+                    "createCommunity flow (server-generated id)",
+                    "user selection of an existing community",
+                    "route/app state for an existing community",
+                    "ask user at runtime",
+                ],
             },
             {
                 id: "lifecycle_owner",
@@ -1188,7 +1287,7 @@ const addCommunity = {
     requiredInputs: () => [
         "community surface: create, browse/join, detail+members, or membership management",
         "community privacy model: public (instant) vs private (join request)",
-        "concrete community ID source (route param, selection, or create flow)",
+        "natural community source (route/app state, discovery, user selection, or create flow)",
         "lifecycle owner for community/member observer cleanup",
         "target screen or component",
     ],
@@ -1205,8 +1304,8 @@ const addCommunity = {
             : ["requiredInputs.design token or theme source file"];
         return [
             {
-                step: "Confirm the community surface, privacy model, community ID source, and target screen before writing code.",
-                evidence: ["requiredInputs.community surface", "requiredInputs.community privacy model", "requiredInputs.concrete community ID source"],
+                step: "Confirm the community surface, privacy model, natural community source, and target screen before writing code.",
+                evidence: ["requiredInputs.community surface", "requiredInputs.community privacy model", "requiredInputs.natural community source"],
             },
             {
                 step: "Implement the community/member query with the platform's Live Collection (AmityCommunityRepository / getMembers), with cleanup on the lifecycle owner.",
@@ -1229,13 +1328,11 @@ const addCommunity = {
         "community.avatar-from-sdk",
         "community.display-name-from-sdk",
         "moderation.role-gated-action",
-        "validate_setup",
-        "run_sensors",
     ],
     stopConditions: (ctx) => filterStops(ctx.answers, [
         { id: "community_scope", text: "The community surface is unknown; do not assume create vs browse vs members vs management." },
         { id: "community_privacy", text: "The privacy model is unknown; public (instant) and private (join-request) flows differ and must not be guessed." },
-        { id: "community_target", text: "The community ID source is unknown; do not invent a communityId." },
+        { id: "community_target", text: "The natural community source is unknown; do not invent a communityId." },
         { id: "lifecycle_owner", text: "The lifecycle owner for community/member observer cleanup is unknown." },
     ]),
     resolvePlan: () => [
@@ -1290,10 +1387,17 @@ const addFollow = {
             },
             {
                 id: "follow_target",
-                question: "Where does the target userId come from (route param, profile selection, current user)?",
-                why: "The coding agent must not invent a userId; it needs a concrete source.",
+                question: "Whose social graph is this — the current user's own (follower/following lists, counts), another user's profile, or a follow/unfollow button (always another user)?",
+                why: "Scope this to the surface. For the current user's OWN follower/following lists, counts, and relationship state, the ID-free default is getCurrentUser()/client.userId — pass that own id to getFollowInfo (counts) and getFollowers/getFollowings (lists); the SDK routes those to the ID-free /me endpoint when the id is your own, so no external userId is needed. A follow/unfollow BUTTON always targets ANOTHER user, so a concrete target userId is required there (do not default it to self); viewing another user's profile/lists likewise needs that user's id. The no-invent rule applies to IDs: never invent a userId.",
                 required: true,
                 blocksImplementationWhenMissing: true,
+                options: [
+                    "current user, own graph (getCurrentUser()/client.userId — for own lists/counts)",
+                    "another user's profile (their userId — for viewing their lists/counts)",
+                    "follow/unfollow button target (another user's userId — required, never self)",
+                    "route param userId",
+                    "ask user at runtime",
+                ],
             },
             {
                 id: "lifecycle_owner",
@@ -1359,8 +1463,6 @@ const addFollow = {
         "profile.identity-from-sdk",
         "profile.avatar-from-sdk",
         "profile.social-counts",
-        "validate_setup",
-        "run_sensors",
     ],
     stopConditions: (ctx) => filterStops(ctx.answers, [
         { id: "follow_surface", text: "The social-graph surface is unknown; do not assume follow button vs lists vs blocked users." },
@@ -1455,9 +1557,6 @@ const addNotifications = {
         "notifications.tray-live",
         "notifications.mark-seen",
         "notifications.preferences-respected",
-        "this is in-app tray, not push setup",
-        "validate_setup",
-        "run_sensors",
     ],
     stopConditions: (ctx) => filterStops(ctx.answers, [
         { id: "notification_surface", text: "The notification surface is unknown; do not assume tray vs badge vs settings." },

package/dist/productExpectations.js

@@ -1,11 +1,13 @@
 export const PRODUCT_EXPECTATION_TITLES = {
     "feed.target-resolved": "Feed target comes from app state",
+    "feed.source-used": "Feed source uses SDK post APIs",
     "feed.ui-states-present": "Feed renders loading, empty, and error states",
     "feed.pagination-wired": "Feed pagination is wired",
     "moderation.affordance-present": "UGC moderation affordance is present",
     "posts.status-filtered": "Post queries filter unsafe statuses",
     "pagination.cursor-opaque": "Pagination cursors stay opaque",
     "unread.server-synced": "Unread counts use the server-synced stream",
+    "feed.post-body-rendering": "Feed renders post body content",
     "feed.rich-post-rendering": "Feed renders rich post types",
     "feed.rich-post-composer-scope": "Feed composer surfaces rich post scope",
     "feed.post-type-scope-explicit": "Feed post-type scope is explicit",
@@ -45,6 +47,12 @@ const platformBindings = (expectationId, sensorsByPlatform) => Object.entries(se
     platform,
 })));
 export const PRODUCT_EXPECTATION_BINDINGS = [
+    ...platformBindings("feed.source-used", {
+        typescript: "typescript.feed.source-used",
+        "react-native": "react-native.feed.source-used",
+        flutter: "flutter.feed.source-used",
+        ios: "ios.feed.source-used",
+    }),
     ...platformBindings("feed.target-resolved", {
         typescript: ["typescript.feed.target.literal", "typescript.feed.target-type-explicit"],
         "react-native": ["react-native.feed.target.literal", "react-native.feed.target-type-explicit"],
@@ -114,6 +122,13 @@ export const PRODUCT_EXPECTATION_BINDINGS = [
         flutter: "flutter.unread.subscribed-not-counted",
         ios: "ios.unread.subscribed-not-counted",
     }),
+    ...platformBindings("feed.post-body-rendering", {
+        typescript: "typescript.feed.post-body-rendered",
+        "react-native": "react-native.feed.post-body-rendered",
+        android: "android.feed.post-body-rendered",
+        flutter: "flutter.feed.post-body-rendered",
+        ios: "ios.feed.post-body-rendered",
+    }),
     {
         expectationId: "feed.rich-post-rendering",
         sensorId: "typescript.feed.post-datatype-handled",