The Steward's alarms

What becomes an alarm#

After every round, the Steward lists the few things that need you. Code decides each one, no model. A condition becomes an alarm once it has lasted its while:

Pull requests in a repository where merging is off are left to you, and no alarm counts their hours.

Castellan raises the alarms about the manor as a whole (an agent whose page is down, an update it couldn't install, Reeve's alerts), so the Steward raises only these. See Needs you, notifications and quiet hours.

How they reach you#

An alarm is raised once, and then:

• It's at the top of the Steward's page, under Needs you, until its condition clears.
• It's in Castellan's Needs you, with the rest of the manor's.
• One Windows notification comes for all the alarms raised in a round, while A Windows notification for each is on in the Steward's settings. Clicking it opens the Steward's page.

The Steward never acts on an alarm: it says what it saw, and what to do.

Dismiss#

Dismiss quiets an alarm until its condition clears. If it comes back after that, so does the alarm.

An update that was rolled back#

Castellan installs the Steward's updates by itself, and each one is on probation. Before anything changes, the version it replaces is copied aside. The new one must start, answer as the new version for 90 seconds, and show its page. If it doesn't, it's rolled back at once: the old version is put back and started again, and the new one's copy is kept for a look.

That version is then refused by every install after, so Castellan's automatic updates give up on it, and it's an alarm. A newer version installs as usual. Dismiss on the alarm is your look, and allows that version again; so does this:

node $HOME\.steward\app\src\cli.ts allow-update 0.35.0

Changing them#

In the Steward's settings, under Alarms:

• Raise alarms: off, nothing is raised.
• A Windows notification for each: off, alarms stay on the pages only.
• A PR waiting for: how long a held pull request waits before it's an alarm, 1 to 168 hours.