Summary

The built-in BOOT.md startup hook creates a bare AIAgent(...) instead of using the gateway's resolved model/runtime configuration.

In a gateway configured with a custom endpoint or other non-default runtime provider, the BOOT agent can start without the expected auth/runtime kwargs and fail immediately with 401s such as Missing Authentication header.

Expected

BOOT.md should run with the same resolved gateway model/runtime settings as a normal gateway turn.

Repro

1. Configure the gateway to use a provider that requires explicit runtime auth (for example a custom OpenAI-compatible endpoint).
2. Add ~/.hermes/BOOT.md.
3. Start the gateway.
4. Observe the startup BOOT agent fail before it can do any useful work.

Proposed fix

Resolve the BOOT agent's model/runtime via the same gateway helpers used for normal turns and add a regression test so the runtime kwargs keep flowing through.