Writing a Goal Condition That Actually Works

A developer, in Manual permission mode, runs:

/goal migrate every file in src/legacy/ off the deprecated `request`
library and onto `fetch`

They then leave their desk expecting to come back to a finished migration.

1. Identify two distinct reasons this specific setup is unlikely to run unattended the way they expect, one about the permission mode and one about how the condition itself is written.
2. Rewrite the condition so it gives the evaluator something concrete to check, and add a bound that keeps a stuck run from running forever.
3. Suppose partway through, one file's migration spawns a subagent that takes 40 minutes to finish investigating a tricky edge case. Explain what /goal does about evaluation during that window, and why that behavior makes sense given what the evaluator is allowed to look at.