internal/core/history/store_boundary_test.go TestStorePathBoundaryScannerIsArmed builds its hostile literals by ranging over storePathNeedles, the scanner's own needle list, so a needle dropped from storePathNeedles shrinks the armed test instead of failing it: the proof that invariant 15's store-path scanner catches each spelling moves with the thing it is meant to check.

internal/core/history/store_boundary_test.go TestStorePathBoundaryScannerIsArmed builds its hostile literals by ranging over storePathNeedles, the scanner's own needle list, so a needle dropped from storePathNeedles shrinks the armed test instead of failing it: the proof that invariant 15's store-path scanner catches each spelling moves with the thing it is meant to check.

Grounds

• pursued: removing any one needle from storePathNeedles fails TestStorePathBoundaryScannerIsArmed naming that literal (watched on a scratch copy with history/transcripts removed: the old test passed, the new one failed); a needle removal that the test still passes would show it wrong.