8 Commits

Author	SHA1	Message	Date
Niklas Ye	9d1df2b611	Show week numbers on the rota, and assign a whole week from them ... The rota grid starts each row with its ISO week number, and for an owner the number is a button: one tap opens a sheet for that week, showing who holds each of its seven days, and puts one person on all of them. A rota is usually handed out by the week, and seven taps on seven days was the only way to do it short of the range form. ISO 8601 numbering, because the grid already runs Monday to Sunday: week 1 is the one holding the year's first Thursday, which is taken from the Thursday of the row so the year boundaries come out right (2025-12-29 is week 1 of 2026, 2020-12-31 is week 53). Days already past are left alone. Who was on call last Tuesday is a fact, and "the whole week" should not rewrite it, so a half-elapsed week covers the days still to come and the sheet says so; a week that is entirely over has nothing to assign. By default the assignment replaces whoever holds those days, as the day sheet does and the sheet states, and a checkbox limits it to the days nobody has yet. The overhang into the neighbouring month is part of the same week and is included. Web UI only: the existing schedule endpoint already takes a list of dates and a replace flag, so nothing changed on the server and there is nothing to mirror in terdut-tui.	2026-09-26 09:19:35 +02:00
Niklas Ye	e616c82646	Show team members as a list, with who is on call and who cannot be paged ... Team -> Members was a two-column table and an inline add form. It is now a table in the style of Switches, Sources and Escalation: a status badge, the member, their role, their next rota day, when they were last active and when they joined. Adding a member and changing a role moved into sheets, and removing one asks first. The badge is the one that matters at 03:00: On call if the rota has them today, Reachable if they have an ntfy topic, and Can't be paged when a page to them would go nowhere -- no topic, or a disabled account -- with the reason under their name. Not being pageable wins over being on call, since an on-call person nobody can reach is the case worth seeing before an incident finds it. The rules are the notifier's own. The topic itself is never in the response, only whether one is set. Last active is the newer of a member's newest session and API-key use, and is shown to every member of the team like the rest of the list. Rota days are UTC dates, and the page formats them as such so a day cannot show up as the one before. Removing a member leaves the rota days already assigned to them alone, which the confirm says, so they are reassigned from the Rota tab rather than silently dropped. Demoting the last owner is now refused with 409, as removing them already was: it was the same outcome by another route, a team with nobody who can edit it. API: GET /members gains status, on_call, next_shift, pageable, problem and last_active_at; additive, no migration, and terdut-tui needs nothing. POST /members answers 409 for the last-owner demotion.	2026-09-26 09:04:54 +02:00
Niklas Ye	1f1faa437c	Show the escalation ladder as a list, with who it would page and where it is ... Team -> Escalation was the draft form on the page, which showed the ladder only as inputs. It is now a table in the style of Switches and Sources: a row per level with a status badge, who it pages, the wait before the next level, and the open incidents currently waiting on it. Below it, the repeat count, the fallback topic and when the ladder last escalated (linking the incident). The editor moved into an "Edit ladder" sheet, so a poll of the page underneath can no longer throw away half an edit, and the page-level draft state went with it. Targets are resolved to who they mean today, and the badge says what would actually happen: Ready, Escalating (an unanswered incident has climbed to level 2 or higher), or Pages nobody. The last is the one worth seeing before an incident finds it: an empty rota, a person with no ntfy topic or a disabled account each make a rung a silence with a number on it, and the target says which. The rules are pageLevel's own, so the page cannot promise a page the notifier would skip. "Last escalated" comes from the escalated timeline events that already exist, so there is no migration. Acknowledging or resolving takes an incident off the ladder, so Escalating clears then while the history stays. API: GET /escalation gains status and waiting per level, username, reachable and problem per target, and last_escalated_at and last_escalated_incident_id. Output only and additive; PUT is unchanged and terdut-tui needs nothing.	2026-09-26 08:28:24 +02:00
Niklas Ye	d675f8ec9b	List alert sources with their status and last arrival on Team -> Sources ... Like Team -> Switches, the page is now a table: a status badge (Active if the key posted within a day, Quiet if it has but not lately, Never used), when it last posted a webhook, when an alert last arrived on it, how many distinct alerts it refreshed in the last 24 hours, and when it was created. Adding a source moved into a "New source" sheet, and owners can rename one from its row. "Last alert" and the count needed alerts to remember which source they came in on, which they never did, so migration 010 adds alerts.integration_id and every accepted payload stamps it. Last sender wins when two sources post the same fingerprint. It is not backfilled: a NULL says "before this was recorded" rather than guessing, and it heals by itself as Alertmanager re-sends each alert every repeat_interval. Revoking a source keeps its alerts, unattributed. Last webhook and last alert are separate on purpose: a payload with nothing usable in it stamps the first and not the second. The Quiet threshold is a fixed day, a colour and not an alarm, since silence that should page is what dead man's switches are for. The counts are indexed subqueries (alerts_integration_idx) rather than a join, which would read every alert a source ever delivered. API: the integrations list gains status, last_alert_at and alerts_24h, and PATCH /api/teams/{id}/integrations/{id} renames. Both are additive; terdut-tui needs nothing.	2026-09-26 07:52:07 +02:00
Niklas Ye	f3918b863c	List dead man's switches with their status on Team -> Switches ... The page was a bare form: it did not say which switches existed or whether they were alive. It now lists them, each with a Healthy, Dead or Dormant badge, when its heartbeat was last heard and when it last opened an incident (linked while that incident is open). A matcher that several clusters satisfy is broken down per cluster, since a live cluster must not hide a dead one. The form moved into a "New switch" sheet, and each row has a Remove with a confirm. That needed a switch to be a thing, so switches are rows now (migration 009) with their own name, matcher, timeout and severity, instead of one string with one team-wide timeout in deadman_configs. Existing configuration is split into one row per matcher; a team whose timeout was zero simply has none. The sweeper and the status endpoint share one death rule (deadmanAlert.dead), so the page cannot disagree with the pager. Incident group keys are unchanged, so incidents that are open across the upgrade keep working. The environment defaults (TERDUT_DEADMAN_*) are seeded into teams once per install, recorded in settings, so a team that deletes its last switch does not get it back on the next restart. Installs that already had per-team rows are marked as seeded by the migration. Removing a switch stops the watching but leaves an incident it already opened open until someone resolves it. API: GET/PUT /api/teams/{id}/deadman are replaced by GET/POST /deadman/switches and DELETE /deadman/switches/{switchID}. terdut-tui does not call them, so nothing to mirror there.	2026-09-25 23:40:55 +02:00
Niklas Ye	3cdd5aee1f	Give the Team tab sub-sections of its own ... The Team tab was five cards stacked on one page: the rota, the escalation ladder, the alert sources, the dead man's switches and the membership. 07914d5 split the Admin tab for three reasons, and all three were sharper here. There was no way to link somebody to the escalation ladder, which is the thing a team owner most often has to be talked through. There was no way to the switches but scrolling past a month of rota -- and the rota became a month grid in v0.18.0, which made the page taller rather than shorter. And the poll loop refetched six endpoints every tick however little of the page you were looking at. Each is now a route: /team/rota, /team/members, /team/escalation, /team/sources, /team/deadman, reached from the same strip of links the Admin tab uses, with /team an overview. A page fetches only what it shows, so the switches are one GET and the sources are one, where every tick used to be six. Three of the five fetch the member list besides their own endpoint, and for the same reason each time: a rota entry, a ladder target and a role are all a person, and the page has to be able to name them. The overview is the one that fetches everything, because saying how much of each there is means asking each of them -- who is on call today, how many members and owners, how many ladder levels and whether a fallback follows them, how many keys and how many never used, how many switches. That is what it is for; a strip that already links to the five does not need a second menu that repeats it. team.js owns the table of its six routes, as admin.js owns its four, and app.js parses against both rather than keeping a third list to drift from them. The table carries a title beside the label where the strip's word is too thin to name a page on its own: "Sources" is a fine tab and a poor browser tab, so that page titles as Alert sources and the switches keep their apostrophe in the top bar. menuItem left admin.js for ui.js as menuCard, since both tabs now open on one, and its CSS went from .admin-menu* to .overview-*. That is the rename .user-link -> .row-link was in v0.18.0, for the same reason: the class was named after the first page that used it rather than after what it is. The read-only notice a member sees is now on the overview only. It explains why the controls further down are missing, and a page that is nothing but the rota grid has no controls to explain. The team picker sits above the strip, because it changes the subject of all five, and it drops the ladder draft when it moves -- an unsaved edit belongs to the team it was started in. No server change. Extensionless paths already fall back to index.html, so /team/rota survives a reload the way /admin/users/{id} does, and no endpoint, payload or permission moved. Nobody has looked at this in a browser, the caveat 07914d5 and a6fa673 carried. What is checked is the wiring, and rather more of it than last time: every sub-page was rendered against a stub fetch and a pocket DOM, each with exactly one aria-current and fetching only the endpoints named above; and app.js itself was booted the same way and walked through all seventeen URLs the app has, which resolve to one section each with the right title -- the six new ones, the four Admin ones, both subject pages, and /incidents/42 and /nonsense still falling to the queue. Whether six entries scroll cleanly at phone width is not checked. Claude-Session: https://claude.ai/code/session_01RHPj4ggeFdEjKKfm4SHbD7	2026-09-22 12:23:11 +02:00
Niklas Ye	67d68ce058	Show the rota as a month rather than a list of dates ... The Team tab printed the next thirty days as thirty rows of date, name and a Clear button. That is a rota spelled out one day at a time, and it is the one shape the question cannot be read in: what anybody wants from a rota is who holds which stretch, and thirty names down a column hides a handover between two rows that look the same. It was also the longest thing on the page by a wide margin, so the escalation ladder and the alert sources sat below a screen of dates. It is a month now, Monday to Sunday, one coloured initial per day. A shift becomes a run of one colour, which is the shape the answer actually has; a gap becomes a hole you can see. The legend underneath says whose colour is whose, and one line says how many days are left uncovered, counting only from today -- an empty Tuesday last week is history, not a hole somebody still has to fill. Laid out like the on-call page's week, deliberately: heading and arrows outside the card, days inside it. It is the same rota, and two pages showing it two ways would be two things to learn. Colours come from a person's place in the member list, so they hold still as you page between months, and six of them repeat -- the initial inside still tells two people apart, and a legend that has to explain nine hues is not a legend. They are not the severity palette: nothing on a rota is critical, and a red Thursday would read as one. --teal and --pink are new in both themes for the two the palette was short. The per-row Clear button had nowhere left to live, so a day opens the sheet the app already uses for confirmations: who holds it, a picker, Assign and Clear. That assign sends replace=true where the range form still asks first, and the difference is the point -- the sheet has just named whoever holds the day, so taking it from them is the thing that was asked for rather than something to warn about. The range form is unchanged and folded into a details, since filling a whole shift is what it is for; it opens on the month above it rather than on today, so paging to March to fill March does not hand you September. The server is untouched. The month drawn is the month fetched -- the grid's Monday overhang and its trailing days are real days and are fetched with it -- so paging is one GET /api/teams/{id}/schedule per month with from and to, where it used to be one fixed thirty-day window. No new endpoint, no change to what the API returns, and terdut-tui is unaffected. Nobody has looked at this in a browser either. What is checked is the rendering: team.js's own refresh() was run against a stub fetch and a pocket DOM for September 2026, and it produces 35 cells for a month whose 1st is a Tuesday, the right from/to on the schedule call, today marked on the 22nd, three people in the legend with "you" on the viewer, the gap count over a five-day hole, and -- as a member rather than an owner -- the same grid as plain divs with no sheet and no range form. How it looks at phone width, and whether the six colours hold up in dark mode, are not checked. Claude-Session: https://claude.ai/code/session_01RHPj4ggeFdEjKKfm4SHbD7	2026-09-22 09:13:36 +02:00
Niklas Ye	d728af53b1	Put a team's own settings in the web UI ... Closes #17. Everything a team owner configures was API-only: escalation, integrations, dead man's switches, membership, and the rota -- which the on-call view still described as the TUI's job, and the TUI has been broken against this server since teams landed. Setting up the feature this whole line of work exists for meant using curl. A Team tab now holds all of it, one team at a time, with a picker for somebody in more than one. An owner edits; a member sees the same page without the controls, because the server refuses their writes anyway -- hiding a button is a courtesy to the reader, not the thing enforcing anything. The escalation editor holds a draft and sends the whole ladder, because the API replaces it wholesale: the levels are an order, and patching one rung leaves the numbering of the others undecided. Adding a level defaults to five minutes and the rota, which is the shape almost every ladder starts as. An integration key is returned exactly once, so creating one opens a panel that says so, shows the URL large with a copy button, and renders the Alertmanager receiver snippet with the URL already in it -- the next thing anybody does with that key is paste it into a config. The panel stays until it is dismissed rather than disappearing on the next re-render. The incident view gains where an incident is on the ladder and when the next page is due, which is the question somebody looking at an unacknowledged incident actually has. The API carries it: the incident payload now includes escalation_level and escalation_due_at, the latter computed in the incident SELECT by joining the level's timeout, so a list costs no extra queries. Verified against a live server by making every call the page makes, including the writes: the six reads the Team tab issues, a two-level ladder saved and read back, an integration created and its key returned once, three days of rota assigned, switches set, and an incident showing level 1 with a due time five minutes out. Claude-Session: https://claude.ai/code/session_01RHPj4ggeFdEjKKfm4SHbD7	2026-09-20 21:22:24 +02:00