pub fn load_agent_source(path: &str) -> Result<AgentSource>Expand description
Find the agent’s manifest and parse it, once.
The parse is unconditional. It used to happen only when there were region
flags to validate, but the blueprint’s name and description are now needed
for the editor template too, and parsing here is strictly better regardless:
it is the same parser the daemon runs on the same file moments later, so a
manifest that fails here would have failed there, and parse manifest: <toml error> before the daemon is contacted beats a spawn rejection after.