Public status page, SVG uptime badge (issue

A static, namespaced SVG — a fixed "uptime" label plus a status-colored message, <pct>% · <state> (or no data · <state> when the 30-day average has no data yet) — rendered from the same cached View the HTML page, RSS, Atom, and JSON siblings share — requests landing on the same cache entry always render identical state, but a rebuild after the entry's TTL expires (or a downstream cache holding the two URLs independently) can leave the badge and page briefly disagreeing across that boundary. Resolved, cached, and error-handled identically to those four siblings (same token-shape check, same GetStatusPageByToken lookup folding an unknown/off/deleted/ suspended token into one 404, same view cache and Age/Cache-Control computation, recomputed from the live clock on every response). No style element, no inline style attribute, no script element, and no external reference — presentation attributes only, so the document stays inside the status host's Content-Security-Policy and renders safely through an image proxy such as GitHub's camo.