showdar-testlisted

# Showdar Test ## Purpose - Match test level to the boundary/risk being proven. - Produce tests that fail for real regressions rather than implementation rearrangement. - Use unit, integration, component/widget, E2E, and regression tests deliberately. - Keep coverage fast and deterministic while preserving realistic contracts where they matter. - Read `references/test-smells.md` before expanding an already-fragile test suite. ## When to use - Designing test strategy for a feature or migration. - Adding regression coverage for a confirmed bug. - Reviewing whether existing tests prove changed behavior. - Choosing between unit, integration, widget/component, and E2E levels. - Stabilizing flaky tests when the test itself obscures the invariant. ## When not to use - Root cause is unknown; debug first so the regression test targets the real defect. - The user only wants code review without test implementation. - Do not create E2E coverage for every branch already proven cheaply at lower levels. - Do not redesign production architecture solely to make mocks easier. ## Inputs and assumptions - Behavior/invariant to prove and the boundary where it can fail. - Existing test framework and project commands; detect with `scripts/detect-test-tools.mjs` when useful. - Existing fixtures/helpers should be reused when they improve clarity, not because they are available. - External systems should be real/ephemeral at the level where their semantics are under test. ## Non-negotiable ru