[P2] Redeploy fragility — multiple stray web procs; harden + document #46

New issue

Open

opened 2026-05-23 21:52:28 +00:00 by thabeta · 0 comments

thabeta commented

2026-05-23 21:52:28 +00:00

Owner

Problem
Restarting hero_shrimp_web repeatedly left several stray processes; the bound one wins nondeterministically and which binary serves web.sock isn't obvious. Redeploy depends on a fragile manual procedure.

Evidence

Observed 5 concurrent hero_shrimp_web PIDs after repeated relaunches this session.

Proposed fix
A single supervised launcher (or systemd unit) that kills predecessors, verifies the socket owner, and refuses to run two instances.

Filed from a comparative audit of Hero Shrimp vs Qwen-Code / kimi-cli / picoclaw (2026-05-23). Severity in title: P0=correctness/trust, P1=reliability/UX, P2=cleanup.

**Problem** Restarting `hero_shrimp_web` repeatedly left several stray processes; the bound one wins nondeterministically and which binary serves `web.sock` isn't obvious. Redeploy depends on a fragile manual procedure. **Evidence** - Observed 5 concurrent `hero_shrimp_web` PIDs after repeated relaunches this session. **Proposed fix** A single supervised launcher (or systemd unit) that kills predecessors, verifies the socket owner, and refuses to run two instances. --- _Filed from a comparative audit of Hero Shrimp vs Qwen-Code / kimi-cli / picoclaw (2026-05-23). Severity in title: P0=correctness/trust, P1=reliability/UX, P2=cleanup._