Niklas Ye 17ee290d90 docs: the ack token is scoped, not single-use ...

The handler never deletes the token: it stays valid until expires_at and
is purged by the sweeper, so a second tap is an idempotent no-op rather
than a rejection. Caught by pressing Acknowledge twice against the live
server. What bounds the token is scope -- one incident, one action, one
day -- not a use count.

2026-08-07 11:41:15 +02:00

..

alertmanager.go

Page the on-call person when an incident opens

2026-08-07 08:51:38 +02:00

alerts.go

Turn incoming alerts into incidents

2026-07-30 17:02:13 +02:00

api_test.go

Page the on-call person when an incident opens

2026-08-07 08:51:38 +02:00

archiver.go

Page the on-call person when an incident opens

2026-08-07 08:51:38 +02:00

helpers.go

Stage 2: users, API key auth, bootstrap endpoint

2026-05-20 21:51:09 +02:00

incident_store.go

Page the on-call person when an incident opens

2026-08-07 08:51:38 +02:00

incidents_test.go

Turn incoming alerts into incidents

2026-07-30 17:02:13 +02:00

incidents.go

Page the on-call person when an incident opens

2026-08-07 08:51:38 +02:00

middleware.go

Stage 2: users, API key auth, bootstrap endpoint

2026-05-20 21:51:09 +02:00

notifier.go

Page the on-call person when an incident opens

2026-08-07 08:51:38 +02:00

notify_ack.go

Page the on-call person when an incident opens

2026-08-07 08:51:38 +02:00

notify_test.go

Page the on-call person when an incident opens

2026-08-07 08:51:38 +02:00

router.go

docs: the ack token is scoped, not single-use

2026-08-07 11:41:15 +02:00

schedule.go

Stage 5: on-call schedule

2026-05-20 22:28:23 +02:00

stats.go

Turn incoming alerts into incidents

2026-07-30 17:02:13 +02:00

users.go

Page the on-call person when an incident opens

2026-08-07 08:51:38 +02:00