# Run 2 — NOT a measurement of the template (kept as a record)

Run 1's drill bump (`walk_prowlarr.py`, drill commit f2b0cc1) opened the drill's `.felhom.yml` for writing BEFORE it read
it, so the file became EMPTY. Run 1's install, gate, first-admin, stranger and lock-out checks happened before that
commit and stand. Run 1's Update and run 2 as a whole ran with an EMPTY `.felhom.yml` on the box: no deploy fields, so
`app.yaml` `env: {}`, the traefik rule `Host(\`.enkisfelhom.hu\`)` and the app unreachable from outside (every
`gate: … not routed (404)` line). The seed still read back because the fixture talks to the app inside its container.

The defect was in the test tool, not in the product. Drill commit e917a58 put the full file back; run 3 (`../run3/`)
re-proves the step and the restore with it, and writes `../prowlarr/box-verdict-prowlarr.json`. Run 1's verdict is kept
as `../prowlarr/box-verdict-prowlarr-run1-empty-meta.json`.

One true fact from run 2, product behaviour: a restore after „remove, keep backups" brings the app back at the image
recorded in the backup (version-2.5.2.5491 here, the image before the Update), not at the catalog's newest.