Start with the incident routine, then run three deliberately small experiments. The goal is to make each decision explainable with an observation and a test.
01The first 15 minutes of a Linux incidentExplanatory guide · not a lab report · 3 min read02A 404 is a clue. Test before you restart.Workspace-tested lab · 3 min read03Catch a changed artifact before deploymentWorkspace-tested lab · 3 min read04An HTTP 200 can still need a rollbackWorkspace-tested lab · 3 min read
What was actually tested?
The lab ran in an AI-assisted isolated Linux workspace with Python 3.12.14 on 29 September 2026 UTC. All three experiments passed their assertions. This is not a claim of testing on Romeo’s miniPC, a customer environment, or a production service.
The download includes the script, configuration, README, captured transcript, and a GitLab CI example. The CI example has not been run against a live GitLab instance here.
Download the reproducible labWhat to do after the last note
Rerun it in your own disposable Linux or WSL environment. Record the version and output, then use the checklist to apply the reasoning to a change you are authorized to make.