Function non_interactive_warning 

pub fn non_interactive_warning(
    workdir: &Path,
    concern: &WorkdirConcern,
) -> String

What to warn when there is no terminal to ask on.

The run proceeds. Refusing would break every unattended caller - CI, a pipe, --yolo - and a prompt nobody can answer is worse still, because it parks the run until something times it out and reads as a hang.

The cost of that choice is that the guard is advisory in exactly the unattended case issue #252 came from, so this line is the whole mitigation: it goes to stderr on every such run, names the directory, and says how to silence it. Someone reading the log afterwards should be able to find the moment an agent was pointed at a home directory.