What changed and why

This adds a diagnostics-first followup to the profile-scoped memory discussion in #4726. hermes honcho status now tells the active profile whether it is using a strict profile-isolated workspace, sharing a workspace with distinct user peers, or sharing the same workspace and user peer with other profiles. hermes honcho status --all now summarizes cross-profile namespace groups and warns when multiple AI peers share the same workspace/user namespace, because gateway session keys are still AI-peer agnostic today.

Per the reporter's followup, this intentionally stops short of changing Honcho routing semantics. The goal is to make the current sharing policy and the gateway-collision risk visible to operators before introducing any new namespace mode or session-prefix behavior.

How to test

• Run pytest tests/honcho_plugin/test_cli.py -q --timeout=60
• Configure two Honcho profiles that share the same workspace and peerName but use different aiPeer values, then run hermes honcho status inside one profile and confirm it reports a shared user memory namespace plus the gateway-session warning.
• Run hermes honcho status --all and confirm it groups shared namespaces and prints the same warning for multi-AI-peer shared-user layouts.

What platforms tested on

• macOS (local pytest run in the worker sandbox)

Fixes #4726