# Resource-to-scenario coverage

Read the runner's `docs/integration/onboarding-coverage.md` before preparing
definitions or maintaining coverage. It specifies the `CoverageRequest`,
`prepareCoverage` and `validateCoverageApproval` interfaces exported by
`tooling/onboarding/coverage.mts`, the concrete review sequence, preservation
checks and structural-only validation boundary.

First settle the runtime user's initial scope/priorities and scenario
expectations in live discussion. Present conflicts and inaccessible/uninspected
resources as explicit questions/gaps. Prepare only agreed definitions, with
blocked execution prerequisites retained honestly. Keep the coverage index
outside the catalog; definitions own their execution contract.

Show the exact candidate definition/index changes, obtain approval, revalidate
current files with the helper immediately before host-owned writes. Apply only a
successful validation result's immutable `changes`; the mutable preparation is
not the write authority. Inspect the written catalog through the runner. On resume, re-read evidence and current
files; a saved approval ID is not indefinite authorization. Keep runtime/server
support with `test-support.md` and its separately approved mechanisms.