You're offline — showing cached data

MC-4612

Home rail: thread close_reason onto session rows to restore genuine-failure signal
2026-06-13 08:50:45 SAST
Home Board MC-4612

Home rail: thread close_reason onto session rows to restore genuine-failure signal

Follow-up from MC-4607 council. The session-history rail row dict has no close_reason, so MC-4607 maps ALL non-live runtime states to neutral 'History' (avoids a false-red wall ...
State Done Next Action Closed Owner Luci Runtime Closed Age 11d ago
MC-4612
Ticket is done; runtime is closed. · cwd /home/lucienne/workspace/state/control-room-worktrees/mc-4612-home-rail-close-reason · uptime 10d 3h · last activity 10d 0h ago

Description

MC-4612
Follow-up from MC-4607 council. The session-history rail row dict has no close_reason, so MC-4607 maps ALL non-live runtime states to neutral 'History' (avoids a false-red wall from reaped tmux runtimes, close_reason=tmux_session_missing). Cost: a genuinely crashed runtime no longer shows any failure cue in the rail. Fix: add close_reason (and/or a terminal chat status) to the recent_threads row builder in models.get_home_zones / _home_thread_runtime_summary, then in dashboard_v2.html show 'Failed' only when close_reason indicates a real error (not tmux_session_missing/reaped/stopped). Restores real signal without the wall. Council: Gemini+GLM+Codex flagged the signal loss; Opus called current state an acceptable honest tradeoff.

Activity

done
Luci is working...
Live
No activity yet
Help