## Problem
Browsers could retain the local admin page, assets, or error responses,
leaving users on stale UI state after an FCC update.
## Changes
| Before | After |
| --- | --- |
| Admin responses had no complete cache policy, and route-level handling
missed exception responses. | A dedicated admin response boundary sends
`Cache-Control: no-store` for every `/admin` response, including 403,
404, validation, and unexpected errors. |
| Admin API fetches used the browser's default cache mode. | Admin API
fetches explicitly use `cache: "no-store"`. |
| Cache behavior was untested. | Tests cover HTML, assets, JSON, failure
responses, and path scoping. |
<!-- greptile_comment -->
<details open><summary><h3>Greptile Summary</h3></summary>
This PR prevents browsers from retaining stale admin UI responses. The
main changes are:
- Adds `Cache-Control: no-store` to successful and error responses under
`/admin`.
- Sets admin API fetches to use the browser's `no-store` cache mode.
- Adds te…