tutti-record-agent-session-replay

# Qualify Tutti Agent Session Replay Cassettes Work from the Tutti checkout. Keep product implementation and the generic runner in Tutti; keep Case metadata, **scenario scripts**, fixtures, qualified Cassettes, and evidence in the external case repository (`tutti-os/tutti-replay`). Mental model (script-first, not UI recording): 1. Humans/agents **write** a deterministic `scenarios/*.mjs` (prepare / drive / assert) in the case repository — that script is the recording plan. 2. **Record** means: Tutti runner launches Desktop, CDP-executes that script against a **live** Provider, and captures the Cassette. There is no separate click-to-record UI workflow for Session Replay. 3. Day-to-day Record/Replay is usually triggered from the case repository QA console; this skill is for Tutti-side CLI qualification, diagnosis, runner or Replay product defects, and new Provider capture support. Prove qualification in this order: `existing scenario script -> live Record (script + Provider) -> structural audit -> fresh Replay -> optional publication` Never call a Cassette qualified until Record, audit, and a fresh isolated Replay have all passed. If the scenario script itself is missing or wrong, stop and use the case repository `write-replay-case` skill — do not invent Cases inside Tutti. Qualification is assertion-specific, not command-specific. A `replay passed` exit proves transport and semantic playback, but does not prove that every Case action ran during Replay. B...