name: A --files-from the tool cannot stat is reported, and the run continues
why: The sibling case pins a path the tool cannot stat being skipped, because it was never shown to be in scope. A file named by --files-from is different: the caller pointed at it, so failing to read it is an error rather than a silence, exactly as a missing one already is. The condition reaches the same trap by another door -- _describe_error resolves the condition before the class, and Path.is_dir re-raises anything outside its own ignore list, so describing the failure crashed while describing it. The error names the condition in the tool's own vocabulary rather than the runtime's, which is what lets this be pinned byte for byte at all.
argv: --write --json --files-from aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.md note.md
exit_code: 1
