hub (unreleased): the record of an off-site account outlives an untick; RESET and delete take the account down (R-1375, D71); runbook: a household or a tester leaves (D74)
gates / gates (push) Successful in 2m0s

An untick alone takes nothing down (pinned first). Tests run the real save and RESET over the repository's fake
provider. Not deployed.

Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
admin committed 2026-11-14 17:56:29 +01:00
1 parent 186f3fca58
commit e5c643d73d
11 files changed
+563 -2

No files matched your search

@@ -402,6 +402,41 @@ attempts, 7 s apart, a log line each) in the provision and the F-14 re-issue pat
the operator-only `pbsdr_provision_failed` („… save the customer config to retry"). Live 2026-10-26 on hub rc.1: a fresh
Tester4 install provisioned the tier on the first try.
### 14.1 The off-site account when its tier is switched off [FACT — built, not released: hub `main` after v0.181.0, 2026-11-14; D71, `09` §3 decision 291, R-1375]
The first off-site tier (the app copies) is a sub-account at the storage provider. The household's config form
rebuilds the whole config at every save, so until this change an UNTICK dropped the `offsite` block and the hub forgot
the account: a later RESET or delete skipped it, and the account stayed at the provider — paid for, with the
household's copies in it, and no record anywhere (endings EH06 and EH01).
- **An untick takes nothing down.** No provider call, no purge. This is the wrong case the tests pin first
(`TestD71_UntickKeepsTheAccountAndItsRecord_ResetTakesItDown`).
- **The hub keeps the record.** `offsite.KeepAccountRecord` runs at every save: a tier that was ticked AND provisioned
and is now unticked leaves `offsite_account` in the config (type, user, host, the time of the untick); later saves
carry it. It is not an `offsite` block, so the box is handed the tier as off. A tier that was ticked and never
provisioned made no account and leaves no record.
- **RESET and delete take the account down when a record exists** — ticked or not (`web.offsiteChoice` reads the
tick OR the record; both previews name the account). The folder is purged first, then the account is deleted, as
before (R-32); the record goes with the account.
- **Ticking again** takes the same account back into use (the provider is asked by the household's label) and the
record is gone: the descriptor is the record again.
- **The config form says it:** „The off-site tier is OFF, and this household's account still exists at the provider”.
**An account that lost its record before this release** (unticked, then saved, before the fix): the hub cannot know
it. One act finds them — at the provider's page, read each sub-account's label `felhom-customer=<id>`; for each one
whose household has the tier unticked in the hub, tick the tier again and save (the same account comes back, and its
record with it), then untick if it shall stay off. For a household that is gone: remove the account by hand, by its
label (`audits/RETIRE-peti-2026-09-25.md` A3). `runbooks/household-leaves.md`, „The untick trap”.
**The second off-site tier** (the whole-box copies on ep0) never had this fault: switching it off keeps its place and
its descriptor (`enabled:false`, coordinates kept — `TestPBSDR_DisableKeepsTenancy`), and RESET and delete take it
down by the customer id, ticked or not.
**Not proven:** on a deployed hub, or against the real provider. The tests run the real save, the real RESET and the
repository's fake provider (`hetznerapi.Fake`); 9 mutations seen red, one of them only after a missing test case was
added (`audits/night-build-2026-11-14/B/redproof-hub-offsite-record.txt`).
## 15. Customer e-mails — what the hub writes to a household [hub v0.118.0, R-558]
**The section this document did not have.** The hub composes every sentence a household reads before