set-lineuplisted

# Set Lineup (Browser Playbook) Set a lineup on the user's platform through their own logged-in browser session. Two phases, one hard gate: **never save a lineup change without explicit user confirmation.** ## Execution boundary - Treat this as an execution skill, not a general advice skill. If the user already named the swaps, carry out those swaps. - If the user asks you to "set my lineup" without naming the swaps, read the live roster and then run `lineup-strategy:start-sit` if it is installed. Its globally optimized, evidence-qualified recommendation becomes the proposed target lineup; it is not authorization to apply anything. - If `lineup-strategy:start-sit` is unavailable, either ask the user to name the intended swaps or reproduce its full decision contract inline before returning to execution: optimize the whole legal lineup rather than filling slots greedily, honor locks and kickoff times, preserve late-swap optionality, timestamp the analysis, and require official status plus a second credible source for any injury-driven change. A page-visible projection or status tag alone is not enough. If the user is still debating broader ranges of outcomes or waiver implications, finish that read-only analysis before proceeding. ## Ground rules (all roster-ops skills) - **The user's session is the auth.** Never ask for, read, store, or type usernames, passwords, or 2FA codes. If a login page, 2FA challenge, captcha, or "unusual activity" interstitial appears **at any poi