feat(docker): close Podman support gaps in doctor, setup, and runtime detection

[zjc-enigma]

Summary

Building on PR #10066 which added find_docker() with Podman fallback, this closes the remaining gaps where Podman users see incorrect diagnostics or Docker-only error messages.

• tools/environments/docker.py: Add is_podman() and runtime_name() helpers; skip --storage-opt size= probe for Podman (unsupported); use runtime-aware error messages
• hermes_cli/doctor.py: Use find_docker() instead of hardcoded shutil.which("docker") — recognizes Podman as a valid container runtime
• hermes_cli/setup.py: Detect Podman when configuring the container backend, show install links for both Docker and Podman

Changes

tools/environments/docker.py

• New is_podman(): cached check if resolved runtime is Podman (checks basename for "podman")
• New runtime_name(): returns "Podman" or "Docker" for user-facing messages
• _storage_opt_supported(): early-returns False for Podman (no per-container --storage-opt size=)
• _ensure_docker_available(): error messages now mention both runtimes when neither found, use runtime_name() for runtime-specific messages

hermes_cli/doctor.py

• Container runtime check now uses find_docker() to detect either Docker or Podman
• Displays the correct runtime name in diagnostics
• "not found" message now says "docker/podman" instead of just "docker"

hermes_cli/setup.py

• Container backend setup uses find_docker() to detect either runtime
• Shows Podman install link alongside Docker when neither is found

Tests

• 6 new tests in test_docker_find.py: TestIsPodman (5 cases) + TestStorageOptPodman (1 case)
• Updated 2 existing tests for new error message wording

Test plan

• uv run pytest tests/tools/test_docker_find.py -v — 15/15 pass
• uv run pytest tests/tools/test_docker_environment.py -v — 18/18 pass
• uv run pytest tests/hermes_cli/test_doctor.py -v — 19/19 pass
• Manual: run hermes doctor with only Podman installed — shows "podman (optional)" / "podman (daemon running)"
• Manual: run hermes setup with only Podman — shows "Podman found: /usr/bin/podman"

🤖 Generated with Claude Code

[teknium1]

Thanks for closing the remaining Podman diagnostics gap. Current main confirms the central premise: find_docker() already falls back to Podman (tools/environments/docker.py:270-303), while doctor and setup still hard-code Docker (hermes_cli/doctor.py:1462-1465, hermes_cli/setup.py:1238-1243).

Problems

• The added doctor test covers only the Termux/no-runtime path. It does not exercise the new Podman-only find_docker() path or verify that doctor runs podman info.
• A sibling diagnostic remains Docker-only in tools/terminal_tool.py:2810-2815: the check uses find_docker() but logs “Docker executable not found.”

Suggested changes

• Add a mocked Podman-only doctor regression test that asserts both the displayed runtime and the executable used for info.
• Align the terminal requirement-check error wording with the runtime-agnostic discovery behavior.

This is an automated hermes-sweeper review.

[teknium1]

Please add a regression test for this Podman-only path: make Docker unavailable, resolve Podman here, and assert doctor reports Podman and invokes the resolved executable for info. The added doctor test currently only covers the Termux case where both runtimes are absent.