Description
The WASM compile goroutine in cmd/gh-aw-wasm/main.go:48 launches doCompile with no recover(). A panic inside doCompile crashes the entire WASM runtime and leaves the JavaScript Promise unresolved — a hard hang for browser users. This is the single most critical goroutine-lifecycle gap identified in the 2026-07-23 Repository Quality report (7 bare production goroutines, 2 without recover()).
Expected Impact
Browser/WASM users get a rejected Promise with a diagnostic error instead of a silent, unrecoverable hang. Removes the only CRITICAL-rated goroutine hygiene issue.
Suggested Agent
Copilot SWE Agent (fix task type merges at 81%; this is a sharply-scoped fix).
Estimated Effort
Fast (< 30 min) — wrap the goroutine body in a deferred recover() that rejects the Promise with the panic value.
Data Source
DeepReport Intelligence analysis 2026-07-23; Repository Quality report #47586.
Generated by 🔬 Deep Report · age00 · 242.8 AIC · ⌖ 11.4 AIC · ⊞ 10.3K · ◷
Description
The WASM compile goroutine in
cmd/gh-aw-wasm/main.go:48launchesdoCompilewith norecover(). A panic insidedoCompilecrashes the entire WASM runtime and leaves the JavaScript Promise unresolved — a hard hang for browser users. This is the single most critical goroutine-lifecycle gap identified in the 2026-07-23 Repository Quality report (7 bare production goroutines, 2 without recover()).Expected Impact
Browser/WASM users get a rejected Promise with a diagnostic error instead of a silent, unrecoverable hang. Removes the only CRITICAL-rated goroutine hygiene issue.
Suggested Agent
Copilot SWE Agent (fix task type merges at 81%; this is a sharply-scoped fix).
Estimated Effort
Fast (< 30 min) — wrap the goroutine body in a deferred
recover()that rejects the Promise with the panic value.Data Source
DeepReport Intelligence analysis 2026-07-23; Repository Quality report #47586.