@amityco/social-plus-vise 0.14.20 → 0.14.22

package/CHANGELOG.md

@@ -4,6 +4,27 @@ All notable changes to `@amityco/social-plus-vise` are documented in this file.
 
 The format is loosely based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## 0.14.22 — 2026-06-05
+
+### Added
+- **Multi-surface social workplans:** broad social requests now include a `socialWorkplan` sequence that decomposes feed, comments, chat, and profile work into ordered per-surface plans with focused `vise plan` / `vise init` commands.
+
+### Changed
+- **Broad social intake:** when a multi-surface workplan exists, Vise no longer blocks the top-level plan on `feature_surface`; focused per-surface runs still use `--answer feature_surface=<surface>` before implementation.
+
+### Verified
+- Product-flow, CLI, fixture, improvement-discovery, and host-agent smoke coverage now lock the multi-surface workplan path while preserving answered single-surface init behavior.
+
+## 0.14.21 — 2026-06-05
+
+### Changed
+- **Core surface product expectations:** feed, comment tray, chat inbox, and profile plans now surface shared product expectations for post-type scope, composer type scope, live comment lists, comment creation, comment UI states, live channel lists, channel-list sorting, profile identity, and profile avatars.
+- **Plan-time scope questions:** add-feed plans now ask for feed post-type and composer scope; add-comments asks for comment tray scope; add-chat asks for inbox unread/sorting scope; add-follow asks for profile identity scope.
+- **Broad social routing clarity:** `feature_surface` now lists `comments` as a first-class option alongside feed, profile, community, chat, and notifications.
+
+### Verified
+- Targeted product-flow and capability coverage now locks the feed-forward path for the new shared expectations across TypeScript, React Native, Android, Flutter, and iOS SDK surfaces.
+
 ## 0.14.20 — 2026-06-05
 
 ### Changed

package/README.md

@@ -161,14 +161,15 @@ Aggregate: **98/99 expected feed capabilities** and **27/27 selected optional ca
 
 ### Current Release Validation
 
-Version 0.14.20 carries current release proof around the full feed-forward, product-expectation, and validation flow:
+Version 0.14.22 carries current release proof around the full feed-forward, product-expectation, and validation flow:
 
 | Surface | What was validated |
 |---|---|
 | **Product flow** | Local end-to-end smoke covers design extraction, plan feed-forward, blocking intake, answered init, capability check, design conformance, and sensor discovery. |
-| **Plan questions** | Plans surface blocking questions such as `feature_surface` and `design_contract_confirmation`, plus optional choices such as `feed_optional_capabilities`. |
+| **Multi-surface planning** | Broad social requests are decomposed into a `socialWorkplan` sequence for feed, comments, chat, and profile work instead of forcing a single top-level surface choice. Each surface includes focused `vise plan` / `vise init` commands for the host agent to run when implementing that slice. |
+| **Plan questions** | Plans surface blocking questions such as `design_contract_confirmation`, product-scope questions such as `feed_post_type_scope`, `feed_composer_type_scope`, `comment_tray_scope`, `chat_inbox_scope`, and `profile_identity_scope`, plus optional choices such as `feed_optional_capabilities`. Focused plans still accept `feature_surface` answers when the agent is ready to implement one surface. |
 | **Capability-to-sensor flow** | Vise checks platform support, matches the prompt to available capabilities, offers supported features as questions, records answers, and turns selected answers into sensors in `vise check`. |
-| **Shared product expectations** | Public IDs such as `feed.target-resolved`, `comments.thread-read-write`, `chat.channel-target-resolved`, `community.avatar-from-sdk`, `community.display-name-from-sdk`, `moderation.role-gated-action`, `follow.relationship-live`, `profile.social-counts`, and `notifications.tray-live` stay platform-agnostic while check results retain concrete `contractRuleId` and `validator.sensorId` evidence when deterministic sensors exist. |
+| **Shared product expectations** | Public IDs such as `feed.target-resolved`, `feed.post-type-scope-explicit`, `comments.creation-affordance`, `chat.channel-list-order-explicit`, `community.avatar-from-sdk`, `moderation.role-gated-action`, `follow.relationship-live`, `profile.identity-from-sdk`, `profile.social-counts`, and `notifications.tray-live` stay platform-agnostic while check results retain concrete `contractRuleId` and `validator.sensorId` evidence when deterministic sensors exist. |
 | **Rule detection** | TP-track dashboard detects **321/321 seeded rule gaps (100.0%)** in the static corpus. |
 | **Packed-package smoke** | Packed-package and host-agent smokes exercise the release tarball path, surfaced plan questions, selected optional capability sensors, rejected design confirmation handling, and exact contract-rule evidence for shared product expectations. |
 

package/dist/capabilities.js

@@ -569,6 +569,50 @@ export const SHARED_PRODUCT_EXPECTATIONS = [
         deterministicPlatforms: ["android", "flutter", "ios", "typescript"],
         hint: "implement the selected rich composer paths or record an explicit text-only/rich-post scope decision",
     },
+    {
+        id: "feed.post-type-scope-explicit",
+        label: "Feed post-type scope",
+        outcomes: ["add-feed"],
+        kind: "shared-expectation",
+        availability: [
+            {
+                label: "SDK rich post models/accessors",
+                symbols: [
+                    /\b(?:ContentDataImage|ImageData|AmityImagePost\w*|ImagePost\w*)\b/i,
+                    /\b(?:ContentDataVideo|VideoData|AmityVideoPost\w*|VideoPost\w*)\b/i,
+                    /\b(?:ContentDataFile|FileData|AmityFilePost\w*|FilePost\w*)\b/i,
+                    /\b(?:ContentDataPoll|PollData|AmityPollPost\w*|PollPost\w*)\b/i,
+                    /\b(?:ContentDataClip|AmityClipPost\w*|ClipPost\w*)\b/i,
+                    /\b(?:ContentDataRoom|LiveStreamData|AmityRoomPost\w*|RoomPost\w*|LiveStreamPost\w*)\b/i,
+                ],
+            },
+        ],
+        deterministicPlatforms: [],
+        hint: "before building, name the SDK-available post types the feed will render: image, video, file, poll, clip, room/livestream, custom, or an explicit text-only scope",
+    },
+    {
+        id: "feed.composer-type-scope-explicit",
+        label: "Post composer type scope",
+        outcomes: ["add-feed"],
+        kind: "shared-expectation",
+        availability: [
+            {
+                label: "SDK rich post creation",
+                symbols: [
+                    /\bcreateImagePost\b/i,
+                    /\bcreateVideoPost\b/i,
+                    /\bcreateFilePost\b/i,
+                    /\bcreatePollPost\b/i,
+                    /\bcreateClipPost\b/i,
+                    /\bcreateRoomPost\b/i,
+                    /\bcreateMixedAttachmentPost\b/i,
+                    /\bcreatePost\b/i,
+                ],
+            },
+        ],
+        deterministicPlatforms: [],
+        hint: "before building a composer, name which SDK-available creation paths are in scope and which are intentionally excluded",
+    },
     {
         id: "comments.target-resolved",
         label: "Resolved comment target",
@@ -595,6 +639,48 @@ export const SHARED_PRODUCT_EXPECTATIONS = [
         deterministicPlatforms: ["android", "flutter", "ios", "typescript"],
         hint: "if comments are shown, pair the list with a composer and loading/error/empty states unless the surface is explicitly read-only",
     },
+    {
+        id: "comments.list-live",
+        label: "Live comment list",
+        outcomes: ["add-feed", "add-comments"],
+        kind: "shared-expectation",
+        availability: [
+            {
+                label: "SDK comment query/live APIs",
+                symbols: [/\bgetComments\b/i, /\bqueryComments\b/i, /\bCommentRepository\b/i, /\bLiveCollection\b/i, /\bPagingData\b/i],
+            },
+        ],
+        deterministicPlatforms: [],
+        hint: "render a live comment list from the parent entity, not a static empty tray or placeholder",
+    },
+    {
+        id: "comments.creation-affordance",
+        label: "Comment creation affordance",
+        outcomes: ["add-feed", "add-comments"],
+        kind: "shared-expectation",
+        availability: [
+            {
+                label: "SDK comment creation",
+                symbols: [/\bcreateComment\b/i, /\bCommentCreate\b/i, /\bAmityCommentCreateOptions\b/i],
+            },
+        ],
+        deterministicPlatforms: [],
+        hint: "when comments are in scope, include a composer that calls the SDK createComment path, or explicitly record read-only scope",
+    },
+    {
+        id: "comments.ui-states-present",
+        label: "Comment loading/empty/error states",
+        outcomes: ["add-feed", "add-comments"],
+        kind: "shared-expectation",
+        availability: [
+            {
+                label: "SDK comment query/live APIs",
+                symbols: [/\bgetComments\b/i, /\bqueryComments\b/i, /\bCommentRepository\b/i, /\bLiveCollection\b/i, /\bPagingData\b/i],
+            },
+        ],
+        deterministicPlatforms: [],
+        hint: "comment trays should distinguish loading, empty, error, and data states before showing an empty list",
+    },
     {
         id: "chat.channel-target-resolved",
         label: "Resolved chat channel",
@@ -651,6 +737,34 @@ export const SHARED_PRODUCT_EXPECTATIONS = [
         deterministicPlatforms: ["android", "flutter", "ios", "typescript"],
         hint: "match the SDK channel type to the selected chat shape: conversation for direct messages, community/group for shared channels, broadcast where applicable",
     },
+    {
+        id: "chat.channel-list-live",
+        label: "Live chat channel list",
+        outcomes: ["add-chat"],
+        kind: "shared-expectation",
+        availability: [
+            {
+                label: "SDK channel query/live APIs",
+                symbols: [/\bChannelRepository\b/i, /\bgetChannels\b/i, /\bqueryChannels\b/i, /\bAmityChannel\b/i, /\bLiveCollection\b/i, /\bPagingData\b/i],
+            },
+        ],
+        deterministicPlatforms: [],
+        hint: "build the inbox from SDK channel queries or live collections, not static rows or a fixed channel",
+    },
+    {
+        id: "chat.channel-list-order-explicit",
+        label: "Explicit chat channel-list order",
+        outcomes: ["add-chat"],
+        kind: "shared-expectation",
+        availability: [
+            {
+                label: "SDK channel sort/order",
+                symbols: [/\bChannelSort\b/i, /\bAmityChannelSortOption\b/i, /\bsortByLastActivity\b/i, /\bsortBy\b/i, /\blastActivity\b/i, /\bsortingOrder\b/i],
+            },
+        ],
+        deterministicPlatforms: [],
+        hint: "declare inbox/channel-list sorting, usually last activity descending, so the UI cannot reverse recency by default",
+    },
     {
         id: "chat.unread-visible",
         label: "Chat unread counts",
@@ -814,6 +928,34 @@ export const SHARED_PRODUCT_EXPECTATIONS = [
         deterministicPlatforms: [],
         hint: "make automatic follow vs pending approval explicit, including accept/decline states where the SDK exposes them",
     },
+    {
+        id: "profile.identity-from-sdk",
+        label: "Profile identity from SDK",
+        outcomes: ["add-follow"],
+        kind: "shared-expectation",
+        availability: [
+            {
+                label: "SDK user identity APIs",
+                symbols: [/\bUserRepository\b/i, /\bgetUser\b/i, /\bgetUsers\b/i, /\bAmityUser\b/i, /\bdisplayName\b/i, /\buserId\b/i],
+            },
+        ],
+        deterministicPlatforms: [],
+        hint: "source profile name, id, avatar, and relationship state from the SDK user/profile object instead of placeholders",
+    },
+    {
+        id: "profile.avatar-from-sdk",
+        label: "Profile avatar from SDK",
+        outcomes: ["add-follow"],
+        kind: "shared-expectation",
+        availability: [
+            {
+                label: "SDK user avatar fields/accessors",
+                symbols: [/\bavatar\b/i, /\bavatarImage\b/i, /\bavatarUrl\b/i, /\bavatarFileId\b/i, /\bgetAvatar\b/i, /\bfileUrl\b/i, /\bfileURL\b/i],
+            },
+        ],
+        deterministicPlatforms: [],
+        hint: "render the SDK user avatar when present and fall back to initials only when the SDK has no avatar field",
+    },
     {
         id: "profile.social-counts",
         label: "Profile follower/following counts",

package/dist/outcomes.js

@@ -492,7 +492,7 @@ const addFeed = {
                 why: "The request is broad, so the coding agent needs one product surface before it can choose SDK docs, UI states, and target files.",
                 required: true,
                 blocksImplementationWhenMissing: true,
-                options: ["feed", "profile", "community", "chat", "notifications"],
+                options: ["feed", "comments", "profile", "community", "chat", "notifications"],
             });
         }
         questions.push({
@@ -526,12 +526,28 @@ const addFeed = {
             blocksImplementationWhenMissing: false,
             options: ["comments + replies", "reactions", "notifications", "sharing", "feed only (no engagement)"],
         });
+        questions.push({
+            id: "feed_post_type_scope",
+            question: "Which SDK-available post types should the feed render?",
+            why: "A feed that renders only text can look complete in a smoke test while image, video, poll, clip, room, and custom posts are blank. The agent should either render the available post types or record an explicit text-only/product subset decision.",
+            required: false,
+            blocksImplementationWhenMissing: false,
+            options: ["all SDK-available post types", "text only", "text + image + video", "text + image + video + poll", "custom subset"],
+        });
+        questions.push({
+            id: "feed_composer_type_scope",
+            question: "Which SDK-available post creation types should the composer expose?",
+            why: "Post creation often ships as text-only while the feed can render richer content. The agent should align composer scope with the product decision and SDK availability.",
+            required: false,
+            blocksImplementationWhenMissing: false,
+            options: ["all SDK-available creation types", "text only", "text + media", "text + media + poll", "custom subset"],
+        });
         return filterAnswered(ctx.answers, questions);
     },
     requiredInputs: () => [
         "live data shape: single object or collection",
         "lifecycle owner for subscribe/unsubscribe cleanup",
-        "feature choice: feed, profile, community, chat, notifications, or another social surface",
+        "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",
         "target screen or route for the feed UI",
@@ -586,6 +602,7 @@ const addFeed = {
                 evidence: [
                     "capabilityAvailability.available",
                     "optionalCapabilities.choices",
+                    "intake.feed_composer_type_scope",
                     "social-plus-sdk/social/content-management/posts/creation/image-post",
                     "social-plus-sdk/core-concepts/file-handling/upload",
                 ],
@@ -594,7 +611,7 @@ const addFeed = {
             { 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"],
+                evidence: ["social-plus-sdk/social/posts", "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.",
@@ -662,6 +679,11 @@ const addFeed = {
         "unread.server-synced",
         "feed.rich-post-rendering",
         "feed.rich-post-composer-scope",
+        "feed.post-type-scope-explicit",
+        "feed.composer-type-scope-explicit",
+        "comments.list-live",
+        "comments.creation-affordance",
+        "comments.ui-states-present",
         "comments.thread-read-write",
         "profile.social-counts",
     ],
@@ -750,6 +772,14 @@ const addComments = {
                 required: true,
                 blocksImplementationWhenMissing: true,
             },
+            {
+                id: "comment_tray_scope",
+                question: "Should the comment tray include the live list, composer, and loading/error/empty states?",
+                why: "A tray that only opens, only shows placeholders, or only reads comments misses the expected comment workflow. If any part is intentionally omitted, the agent should record that product decision.",
+                required: false,
+                blocksImplementationWhenMissing: false,
+                options: ["list + composer + states", "read-only list", "composer elsewhere", "custom subset"],
+            },
         ];
         return filterAnswered(ctx.answers, questions);
     },
@@ -784,8 +814,8 @@ const addComments = {
                 evidence: [commentDocPath(ctx.platform), liveDataPlatformPath(ctx.platform)],
             },
             { step: "Reuse the host app's existing visual system for the comment UI.", evidence: designEvidence },
-            { step: "Implement loading, empty, error, and data states for comments.", evidence: ["implementationRules.file-specific edits"] },
-            { step: "Add comment creation (composer) with auth gate and error handling.", evidence: ["requiredInputs.concrete parent entity ID"] },
+            { step: "Implement the live comment list plus loading, empty, error, and data states before showing an empty tray.", evidence: ["implementationRules.file-specific edits", "intake.comment_tray_scope"] },
+            { step: "Add comment creation (composer) with auth gate and error handling unless the product explicitly chose a read-only tray.", evidence: ["requiredInputs.concrete parent entity ID", "intake.comment_tray_scope"] },
             { step: "Wire moderation affordance (report/hide/delete) on each comment.", evidence: ["implementationRules.file-specific edits"] },
             { step: "Run validate_setup and detected command sensors after edits.", evidence: ["validate_setup", "run_sensors"] },
         ];
@@ -794,6 +824,9 @@ const addComments = {
         "comment target resolved",
         "no invented postId/commentId",
         "comments.target-resolved",
+        "comments.list-live",
+        "comments.creation-affordance",
+        "comments.ui-states-present",
         "comments.thread-read-write",
         "moderation.affordance-present",
         "pagination.cursor-opaque",
@@ -988,6 +1021,14 @@ const addChat = {
                 required: true,
                 blocksImplementationWhenMissing: false,
             },
+            {
+                id: "chat_inbox_scope",
+                question: "Should the chat inbox show live channels with unread badges and explicit recency sorting?",
+                why: "A message thread can work while the inbox silently drops unread state or reverses channel recency. The agent should confirm the channel-list behavior before building.",
+                required: false,
+                blocksImplementationWhenMissing: false,
+                options: ["live channels + unread + last activity sort", "thread only", "no unread badges", "custom sort"],
+            },
         ];
         return filterAnswered(ctx.answers, questions);
     },
@@ -1019,7 +1060,8 @@ const addChat = {
             },
             { 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: "Render unread counts/badges from the SDK on channel rows or the chat tab (`channel.getUnreadCount()`, `getSubChannelsUnreadCount()`, or `AmityCoreClient.observeUserUnread()` / `getTotalChannelUnread()`), and declare message order explicitly with `AmityMessageQuerySortOption.FIRST_CREATED` or `LAST_CREATED` so the UI cannot invert the thread by relying on defaults.", evidence: ["social-plus-sdk/chat/channels", "social-plus-sdk/chat/messages"] },
+            { 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(), or startMessageReceiptSync paired with stopMessageReceiptSync on the view lifecycle) so the server-side unread count actually decrements. Reading the unread count without ever marking read leaves the badge stuck.", evidence: ["requiredInputs.read receipt and typing indicator requirements"] },
             { step: "Add moderation affordance on messages.", evidence: ["requiredInputs.moderation flow for chat messages"] },
             { step: "Run validate_setup and detected command sensors after edits.", evidence: ["validate_setup", "run_sensors"] },
@@ -1030,6 +1072,8 @@ const addChat = {
         "chat.message-observer-cleanup",
         "chat.send-error-handling",
         "chat.channel-shape-matched",
+        "chat.channel-list-live",
+        "chat.channel-list-order-explicit",
         "moderation.affordance-present",
         "unread.server-synced",
         "pagination.cursor-opaque",
@@ -1243,6 +1287,14 @@ const addFollow = {
                 required: true,
                 blocksImplementationWhenMissing: true,
             },
+            {
+                id: "profile_identity_scope",
+                question: "Should profile screens show SDK-backed identity, avatar, follower/following counts, and relationship state?",
+                why: "Profile screens often keep placeholder counts or initials while follow state works elsewhere. The agent should confirm which profile fields are in scope and source them from the SDK.",
+                required: false,
+                blocksImplementationWhenMissing: false,
+                options: ["identity + avatar + counts + relationship", "counts only", "relationship only", "custom subset"],
+            },
         ];
         return filterAnswered(ctx.answers, questions);
     },
@@ -1272,6 +1324,7 @@ const addFollow = {
                 evidence: ["social-plus-sdk/social/user-relationship/following/get-follower-following-list", liveDataPlatformPath(ctx.platform)],
             },
             { step: "Handle the follow-request approval flow (pending/accept/decline) when following is not automatic.", evidence: ["requiredInputs.follow model"] },
+            { step: "Populate profile identity from the SDK user/profile object: displayName/userId, SDK avatar URL with initials only as fallback, follower/following counts, and relationship state. Do not ship placeholder count labels or generated initials as the only avatar source.", evidence: ["social-plus-sdk/social/user-profile", "intake.profile_identity_scope", "capabilityAvailability.available"] },
             { step: "Wire block/unblock and a blocked-users surface where in scope.", evidence: ["social-plus-sdk/social/user-relationship/blocking/block-unblock-user"] },
             { step: "Reuse the host app's existing visual system; implement loading/empty/error/data states.", evidence: designEvidence },
             { step: "Run validate_setup and detected command sensors after edits.", evidence: ["validate_setup", "run_sensors"] },
@@ -1281,6 +1334,8 @@ const addFollow = {
         "follow.target-resolved",
         "follow.relationship-live",
         "follow.model-explicit",
+        "profile.identity-from-sdk",
+        "profile.avatar-from-sdk",
         "profile.social-counts",
         "validate_setup",
         "run_sensors",

package/dist/productExpectations.js

@@ -8,12 +8,19 @@ export const PRODUCT_EXPECTATION_TITLES = {
     "unread.server-synced": "Unread counts use the server-synced stream",
     "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",
+    "feed.composer-type-scope-explicit": "Post composer type scope is explicit",
     "comments.target-resolved": "Comment target comes from the parent entity",
     "comments.thread-read-write": "Comment threads support reading and creation",
+    "comments.list-live": "Comment tray lists comments live",
+    "comments.creation-affordance": "Comment tray includes comment creation",
+    "comments.ui-states-present": "Comment tray renders loading, empty, and error states",
     "chat.channel-target-resolved": "Chat channel comes from app state",
     "chat.message-observer-cleanup": "Chat message observers clean up on lifecycle end",
     "chat.send-error-handling": "Chat send failures are handled",
     "chat.channel-shape-matched": "Chat channel type matches the requested shape",
+    "chat.channel-list-live": "Chat channel list stays live",
+    "chat.channel-list-order-explicit": "Chat channel list sorting is explicit",
     "chat.unread-visible": "Chat unread counts are visible",
     "chat.message-order-explicit": "Chat message order is explicit",
     "community.target-resolved": "Community target comes from app state",
@@ -25,6 +32,8 @@ export const PRODUCT_EXPECTATION_TITLES = {
     "follow.target-resolved": "Follow target comes from app state",
     "follow.relationship-live": "Follow relationships stay live",
     "follow.model-explicit": "Follow approval model is explicit",
+    "profile.identity-from-sdk": "Profile identity comes from the SDK",
+    "profile.avatar-from-sdk": "Profile avatar comes from the SDK",
     "profile.social-counts": "Profile social counts come from the SDK",
     "notifications.tray-live": "Notification tray is observed live",
     "notifications.mark-seen": "Notification seen state clears server-side",

package/dist/tools/integration.js

@@ -82,7 +82,21 @@ async function buildIntegrationPlan(repoPath, request, surfacePath, answers = {}
     const designReview = designReviewGuidance(repoRoot, designContract, answers);
     const acceptedDesignContract = designReview.status === "accepted" ? designContract : null;
     const designBrief = acceptedDesignContract ? buildDesignBrief(acceptedDesignContract) : undefined;
-    const intake = intakeFor(ctx, definition.intakeQuestions(ctx), outcome, designBrief, capabilityAvailability, designReview);
+    const socialWorkplan = await socialWorkplanFor({
+        request,
+        answers,
+        repoPath: repoRoot,
+        platform,
+        platforms: inspection.platforms,
+        designSignals: inspection.designSignals,
+        designBrief,
+        designReview,
+        sensors,
+    });
+    const outcomeQuestions = socialWorkplan
+        ? definition.intakeQuestions(ctx).filter((question) => question.id !== "feature_surface")
+        : definition.intakeQuestions(ctx);
+    const intake = intakeFor(ctx, outcomeQuestions, outcome, designBrief, capabilityAvailability, designReview);
     // Advisory SDK-version currency guidance (npm registry for TS/RN; version-agnostic
     // for native). Best-effort — degrades to greenfield "install latest + pin" if the
     // registry is unreachable. Never gates.
@@ -108,6 +122,7 @@ async function buildIntegrationPlan(repoPath, request, surfacePath, answers = {}
         platform,
         supportLevel,
         intent: intentFor(request, definition.interpretation),
+        socialWorkplan,
         capabilityAvailability,
         designReview,
         decisionsRequired,
@@ -123,7 +138,7 @@ async function buildIntegrationPlan(repoPath, request, surfacePath, answers = {}
         availableSurfaces: inspection.surfaces,
         applicableRules: await applicableCompliancePlanRuleSummaries(outcome, inspection.platforms),
         sensors: sensors.map((sensor) => ({ name: sensor.name, command: sensor.command, source: sensor.source })),
-        stopConditions: composeStopConditions(ctx, definition.stopConditions(ctx), inspection.surfaces, surfacePath),
+        stopConditions: composeStopConditions(ctx, definition.stopConditions(ctx), inspection.surfaces, surfacePath, Boolean(socialWorkplan)),
         evidencePolicy: "Every implementation step must cite at least one detected file, docs page, validator rule, or required user input. If evidence is missing, stop and ask the user instead of inventing details.",
         designContract: acceptedDesignContract ? designContractGuidance(acceptedDesignContract) : undefined,
         completenessChecklist: completenessChecklistFor(outcome),
@@ -162,6 +177,113 @@ function optionalCapabilitiesFor(outcome, answers, request, availability) {
         selected: selectedOptionalCapabilityIds(outcome, answers, request, availableIds),
     };
 }
+const SOCIAL_SURFACE_SEQUENCE = [
+    {
+        id: "feed",
+        outcome: "add-feed",
+        label: "Feed and post creation",
+        aliases: [/\b(feed|timeline|news feed|post list|posts?|create post|post creation|compose post|composer|reactions?)\b/i],
+        defaultForGenericBroad: true,
+    },
+    {
+        id: "comments",
+        outcome: "add-comments",
+        label: "Comments and replies",
+        aliases: [/\b(comments?|replies|reply|discussion thread|comment tray|comment composer)\b/i],
+        defaultForGenericBroad: true,
+    },
+    {
+        id: "chat",
+        outcome: "add-chat",
+        label: "Chat inbox and thread",
+        aliases: [/\b(chat|messaging|dm|direct message|conversation|group chat|channel|inbox)\b/i],
+        defaultForGenericBroad: true,
+    },
+    {
+        id: "profile",
+        outcome: "add-follow",
+        label: "Profile and follow graph",
+        aliases: [/\b(profile|profiles|follow|unfollow|followers?|following|social graph|relationship)\b/i],
+        defaultForGenericBroad: true,
+    },
+    {
+        id: "community",
+        outcome: "add-community",
+        label: "Community management",
+        aliases: [/\b(create|manage|join|leave|membership|members?|roles?|invitations?|categories?)\s+(?:a\s+|the\s+)?communit/i, /\bcommunity\s+(creation|management|members?|roles?|invitations?|categories|settings|moderation)\b/i],
+    },
+    {
+        id: "notifications",
+        outcome: "add-notifications",
+        label: "In-app notifications",
+        aliases: [/\b(notification tray|notification cent(?:er|re)|in-?app notifications?|notification settings?|notification preferences?)\b/i],
+    },
+];
+async function socialWorkplanFor(args) {
+    if (!BROAD_SOCIAL_REGEX.test(args.request) || hasAnswer(args.answers, "feature_surface")) {
+        return undefined;
+    }
+    const matched = SOCIAL_SURFACE_SEQUENCE.filter((surface) => surface.aliases.some((pattern) => pattern.test(args.request)));
+    const selected = matched.length > 0
+        ? matched
+        : SOCIAL_SURFACE_SEQUENCE.filter((surface) => surface.defaultForGenericBroad);
+    if (selected.length <= 1) {
+        return undefined;
+    }
+    const sequence = [];
+    for (const surface of selected) {
+        const definition = getOutcomeDefinition(surface.outcome);
+        const capabilityAvailability = await platformCapabilityAvailability(surface.outcome, args.platform);
+        const surfaceAnswers = { ...args.answers, feature_surface: surface.id };
+        const surfaceCtx = {
+            ...planContextFor({
+                request: args.request,
+                outcome: surface.outcome,
+                platform: args.platform,
+                platforms: args.platforms,
+                designSignals: args.designSignals,
+                answers: surfaceAnswers,
+            }),
+            broadSocialRequest: false,
+        };
+        const intake = intakeFor(surfaceCtx, definition.intakeQuestions(surfaceCtx), surface.outcome, args.designBrief, capabilityAvailability, args.designReview);
+        const matchedPrompt = matched.some((match) => match.id === surface.id);
+        const commonArgs = `. --request ${shellQuote(args.request)} --answer feature_surface=${surface.id}`;
+        sequence.push({
+            id: surface.id,
+            order: sequence.length + 1,
+            outcome: surface.outcome,
+            label: surface.label,
+            matchedPrompt,
+            reason: matchedPrompt
+                ? `The request explicitly mentions ${surface.label.toLowerCase()}.`
+                : "The request is generic broad social work, so Vise includes this core surface in the default sequence.",
+            planCommand: `vise plan ${commonArgs}`,
+            initCommand: `vise init ${commonArgs}`,
+            intake: {
+                status: intake.status,
+                questions: intake.questions,
+                remainingBlocking: intake.remainingBlocking,
+            },
+            capabilityAvailability,
+            validation: ["validate_setup", "run_sensors", ...definition.validation(args.platform)],
+            docs: definition.docs(args.platform).filter((doc) => doc.path !== "unknown"),
+            optionalCapabilities: optionalCapabilitiesFor(surface.outcome, surfaceAnswers, args.request, capabilityAvailability),
+            sensors: args.sensors.map((sensor) => ({ name: sensor.name, command: sensor.command, source: sensor.source })),
+        });
+    }
+    const status = sequence.some((surface) => surface.intake.remainingBlocking > 0) ? "needs-answers" : "ready";
+    return {
+        kind: "social-multi-surface",
+        status,
+        note: "This broad social request is decomposed into ordered per-surface plans. Initialize and check one surface at a time so each sidecar has one outcome, while using this sequence as the coordinated product workplan.",
+        sequence,
+        nextStep: "Resolve each surface's blocking questions, then run the listed plan/init command for that surface before implementation. After each surface build, run `vise check .`, `vise sync .`, `vise validate .`, and `vise run-sensors .`.",
+    };
+}
+function shellQuote(value) {
+    return `'${value.replace(/'/g, "'\\''")}'`;
+}
 function designReviewGuidance(repoRoot, contract, answers) {
     if (!contract) {
         return {
@@ -371,7 +493,7 @@ function composeImplementationRules(ctx, outcomeRules) {
     }
     return rules;
 }
-function composeStopConditions(ctx, outcomeStops, surfaces, surfacePath) {
+function composeStopConditions(ctx, outcomeStops, surfaces, surfacePath, hasSocialWorkplan = false) {
     const stops = [
         "A required secret is missing and no safe ignored local env file or non-secret template path is clear.",
         "The target file is ambiguous or missing and no safe conventional location is detected.",
@@ -387,7 +509,7 @@ function composeStopConditions(ctx, outcomeStops, surfaces, surfacePath) {
         stops.push(`Multiple app surfaces detected (${surfaces.map((surface) => surface.path).join(", ")}); call this tool again with surfacePath set to the target app surface.`);
     }
     stops.push(...outcomeStops);
-    if (ctx.broadSocialRequest && !hasAnswer(ctx.answers, "feature_surface")) {
+    if (ctx.broadSocialRequest && !hasAnswer(ctx.answers, "feature_surface") && !hasSocialWorkplan) {
         stops.push("The requested social feature is too broad; confirm the first feature surface before implementing.");
     }
     if (ctx.mentionsDesign && ctx.designSignals.length === 0 && !hasAnswer(ctx.answers, "design_source")) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@amityco/social-plus-vise",
-  "version": "0.14.20",
+  "version": "0.14.22",
   "description": "Skill-guided deterministic CLI for social.plus SDK integration assistance.",
   "license": "SEE LICENSE IN LICENSE",
   "type": "module",