Skip to content
Catalyst Catalyst Catalyst

Catalyst Dev — Change Log
All versions All versions forward

Version 12.47.0

Aug 06, 2026

Stranded Ticket Recovery & Monitoring Node Substrate

The board-health delegate now detects mid-pipeline tickets that have gone dark — no worker, no live job, no recent recovery intent — and routes each one to the appropriate revival path (open PR remediation, remote branch resume, or fresh restart). Separately, monitor and developer nodes now run a proper event-mirror substrate instead of the execution core, so observation-only machines no longer accidentally join the dispatch roster; catalyst doctor and verify-node both surface a dead mirror as a real failure rather than silently passing. Several correctness fixes ship alongside: stranded-ticket evidence was previously never populated due to a map key mismatch, recovery-pass reclaim was silently failing on non-FSM phases, and queued/blocked labels now clear reliably once a ticket starts running.

PRs

  • dev: CTL-1644 board-health delegate detects stranded mid-pipeline tickets and routes each to revival or escalation (#3043) (e807fd5)
  • dev: CTL-1654 interactive nodes carry event/monitoring substrate without execution layer (#3016) (42a623c)
  • dev: address upstream review findings on PR #2851 (#3052) (6414e01)
  • dev: CTL-1571 make queued/blocked labels retractable once a ticket starts (#3045) (aa5fe53)
  • dev: CTL-1657 guard reclaim supersede-check against non-FSM phases (#3027) (58a3849)
  • dev: CTL-1662 event-mirror survives reboot + doctor catches it dead (#3038) (89a0e0b)
  • dev: fix bash 3.2 syntax error in setup-plugin-source.sh (#3049) (6dc6e22)