Bugs Resolved index + write-up for issue #70 A landing page for resolved bug reports, linked from the sidebar, and the first dedicated write-up under it: why renaming the Operational impact level split the status board in two. The #70 page covers the reported symptom, the reason healthy services were the broken ones (their status is derived, not stored, so six places invented the literal 'Operational'), the four further faces of the same bug that were not reported, the fix via the is_default flag, a colour-keyed file table, and how it was verified including the positive control. The index also lists two closed bug reports that have no write-up yet, so the gap is visible rather than forgotten. Service-Status gains a paragraph on how a healthy service's status is derived, linking to the write-up.