@amityco/social-plus-vise 1.0.1 → 1.1.1

package/dist/capabilities.js

@@ -1,33 +1,24 @@
-/**
- * Feature-completeness assessment.
- *
- * Boundary (see the validation-boundaries principle): completeness is a "this is
- * missing" claim — a universal-negative over open-ended correct implementations
- * unless the customer/agent explicitly removes it from scope. Missing capabilities
- * now produce `completeness-gap` in `vise check`; a recorded scope-omit reason is
- * the false-positive escape hatch.
- *
- * Memory-independence comes from inversion: VISE authors the canonical capability
- * set per outcome; the agent must OPT OUT of a capability with a recorded reason
- * (`// vise: scope-omit <id> <reason>`), which `check` reads and reports. The
- * agent subtracts with justification — it doesn't have to remember the set.
- *
- * Baseline capability gates must stay narrow. For add-feed, pagination is the
- * mandatory capability. For add-comments, the comment composer is mandatory.
- * For add-chat, sending plus read/unread state are mandatory. For add-follow,
- * follower/following relationship data is mandatory. Replies, mentions,
- * edit/delete, typing, media-message types, block lists, and deeper moderation
- * scope are scoped separately. Richer composer affordances are selected optional sensors.
- */
 import { readdir, readFile, stat } from "node:fs/promises";
 import path from "node:path";
 import { canonicalPlatform, getSdkFacts } from "./tools/sdkFacts.js";
-// Canonical, Vise-authored capability catalog — the SDK feature surface
-// (grounded in rules/*.yaml + SKILL.md, not guessed). Baseline gating is applied
-// by baselineCapabilities(); not every catalog item is mandatory for every outcome.
+export function slimCapabilityItem(i) {
+    return { id: i.id, status: i.status, validator: i.validator };
+}
+export function slimCapabilityAvailability(ca) {
+    if (!ca)
+        return undefined;
+    return {
+        platform: ca.platform,
+        ...(ca.canonicalPlatform !== undefined ? { canonicalPlatform: ca.canonicalPlatform } : {}),
+        outcome: ca.outcome,
+        source: ca.source,
+        note: ca.note,
+        available: ca.available.map(slimCapabilityItem),
+        unavailable: ca.unavailable.map(slimCapabilityItem),
+        unknown: ca.unknown.map(slimCapabilityItem),
+    };
+}
 export const CAPABILITIES = [
-    // ── add-feed: post dataTypes (a feed parent is usually 'text'; rich content
-    //    rides on child posts — render each type the feed can return) ──────────
     {
         id: "post-image",
         label: "Image posts",
@@ -39,10 +30,6 @@ export const CAPABILITIES = [
         id: "post-video",
         label: "Video posts",
         outcomes: ["add-feed"],
-        // Native idioms differ from TS: Android matches a sealed-class case
-        // `AmityPost.Data.VIDEO`, Flutter an enum `AmityDataType.VIDEO`, both expose
-        // getVideo()/videoData. Without these the catalog false-reports video as missing
-        // on Kotlin/Dart even when the agent handles it (found on Netflix native builds).
         symbols: [/\bgetVideo\w*/, /\bgetVideoUrl\b/, /AmityVideo/i, /AmityPost\.Data\.VIDEO\b/, /['"]video['"]/, /Data(?:Type)?\.VIDEO\b/, /\bvideoData\b/],
         hint: "resolve video posts via getVideo / the VIDEO dataType from the parent or a child post",
     },
@@ -88,8 +75,6 @@ export const CAPABILITIES = [
         symbols: [/\bmentionees\b/, /\bmentionedUsers\b/, /metadata.*mention/i, /['"]mention['"]/],
         hint: "wrap @mention spans from metadata offsets and resolve userId→name; pass mentionees on create to notify",
     },
-    // ── add-feed: broader social.plus content surfaces (advisory — opt out if a
-    //    plain post feed; these are distinct social.plus features) ─────────────
     {
         id: "story",
         label: "Stories (ephemeral image/video)",
@@ -111,7 +96,6 @@ export const CAPABILITIES = [
         symbols: [/AmityRoomRepository/i, /\bcreateRoom\b/, /createRoomAndStartStreaming/i, /getBroadcastData/i, /createLiveStreamPost/i, /\bgoLive\b/i, /startPublish/i],
         hint: "live rooms/broadcasting via AmityRoomRepository (createRoom, go-live, live-viewing); post the stream with createLiveStreamPost (distinct from rendering a livestream post in the feed)",
     },
-    // ── add-feed: engagement surfaces ─────────────────────────────────────────
     {
         id: "comments",
         label: "Comment thread (list + composer)",
@@ -161,7 +145,6 @@ export const CAPABILITIES = [
         symbols: [/\bflagPost\b/, /\bflagComment\b/, /\bflagMessage\b/, /\.report\(\)/, /\bflaggedByMe\b/, /\bisFlagged/i],
         hint: "show report/flag for non-authors; gate moderator-only actions by role",
     },
-    // ── add-comments: depth ───────────────────────────────────────────────────
     {
         id: "comment-composer",
         label: "Comment composer (write)",
@@ -190,7 +173,6 @@ export const CAPABILITIES = [
         symbols: [/\bflagComment\b/, /\.report\(\)/, /\bflaggedByMe\b/],
         hint: "show flag/report on comments for non-authors",
     },
-    // ── add-chat: depth ───────────────────────────────────────────────────────
     {
         id: "send-message",
         label: "Send message",
@@ -223,7 +205,7 @@ export const CAPABILITIES = [
         id: "read-state",
         label: "Read state / unread count",
         outcomes: ["add-chat"],
-        symbols: [/\bmarkRead\b/, /\bmarkAsRead\b/, /startMessageReceiptSync/i, /\bunreadCount\b/],
+        symbols: [/\bmarkRead\b/, /\bmarkAsRead\b/, /\bunreadCount\b/],
         hint: "mark channel/messages read so the server's unread count decrements",
     },
     {
@@ -240,7 +222,6 @@ export const CAPABILITIES = [
         symbols: [/getMembers/i, /ChannelMember/i, /\bmembership\b/i, /\bgetChannelMembers\b/i],
         hint: "list/observe channel members; handle join/leave",
     },
-    // ── add-community ─────────────────────────────────────────────────────────
     {
         id: "community-create",
         label: "Create community",
@@ -290,7 +271,6 @@ export const CAPABILITIES = [
         symbols: [/AmityCommunityCategory/i, /getCategories/i, /categoryIds?/i],
         hint: "organize communities by category (AmityCommunityCategory)",
     },
-    // ── add-moderation: depth ─────────────────────────────────────────────────
     {
         id: "report-flow",
         label: "Report / flag flow",
@@ -319,7 +299,6 @@ export const CAPABILITIES = [
         symbols: [/isDeleted/i, /\bisFlagged/i, /hasFlaggedComment/i, /blockedContent/i, /\bhidden\b/i],
         hint: "render a placeholder for deleted/flagged content rather than hiding it silently",
     },
-    // ── add-follow (social graph) ─────────────────────────────────────────────
     {
         id: "follow-unfollow",
         label: "Follow / unfollow",
@@ -355,7 +334,6 @@ export const CAPABILITIES = [
         symbols: [/getBlockedUsers/i, /blockedUsers/i],
         hint: "surface a managed blocked-users list (getBlockedUsers)",
     },
-    // ── add-notifications (in-app tray) ───────────────────────────────────────
     {
         id: "notification-tray",
         label: "Notification tray / inbox",
@@ -378,9 +356,6 @@ export const CAPABILITIES = [
         hint: "respect Amity's server-side notification settings/preferences (getSettings)",
     },
 ];
-// Optional capabilities are not baseline compliance. `vise plan` offers them as
-// explicit feed-forward choices; `vise init --answer feed_optional_capabilities=...`
-// records selected choices; `vise check` then evaluates these source sensors.
 export const OPTIONAL_CAPABILITIES = [
     {
         id: "post-image-upload",
@@ -1183,26 +1158,12 @@ function baselineCapabilities(outcome) {
     const baseline = new Set(baselineIds);
     return caps.filter((capability) => baseline.has(capability.id));
 }
-/** The Vise-authored baseline capability checklist for an outcome. */
 export function capabilityChecklist(outcome) {
     return baselineCapabilities(outcome).map((c) => ({ id: c.id, label: c.label, hint: c.hint }));
 }
-/**
- * The Vise-owned completeness id vocabulary — every id a Block Factory contract
- * may reference in `providesCapabilities`. Vise owns this id space; the factory
- * owns the per-block declaration (see block-factory/docs/vise-boundary.md).
- */
 export function completenessCapabilityIds() {
     return new Set(CAPABILITIES.map((capability) => capability.id));
 }
-/**
- * Overlay installed-block evidence onto a source-scan completeness assessment.
- * A still-missing checklist capability becomes present with evidence
- * `source: "block:<blockId>"` when a locally validated installed block declares
- * it in `providesCapabilities`. Callers are responsible for the local validation
- * (package declared + filesTouched intact); on drift they must simply not pass
- * the capability here, so the normal gap returns.
- */
 export function applyBlockProvidedCompleteness(assessment, provided) {
     if (provided.length === 0 || assessment.missing.length === 0) {
         return assessment;
@@ -1231,7 +1192,6 @@ export function applyBlockProvidedCompleteness(assessment, provided) {
     }
     return { ...assessment, present, missing };
 }
-/** Optional feed-forward choices. These are not baseline completeness requirements. */
 export function optionalCapabilityChecklist(outcome, availableIds) {
     const available = availableIds ? new Set(availableIds) : undefined;
     return OPTIONAL_CAPABILITIES
@@ -1296,7 +1256,6 @@ export function assessSelectedOptionalCapabilities(source, outcome, selectedIds
         note: "Selected optional capabilities are enforced only after the user or host agent opts in through `feed_optional_capabilities`. They are source sensors, not baseline compliance rules.",
     };
 }
-/** Pure assessment over already-read source text. */
 export function assessCompleteness(source, outcome) {
     const caps = baselineCapabilities(outcome);
     const optOuts = new Map();
@@ -1339,14 +1298,13 @@ export function assessCompleteness(source, outcome) {
     }
     return { outcome, present, missing, optedOut, invalidOptOuts: invalid, note: ADVISORY_NOTE };
 }
-// ── Bounded source read (advisory; perf-bounded like the design check scan) ──
 const SCAN_EXTS = new Set([".ts", ".tsx", ".js", ".jsx", ".dart", ".kt", ".java", ".swift", ".vue"]);
 const SKIP_DIRS = new Set(["node_modules", ".git", "dist", "build", ".next", "out", "coverage", "vendor", ".dart_tool", "pods", "macos", "windows", "linux"]);
 const MAX_FILES = 1500;
 const MAX_FILE_BYTES = 1_000_000;
 export async function assessProjectCompleteness(root, outcome) {
     if (baselineCapabilities(outcome).length === 0) {
-        return null; // outcome has no completeness checklist
+        return null;
     }
     return assessCompleteness(await readProjectSource(root), outcome);
 }
@@ -1386,7 +1344,6 @@ async function readProjectSource(root) {
                     }
                 }
                 catch {
-                    // skip unreadable
                 }
             }
         }

package/dist/intelligence/grounding.js

@@ -1,27 +1,9 @@
 import { readFile } from "node:fs/promises";
 import path from "node:path";
 import { fileURLToPath } from "node:url";
-// Deterministic grounding contract for agent-driven variant selection (experience-factory rebuild,
-// Option A). The factory does NOT call a model: the driving coding agent performs the semantic
-// understanding (customer request -> variant) and hands the factory a selection. This module is the
-// factory's deterministic half — it enforces that the agent's selection is GROUNDED in the catalog
-// and surfaces honest review signals. It performs no inference and no IO in its core function, so it
-// is fully reproducible (the determinism lives here; the non-determinism lives in the visible driver).
-//
-// Contract, by evidence from the spike + stress test (benchmarks/experience-calibration/
-// semantic-understanding-spike.mjs and -stresstest.mjs):
-//   - variantId MUST be a catalog id, or the literal "none" (the agent's honest no-fit answer).
-//     Anything else is a hallucination and is REJECTED.
-//   - rationale is REQUIRED (explainability is a core principle of the factory).
-//   - confidence is expected (high|medium|low); low confidence and "none" are not failures — they are
-//     honest signals that the human/agent should reconsider or that the catalog may need a new variant.
 export const GROUNDING_SCHEMA_VERSION = "2026-06-07.vise-grounding.v1";
 export const NO_FIT = "none";
 const CONFIDENCE_VALUES = ["high", "medium", "low"];
-/**
- * Validate an agent-provided variant selection against the catalog. Pure and deterministic: given the
- * same selection and the same catalog id set it always returns the same result.
- */
 export function groundSelection(selection, catalogVariantIds) {
     const ids = [...catalogVariantIds];
     const idSet = new Set(ids);
@@ -31,7 +13,6 @@ export function groundSelection(selection, catalogVariantIds) {
     const rawConfidence = typeof selection?.confidence === "string" ? selection.confidence.trim().toLowerCase() : "";
     const isNoFit = rawVariant.toLowerCase() === NO_FIT;
     const isKnownVariant = idSet.has(rawVariant);
-    // 1. Grounding: variant must be a catalog id or the explicit no-fit answer.
     if (!isNoFit && !isKnownVariant) {
         signals.push({
             code: "hallucinated-variant",
@@ -48,7 +29,6 @@ export function groundSelection(selection, catalogVariantIds) {
             message: `The agent reported no catalog variant fits this request. Reconsider the request, or treat this as a candidate for a new catalog variant.`,
         });
     }
-    // 2. Rationale is required for explainability (applies to a real variant and to "none").
     if (!rationale) {
         signals.push({
             code: "missing-rationale",
@@ -56,7 +36,6 @@ export function groundSelection(selection, catalogVariantIds) {
             message: `A rationale is required: the selection must explain, grounded in the request and catalog, why this variant (or "${NO_FIT}") was chosen.`,
         });
     }
-    // 3. Confidence (advisory but expected). Invalid value is a contract violation; absence/low are signals.
     let confidence = null;
     if (!rawConfidence) {
         signals.push({ code: "missing-confidence", severity: "warn", message: `No confidence was provided; expected one of ${CONFIDENCE_VALUES.join(", ")}.` });
@@ -91,12 +70,10 @@ function summarize(status, variantId, signals) {
         return `Selection rejected: ${signals.filter((s) => s.severity === "error").map((s) => s.code).join(", ")}.`;
     return `Selection accepted with review signals: ${signals.map((s) => s.code).join(", ")}.`;
 }
-/** Resolve the catalog directory shipped in the package (packages/intelligence/catalog). */
 export function catalogDir() {
     const moduleDir = path.dirname(fileURLToPath(import.meta.url));
     return path.resolve(moduleDir, "..", "..", "packages", "intelligence", "catalog");
 }
-/** Load the set of valid variant ids from the declarative catalog. */
 export async function loadCatalogVariantIds(dir = catalogDir()) {
     const raw = await readFile(path.join(dir, "variants.json"), "utf8");
     const parsed = JSON.parse(raw);

package/dist/intelligence/placement.js

@@ -1,7 +1,6 @@
 import { readFileSync } from "node:fs";
 import path from "node:path";
 import { fileURLToPath } from "node:url";
-// Display order — drives CREATIVE_SURFACE_HINTS and, downstream, surfaceSequence.
 export const SURFACE_REGISTRY = [
     { id: "feed", outcome: "add-feed", label: "Feed and content surface" },
     { id: "comments", outcome: "add-comments", label: "Comments and replies" },
@@ -10,9 +9,6 @@ export const SURFACE_REGISTRY = [
     { id: "community", outcome: "add-community", label: "Community management and identity" },
     { id: "notifications", outcome: "add-notifications", label: "Notifications and activation" },
 ];
-// Scan order for reducing an object list to its surfaces/outcomes. Kept distinct from the display
-// order above to reproduce the pre-derivation if-chain output byte-for-byte (community was scanned
-// before profile). Faithful-reproduction only; could be unified if order is proven immaterial.
 const SURFACE_SCAN_ORDER = ["feed", "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));
@@ -20,8 +16,6 @@ function catalogRoot() {
     const moduleDir = path.dirname(fileURLToPath(import.meta.url));
     return path.resolve(moduleDir, "..", "..", "packages", "intelligence", "catalog");
 }
-// object id -> surface / block, in catalog declaration order. Read synchronously at module load so
-// the SOCIAL_PLUS_OBJECTS export and the lookup functions stay synchronous (matches prior contract).
 const objectSurface = new Map();
 const objectBlock = new Map();
 {
@@ -41,8 +35,6 @@ const objectBlock = new Map();
         }
     }
 }
-// SDK-backed objects are exactly those placed on a surface; app-layer (knowledge/prediction) and
-// in-development objects declare no surface and are excluded.
 export const SOCIAL_PLUS_OBJECTS = new Set(objectSurface.keys());
 export function surfaceIdsForObjects(objectIds) {
     const present = new Set(objectIds);
@@ -60,7 +52,6 @@ export function outcomesForObjects(objectIds) {
 export function blockIdForObject(objectId) {
     return objectBlock.get(objectId);
 }
-// Object ids bound to a surface, in catalog declaration order (used to build CREATIVE_SURFACE_HINTS).
 export function surfaceObjectIds(surfaceId) {
     const ids = [];
     for (const [id, surface] of objectSurface) {

package/dist/outcomes.js

@@ -17,8 +17,16 @@ export const CLASSIFY_ORDER = [
     "setup-sdk",
 ];
 const PUSH_PATTERNS = [/\b(push(?:\s+notification)?|push(?:\s+notifications)?|firebase|fcm|apns)\b/];
+const STORY_REGEX = /\bstor(?:y|ies)\s+(?:tray|ring|bar|reel|carousel|viewer|highlight|feature|collection)\b|\b(?:add|adding|build|building|create|creating|implement|implementing|show|render|rendering|display|displaying)\s+(?:a\s+|an\s+|the\s+)?(?:active\s+|community\s+)?stor(?:y|ies)\b/;
+const SEARCH_REGEX = /\b(?:search|find)\s+(?:for\s+)?(?:users?|people|communit(?:y|ies)|posts?|channels?|messages?|members?|content)\b|\b(?:user|people|communit(?:y|ies)|post|content|global|message)\s+search\b|\bsearch\s+(?:bar|screen|box|field|page|results?|ui|view|feature)\b|\bsemantic search\b|\b(?:add|adding|build|building|implement|implementing|create|creating)\s+(?:a\s+|an\s+|the\s+)?search\b/;
+const EVENT_REGEX = /\bevent\s+(?:calendar|list|feed|page|screen|details?)\b|\battendee(?:s)?\s+list\b|\bRSVP\b|\b(?:add|adding|build|building|create|creating|implement|implementing|show|display)\s+(?:a\s+|an\s+|the\s+)?events?\b/i;
+const LIVESTREAM_REGEX = /\blive\s?stream(?:ing)?\b|\blive\s+video\b|\blive\s+room\b|\b(?:add|adding|build|building|create|creating|implement|implementing|start|starting|watch|watching|play|playing)\s+(?:a\s+|an\s+|the\s+)?(?:live\s+)?(?:livestream|live\s+stream|live\s+room)\b/i;
 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/,
+    STORY_REGEX,
+    SEARCH_REGEX,
+    EVENT_REGEX,
+    LIVESTREAM_REGEX,
 ];
 const FEED_PATTERNS = [
     /\b(social feature|social features|feed|timeline|post list|news feed|create post|create a post|post creation|compose post)\b/,
@@ -32,25 +40,19 @@ const MODERATION_OUTCOME_PATTERNS = [
 const CHAT_PATTERNS = [
     /\b(chat|messaging|dm|direct message|conversation|group chat|channel|inbox)\b/,
 ];
-// Community MANAGEMENT/membership — deliberately NOT bare "community" (which
-// co-occurs with feed: "community feed" must route to add-feed, handled by
-// classify order placing add-community AFTER add-feed).
 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)/,
     /\bcommunity\s+(creation|management|members?|roles?|invitations?|categories|settings|moderation)\b/,
 ];
-// Social graph (follow/followers). "block user" is intentionally left to
-// add-moderation; blocking is still a capability under add-follow.
 const FOLLOW_PATTERNS = [
     /\b(follow|unfollow|follower|followers|following)\b/,
     /\b(social graph|user relationship|follow request|followers? list|following list)\b/,
+    /\bblocked\s+users?\b/,
+    /\bmanage\s+blocked\b/,
+    /\bblock\s*list\b/,
+    /\bunblock\b/,
 ];
-// In-app notification tray/inbox/settings. Deliberately NOT bare "notification"
-// and NOT "push notification" (which routes to setup-push).
-// "notification feed"/"notification inbox" deliberately excluded — "feed" and
-// "inbox" are claimed by add-feed / add-chat respectively. Tray/center/in-app/
-// settings are non-colliding.
 const NOTIFICATION_PATTERNS = [
     /\b(notification tray|notification cent(?:er|re)|in-?app notification)/,
     /\bnotification (?:setting|preference)/,
@@ -58,26 +60,46 @@ const NOTIFICATION_PATTERNS = [
 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/];
-// Multi-surface social requests must not collapse to the first matching single
-// outcome. A request like "feed + chat + profile" needs an explicit surface
-// choice or separate contracts, otherwise chat/profile gaps escape an add-feed
-// compliance sidecar.
 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 DESIGN_REGEX = /\bdesign token|design tokens|theme|same design|design system|brand/i;
 export function classifyOutcome(request) {
     const normalized = request.toLowerCase();
-    // Precedence: a feed/timeline build that also mentions comments is a feed
-    // build, not a standalone "add comments to existing content" task. add-feed
-    // carries conditional comment guidance, so a multi-feature feed request must
-    // route there — otherwise add-comments (which precedes add-feed in the
-    // classify order) wins on the bare word "comment" and silently drops every
-    // feed/avatar/poll/notification step. Pure comment requests (no feed signal)
-    // still fall through to add-comments below.
     const matchesFeed = outcomeRegistry["add-feed"].patterns.some((p) => p.test(normalized));
     const matchesComments = outcomeRegistry["add-comments"].patterns.some((p) => p.test(normalized));
     if (matchesFeed && matchesComments) {
         return "add-feed";
     }
+    if (STORY_REGEX.test(normalized)) {
+        if (matchesFeed) {
+            return "add-feed";
+        }
+        if (matchesComments) {
+            return "add-comments";
+        }
+        if (outcomeRegistry["add-chat"].patterns.some((p) => p.test(normalized))) {
+            return "add-chat";
+        }
+    }
+    if (SEARCH_REGEX.test(normalized)) {
+        if (matchesFeed) {
+            return "add-feed";
+        }
+        if (matchesComments) {
+            return "add-comments";
+        }
+        if (outcomeRegistry["add-chat"].patterns.some((p) => p.test(normalized))) {
+            return "add-chat";
+        }
+        if (outcomeRegistry["add-community"].patterns.some((p) => p.test(normalized))) {
+            return "add-community";
+        }
+        if (outcomeRegistry["add-follow"].patterns.some((p) => p.test(normalized))) {
+            return "add-follow";
+        }
+    }
+    if (LIVESTREAM_REGEX.test(normalized) && matchesFeed) {
+        return "add-feed";
+    }
     for (const id of CLASSIFY_ORDER) {
         const def = outcomeRegistry[id];
         if (def.patterns.some((pattern) => pattern.test(normalized))) {
@@ -1062,7 +1084,7 @@ const addChat = {
             { 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 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: "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"] },
             { 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"] },
         ];