Yes frequently I hit this. Largely when I am laying down supporting tooling for tests for example that were not part of a spec (feature). Tests were but not missing tooling. Others are me editing .gitignore for files that resulted from a listing run or README change by me, which was not in scope. Or if I edit a file, that was not in scope.
I like that you call out the store drift check yourself. Have you tried deliberately causing drift to see whether it catches it.. ?
Yes frequently I hit this. Largely when I am laying down supporting tooling for tests for example that were not part of a spec (feature). Tests were but not missing tooling. Others are me editing .gitignore for files that resulted from a listing run or README change by me, which was not in scope. Or if I edit a file, that was not in scope.