Logs
notify-governance.log — last 500 lines
200
500
{"ts": "2026-06-04T15:37:05.666686+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-04T15:37:49.060731+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-04T15:40:55.372700+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-04T15:43:08.791168+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Landed MC-4681, board dispatch fixed"}
{"ts": "2026-06-04T15:43:08.791484+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "board dispatch pickup runtime status MC-4681"}
{"ts": "2026-06-04T15:52:48.023412+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-04T15:52:48.024482+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-04T15:52:48.025192+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-04T15:52:48.025873+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-04T15:52:48.028425+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-04T15:54:25.763255+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-04T15:54:25.763777+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-04T15:54:25.764254+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-04T15:54:25.764762+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-04T15:54:25.766290+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-04T16:33:13.579731+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-04T16:33:13.580645+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-04T16:33:13.581209+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-04T16:33:13.581755+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-04T16:33:13.583127+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-04T16:33:42.837549+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-04T16:33:42.838078+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-04T16:33:42.838545+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-04T16:33:42.839064+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-04T16:33:42.840330+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-05T04:02:06.851006+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LegalMind review: 5 finding(s)\n Auto-fixed: 0, Larry todo: 0, Inbox: 0\nCommit: 176944bc fix(MC-3985): return 424 (not 500) when cloud storage not connected (#415)\n\n"}
{"ts": "2026-06-06T04:02:03.024870+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LegalMind review: 5 finding(s)\n Auto-fixed: 0, Larry todo: 0, Inbox: 0\nCommit: 176944bc fix(MC-3985): return 424 (not 500) when cloud storage not connected (#415)\n\n"}
{"ts": "2026-06-06T22:02:03.186403+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent drifted off `master` \u2192 currently on `kanban/mc-4606-self-heal-budget` in `~/workspace`. CCGram picker, auto-commit hook, and pool dispatch all use this branch as 'current'. Switch back via `cd ~/workspace && git checkout master` or accept drift if intentional. (MC-3840 \u00a715)"}
{"ts": "2026-06-07T04:02:18.212867+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LegalMind review: 5 finding(s)\n Auto-fixed: 0, Larry todo: 0, Inbox: 0\nCommit: 176944bc fix(MC-3985): return 424 (not 500) when cloud storage not connected (#415)\n\n"}
{"ts": "2026-06-08T04:04:06.005207+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LegalMind review: 5 finding(s)\n Auto-fixed: 0, Larry todo: 0, Inbox: 0\nCommit: 176944bc fix(MC-3985): return 424 (not 500) when cloud storage not connected (#415)\n\n"}
{"ts": "2026-06-08T09:02:20.963618+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Weekly claude-mem value eval: **NEEDS REVIEW**\n\nclaude-mem write-heavy, read-thin. 7d: ~5,000 observations captured, 266MB db / 1.4G total, 15 worker procs always running. But `relevance_count=0` on all 12,868 obs and CHROMA_MCP/mem-search queries \u22482/day \u2014 the *active* retrieval half is effectively dead; nobody queries it.\n\nOnly live read path = the passive SessionStart digest (the \"[workspace] recent context\" block injected atop this session, ~50 recent obs). That episodic cross-session recall "}
{"ts": "2026-06-08T18:00:05.724973+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LUCI ALERT: Mission Control API not responding"}
{"ts": "2026-06-08T18:00:29.330510+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udea8 CRITICAL data feed alert (6 stale total)\n\u2022 *Mission Control service* \u2014 age 0.0h / threshold 0.1h\n owner: `systemd:luci-dashboard.service`\n path: `luci-dashboard.service`\n\u2022 *MC /api/health latency* \u2014 age 0.0h / threshold 0.1h\n owner: `systemd:luci-dashboard.service`\n path: `http://127.0.0.1:3001/api/health`\n\n@Lucienne \u2014 3+ feeds stale, please triage."}
{"ts": "2026-06-09T04:01:50.114700+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LegalMind review: 5 finding(s)\n Auto-fixed: 0, Larry todo: 0, Inbox: 0\nCommit: 176944bc fix(MC-3985): return 424 (not 500) when cloud storage not connected (#415)\n\n"}
{"ts": "2026-06-09T08:06:28.915518+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Luci | Morning Briefing \u2014 Tuesday 9 June 2026\n\nTODAY\n\u2022 09:30\u201312:00 Exco Meeting \u2014 Management Boardroom\n\u2022 14:00\u201314:45 Project Heron Q&A: Bank of Utah / ACG \u2014 Teams\n\u2022 15:00\u201315:45 Project Heron Q&A: Genesis \u2014 Teams\n\u2022 [Cayla] School DAY 2\n\nTHIS WEEK\n\nWed 10 Jun \u2014 \u2708 AviaDev 2026, Gaborone (through 12 Jun)\n\u2022 11:00 Airlink 4Z176 JHB \u2192 Gaborone\n\u2022 AviaDev: fleet/route panels, outreach programme, networking (all day)\n\u2022 17:30 AviaDev welcome reception \u2014 GICC\n\u2022 20:30 ACS | Safair AviaDev dinner \u2014 The Beef B"}
{"ts": "2026-06-09T13:30:21.460796+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 1 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M .heal-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M \"dashboard-build/Booking Curves/202606 Booking Curve.csv\"; D dashboard-build/Capacity/reports/Capacity_Actuals_2024-01-01_to_2026-06-03.xlsx; M dashboard-build/Capacity/reports/Capacity_Scheduled_2026-06-01_to_2026-12-31.xlsx`. Reconcile manu"}
{"ts": "2026-06-09T17:45:04.840639+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 1 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M .heal-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M \"dashboard-build/Booking Curves/202606 Booking Curve.csv\"; D dashboard-build/Capacity/reports/Capacity_Actuals_2024-01-01_to_2026-06-03.xlsx; M dashboard-build/Capacity/reports/Capacity_Scheduled_2026-06-01_to_2026-12-31.xlsx`. Reconcile manu"}
{"ts": "2026-06-09T18:02:08.394378+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 2 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M .heal-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M \"dashboard-build/Booking Curves/202606 Booking Curve.csv\"; D dashboard-build/Capacity/reports/Capacity_Actuals_2024-01-01_to_2026-06-03.xlsx; M dashboard-build/Capacity/reports/Capacity_Scheduled_2026-06-01_to_2026-12-31.xlsx`. Reconcile manu"}
{"ts": "2026-06-09T22:45:05.497970+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LUCI ALERT: Mission Control API not responding"}
{"ts": "2026-06-09T23:00:05.726574+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LUCI ALERT: Mission Control API not responding"}
{"ts": "2026-06-09T23:00:12.112761+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udea8 CRITICAL data feed alert (5 stale total)\n\u2022 *Mission Control service* \u2014 age 0.0h / threshold 0.1h\n owner: `systemd:luci-dashboard.service`\n path: `luci-dashboard.service`\n\u2022 *MC /api/health latency* \u2014 age 0.0h / threshold 0.1h\n owner: `systemd:luci-dashboard.service`\n path: `http://127.0.0.1:3001/api/health`\n\n@Lucienne \u2014 3+ feeds stale, please triage."}
{"ts": "2026-06-10T04:02:23.269742+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LegalMind review: 5 finding(s)\n Auto-fixed: 0, Larry todo: 0, Inbox: 0\nCommit: 176944bc fix(MC-3985): return 424 (not 500) when cloud storage not connected (#415)\n\n"}
{"ts": "2026-06-10T12:00:05.513780+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LUCI ALERT: Mission Control API not responding"}
{"ts": "2026-06-10T12:00:24.224092+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udea8 CRITICAL data feed alert (5 stale total)\n\u2022 *Mission Control service* \u2014 age 0.0h / threshold 0.1h\n owner: `systemd:luci-dashboard.service`\n path: `luci-dashboard.service`\n\u2022 *MC /api/health latency* \u2014 age 0.0h / threshold 0.1h\n owner: `systemd:luci-dashboard.service`\n path: `http://127.0.0.1:3001/api/health`\n\n@Lucienne \u2014 3+ feeds stale, please triage."}
{"ts": "2026-06-10T20:39:31.422471+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Ticket MC-1234 moved to in_review"}
{"ts": "2026-06-11T04:05:19.741051+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "LegalMind review: 5 finding(s)\n Auto-fixed: 0, Larry todo: 0, Inbox: 0\nCommit: 176944bc fix(MC-3985): return 424 (not 500) when cloud storage not connected (#415)\n\n"}
{"ts": "2026-06-11T10:00:25.581693+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 1 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M .heal-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M dashboard-build/Dashboard.html; M dashboard-build/dashboard/Dashboard.html; M dashboard-build/dashboard/dashboard_data.json`. Reconcile manually during a quiet window."}
{"ts": "2026-06-12T01:00:24.510560+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 1 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .heal-state.json; M luci-home/memory-backup/-Users-elmar-PKA/MEMORY.md; M luci-home/memory-backup/-home-lucienne-workspace/project_last_rotation.md; M luci-manifest.md; M projects/btc-swing-trader/charts/btc_1D.png; M projects/btc-swing-trader/charts/btc_1h.png`. Reconcile manually during a quiet window."}
{"ts": "2026-06-12T08:01:54.128060+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-12T08:01:54.129035+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-12T08:01:54.129529+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-12T08:01:54.130020+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-12T08:01:54.131237+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-12T08:19:24.373292+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-12T08:19:24.374389+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-12T08:19:24.374927+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-12T08:19:24.375462+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-12T08:19:24.376818+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-12T08:30:21.497479+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 1 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M \"dashboard-build/Booking Curves/202606 Booking Curve.csv\"; M dashboard-build/Dashboard.html; M dashboard-build/SummaryExcel.xlsx; M dashboard-build/SummaryRoute.xlsx`. Reconcile manually during a quiet window."}
{"ts": "2026-06-12T08:35:53.084963+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-12T08:35:53.085403+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-12T08:35:53.085854+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-12T08:35:53.086354+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-12T08:35:53.087584+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-12T09:30:21.796037+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 2 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M \"dashboard-build/Booking Curves/202606 Booking Curve.csv\"; M dashboard-build/Dashboard.html; M dashboard-build/SummaryExcel.xlsx; M dashboard-build/SummaryRoute.xlsx`. Reconcile manually during a quiet window."}
{"ts": "2026-06-12T09:41:05.089546+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "DONE: MC-5011 ticket complete"}
{"ts": "2026-06-12T09:42:07.412868+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-12T09:42:07.413307+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-12T09:42:07.413749+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-12T09:42:07.414200+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-12T09:42:07.415402+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-12T10:18:13.619189+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "MC-5020 progress update from worker"}
{"ts": "2026-06-12T10:18:13.631939+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-12T10:18:13.632578+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-12T10:18:13.633260+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-12T10:18:13.633963+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-12T10:18:13.635702+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-12T10:19:16.739320+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "MC-5020 progress update from worker"}
{"ts": "2026-06-12T10:19:16.748885+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-12T10:19:16.749325+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-12T10:19:16.749806+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-12T10:19:16.750253+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-12T10:19:16.751488+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-12T10:20:38.273433+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "MC-5020 progress update from worker"}
{"ts": "2026-06-12T10:20:38.296749+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-12T10:20:38.297784+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-12T10:20:38.298874+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-12T10:20:38.300078+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-12T10:20:38.302220+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-12T10:22:25.557522+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "MC-5020 progress update from worker"}
{"ts": "2026-06-12T10:22:25.577600+02:00", "reason": "mc_status_dm_allowed_critical", "message": "\ud83d\udd34 CRITICAL: provider auth failed on the MC runtime pool"}
{"ts": "2026-06-12T10:22:25.578494+02:00", "reason": "mc_status_dm_allowed_param", "message": "Landed the keystone board fix (MC-4681). The Mission Control board now refuses to mark a ticket done unless its code is actually merged to master."}
{"ts": "2026-06-12T10:22:25.579358+02:00", "reason": "mc_status_dm_allowed_env", "message": "Dispatch layer is fixed \u2014 the two-day pickup outage + duplicate-worker mess is resolved. Two keystone fixes landed live this morning."}
{"ts": "2026-06-12T10:22:25.580279+02:00", "reason": "mc_status_dm_allowed_env", "message": "Update: the board is dispatching again (fixed the stuck pool by hand). But digging in, the whole ticket-dispatch layer is tangled and I do not want to keep patching it live tonight."}
{"ts": "2026-06-12T10:22:25.582563+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "Need a call from you: the legacy ticket-pickup task keeps coming back on, and I traced it \u2014 it is being enabled by a manual toggle in the dashboard."}
{"ts": "2026-06-12T12:45:04.804131+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 2 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M \"dashboard-build/Booking Curves/202606 Booking Curve.csv\"; M dashboard-build/Dashboard.html; M dashboard-build/SummaryExcel.xlsx; M dashboard-build/SummaryRoute.xlsx`. Reconcile manually during a quiet window."}
{"ts": "2026-06-12T13:30:44.249179+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 7 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M \"dashboard-build/Booking Curves/202606 Booking Curve.csv\"; M dashboard-build/Dashboard.html; M dashboard-build/SummaryExcel.xlsx; M dashboard-build/SummaryRoute.xlsx`. Reconcile manually during a quiet window."}
{"ts": "2026-06-12T14:00:44.917114+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 8 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M \"dashboard-build/Booking Curves/202606 Booking Curve.csv\"; M dashboard-build/Dashboard.html; M dashboard-build/SummaryExcel.xlsx; M dashboard-build/SummaryRoute.xlsx`. Reconcile manually during a quiet window."}
{"ts": "2026-06-12T16:30:44.233744+02:00", "reason": "mc_status_dm_rerouted_to_mc_topic", "message": "\u26a0\ufe0f Luci persistent is behind `origin/master` by 9 commit(s), but `~/workspace` is dirty, so MC-4718 clean-only fast-forward was skipped. First dirty entries: `M .acsa-monthly-state.json; M \"dashboard-build/ACSA Monthly Data.xlsx\"; M \"dashboard-build/ACSA Website Data.xlsx\"; M \"dashboard-build/Booking Curves/202606 Booking Curve.csv\"; M dashboard-build/Capacity/reports/Capacity_Scheduled_2026-06-01_to_2026-12-31.xlsx; M dashboard-build/Dashboard.html`. Reconcile manually during a quiet windo"}