test-quality

# Test Quality ## Config Resolution Skill support project custom. Order: 1. Look `.lattice/config.yaml` in repo root 2. If find, check `paths.test_quality` for custom doc path 3. If custom path exist, read doc & check YAML frontmatter for `mode`: - **`mode: override`** (or no mode): Custom doc take full control. Use instead default. Must be complete -- is only reference. - **`mode: overlay`**: Read `./references/defaults.md` first, then apply custom doc on top. Custom sections replace match sections (by heading). New sections add after. 4. If no config/path/file, read `./references/defaults.md` 5. **Language adaptation**: If `paths.language_idioms` exist in config, read **"Testing Patterns"** section and adapt §5 (Test Naming), §4 (Test Isolation), §6 (Test Data Builders) to language test framework idioms. Language idioms take precedence over pseudocode defaults. Defaults ship w/ skill. Work out-of-box. Override only when team have different standards. ## Self-Validation Checklist STOP after gen each test. Check ALL before continue. If fail, fix. If ambiguous (see Ambiguity Signals), flag -- show options & reasoning. 1. **AAA STRUCTURE**: arrange, act, assert separate w/ blank lines? Any logic (if/loop/try) in arrange or assert? 2. **SINGLE BEHAVIOR**: Test verify one behavior per loaded doc (default: one behavior per test, name need "and" = split)? 3. **ASSERTION QUALITY**: Assert observable behavior, not implementation? Specific enough catch regression? 4. **IS...