unioss-test-evidencelisted

# UNIOSS Test-Case Derivation & Evidence Contract ## Overview The tester derives its own complete case set **mechanically** — coverage never depends on the dispatch prompt happening to name a scenario. Then the evidence contract makes every claim traceable: no pass without this-run proof, no case silently dropped. **Core principle:** derive the full case table before driving anything; a case is either RAN with evidence or SKIPPED out loud. ## Derivation — build the case table first Three sources, all mandatory: 1. **`changes.md`** — every changed call site / flow → **≥1 Normal + ≥1 Abnormal case**. Four modified call sites can never yield two test cases. 2. **Spec acceptance criteria** — every AC → ≥1 case, or an explicit SKIPPED row with a reason. No AC unmapped. 3. **`scope.md`** (ticket root, written by the scope stage just before this one) — every listed affected feature/URL → ≥1 case. Round 2+: prior-round surfaces in the cumulative scope become regression cases. Additional rules: - **Deletion refactor → sibling-survival cases:** exercise the remaining public methods of each edited file's flow (logout, guards, redirects) — proves the deletions didn't break neighbors. - **Shared submodule in the diff → cross-app regression case.** Mandatory, or handed off explicitly — never silently deferred. - **Abnormal floor per flow:** wrong input + missing entity (+ boundary where applicable). - **Dedupe:** one case may satisfy several sources — tag it with every source it co