pub fn clear_gh_login(dir: &Path) -> Result<()>Expand description
Create dir if needed and remove a hosts.yml from it.
A login can land here: gh’s own “not logged in” error tells the reader to
run gh auth login, and doing that inside an agent writes exactly this
file. Clearing it on every spawn is what keeps the guard from being undone
by one well-meant login. Only that one file is removed; gh’s preferences
(config.yml) are left alone.