@amityco/social-plus-vise 0.14.21 → 0.14.22

package/CHANGELOG.md

@@ -4,6 +4,17 @@ 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

package/README.md

@@ -161,12 +161,13 @@ Aggregate: **98/99 expected feed capabilities** and **27/27 selected optional ca
 
 ### Current Release Validation
 
-Version 0.14.21 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`, 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`. |
+| **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`, `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. |

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.21",
+  "version": "0.14.22",
   "description": "Skill-guided deterministic CLI for social.plus SDK integration assistance.",
   "license": "SEE LICENSE IN LICENSE",
   "type": "module",