deploy grimmory (fields beyond DOMAIN/SUBDOMAIN: ['HDD_PATH'], values not printed) -> 202 {'ok': True, 'message': 'Telepítés elindítva – az állapot a kártyán követhető'}
    gate files right after the press: family-gate-grimmory.yml setup-gate-grimmory.yml
    deployed in 85 s: state=running pinned={'grimmory': 'ghcr.io/grimmory-tools/grimmory:v3.5.0', 'grimmory-db': 'mariadb:11.4'}
    family_gate record: family_gate: since: "2026-10-02T07:38:31Z" hosts: - library.enkisfelhom.hu
the household makes the first admin through the setup gate -> 200
    setup gate opened by its probe after ~10 s; gate files: family-gate-grimmory.yml
NOTE: attempt 1 stopped on a HARNESS error: after Grimmory's setup gate opened, box_walk still held the SETUP-gate cookie, which the family gate rightly refused (401 on an API path, no redirect, so no retry). The product behaved as designed. Cleaned up through the product (remove with data, member removed) before attempt 2.
cleanup: remove grimmory WITH data -> ('200', {'ok': True, 'data': {'removed': 'grimmory', 'volumes_removed': ['grimmory_grimmory_db'], 'hdd_paths_removed': ['/mnt/felhom-drives/hdd_1/appdata/grimmory/data (4.0K)'], 'hdd_paths_preserved': [], 'backup_paths_removed': ['/mnt/felhom-drives/hdd_1/backups/primary/grimmory (32K)'], 'verified': True}, 'message': 'Stack grimmory removed'})
cleanup: remove member b4teszt -> {"data":{"members":[],"name":"b4teszt"},"error":"","ok":true}

left: /mnt/felhom-drives/hdd_1/appdata/grimmory
/mnt/felhom-drives/hdd_1/userdata/media/grimmory
