The docs.test_strategy audit scope requires a canonical
docs/test-strategy.html document for each audited package or
workspace boundary. The durable governance records are
core-adr-0003 and core-req-0003.
Rack manifests are necessary but not sufficient for large test programs. They tell reviewers which strata and subtests exist, but they do not always explain parity lanes, custom evidence databases, fixture discovery, generated assets, oracle tools, or why some surfaces intentionally lack equivalent coverage.
The audited source is docs/test-strategy.html. It must be an
accepted HTML document with data-doc="test-strategy". It should
summarize the package or workspace test architecture before a reviewer
drills into tests/rack.toml, STRATUM.toml, surface
manifests, fixture catalogs, or generated signoff evidence.
The first audit slice checks that the document covers scope/architecture, Rack/signoff, lanes/parity/surfaces, fixtures/assets/oracles, and coverage/gaps/evidence. A simple package may explicitly state that a topic is not applicable. A complex package should describe the support code, assets, and generated evidence needed to understand the suite.
The implementation lives in src/wn_dev_std/test_strategy_doc_governance.py and is covered by tests/L0_foundation/test_L0_017_test_strategy_doc_governance.py.