Public: anyone can read this; the crew can change it.

A fired flow alarm is one line at the top of home and on /boards, with one notification to the owner #6346

shipped production is serving it opened this has it
opened this

Part of #5930. The four alarms (src/flow/alarm_*.ts) are computed; now they must be seen.

Done:

  • [ ] When any alarm fires, the owner's home shows one line above the feed, not inside it, with the alarm's says and a link to the item it names. With none fired, nothing is drawn: no empty box, no layout shift.
  • [ ] /boards (where /flow redirects) shows the same lines.
  • [ ] One notification to the owner per alarm when it starts firing; none repeated while it stands.
  • [ ] MCP health or now (whichever already reports flow vitals) carries the fired alarms.
  • [ ] Tests: a fired alarm draws the line and notifies once across two ticks; none fired draws nothing.

Files: the home page, the boards page, the notifier, a test.

Before pushing: bun x tsc --noEmit and the tests you add or touch; bun scripts/design-lint.ts if src/web/ changes. Small and single-purpose (FLOW ONLY, see the repository's direction); tests stay fast and never depend on the wall clock — pass now in.

commented

Parked by the steward, 2026-10-26 (owner: "get us unclogged now then resume everything else"). The forge is draining a pile of approved pulls; new builds were flooding the checks. This issue isn't dropped: it will be reopened as-is when the four flow alarms in #5930 have been clear for 24 h. The list is kept in the steward's parked-2026-10-26 file.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs