Test-plan analysis

Map behavior and risk to existing tests. Use execution coverage as supporting evidence, not proof of assertions.

Inspect before planning

1. Read the scoped requirements, public interfaces, and existing tests.
2. Discover the repository's runner and coverage format.
3. Map each behavior to acceptance scenarios and assertions. Include relevant source paths for navigation.
4. Run or read current applicable coverage evidence through the bounded project wrapper.
5. Update the existing test-plan record; create a new record only within the requested scope.

A test file name does not prove coverage. Conversely, a source file without a same-named test may be covered through a higher interface.

Prioritize