huskies: merge 1235 bug Notifications fire off the filesystem watcher, not the state machine — story 995's TransitionFired subscriber was never wired into startup

This commit is contained in:
Huskies Agent
2026-07-20 14:36:49 +00:00
parent f7b7f21e88
commit 30ca3ad463
2 changed files with 19 additions and 28 deletions
+16 -1
View File
@@ -361,8 +361,23 @@ pub async fn run_bot(
let notif_room_id_strings: Vec<String> = notif_room_ids.iter().map(|r| r.to_string()).collect();
crate::service::notifications::spawn_notification_listener(
Arc::clone(&transport),
move || notif_room_id_strings.clone(),
{
let notif_room_id_strings = notif_room_id_strings.clone();
move || notif_room_id_strings.clone()
},
watcher_rx,
notif_project_root.clone(),
);
// Spawn the TransitionFired-driven stage-notification subscriber (story
// 995) here too — this was previously only wired for WhatsApp/Slack/Discord
// (`startup::bots::spawn_notification_listeners`), leaving Matrix
// deployments with no stage-transition chat notifications at all (story
// 1235). Spawned once here, before the sync loop below, so the task runs
// independently of Matrix sync reconnects/re-logins.
crate::service::notifications::spawn_stage_notification_subscriber(
Arc::clone(&transport),
move || notif_room_id_strings.clone(),
notif_project_root,
);