harshitsinghbhandari 5081cf794b fix(lifecycle): kill clears trackers, send-failure budget, inclusive escalation (Copilot review) ... - OnKillRequested now clears the session's escalation trackers after a successful kill, so a later duration-based TickEscalations can't emit reaction.escalated for a dead session (dispatch is still skipped). - sendToAgent rolls back the attempt (and firstAttemptAt when it set it) on a messenger.Send error, so undelivered messages don't march a reaction toward escalation — honoring "send failures retry next tick" (§4.3). - Duration escalation now uses an inclusive boundary (>=) in both shouldEscalate and TickEscalations, so a 30m reaction escalates at exactly 30m instead of waiting for the next tick. Tests: kill clears trackers + no post-kill escalation; repeated failed delivery never escalates; duration escalation fires at exactly escalateAfter. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-27 13:11:00 +05:30
..
internal	fix(lifecycle): kill clears trackers, send-failure budget, inclusive escalation (Copilot review)	2026-05-27 13:11:00 +05:30
go.mod	chore: scaffold backend/ and frontend/ skeletons for rewrite	2026-05-26 15:22:36 +05:30
main.go	chore: scaffold backend/ and frontend/ skeletons for rewrite	2026-05-26 15:22:36 +05:30