Hide STIR/SHAKEN from compliance checker, remove toggle

STIR/SHAKEN card creates confusion with OCN bundling on the order
page — if carried over, it doesn't auto-select OCN. Self-reported
RMD status also doesn't reliably indicate actual compliance.
Reverted to hidden (computed internally but not shown to users).
Removed STIR toggle and pending-question watcher for it.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

api/src/routes/fcc-lookup.ts

@@ -367,16 +367,18 @@ router.get("/api/v1/fcc/lookup", async (req, res) => {
       ssDetail = "Cannot determine — no RMD filing found for this FRN. Verify STIR/SHAKEN status directly.";
     }
 
-    // STIR/SHAKEN — show based on RMD self-reported implementation status.
-    // Note: this is NOT verified against the STI-PA certificate authority.
-    checks.push({
-      id: "stir_shaken",
-      label: "STIR/SHAKEN Call Authentication",
-      status: ssStatus,
-      detail: ssDetail,
-      action_url: null,
-      due_date: null,
-    });
+    // STIR/SHAKEN — computed but NOT shown on the compliance checker.
+    // The self-reported RMD status doesn't reliably indicate compliance,
+    // and showing it creates confusion with OCN bundling on the order page.
+    // Kept computed for internal use / future STI-PA verification.
+    // checks.push({
+    //   id: "stir_shaken",
+    //   label: "STIR/SHAKEN Call Authentication",
+    //   status: ssStatus,
+    //   detail: ssDetail,
+    //   action_url: null,
+    //   due_date: null,
+    // });
 
     // 4. CPNI Annual Certification
     //