@amityco/social-plus-vise 1.3.0 → 1.4.0

package/rules/feed.yaml

@@ -2,6 +2,72 @@
   "domain": "feed",
   "schema_version": 1,
   "rules": [
+    {
+      "id": "typescript.feed.source-used",
+      "version": 1,
+      "title": "TypeScript feed integration must use SDK post APIs",
+      "severity": "warning",
+      "rationale": "A community/profile-only SDK integration is not an add-feed implementation. Feed surfaces must query or create SDK posts and render SDK post data.",
+      "applies_when": {
+        "platforms": ["typescript"],
+        "outcomes": ["add-feed", "validate-setup"]
+      },
+      "enforcement": {
+        "deterministic": [
+          { "check": "validator-finding-absent", "finding_rule_id": "typescript.feed.source-used" }
+        ],
+        "attestation": {
+          "allowed": false,
+          "host_agent_min_confidence": "high",
+          "human_allowed": false,
+          "evidence_required": []
+        }
+      }
+    },
+    {
+      "id": "react-native.feed.source-used",
+      "version": 1,
+      "title": "React Native feed integration must use SDK post APIs",
+      "severity": "warning",
+      "rationale": "A community/profile-only SDK integration is not an add-feed implementation. Feed surfaces must query or create SDK posts and render SDK post data.",
+      "applies_when": {
+        "platforms": ["react-native"],
+        "outcomes": ["add-feed", "validate-setup"]
+      },
+      "enforcement": {
+        "deterministic": [
+          { "check": "validator-finding-absent", "finding_rule_id": "react-native.feed.source-used" }
+        ],
+        "attestation": {
+          "allowed": false,
+          "host_agent_min_confidence": "high",
+          "human_allowed": false,
+          "evidence_required": []
+        }
+      }
+    },
+    {
+      "id": "flutter.feed.source-used",
+      "version": 1,
+      "title": "Flutter feed integration must use SDK post APIs",
+      "severity": "warning",
+      "rationale": "A community/profile-only SDK integration is not an add-feed implementation. Feed surfaces must query or create SDK posts and render SDK post data.",
+      "applies_when": {
+        "platforms": ["flutter"],
+        "outcomes": ["add-feed", "validate-setup"]
+      },
+      "enforcement": {
+        "deterministic": [
+          { "check": "validator-finding-absent", "finding_rule_id": "flutter.feed.source-used" }
+        ],
+        "attestation": {
+          "allowed": false,
+          "host_agent_min_confidence": "high",
+          "human_allowed": false,
+          "evidence_required": []
+        }
+      }
+    },
     {
       "id": "typescript.feed.target.literal",
       "version": 1,
@@ -1292,6 +1358,191 @@
         }
       }
     },
+    {
+      "id": "typescript.feed.post-body-rendered",
+      "version": 1,
+      "symbol_anchored": {"platform":"typescript","basis":"pattern"},
+      "title": "TypeScript post cards must render the post body when present",
+      "severity": "warning",
+      "rationale": "A feed card that shows only postId, counts, or chrome hides the user's actual post. Render the normal body/description/caption when present. A title field is optional and metadata/custom title payloads are not required.",
+      "applies_when": {
+        "platforms": [
+          "typescript"
+        ],
+        "outcomes": [
+          "add-feed",
+          "validate-setup"
+        ]
+      },
+      "enforcement": {
+        "deterministic": [
+          {
+            "check": "validator-finding-absent",
+            "finding_rule_id": "typescript.feed.post-body-rendered"
+          }
+        ],
+        "attestation": {
+          "allowed": true,
+          "host_agent_min_confidence": "high",
+          "human_allowed": true,
+          "evidence_required": [
+            {
+              "field": "post_body_rendering",
+              "description": "Where the post body/description/caption is read from the SDK object and rendered. Do not use title/metadata/custom payload as required evidence.",
+              "upload_policy": "upload-with-consent"
+            }
+          ]
+        }
+      }
+    },
+    {
+      "id": "react-native.feed.post-body-rendered",
+      "version": 1,
+      "symbol_anchored": {"platform":"react-native","basis":"pattern"},
+      "title": "React Native post cards must render the post body when present",
+      "severity": "warning",
+      "rationale": "A feed card that shows only postId, counts, or chrome hides the user's actual post. Render the normal body/description/caption when present. A title field is optional and metadata/custom title payloads are not required.",
+      "applies_when": {
+        "platforms": [
+          "react-native"
+        ],
+        "outcomes": [
+          "add-feed",
+          "validate-setup"
+        ]
+      },
+      "enforcement": {
+        "deterministic": [
+          {
+            "check": "validator-finding-absent",
+            "finding_rule_id": "react-native.feed.post-body-rendered"
+          }
+        ],
+        "attestation": {
+          "allowed": true,
+          "host_agent_min_confidence": "high",
+          "human_allowed": true,
+          "evidence_required": [
+            {
+              "field": "post_body_rendering",
+              "description": "Where the post body/description/caption is read from the SDK object and rendered. Do not use title/metadata/custom payload as required evidence.",
+              "upload_policy": "upload-with-consent"
+            }
+          ]
+        }
+      }
+    },
+    {
+      "id": "android.feed.post-body-rendered",
+      "version": 1,
+      "symbol_anchored": {"platform":"android","basis":"pattern"},
+      "title": "Android post cards must render the post body when present",
+      "severity": "warning",
+      "rationale": "A feed card that shows only postId, counts, or chrome hides the user's actual post. Render the normal body/description/caption when present. A title field is optional and metadata/custom title payloads are not required.",
+      "applies_when": {
+        "platforms": [
+          "android"
+        ],
+        "outcomes": [
+          "add-feed",
+          "validate-setup"
+        ]
+      },
+      "enforcement": {
+        "deterministic": [
+          {
+            "check": "validator-finding-absent",
+            "finding_rule_id": "android.feed.post-body-rendered"
+          }
+        ],
+        "attestation": {
+          "allowed": true,
+          "host_agent_min_confidence": "high",
+          "human_allowed": true,
+          "evidence_required": [
+            {
+              "field": "post_body_rendering",
+              "description": "Where the post body/description/caption is read from the SDK object and rendered. Do not use title/metadata/custom payload as required evidence.",
+              "upload_policy": "upload-with-consent"
+            }
+          ]
+        }
+      }
+    },
+    {
+      "id": "flutter.feed.post-body-rendered",
+      "version": 1,
+      "symbol_anchored": {"platform":"flutter","basis":"pattern"},
+      "title": "Flutter post cards must render the post body when present",
+      "severity": "warning",
+      "rationale": "A feed card that shows only postId, counts, or chrome hides the user's actual post. Render the normal body/description/caption when present. A title field is optional and metadata/custom title payloads are not required.",
+      "applies_when": {
+        "platforms": [
+          "flutter"
+        ],
+        "outcomes": [
+          "add-feed",
+          "validate-setup"
+        ]
+      },
+      "enforcement": {
+        "deterministic": [
+          {
+            "check": "validator-finding-absent",
+            "finding_rule_id": "flutter.feed.post-body-rendered"
+          }
+        ],
+        "attestation": {
+          "allowed": true,
+          "host_agent_min_confidence": "high",
+          "human_allowed": true,
+          "evidence_required": [
+            {
+              "field": "post_body_rendering",
+              "description": "Where the post body/description/caption is read from the SDK object and rendered. Do not use title/metadata/custom payload as required evidence.",
+              "upload_policy": "upload-with-consent"
+            }
+          ]
+        }
+      }
+    },
+    {
+      "id": "ios.feed.post-body-rendered",
+      "version": 1,
+      "symbol_anchored": {"platform":"ios","basis":"pattern"},
+      "title": "iOS post cards must render the post body when present",
+      "severity": "warning",
+      "rationale": "A feed card that shows only postId, counts, or chrome hides the user's actual post. Render the normal body/description/caption when present. A title field is optional and metadata/custom title payloads are not required.",
+      "applies_when": {
+        "platforms": [
+          "ios"
+        ],
+        "outcomes": [
+          "add-feed",
+          "validate-setup"
+        ]
+      },
+      "enforcement": {
+        "deterministic": [
+          {
+            "check": "validator-finding-absent",
+            "finding_rule_id": "ios.feed.post-body-rendered"
+          }
+        ],
+        "attestation": {
+          "allowed": true,
+          "host_agent_min_confidence": "high",
+          "human_allowed": true,
+          "evidence_required": [
+            {
+              "field": "post_body_rendering",
+              "description": "Where the post body/description/caption is read from the SDK object and rendered. Do not use title/metadata/custom payload as required evidence.",
+              "upload_policy": "upload-with-consent"
+            }
+          ]
+        }
+      }
+    },
     {
       "id": "typescript.feed.target-type-explicit",
       "version": 1,

package/rules/invitation.yaml

@@ -5,6 +5,7 @@
     {
       "id": "typescript.invitation.live-collection",
       "version": 1,
+      "symbol_anchored": { "platform": "typescript", "types": ["InvitationRepository"], "members": ["getMyCommunityInvitations"], "basis": "names-only" },
       "title": "TypeScript community-invitations list should use the reactive getMyCommunityInvitations LiveCollection",
       "severity": "warning",
       "rationale": "Community invitation lists are Live Collections (Amity.InvitationLiveCollection). An invitations screen rendered from a one-shot fetch (no callback) never refreshes as invitations arrive or transition pending -> accepted/rejected/cancelled. Pass the live callback: getMyCommunityInvitations(params, callback). If a static one-shot snapshot is truly intended, add // vise: one-shot query.",
@@ -18,6 +19,7 @@
     {
       "id": "react-native.invitation.live-collection",
       "version": 1,
+      "symbol_anchored": { "platform": "react-native", "types": ["InvitationRepository"], "members": ["getMyCommunityInvitations"], "basis": "names-only" },
       "title": "React Native community-invitations list should use the reactive getMyCommunityInvitations LiveCollection",
       "severity": "warning",
       "rationale": "Community invitation lists are Live Collections. An invitations screen rendered from a one-shot fetch (no callback) never refreshes as invitations arrive or transition pending -> accepted/rejected/cancelled. Pass the live callback: getMyCommunityInvitations(params, callback). If a static one-shot snapshot is truly intended, add // vise: one-shot query.",
@@ -31,6 +33,7 @@
     {
       "id": "android.invitation.live-collection",
       "version": 1,
+      "symbol_anchored": { "platform": "android", "types": ["AmityInvitationRepository"], "members": ["getMyCommunityInvitations"], "basis": "names-only" },
       "title": "Android community-invitations list should observe the invitation PagingData stream",
       "severity": "warning",
       "rationale": "Community invitation lists are Live Collections (getMyCommunityInvitations / getMemberInvitations return Flowable<PagingData<AmityInvitation>>). An invitations screen rendered from a one-shot fetch never refreshes as invitations arrive or change status. Observe the stream instead: getMyCommunityInvitations().doOnNext { _: PagingData -> }.subscribe(). If a static one-shot snapshot is truly intended, add // vise: one-shot query.",
@@ -44,6 +47,7 @@
     {
       "id": "ios.invitation.live-collection",
       "version": 1,
+      "symbol_anchored": { "platform": "ios", "types": ["AmityInvitationRepository"], "members": ["getMyCommunityInvitations"], "basis": "names-only" },
       "title": "iOS community-invitations list should observe the invitation LiveCollection",
       "severity": "warning",
       "rationale": "Community invitation lists are Live Collections (getMyCommunityInvitations / getMemberInvitations return AmityCollection<AmityInvitation>). An invitations screen rendered from a one-shot snapshot never refreshes as invitations arrive or change status. Observe the collection instead: getMyCommunityInvitations().observe { ... }. If a static one-shot snapshot is truly intended, add // vise: one-shot query.",

package/rules/live-data.yaml

@@ -503,6 +503,116 @@
           ]
         }
       }
+    },
+    {
+      "id": "android.live-collection.session-ready-requery",
+      "version": 1,
+      "title": "Android live queries must (re-)run when the session becomes active after the UI mounts",
+      "severity": "warning",
+      "rationale": "The screen that consumes live data usually mounts before login resolves. If the live query is gated on a one-shot session-readiness check at mount (onCreate / onViewCreated / a no-key LaunchedEffect) that returns early and never re-fires, the surface stays permanently empty even though it compiles and the build is green. On a warm device login resolves first by chance; on a cold start the check fires too early and nothing re-runs the query.",
+      "feedforward": "Drive the live query off a REACTIVE session-readiness signal — observe the session/auth state (e.g. a StateFlow) and seed it synchronously from its current value — so the query (re-)runs when the session becomes active, whether that is before or after the view mounted. Do not gate it on a one-shot readiness check at mount (onCreate / onViewCreated / no-key LaunchedEffect) that never re-fires. Render the not-ready and error states as retryable (a visible retry affordance), never a silent dead end.",
+      "applies_when": {
+        "platforms": ["android"],
+        "outcomes": ["add-feed", "add-comments", "add-chat", "setup-live-data", "validate-setup"]
+      },
+      "enforcement": {
+        "deterministic": [
+          { "check": "runtime-smoke-evidence-passed", "path": "sp-vise/evidence/runtime-smoke.json" }
+        ],
+        "attestation": {
+          "allowed": false,
+          "human_allowed": false,
+          "evidence_required": []
+        }
+      }
+    },
+    {
+      "id": "flutter.live-collection.session-ready-requery",
+      "version": 1,
+      "title": "Flutter live queries must (re-)run when the session becomes active after the UI mounts",
+      "severity": "warning",
+      "rationale": "The widget that consumes live data usually mounts before login resolves. If the live query is gated on a one-shot session-readiness check at mount (initState) that returns early and never re-fires, the surface stays permanently empty even though it compiles and the build is green. On a warm device login resolves first by chance; on a cold start the check fires too early and nothing re-runs the query.",
+      "feedforward": "Drive the live query off a REACTIVE session-readiness signal — observe the session/auth state (e.g. a Stream/StateNotifier) and seed it synchronously from its current value — so the query (re-)runs when the session becomes active, whether that is before or after the widget mounted. Do not gate it on a one-shot readiness check in initState that never re-fires. Render the not-ready and error states as retryable (a visible retry affordance), never a silent dead end.",
+      "applies_when": {
+        "platforms": ["flutter"],
+        "outcomes": ["add-feed", "add-comments", "add-chat", "setup-live-data", "validate-setup"]
+      },
+      "enforcement": {
+        "deterministic": [
+          { "check": "runtime-smoke-evidence-passed", "path": "sp-vise/evidence/runtime-smoke.json" }
+        ],
+        "attestation": {
+          "allowed": false,
+          "human_allowed": false,
+          "evidence_required": []
+        }
+      }
+    },
+    {
+      "id": "ios.live-collection.session-ready-requery",
+      "version": 1,
+      "title": "iOS live queries must (re-)run when the session becomes active after the UI mounts",
+      "severity": "warning",
+      "rationale": "The view that consumes live data usually mounts before login resolves. If the live query is gated on a one-shot session-readiness check at mount (.onAppear / viewDidLoad) that returns early and never re-fires, the surface stays permanently empty even though it compiles and the build is green. On a warm machine login resolves first by chance; on a cold start the check fires too early and nothing re-runs the query.",
+      "feedforward": "Drive the live query off a REACTIVE session-readiness signal — observe the SDK session state (e.g. an @Published value sink on the client's session state) and seed it synchronously from its current value — so the query (re-)runs when the session becomes active, whether that is before or after the view appeared. Do not gate it on a one-shot isReady read in .onAppear that never re-fires. Render the not-ready and error states as retryable (a visible retry affordance), never a silent dead end.",
+      "applies_when": {
+        "platforms": ["ios"],
+        "outcomes": ["add-feed", "add-comments", "add-chat", "setup-live-data", "validate-setup"]
+      },
+      "enforcement": {
+        "deterministic": [
+          { "check": "runtime-smoke-evidence-passed", "path": "sp-vise/evidence/runtime-smoke.json" }
+        ],
+        "attestation": {
+          "allowed": false,
+          "human_allowed": false,
+          "evidence_required": []
+        }
+      }
+    },
+    {
+      "id": "typescript.live-collection.session-ready-requery",
+      "version": 1,
+      "title": "TypeScript live queries must (re-)run when the session becomes active after the component mounts",
+      "severity": "warning",
+      "rationale": "The component that consumes live data usually mounts before login resolves. If the live query is gated on a one-shot session-readiness check at mount (useEffect([]) or a single read of client.sessionState) that returns early and never re-fires, the surface stays permanently empty even though it compiles and the build is green. On a warm machine login resolves first by chance; on a cold start the check fires too early and nothing re-runs the query.",
+      "feedforward": "Drive the live query off a REACTIVE session-readiness signal — subscribe to the client session state AND seed it synchronously (e.g. useState(client.sessionState) so an already-established session is not missed) — so the query (re-)runs when the session becomes active, whether that is before or after the component mounted. Do not gate it on a single read of client.sessionState in a mount-only useEffect that never re-fires. Render the not-ready and error states as retryable (a visible retry affordance), never a silent dead end.",
+      "applies_when": {
+        "platforms": ["typescript"],
+        "outcomes": ["add-feed", "add-comments", "add-chat", "setup-live-data", "validate-setup"]
+      },
+      "enforcement": {
+        "deterministic": [
+          { "check": "runtime-smoke-evidence-passed", "path": "sp-vise/evidence/runtime-smoke.json" }
+        ],
+        "attestation": {
+          "allowed": false,
+          "human_allowed": false,
+          "evidence_required": []
+        }
+      }
+    },
+    {
+      "id": "react-native.live-collection.session-ready-requery",
+      "version": 1,
+      "title": "React Native live queries must (re-)run when the session becomes active after the component mounts",
+      "severity": "warning",
+      "rationale": "The screen that consumes live data usually mounts before login resolves. If the live query is gated on a one-shot session-readiness check at mount (useEffect([]) or a single read of client.sessionState) that returns early and never re-fires, the surface stays permanently empty even though it compiles and the build is green. On a warm device login resolves first by chance; on a cold start the check fires too early and nothing re-runs the query.",
+      "feedforward": "Drive the live query off a REACTIVE session-readiness signal — subscribe to the client session state AND seed it synchronously (e.g. useState(client.sessionState) so an already-established session is not missed) — so the query (re-)runs when the session becomes active, whether that is before or after the screen mounted. Do not gate it on a single read of client.sessionState in a mount-only useEffect that never re-fires. Render the not-ready and error states as retryable (a visible retry affordance), never a silent dead end.",
+      "applies_when": {
+        "platforms": ["react-native"],
+        "outcomes": ["add-feed", "add-comments", "add-chat", "setup-live-data", "validate-setup"]
+      },
+      "enforcement": {
+        "deterministic": [
+          { "check": "runtime-smoke-evidence-passed", "path": "sp-vise/evidence/runtime-smoke.json" }
+        ],
+        "attestation": {
+          "allowed": false,
+          "human_allowed": false,
+          "evidence_required": []
+        }
+      }
     }
   ]
 }

package/rules/notification-tray.yaml

@@ -5,6 +5,7 @@
     {
       "id": "typescript.notification-tray.live-collection",
       "version": 1,
+      "symbol_anchored": { "platform": "typescript", "types": ["notificationTray"], "members": ["getNotificationTrayItems"], "basis": "names-only" },
       "title": "TypeScript notification tray should use the reactive Tray LiveCollection",
       "severity": "warning",
       "rationale": "The notification tray is a Live Collection — it updates as notifications arrive and seen-state changes. A one-shot getNotificationTrayItems (no callback) renders a tray that never updates. Pass the live callback: notificationTray.getNotificationTrayItems(params, callback).",
@@ -30,6 +31,7 @@
     {
       "id": "react-native.notification-tray.live-collection",
       "version": 1,
+      "symbol_anchored": { "platform": "react-native", "types": ["notificationTray"], "members": ["getNotificationTrayItems"], "basis": "names-only" },
       "title": "React Native notification tray should use the reactive Tray LiveCollection",
       "severity": "warning",
       "rationale": "The notification tray is a Live Collection — it updates as notifications arrive and seen-state changes. A one-shot getNotificationTrayItems (no callback) renders a tray that never updates. Pass the live callback: notificationTray.getNotificationTrayItems(params, callback).",
@@ -55,6 +57,7 @@
     {
       "id": "android.notification-tray.live-collection",
       "version": 1,
+      "symbol_anchored": { "platform": "android", "types": ["AmityNotificationTray"], "members": ["getNotificationTrayItems"], "basis": "names-only" },
       "title": "Android notification tray should use the reactive Tray LiveCollection",
       "severity": "warning",
       "rationale": "The notification tray is a Live Collection — it updates as notifications arrive and seen-state changes. A one-shot fetch renders a tray that never updates. Observe the collection instead (PagingData via .doOnNext { ... }.subscribe()).",
@@ -80,6 +83,7 @@
     {
       "id": "ios.notification-tray.live-collection",
       "version": 1,
+      "symbol_anchored": { "platform": "ios", "types": ["AmityNotificationTray"], "members": ["getNotificationTrayItems"], "basis": "names-only" },
       "title": "iOS notification tray should use the reactive Tray LiveCollection",
       "severity": "warning",
       "rationale": "The notification tray is a Live Collection — it updates as notifications arrive and seen-state changes. A one-shot completion-handler fetch renders a tray that never updates. Observe the collection instead: getNotificationTrayItems(...).observe { ... }.",

package/rules/poll.yaml

@@ -5,6 +5,7 @@
     {
       "id": "typescript.poll.vote-status-guard",
       "version": 1,
+      "symbol_anchored": { "platform": "typescript", "types": ["PollRepository"], "members": ["votePoll"], "basis": "names-only" },
       "title": "TypeScript poll voting must check poll status / voted-state before allowing a vote",
       "severity": "warning",
       "rationale": "A poll renderer that wires votePoll for each answer but never reads poll.status / poll.isVoted / answer.voteCount lets the user vote on a closed poll (silent backend reject), re-vote without feedback, and shows no results. Gate the vote on poll.status and poll.isVoted, and render answer.voteCount / answer.isVotedByUser.",
@@ -18,6 +19,7 @@
     {
       "id": "react-native.poll.vote-status-guard",
       "version": 1,
+      "symbol_anchored": { "platform": "react-native", "types": ["PollRepository"], "members": ["votePoll"], "basis": "names-only" },
       "title": "React Native poll voting must check poll status / voted-state before allowing a vote",
       "severity": "warning",
       "rationale": "A poll renderer that wires votePoll for each answer but never reads poll.status / poll.isVoted / answer.voteCount lets the user vote on a closed poll (silent backend reject), re-vote without feedback, and shows no results. Gate the vote on poll.status and poll.isVoted, and render answer.voteCount / answer.isVotedByUser.",
@@ -31,6 +33,7 @@
     {
       "id": "android.poll.vote-status-guard",
       "version": 1,
+      "symbol_anchored": { "platform": "android", "types": ["AmityPollRepository"], "members": ["votePoll"], "basis": "names-only" },
       "title": "Android poll voting must check poll status / voted-state before allowing a vote",
       "severity": "warning",
       "rationale": "A poll renderer that wires votePoll for each answer but never reads poll.getStatus() / poll.isVoted / answer.voteCount lets the user vote on a closed poll (silent backend reject), re-vote without feedback, and shows no results. Gate the vote on poll status and isVoted, and render answer.voteCount / answer.isVotedByUser.",
@@ -44,6 +47,7 @@
     {
       "id": "ios.poll.vote-status-guard",
       "version": 1,
+      "symbol_anchored": { "platform": "ios", "types": ["AmityPollRepository"], "members": ["votePoll"], "basis": "names-only" },
       "title": "iOS poll voting must check poll status / voted-state before allowing a vote",
       "severity": "warning",
       "rationale": "A poll renderer that wires votePoll for each answer but never reads poll.isClosed / poll.isVoted / poll.voteCount lets the user vote on a closed poll (silent backend reject), re-vote without feedback, and shows no results. Gate the vote on poll.isClosed and poll.isVoted, and render answer.voteCount / answer.isVotedByUser.",
@@ -57,6 +61,7 @@
     {
       "id": "flutter.poll.vote-status-guard",
       "version": 1,
+      "symbol_anchored": { "platform": "flutter", "types": ["PollRepository"], "members": ["vote"], "basis": "names-only" },
       "title": "Flutter poll voting must check poll status / voted-state before allowing a vote",
       "severity": "warning",
       "rationale": "A poll renderer that wires vote(pollId:) for each answer but never reads poll.status / poll.isVoted / answer.voteCount lets the user vote on a closed poll (silent backend reject), re-vote without feedback, and shows no results. Gate the vote on poll.status (AmityPollStatus) and poll.isVoted, and render answer.voteCount / answer.isVotedByUser.",