fix(terminal): agent-browser cleanup handles agents that relocate the socket dir (v0.227.2)

[vikasprogrammer]

Follow-up to #377 (v0.227.1), caught by end-to-end testing on a real qa session.

The gap

v0.227.1's exit trap ran agent-browser close --all scoped to the session's AGENT_BROWSER_NAMESPACE. But close --all keys off the socket dir, not the namespace — verified live:

• close --all with namespace only → "No active sessions", daemon survives.
• close --all with the socket dir → "✓ Closed session", daemon dies.

And the agents that actually use the browser (qa/engineer/site-porter/website-bot) export a custom AGENT_BROWSER_SOCKET_DIR to a writable per-session dir, because their real HOME is read-only under systemd ProtectHome (it's in their CLAUDE.md). So the trap's plain close --all — which only had the server's default socket dir — missed their daemons entirely. The 0.227.1 fix was ineffective for exactly the agents that leak.

The fix (terminal/claude-launch.sh)

The daemon reliably inherits AGENT_BROWSER_NAMESPACE=aos-<session-id> in its environ even when the agent overrides the socket dir (verified). So the trap now:

1. runs a plain close --all first (covers default-socket-dir daemons / macOS), then
2. on Linux, finds this session's daemons via pgrep + matching AGENT_BROWSER_NAMESPACE in /proc/<pid>/environ, recovers each one's own AGENT_BROWSER_SOCKET_DIR from that environ, and runs close --all scoped to it — with a SIGTERM straggler fallback.

Still namespace-scoped, so it never touches another live session's browser. This stays a root-cause, session-owned cleanup at teardown (not a background GC) — it only ever targets the session's own namespace, at the session's own exit.

Verification

• Reproduced the miss: namespace-only close --all leaves a custom-socket-dir daemon alive.
• Confirmed the recovery path: match by namespace → recover socket dir from environ → close --all → daemon gone, "closed cleanly".
• npm run build ✓ · npm run test:governance → 68/68 ✓ · bash -n claude-launch.sh ✓
• Deterministic on-box integration test to follow after deploy.

🤖 Generated with Claude Code