Analytics · Bug Trend
Severity-weighted burn-down over the open-bug register. Each sparkline is a deterministic derivation of the live count — the latest point equals the number in the table, so the trend never overstates progress.
2
Bugs tracked
0
Still open
2
Known / accepted
0
Severity pressure
Trend by Severity
Bug count per severity bucket, most severe first. The sparkline shows the deterministic burn-down to today's count; the bar tracks each bucket against the busiest one.
Open Register
No actively open bugs — every remaining item is a known, accepted limitation.
BUG-4Realtime out-of-scope for single-image build (no live push)
Live push / Realtime is out-of-scope for the single-image staging build, so views do not auto-refresh. Known and accepted for this build; live push needs the multi-container Supabase stack (Realtime + Kong).
Realtimeknown
BUG-5Email delivers on staging (Mailpit); production relay still to swap
Email now DELIVERS on staging with no external creds via a self-hosted Mailpit catcher (SMTP :1025 / inbox :8025) — verified: POST /recover → 200 and the reset mail landed in the inbox. Remaining for real-inbox PRODUCTION delivery: swap Mailpit for a transactional provider (Resend/Postmark key) — a one-env-block change on a proven seam. Known/accepted for this build.
Auth / email deliveryknown