slack-baltimore-channels-activated

Notes

• 2026-09-09: JES Baltimore Slack Connect lanes activated on Dustin’s instruction. accounts row JES - Baltimore (699233176efec13c6463a620): slack_channel_id=C0BTL2NG134 (#baltimore-production), slack_backlog_channel_id=C0BTPPE74KW (#baltimore-backlog). Both ids added to Hermes connect_denylist; hermes-gateway restarted clean; announcer bot already a member of both. Dry resolution: closeout PMS.OPS.45905 → backlog channel, production-lane Baltimore → production channel. Live now for Baltimore: F1 file receipts, auto F2 on schedule approval, auto F4 on cert send, human-click F3/F7. Not flipped: F7 autonomous asks (MANA only) and pier-log SMS sunset (Manassas only) — Julia keeps SMS pending Dustin’s per-branch OK. Dustin invited Julia Marketis to Slack the same day. No data write path changed; seeding only.
• 2026-09-09 later: F7 flipped for Baltimore on Dustin’s ruling (“sunset the baltimore pier log sms too and add the F7 to Baltimore also”). JES Baltimore added to config.F7_SMS_SUNSET_ACCOUNTS (all three pier-log SMS lanes silenced for Julia) and BALT added to needs_autonomous_ask.F7_AUTONOMOUS_BRANCH_CODES (one-shot autonomous pier-log ask in baltimore-production). entirely-api e875f4e, pushed, three-container rebuild, health 200; tests/test_f7_branch_flips.py pins both gates together. Julia Marketis added to baltimore-production 9/9 morning; baltimore-backlog invite pending, so the F4 backlog auto-post would land in a channel she cannot yet see. Ruling amendment in RULING_CLIENT_LANE_2026-08-30.md section 7.