Runbook Repair Lab
Three fictional runbooks are broken: missing prerequisites, clashing versions, starved downstream steps — tweak them and watch problems vanish.
Runbook Repair Lab is a small tool for thinking through why a runbook will not run: it holds three fictional guides — build a paper town, light a lantern garden, stitch a pocket atlas. Each guide is a sequence of steps, and what each step needs, what it produces, and which tool versions it allows are all written out in the open. Open "Build a paper town" and you see seven problems right away: two missing prerequisites, three tool version conflicts, and two downstream steps stuck because they never got their input. You can change prerequisites yourself, swap tool versions, turn steps on or off, and watch the problem count go up or down; or just click "Try the owner-approved fix" and all three steps pass at once and the problems drop to zero. What makes this tool honest is that every command is display text only — nothing actually runs. The approval and rejection records for fixes are kept too: the lantern garden fix had all its conditions met and was still rejected, which shows nicely that "the conditions are right" is not the same as "it gets approved". One thing to be clear about: the three guides, tools and prerequisites are all fictional, and the demo page is a static snapshot, so your changes do not sync live. It helps you understand how dependencies chain together, step by step, but it cannot judge whether a real command is safe to run.
@煮面等水开