Under the hood
The plugin agent loader now takes a single options object instead of separate arguments, and lost its own error-catching wrapper
What
The internal function that builds an agent definition from a plugin's agent markdown file now takes a single destructured options object instead of a list of separate positional arguments. It also no longer has its own try/catch block that caught load failures, logged an error, and returned null.
Why
This is an internal refactor to how plugin agents are loaded.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding suggests error handling for load failures likely moved to the calling code but doesn't confirm where it now lives.