waiver-scanlisted

# Waiver Scan: Fit Over Fame Rank available players against **this roster's holes**, not a generic top-adds list. A backup RB one injury from a workload is worth more to a team with a thin RB room than the "consensus #1 add" WR is to a team already starting three good ones. ## Step 1: Load context Read `leagues.md` from the project root first — the fields that matter here are scoring, starting slots, waiver system, playoff weeks, and any weekly acquisition cap. If the file is missing or those fields are blank, ask for them and suggest running `fantasy-league-setup:league-config`. If more than one league is defined, use the one marked `(default)`. An acquisition cap changes everything downstream: where adds are limited, each claim must clear a much higher bar and churning streamers is off the table. Pin time-sensitive recommendations to an **as-of** timestamp. When a player's value depends on an injury, benching, suspension, or activation, cite both the official status input and a second credible source before treating the role change as settled. If the evidence is incomplete, keep the ranking provisional and say the default action is to wait rather than force a move. ## Step 2: Get the two inputs 1. **The user's roster** — read from their platform if browser automation is available, otherwise pasted. Include the current week and any injury designations. 2. **The available player pool** — read the platform's free-agent list directly, or ask for a paste. Do not rely on o