Awesome Tests

Critical rules

Before any activity, read references/test-quality-gates.md fully and apply its contextual gates.
Optimize meaningful confidence per maintenance cost, not test count or coverage theater.
Map every test to an observable behavior or material risk and its intended failure signal.
Prefer public or user-visible contracts over implementation details. Assert exact text, order, calls, or snapshots only when they are contractual rather than incidental.
Require deterministic, isolated tests. Follow repository conventions and use the cheapest layer with sufficient fidelity.
Treat counts, coverage, mocks, snapshots, test IDs, multiple assertions, and smell names as contextual signals, never automatic findings or acceptance gates.
Do not edit production code unless the user explicitly requests it. Preserve unrelated code and owner state.

Prove a test can fail, when safe, in this order: