Pending actions for Tam

1. Hermes gateway restart (BLOCKING Nova/Echo Telegram bots)

Nova and Echo profiles are fully configured (tokens, .env, SOUL.md, skills, config.yaml) but their Telegram bots won't start until the gateway restarts.

Command (run from a shell outside the gateway): hermes gateway restart

This picks up nova/echo profiles and starts @NovaSolOS_bot and @EchoSolOS_bot.

2. Pulse-laptop A2A compatibility

Pulse-laptop A2A tunnels (18441-18443) are up and responding to POST / with JSON-RPC, but they return 404 on /.well-known/agent-card.json (V3's discovery path). This means pulse-laptop is running a different A2A implementation (possibly V2-era or a different framework). V3's serve.py uses /.well-known/agent-card.json for discovery.

Impact: Brain agents cannot discover Pulse agents via the standard V3 card path. Recommendation: Tam should either upgrade pulse-laptop to V3 serve.py or provide the correct discovery path for the current implementation.

3. Prod A2A capability (ready, not deployed)

Prod has a2a-sdk/starlette/protobuf/sse-starlette installed and V3 code synced. Prod registry has no agents with host=prod, so no A2A listeners run there by design. If Young wants Heart on prod, Min updates registry with host=prod entries and Sol deploys 5 units (10 min).