[P2] Two status vocabularies (raw vs mapped) risk re-divergence #45

New issue

Open

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

thabeta commented

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

Owner

Problem
The server speaks both raw (completed/running/paused) and mapped (done/working/blocked) statuses; the UI partially unified via a jobPhase() helper, but new statuses can re-diverge and a job can render active in one place and empty in another.

Evidence

crates/hero_shrimp_web/ui/src/store.ts status classifier.

Proposed fix
One canonical status enum at the source, mapped exactly once.

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** The server speaks both raw (`completed/running/paused`) and mapped (`done/working/blocked`) statuses; the UI partially unified via a `jobPhase()` helper, but new statuses can re-diverge and a job can render active in one place and empty in another. **Evidence** - `crates/hero_shrimp_web/ui/src/store.ts` status classifier. **Proposed fix** One canonical status enum at the source, mapped exactly once. --- _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._