What does this PR do?

agent/bedrock_adapter.py already defers import boto3 until the provider is actually used, but on a base install (no [all] extras) that deferred import just raises ModuleNotFoundError — there's nothing that actually installs boto3.

tools/lazy_deps.py already registers a provider.bedrock entry pointing at boto3==1.42.89. This PR wires the adapter to call lazy_deps.ensure("provider.bedrock") at module load, so the first import of the Bedrock adapter triggers the install.

The ensure() call is wrapped in try / except Exception: pass so that:

• Environments where lazy_deps isn't importable (test stubs, etc.) don't break
• An install failure surfaces as the real downstream ImportError from the existing lazy import block, not a confusing lazy_deps stack

After #24220 / #24515 removed boto3 from the [all] extras, users on a base install hit ModuleNotFoundError: No module named 'boto3' the first time the Bedrock provider is touched, even though the lazy_deps registration was already in place to handle exactly this case.

Related Issue

No open issue — surfaced as a regression after the boto3-from-extras removal in #24220 / #24515.

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• agent/bedrock_adapter.py — 13-line try / except block at the top of the module that calls lazy_deps.ensure("provider.bedrock", prompt=False) so boto3 is installed on first import. Pinned version (boto3==1.42.89) comes from the existing tools/lazy_deps.py registration — not changed here.

How to Test

On a clean venv with pip install hermes-agent (no extras):

1. Confirm the regression on main:

   python -c "from agent.bedrock_adapter import BedrockAdapter"
   # ModuleNotFoundError: No module named 'boto3'

2. Apply this PR.
3. Re-run the same import:

   python -c "from agent.bedrock_adapter import BedrockAdapter"
   # lazy_deps installs boto3==1.42.89, import succeeds

4. Run the existing test suite:

   pytest tests/ -q
   

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (chore(deps):)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix (single 13-line addition to one file)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes — N/A (this is a deps-bootstrap shim that runs at import time; behavior is "lazy_deps installs the package", which is already covered by lazy_deps' own tests)
• I've tested on my platform: Ubuntu 24.04 (Amazon Linux 2023 runtime)

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — N/A (internal bootstrap shim; user-visible behavior is unchanged)
• I've updated cli-config.yaml.example if I added/changed config keys — N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — lazy_deps is the existing cross-platform install path; no new platform-specific code
• I've updated tool descriptions/schemas if I changed tool behavior — N/A