A public demo: one lockout, walked through step by step · Systems Admin devlog

This Role's work is invisible on a normal day, so its demo is a guided tour rather than an app. It follows a lockout from beginning to end: a typo in a helper that every safety check shares, every Agent refused at once, the health check that finds the cause, the last good version restored, the same check run again, and the report afterwards.
The studio in the tour is made up, and the page says so at the top. The Agents, commits and output are invented. The order of the steps is the real recovery plan from Iteration 4.
Visitors click through it at their own pace. At the point where there are three ways out (a broken shared file, a broken Python install, or a cause that isn't known yet), they can open each one to see what it involves.
It's built from the studio's shared UI kit, and two checks run before it can be published: one stops the page reading hidden test switches from its address, and the site's own leak check confirms there are no private terms or file paths. It now carries the Systems Admin's helmet art.