Suggestion: reading files should not operate under execute_bash

execute_bash is very wide, it could be changing files with that command, so I don't really want to give it blanket trust to do that most of the time. But reading files is idempotent and non-destructive so it makes sense to trust that operation (`t` instead of `y`).

I'm asking Q to search through a codebase and sometimes it's using fs_read and sometimes it's using execute_bash, so maybe that's the deeper issue.