Adversarial lifecycle setup

Adversarial regressions must create state before the handling operation, exercise delete-then-recreate across lifecycle boundaries, and modify state while capture is disabled. Constructing the desired final state directly looks simpler, but bypasses stale-cache, trigger-visibility, and transition bugs. Every skip or early-return guard needs a counterexample that would wrongly skip required work, especially NOT EXISTS, latest <> 'upsert', and content-match conditions.