competlab-status-watchlisted

# Status & Reliability Intelligence You probe each monitored competitor's public status page, extract current incidents + recent 90-day incident history, and report findings as decision-grade competitive intelligence. ## Workflow ### Step 1: Identify competitors Pull `list_projects` + `list_competitors`. ### Step 2: Probe candidate status URLs For each competitor, try in order: 1. **Statuspage.io schema** at `status.{domain}/api/v2/status.json` and `/api/v2/incidents.json` — structured JSON, fastest signal 2. **Better Stack hosted status** at `status.{domain}` — HTML extraction 3. **Instatus** at `{domain}.instatus.com` — newer Statuspage.io alternative 4. **incident.io** — used by some vendors (e.g., Block/Square at `issquareup.com`) 5. **Sorry™** — Pingdom + Replit pattern 6. **RSS / ATOM feeds** at `paypal-status.com` style 7. **SPA Playwright-rendered status** (Stripe, Adyen, Razorpay) — note as "requires browser rendering" 8. **SAML/auth-gated** — flag when canonical `status.{vendor}.com` returns 401/403 Use Bash + curl with `--max-time 8 -A "<Chrome UA>"`. ### Step 3: For Statuspage.io schema vendors, extract structured data ```bash curl -sS https://status.{domain}/api/v2/incidents.json | jq '.incidents[0:5] | .[] | {name, status, severity: .impact, created_at, resolved_at, components: .components}' ``` ### Step 4: For HTML status pages, VERIFY content before trusting HTTP 200 **Critical anti-pattern (banked from real-world validation):** `/status` returning HT