Build out "status page" to post incident/interruption content

## Context

Letting users know what's going on within a system is part of a well designed user experience. We need to identify what should be surfaced for the user. Users should be informed about what is going on while interacting with the machine or a system or a thing through continuous feedback within a reasonable time or can be within a fixed period of time.

This also came up in incident: [2026-02-02-client-ip-detection-causing-hcaptcha-errors](https://docs.google.com/document/d/1fVSzj3jlPJmd9hcdIQYt1aePXlS6zP1WCp-_32R_hNc/edit?tab=t.0)
for how we might **consider building a status / incident page** so that we can post this kind of interruption or issue without having to send an email.

## Why

- Something similar to Notify: https://status.notification.canada.ca/#en
- Avoids having to send so many email updates throughout an incident
- Related: #402

## What's involved

- [ ] Identify scenarios where system status is hidden from the user
- [ ] Define reasonable amounts of time for feedback
- [ ] Explore options for surfacing system status
- [ ] Develop designs for visibility
- [ ] Potential usability testing of options

## References

- [NN/g](https://www.nngroup.com/articles/visibility-system-status/)
- [UX Planet](https://uxplanet.org/1-visibility-of-system-status-simplified-by-the-examples-1cca76f59b6a)
Acceptance criteria