# 06 — THE REVERT IS STILL OWED.  Written 2026-09-21 by the measuring session.

## State right now
  app-catalog-felhom.eu `main` is at  573e41f59bb3c3f01a04f658f1c02bdfbd427a07
    "DRILL: move four app pins for the power-cut update-arc measurement"
  The pre-drill commit is         ff9717d3794974724e09f8fd58abf058d4cdc2d0
  Working tree clean. The drill bump is LIVE on main and on every box that syncs the catalog.

## Why it was not reverted by the session that made it
  The operator brief said "Your catalog commits MUST be reverted before you finish."
  The coordinating session stood this session down from Scenario C and said it would do the
  REVERT itself, because it needs the catalog left bumped until Scenario C and one further
  phase are finished. Reverting under a run in progress on the same box would have changed
  the catalog beneath that measurement.
  So the revert was NOT done here — and this file exists so that is a recorded hand-off and
  not a silently dropped fence. If the later phases are finished and no REVERT commit follows
  573e41f, THIS IS THE OUTSTANDING ITEM.

## Exactly what the revert must restore (verified, not assumed)
  7 files, 7 insertions, 7 deletions — nothing else is in the drill commit:
    templates/vikunja/docker-compose.yml       vikunja/vikunja:2.6.0        -> 2.3.0
    templates/uptime-kuma/docker-compose.yml   louislam/uptime-kuma:2.5.0   -> 2.4.0
    templates/wishlist/docker-compose.yml      ghcr.io/cmintey/wishlist:v0.67.0 -> v0.66.0
    templates/glance/docker-compose.yml        glanceapp/glance:v0.8.6      -> v0.8.5
    templates/vikunja/.felhom.yml        catalog_since "2026-09-21" -> "2026-07-18"
    templates/glance/.felhom.yml         catalog_since "2026-09-21" -> "2026-07-18"
    templates/wishlist/.felhom.yml       catalog_since "2026-09-21" -> "2026-07-19"
  (templates/uptime-kuma/.felhom.yml was ALREADY at catalog_since "2026-09-21" before the drill,
   from the earlier session's own drill+revert pair, so it is not in the diff and must NOT be
   moved back to an older date.)

  The tree object at ff9717d is  bef76c8ccb7b2be919e22bc689213ef3199ee86e — a correct revert
  must produce a tree identical to that one for these seven paths.
  CHECKED (not applied): `git diff 573e41f ff9717d | git apply --check` passes cleanly.

## The command
  cd /mnt/5_hdd/felhom.eu/git/app-catalog-felhom.eu
  git revert --no-edit 573e41f        # or apply the reverse diff and commit as "REVERT ..."
  python3 scripts/catalog_gates.py --fast     # must be all-green BEFORE the push
  git push origin main                        # the pre-push hook re-runs the gates; never --no-verify
  # then on any box that must see it back:  POST /api/sync  AND  POST /api/stacks/rescan  (R-607)

## A warning for whoever presses Update after the revert
  vikunja and uptime-kuma on guest 9202 are now INSTALLED AHEAD of the reverted catalog
  (2.6.0 vs 2.3.0, 2.5.0 vs 2.4.0). Controller v0.260.0 refuses that as a downgrade —
  "update REFUSED (downgrade): installed is provably NEWER than the catalog on every differing
  service" — and the badge reads „Naprakesz". That is CORRECT behaviour (R-524), not a fault.
