project-config-and-testslisted

# Project Config And Tests This is a composable project overlay, not a standalone implementation workflow. Use it with matching language or discipline guidance when the main task is a configuration contract or deterministic tests at that boundary. For review, inspect these contracts and report findings without editing config, tests, or process state. For implementation, apply only the requested changes and use isolated fixtures for validation. ## When to use The task involves configuration sources or precedence, defaults, parsing, normalization, path resolution, or deterministic tests around those seams. ## Not for Do not use this for general feature work (use the matching principle skill and add `project-core-dev` only when repository-specific completion evidence is not concrete), general test strategy (`tester-mindset`), framework-specific test implementation, vendored dependency changes (`project-vendor-boundary`), release-only work (`project-release-maintainer`), or environment diagnosis whose cause has not been isolated (`project-platform-diagnose`). ## Workflow 1. Establish the contract before editing: sources, precedence, defaults, and the behavior of missing, empty, malformed, and unsupported values. 2. Preserve help, version, and recovery paths when they can operate safely without valid config. Fail fast or fail closed when continuing would be unsafe or would silently apply misleading behavior. 3. Separate pure parsing and normalization from environm