@amityco/social-plus-vise 0.4.0

package/dist/outcomes.js

@@ -0,0 +1,574 @@
+export function hasAnswer(answers, id) {
+    const value = answers[id];
+    return typeof value === "string" && value.trim() !== "";
+}
+const CLASSIFY_ORDER = [
+    "setup-push",
+    "setup-live-data",
+    "add-feed",
+    "troubleshoot",
+    "validate-setup",
+    "setup-sdk",
+];
+const PUSH_PATTERNS = [/\b(push|notification|firebase|fcm|apns)\b/];
+const LIVE_PATTERNS = [
+    /\b(live object|live objects|live collection|live collections|realtime collection|real-time collection|observe|observer|subscribe|subscription|unsubscribe|live update|live updates)\b/,
+];
+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 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)\b/];
+export const BROAD_SOCIAL_REGEX = /\b(nice|social features|social feature|engagement|community experience)\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();
+    for (const id of CLASSIFY_ORDER) {
+        const def = outcomeRegistry[id];
+        if (def.patterns.some((pattern) => pattern.test(normalized))) {
+            return id;
+        }
+    }
+    return "unknown";
+}
+export function getOutcomeDefinition(outcome) {
+    return outcomeRegistry[outcome];
+}
+const SUPPORTED_PLATFORMS_FOR_PATH_AUDIT = ["android", "flutter", "ios", "typescript", "react-native"];
+export function knownDocPaths() {
+    const seen = new Set();
+    for (const outcome of Object.keys(outcomeRegistry)) {
+        const definition = outcomeRegistry[outcome];
+        for (const platform of SUPPORTED_PLATFORMS_FOR_PATH_AUDIT) {
+            for (const doc of definition.docs(platform)) {
+                if (doc.path && doc.path !== "unknown") {
+                    seen.add(doc.path);
+                }
+            }
+        }
+    }
+    return Array.from(seen).sort();
+}
+export function planContextFor(args) {
+    return {
+        request: args.request,
+        outcome: args.outcome,
+        platform: args.platform,
+        platforms: args.platforms,
+        designSignals: args.designSignals,
+        mentionsDesign: DESIGN_REGEX.test(args.request),
+        broadSocialRequest: BROAD_SOCIAL_REGEX.test(args.request),
+        answers: args.answers ?? {},
+    };
+}
+export function platformQuickStart(platform) {
+    const paths = {
+        android: "social-plus-sdk/getting-started/platform-setup/mobile/android-quick-start",
+        flutter: "social-plus-sdk/getting-started/platform-setup/mobile/flutter-quick-start",
+        ios: "social-plus-sdk/getting-started/platform-setup/mobile/ios-quick-start",
+        typescript: "social-plus-sdk/getting-started/platform-setup/web/web-quick-start",
+        "react-native": "social-plus-sdk/getting-started/platform-setup/web/web-quick-start",
+    };
+    return {
+        path: paths[platform] ?? "unknown",
+        reason: "Canonical SDK setup guidance for the detected platform.",
+    };
+}
+export function pushSetupPath(platform) {
+    const paths = {
+        android: "social-plus-sdk/core-concepts/realtime-communication/push-notifications/setup/android-setup",
+        flutter: "social-plus-sdk/core-concepts/realtime-communication/push-notifications/setup/flutter-setup",
+        ios: "social-plus-sdk/core-concepts/realtime-communication/push-notifications/setup/ios-setup",
+        typescript: "social-plus-sdk/core-concepts/realtime-communication/push-notifications/setup/web-setup",
+        "react-native": "social-plus-sdk/core-concepts/realtime-communication/push-notifications/setup/react-native-setup",
+    };
+    return paths[platform] ?? "unknown";
+}
+function filterAnswered(answers, questions) {
+    return questions.filter((question) => !hasAnswer(answers, question.id));
+}
+function filterStops(answers, stops) {
+    return stops.filter((stop) => !hasAnswer(answers, stop.id)).map((stop) => stop.text);
+}
+export function liveDataPlatformPath(platform) {
+    const paths = {
+        android: "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/android",
+        flutter: "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/flutter",
+        ios: "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/ios",
+        typescript: "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/typescript",
+        "react-native": "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/typescript",
+    };
+    return paths[platform] ?? "unknown";
+}
+const setupSdk = {
+    id: "setup-sdk",
+    patterns: SETUP_PATTERNS,
+    interpretation: "Implement setup-sdk.",
+    docsQuery: (platform) => `${platform} quick start setup`,
+    docs: (platform) => [
+        platformQuickStart(platform),
+        {
+            path: "social-plus-sdk/getting-started/authentication",
+            reason: "Canonical login, session, and authentication ordering guidance.",
+        },
+    ],
+    intakeQuestions: () => [],
+    requiredInputs: () => [],
+    implementationRules: () => [],
+    implementationSteps: (ctx) => [
+        { step: "Verify or add the platform SDK dependency.", evidence: [platformQuickStart(ctx.platform).path, "targetFiles.dependency"] },
+        {
+            step: "Initialize the social.plus client exactly once with API key and explicit region.",
+            evidence: [platformQuickStart(ctx.platform).path, "requiredInputs.social.plus API key local env/config variable", "requiredInputs.social.plus region"],
+        },
+        {
+            step: "Wire login after user identity is known and before social.plus API queries/subscriptions.",
+            evidence: ["social-plus-sdk/getting-started/authentication", "requiredInputs.user identity source for login"],
+        },
+        { step: "Run validate_setup and detected command sensors after edits.", evidence: ["validate_setup", "run_sensors"] },
+    ],
+    validation: (platform) => [`${platform}.setup.present`, `${platform}.login.present`, `${platform}.region.explicit`],
+    stopConditions: () => [],
+    resolvePlan: (platform) => {
+        if (platform === "android") {
+            return [
+                { file: "app/build.gradle or app/build.gradle.kts", intent: "Add the social.plus Android SDK dependency." },
+                { file: "Application class", intent: "Initialize the SDK once at app startup with API key and region." },
+                { file: "Login/auth flow", intent: "Call login after the app has a known user identity." },
+            ];
+        }
+        if (platform === "flutter") {
+            return [
+                { file: "pubspec.yaml", intent: "Add the social.plus Flutter dependency." },
+                { file: "lib/main.dart", intent: "Ensure Flutter binding is initialized before SDK setup." },
+                { file: "Login/auth flow", intent: "Call login after the app has a known user identity." },
+            ];
+        }
+        return [{ file: "customer app", intent: "Inspect the app and fetch relevant docs before proposing code changes." }];
+    },
+    resolveVerification: () => [
+        "Confirm SDK setup runs before any social.plus API call.",
+        "Confirm the SDK reads the API key from an environment/config placeholder and the region matches the customer's social.plus console project.",
+    ],
+    resolveNotes: () => [],
+};
+const setupPush = {
+    id: "setup-push",
+    patterns: PUSH_PATTERNS,
+    interpretation: "Set up push notifications with platform credentials, user permission/token handling, device registration after login, and unregister on logout or user switch.",
+    docsQuery: (platform) => `${platform} push notification setup`,
+    docs: (platform) => [
+        {
+            path: "social-plus-sdk/core-concepts/realtime-communication/push-notifications/overview",
+            reason: "Push notification architecture, delivery options, and cross-platform setup overview.",
+        },
+        {
+            path: pushSetupPath(platform),
+            reason: "Canonical push notification setup for the detected platform.",
+        },
+        {
+            path: "social-plus-sdk/core-concepts/realtime-communication/push-notifications/register-and-unregister-push-notifications-on-a-device",
+            reason: "Device registration and logout/user-switch cleanup guidance.",
+        },
+        {
+            path: "social-plus-sdk/core-concepts/realtime-communication/push-notifications/settings/overview",
+            reason: "Notification preference settings for user/channel/community controls.",
+        },
+    ],
+    intakeQuestions: (ctx) => filterAnswered(ctx.answers, [
+        {
+            id: "push_platform",
+            question: "Which push platform and credentials are already configured for this app?",
+            why: "Device registration only works after platform push setup is complete in the app and social.plus console.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+            options: ["FCM", "APNS", "web push", "cross-platform FCM/APNS"],
+        },
+        {
+            id: "device_token_source",
+            question: "Where does the host app request notification permission and obtain the device token?",
+            why: "The social.plus SDK registers a token; the host app remains responsible for permission prompts and token creation.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+        },
+        {
+            id: "logout_user_switch_flow",
+            question: "Which logout or user-switch flow should unregister the device token?",
+            why: "A registered device is associated with one user at a time, so cleanup prevents notifications going to the wrong user.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+        },
+    ]),
+    requiredInputs: () => [
+        "customer-owned Firebase/APNS/Web Push configuration",
+        "device token source from the host app",
+        "notification permission request flow",
+        "device registration and logout/user-switch behavior",
+    ],
+    implementationRules: () => [
+        "Do not fabricate Firebase/APNS/Web Push configuration. Use customer-provided push credentials and files only.",
+        "Do not register a device token before social.plus login succeeds.",
+        "Always unregister the device token on logout or user switch so a device is not tied to the wrong user.",
+        "Do not implement platform permission prompts or token creation unless the host app's push library and ownership are identified.",
+    ],
+    implementationSteps: (ctx) => [
+        { step: "Verify SDK setup and login are already correct before push work.", evidence: ["validate_setup", "social-plus-sdk/getting-started/authentication"] },
+        {
+            step: "Confirm platform push credentials and app-side permission/token ownership.",
+            evidence: [
+                "requiredInputs.customer-owned Firebase/APNS/Web Push configuration",
+                "requiredInputs.device token source from the host app",
+                pushSetupPath(ctx.platform),
+            ],
+        },
+        {
+            step: "Wire platform push config using only customer-provided Firebase/APNS/Web Push material.",
+            evidence: [pushSetupPath(ctx.platform), "requiredInputs.customer-owned Firebase/APNS/Web Push configuration"],
+        },
+        {
+            step: "Register device after login and unregister on logout/user switch.",
+            evidence: ["social-plus-sdk/core-concepts/realtime-communication/push-notifications/register-and-unregister-push-notifications-on-a-device"],
+        },
+        { step: "Run validate_setup and detected command sensors after edits.", evidence: ["validate_setup", "run_sensors"] },
+    ],
+    validation: (platform) => [
+        "push permission and token source identified",
+        "device registration after login",
+        "unregister on logout/user switch",
+        `${platform}.push.unregister.present`,
+    ],
+    stopConditions: (ctx) => filterStops(ctx.answers, [
+        { id: "push_platform", text: "Firebase/APNS/Web Push configuration is not present or not provided by the customer." },
+        { id: "device_token_source", text: "The host app's notification permission and device-token source is unknown." },
+        { id: "logout_user_switch_flow", text: "No logout or user-switch cleanup point is identified for unregistering device tokens." },
+    ]),
+    resolvePlan: () => [
+        { file: "Platform notification config", intent: "Wire customer-owned Firebase/APNS configuration." },
+        { file: "Login/auth flow", intent: "Register the device after login and unregister on logout." },
+    ],
+    resolveVerification: () => [
+        "Confirm device registration happens after login.",
+        "Confirm unregister runs on logout or user switch.",
+    ],
+    resolveNotes: () => [
+        "Push setup usually needs customer-owned Firebase/APNS values; do not invent secrets or config IDs.",
+    ],
+};
+const setupLiveData = {
+    id: "setup-live-data",
+    patterns: LIVE_PATTERNS,
+    interpretation: "Set up Live Object or Live Collection observation with loading/error states, granular updates, and cleanup when the view/component lifecycle ends.",
+    docsQuery: (platform) => `${platform} live objects live collections`,
+    docs: (platform) => [
+        {
+            path: "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/overview",
+            reason: "Live Object and Live Collection lifecycle, snapshots, loading/error states, and cleanup guidance.",
+        },
+        {
+            path: liveDataPlatformPath(platform),
+            reason: "Platform-specific Live Object and Live Collection implementation patterns.",
+        },
+        {
+            path: "social-plus-sdk/core-concepts/realtime-communication/realtime-events/overview",
+            reason: "Real-time event subscription context for live data updates.",
+        },
+    ],
+    intakeQuestions: (ctx) => filterAnswered(ctx.answers, [
+        {
+            id: "live_data_shape",
+            question: "Is the UI observing one object or a collection?",
+            why: "Live Objects and Live Collections have different callback shapes, update semantics, and UI handling.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+            options: ["single object", "collection"],
+        },
+        {
+            id: "live_data_domain",
+            question: "Which domain should be observed?",
+            why: "The docs and SDK entrypoints differ for posts, comments, messages, channels, users, and communities.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+            options: ["posts", "comments", "messages", "channels", "users", "communities", "stories"],
+        },
+        {
+            id: "lifecycle_owner",
+            question: "Which component, screen, ViewModel, or controller owns the subscription lifecycle?",
+            why: "Observers must be cleaned up when the UI lifecycle ends to avoid duplicate subscriptions and memory leaks.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+        },
+    ]),
+    requiredInputs: () => [
+        "live data shape: single object or collection",
+        "lifecycle owner for subscribe/unsubscribe cleanup",
+        "observed domain: posts, comments, messages, channels, users, communities, or stories",
+        "query/filter/sort and pagination requirements",
+        "UI handling for loading, empty, error, insertion, deletion, and modification states",
+    ],
+    implementationRules: () => [
+        "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.",
+        "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.",
+    ],
+    implementationSteps: (ctx) => [
+        {
+            step: "Confirm whether the UI needs a Live Object or Live Collection and which domain it observes.",
+            evidence: ["requiredInputs.live data shape", "requiredInputs.observed domain"],
+        },
+        {
+            step: "Fetch Live Objects/Collections docs plus platform-specific implementation guidance.",
+            evidence: [
+                "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/overview",
+                liveDataPlatformPath(ctx.platform),
+            ],
+        },
+        {
+            step: "Implement the subscription in the owning lifecycle scope and render loading, empty, error, and data states.",
+            evidence: ["requiredInputs.lifecycle owner for subscribe/unsubscribe cleanup", "implementationRules.loading-error-states"],
+        },
+        {
+            step: "For collections, apply insertion, deletion, and modification changes without unnecessary full-list rerenders.",
+            evidence: ["social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/overview"],
+        },
+        {
+            step: "Clean up the observer/subscription when the owner unmounts, disposes, or disappears.",
+            evidence: ["implementationRules.cleanup", "validate_setup"],
+        },
+        { step: "Run validate_setup and detected command sensors after edits.", evidence: ["validate_setup", "run_sensors"] },
+    ],
+    validation: (platform) => [
+        "live data owner identified",
+        "loading and error states handled",
+        "subscription cleanup on lifecycle end",
+        `${platform}.live.cleanup`,
+    ],
+    stopConditions: (ctx) => filterStops(ctx.answers, [
+        { id: "live_data_shape", text: "The request does not identify whether the UI needs a Live Object or Live Collection." },
+        { id: "lifecycle_owner", text: "The lifecycle owner for subscription cleanup is unknown." },
+    ]),
+    resolvePlan: () => [
+        {
+            file: "Target screen/component/controller",
+            intent: "Observe the Live Object or Live Collection and render loading, empty, error, and data states.",
+        },
+        {
+            file: "Data source/repository module",
+            intent: "Encapsulate get/query calls and clean up subscriptions when the lifecycle owner ends.",
+        },
+    ],
+    resolveVerification: () => [
+        "Confirm Live Object/Collection observers clean up on unmount/dispose/disappear.",
+        "Confirm loading and error states are rendered before data is treated as ready.",
+    ],
+    resolveNotes: () => [
+        "Live Object and Live Collection work needs an explicit lifecycle owner so observers can be cleaned up.",
+    ],
+};
+const addFeed = {
+    id: "add-feed",
+    patterns: FEED_PATTERNS,
+    interpretation: "Add a social feed or social content surface using the customer app's existing design system.",
+    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/core-concepts/realtime-communication/live-objects-collections/overview",
+            reason: "Live Object and Live Collection lifecycle, snapshots, loading/error states, and cleanup guidance.",
+        },
+        {
+            path: liveDataPlatformPath(platform),
+            reason: "Platform-specific Live Object and Live Collection implementation patterns.",
+        },
+        {
+            path: "social-plus-sdk/core-concepts/realtime-communication/realtime-events/overview",
+            reason: "Real-time event subscription context for live data updates.",
+        },
+    ],
+    intakeQuestions: (ctx) => {
+        const questions = [];
+        if (ctx.broadSocialRequest) {
+            questions.push({
+                id: "feature_surface",
+                question: "Which social surface should be implemented first?",
+                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"],
+            });
+        }
+        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.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+            options: ["global", "user", "community"],
+        });
+        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.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+            options: ["existing communityId", "current user's feed", "selected user's feed", "app-defined/global feed", "ask user at runtime"],
+        });
+        questions.push({
+            id: "target_screen_or_route",
+            question: "Which screen, route, or component should receive the social UI?",
+            why: "Vise can identify platform files, but the host app owns navigation and product placement.",
+            required: true,
+            blocksImplementationWhenMissing: true,
+        });
+        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",
+        "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",
+    ],
+    implementationRules: () => [
+        "Do not invent or hardcode communityId, targetId, feedId, channelId, or any other feed target. Ask for the target or implement a user/customer-owned selection flow.",
+        "Do not ask for API keys in chat. Create an env/config placeholder and tell the user to fill the real value locally.",
+    ],
+    implementationSteps: (ctx) => {
+        const designEvidence = ctx.designSignals.length > 0
+            ? ctx.designSignals.map((signal) => signal.file)
+            : ["requiredInputs.design token or theme source file"];
+        return [
+            {
+                step: "Confirm the target route/screen, feed scope, and concrete feed target before writing code.",
+                evidence: [
+                    "requiredInputs.feed scope",
+                    "requiredInputs.concrete feed target",
+                    "requiredInputs.target screen or route",
+                ],
+            },
+            {
+                step: "Fetch the canonical social/feed docs and use platform-appropriate live collection patterns.",
+                evidence: [
+                    "social-plus-sdk/social/posts",
+                    "social-plus-sdk/core-concepts/realtime-communication/live-objects-collections/overview",
+                ],
+            },
+            { 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: "Run validate_setup and detected command sensors after edits.", evidence: ["validate_setup", "run_sensors"] },
+        ];
+    },
+    validation: (platform) => [
+        "feed target identified",
+        "no invented communityId/targetId/feedId",
+        `${platform}.feed.target.literal`,
+    ],
+    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." },
+    ]),
+    resolvePlan: () => [
+        {
+            file: "Target screen/component",
+            intent: "Add a feed query and render loading, empty, error, and item states.",
+        },
+        { file: "Navigation route", intent: "Expose the feed surface from the existing app navigation." },
+    ],
+    resolveVerification: () => [
+        "Confirm the feed screen handles loading, empty, error, and data states.",
+        "Confirm the feed query is scoped to the intended global, user, or community feed.",
+    ],
+    resolveNotes: () => [],
+};
+const troubleshoot = {
+    id: "troubleshoot",
+    patterns: TROUBLESHOOT_PATTERNS,
+    interpretation: "Implement troubleshoot.",
+    docsQuery: (platform) => `${platform} troubleshooting authentication setup`,
+    docs: () => [
+        {
+            path: "social-plus-sdk/getting-started/authentication",
+            reason: "Authentication and session issues are common setup failure causes.",
+        },
+        {
+            path: "social-plus-sdk/core-concepts/foundation/logging",
+            reason: "Logging and diagnostics guidance for debugging integration failures.",
+        },
+    ],
+    intakeQuestions: () => [],
+    requiredInputs: () => [],
+    implementationRules: () => [],
+    implementationSteps: () => [
+        { step: "Gather more evidence before implementation.", evidence: ["stopConditions", "search_docs", "inspect_project"] },
+    ],
+    validation: () => [],
+    stopConditions: () => [],
+    resolvePlan: () => [
+        { file: "customer app", intent: "Inspect the app and fetch relevant docs before proposing code changes." },
+    ],
+    resolveVerification: () => [],
+    resolveNotes: () => [],
+};
+const validateSetup = {
+    id: "validate-setup",
+    patterns: VALIDATE_PATTERNS,
+    interpretation: "Implement validate-setup.",
+    docsQuery: (platform) => `${platform} quick start setup`,
+    docs: (platform) => [
+        platformQuickStart(platform),
+        {
+            path: "social-plus-sdk/getting-started/authentication",
+            reason: "Canonical login, session, and authentication ordering guidance.",
+        },
+    ],
+    intakeQuestions: () => [],
+    requiredInputs: () => [],
+    implementationRules: () => [],
+    implementationSteps: () => [
+        { step: "Gather more evidence before implementation.", evidence: ["stopConditions", "search_docs", "inspect_project"] },
+    ],
+    validation: () => [],
+    stopConditions: () => [],
+    resolvePlan: () => [
+        { file: "customer app", intent: "Inspect the app and fetch relevant docs before proposing code changes." },
+    ],
+    resolveVerification: () => [
+        "Confirm SDK setup runs before any social.plus API call.",
+        "Confirm the SDK reads the API key from an environment/config placeholder and the region matches the customer's social.plus console project.",
+    ],
+    resolveNotes: () => [],
+};
+const unknown = {
+    id: "unknown",
+    patterns: [],
+    interpretation: "Implement unknown.",
+    docsQuery: (platform) => `${platform} quick start setup`,
+    docs: () => [],
+    intakeQuestions: () => [],
+    requiredInputs: () => [],
+    implementationRules: () => [],
+    implementationSteps: () => [
+        { step: "Gather more evidence before implementation.", evidence: ["stopConditions", "search_docs", "inspect_project"] },
+    ],
+    validation: () => [],
+    stopConditions: () => [],
+    resolvePlan: () => [
+        { file: "customer app", intent: "Inspect the app and fetch relevant docs before proposing code changes." },
+    ],
+    resolveVerification: () => [],
+    resolveNotes: () => [],
+};
+const outcomeRegistry = {
+    "setup-sdk": setupSdk,
+    "setup-push": setupPush,
+    "setup-live-data": setupLiveData,
+    "add-feed": addFeed,
+    troubleshoot,
+    "validate-setup": validateSetup,
+    unknown,
+};