Rebased on latest main and force-pushed the branch.

Local verification:

• ./scripts/run_tests.sh tests/hermes_cli/test_plugin_scanner_recursion.py::TestBundledBackendAutoLoad::test_bundled_platform_plugins_use_path_derived_keys tests/hermes_cli/test_plugin_scanner_recursion.py::TestBundledBackendAutoLoad::test_bundled_image_gen_openai_autoloads tests/gateway/test_plugin_platform_interface.py

Marked ready for review.

Rebased on latest main (as of 2026-05-18) and force-pushed.

Local verification:

• ./scripts/run_tests.sh tests/hermes_cli/test_plugin_scanner_recursion.py::TestBundledBackendAutoLoad::test_bundled_platform_plugins_use_path_derived_keys

(Still seeing no CI statuses reported on the PR head; may need maintainer Actions approval for fork PRs.)

Thanks for the focused fix. I verified the premise still holds on current main: PluginManager scans repo_plugins / "platforms" as a separate root at hermes_cli/plugins.py:1186, and _parse_manifest falls back to the manifest name when prefix is empty at hermes_cli/plugins.py:1405. With plugins/platforms/teams/plugin.yaml:1 declaring name: teams-platform, runtime discovery registers teams-platform.

The plugin-management CLI takes the other path: _scan_level recurses from the bundled plugins root and builds sub_prefix from directories at hermes_cli/plugins_cmd.py:876, so the same plugin is surfaced as platforms/teams. The PR’s diff changes the bundled-platform runtime scan to pass prefix="platforms" and adds a regression assertion for platforms/teams, which matches the existing key model without adding new plugin surface or core tool footprint.

I did not find a blocker in this diff. This is an automated hermes-sweeper review.