Table of Contents
v7.2.1 — Catch setup and retained rollback
Native Catch is live in owner Lobby 1. Catch guide · Current rooms.
This patch reuses an unused lobby's retained public Discord panel as well as its control channel. Missing or colliding routes are refused before committing configuration; existing rooms keep their panels and permissions.
Completed Catch setup transactions can be reviewed and rolled back after an upgrade through the exact root-protected committed installation history. The original runtime digest stays recorded. Pending, foreign or unverifiable transactions remain blocked. Configuration rollback retains Catch history/opinions and current sibling preferences while keeping a compatible controller and hub.
The exact reviewed predecessors are v7.1.20 and v7.2.0. This is a shared-controller release: automatic application waits for every configured room on that host to become safely empty. Upgrading does not add or replace rooms, change authorization/enrollment, or enable an opted-out service. Existing Standard/Mania settings and reliability repairs remain included.
Scope and qualification
The full native catalog has 13,395 records, including 12,317 eligible Ranked/Approved charts before room filters. Catch is NM, fixed difficulty, initial 3.00–4.00★; Loved, conversions, styles, farm and automatic difficulty stay excluded. Gameplay, supervisor code, dependency wheels and legacy readers are unchanged from v7.2.0.
Sixteen corrective unit cases, a fresh installed full-catalog Catch case, a retained v7.2.0 Catch-plan upgrade/rollback and a two-room signed automatic v7.1.20 upgrade passed. Configuration rollback retained Catch opinions and restarted the original rooms; enabled four-room Discord routing was checked. All invented donor rooms closed and processes were retired. Public artifact scans have zero unresolved findings. The broader v7.2.0 full-catalog and compatibility evidence remains applicable to unchanged code; the entire repository suite was not repeated, and historical unavailable/failing fixtures are documented in VALIDATION.json.
The actual owner startup, artwork, website and Discord connection are verified separately. No Catch player gameplay or manual Discord-button acceptance is claimed yet. The independently pinned owner recovery code was explicitly reviewed and refreshed without changing its policy or boot preferences.
Operators
Use the verified installer and Native Catch operator guide in the release. Catch addition is explicit and takes reviewed JSON through catch-pilot-prepare –settings-stdin. Keep state on any uncertain result; do not repeat room creation or delete a journal. The optional normalization helper only accepts stopped, positively closed diagnostic rows and creates no rooms.
Qualified installation target remains Linux x86_64/glibc, Python 3.12 and systemd. ARM and additional operating systems are not qualified by this release.
Installer, checksums and exact validation evidence · Native Catch foundation · Release history