qol-adversarial-testlisted

# Adversarial Test Treat adversarial testing as an evidence-producing engineering loop, not random abuse. Attack explicit invariants through the same surface used by users and production, preserve every real failure, and turn stable attacks into one repeatable workflow. ## Establish authority Classify the request before editing product code: - **Test, diagnose, or report:** reproduce and explain bugs; do not implement fixes. - **Battle-harden, stabilize, or make it work:** reproduce, add regression coverage, fix, and verify. - **Ambiguous:** continue read-only and isolated testing; ask before a product change that materially expands scope. Never let a test-storm broaden access to production data, destructive operations, external messages, or unrelated systems. ## Run the loop 1. **Load local rules.** Read repository instructions and applicable testing, architecture, platform, tracing, VM, and commit skills before acting. 2. **Define the contract.** Write the target, real entrypoint, user-visible invariants, exact platform/build/session, source revision and worktree state, state touched, destructive boundary, and pass criteria. Preserve unrelated user changes. 3. **Map the path.** Trace the request from entrypoint through process, IPC/network, persistence, and platform boundaries. Locate existing tests, isolation seams, logs, traces, cleanup commands, and native workflow runners. Stop reconnaissance once the real entrypoint, mutable boundaries, oracle, and safe launch c