Reviewed snapshots, not live browser scraping

What the web app reads

Pulse Draft Kit web reads the same app-safe published snapshot contract used by the app path. A guarded backend workflow reviews source material, prepares app-safe player intel, and publishes approved snapshots for the app and web to consume.

reviewed backend workflow → app-safe snapshot → read-only app/web clients

What appears in the web app

• Player Pulse cards summarize reviewed player-specific draft signals, including direction, confidence, injury state, reasons, and source counts.
• Source Breakdown shows reviewed source notes and proof links for players where that trail has been explicitly published.
• Pulse Heat (the cheat sheet’s 🌶️/❄️ toggle) marks a small set of conviction buys and fades computed from published signals — opportunity data, reviewed source movement, and our projection stance. Every icon carries its reasons; most players deliberately stay unmarked.
• Honest empty states stay visible when a player, Main Feed, injury update, or Source Breakdown lane has not been published yet.

What the browser does not do

• The web app does not scrape articles, videos, podcasts, or social posts in your browser.
• The web app does not score players, normalize raw artifacts, or publish content.
• The web app does not expose admin controls, scheduler controls, review queues, internal tables, or Supabase write paths.
• Main Feed publishing and Player Pulse movement remain separate approval-gated lanes.

Current snapshot state