Locking the test file protects the assertions, but the independent rerun should also prove that all six intended tests actually executed against the edited inventory module. A green process exit can still come from empty discovery or importing an installed copy instead of the fresh workspace.

I would record discovered test IDs, executed count and the resolved module path alongside the test hash. Make a zero-test run fail the bench, and retain the six per-test outcomes rather than only Yes in the pilot table. Those checks preserve your small reproducible setup while making its PASS evidence about the intended implementation rather than just the test runner's exit status.