It’s probably not intended, but will likely need a policy to turn into an error. Looking at the code, if the path is not absolute, it gets appended to the current source directory. It seems that this ends up reading a directory…but not failing? Does it do the same thing with another directory (not file) path?
Ugh, thanks. We’ll have to really increase the test suite to cover this policy’s behavior (assuming we want it to fix all relevant file(*) subcommands).