Recover a Stale Remote State Lock

Inspect and safely remove a stale lock from a local HTTP state backend.

A advanced Linux challenge worth 20 points. Solve it hands-on in a real Linux environment in your browser - no local setup, no fake shells.

The Challenge

Incident: The shared state backend at http://127.0.0.1:7777/state reports that CI runner 07 still owns lock stale-build-42, but that runner terminated yesterday. The backend is a local, network-isolated HTTP service with a real persisted lock record.

Confirm no live process owns that run, inspect the lock error, use terraform force-unlock with the exact stale ID, and complete a clean terraform apply. Do not delete or edit the state file. Run check when done.