qa-baseline

# QA Baseline Create `.maestro/features/<id>/baseline.md` before feature edits start. This is the behavior oracle for `feature ship`, not a list of tests. Activate: `maestro hook record --event skill_activation --skill qa-baseline` ## Use - `maestro feature accept` is blocked on missing or empty `baseline.md`. - A behavioral amend added acceptance or area and the baseline must be fresh. - The feature touches user-visible, data, security, persistence, compatibility, release, or workflow behavior. ## Do 1. Read `maestro feature show <id>` for acceptance criteria and areas. 2. Identify the smallest real user/operator scenarios that could regress. Cover risk dimensions that matter: actor, entrypoint, state/lifecycle, data shape, environment/channel, integration boundary, permissions/trust, failure recovery, and non-functional behavior. 3. Include a workflow chain when the feature changes a trunk journey, for example setup -> create work -> record proof -> verify -> inspect output. Keep isolated probes for safety-critical local invariants such as rollback, auth, parsers, schemas, install ownership, migration, and destructive guards. 4. Give each behavioral scenario a stable `[bl-NNN]` id. These ids are the ship coverage units. No behavioral surface means record that explicitly and use no ids. 5. Capture the current-behavior oracle: setup, action, expected observable result, evidence to capture, and reproduction steps. 6. Write the contract below ...