Unified tests requirements

The following are repository responsibility candidates inferred from source and configured workflows. They link to project requirements but are not approved customer requirements.

ID	Candidate responsibility	Evidence class	Approval/status
TST-REQ-001	Keep Markdown test intent, extracted production target, mocks and executable assertions traceable by function.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
TST-REQ-002	Select a compatible test variant from the target source ref, with explicit fallback and override behavior.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
TST-REQ-003	Build and run focused niseCore matcher/sensor/storage and WBF capture/wake suites.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
TST-REQ-004	Report skipped, build-failed and execution-failed states distinctly; absence of a run is not success.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
TST-REQ-005	Keep dev as current test implementation and do not mistake the small main branch for full test coverage.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected

See project requirements and traceability.