== MUTATION: THE WRONG CASE: an untick takes the account down
   RED on the mutant, GREEN on the real file
     --- FAIL: TestD71_UntickKeepsTheAccountAndItsRecord_ResetTakesItDown (0.05s)
     d71_offsite_account_record_test.go:81: AN UNTICK TOOK SOMETHING DOWN: 0 account(s) left (want 1), 1 purge call(s) (want 0)
== MUTATION: the record is not kept at the save (the old behaviour: the hub forgets the account)
   RED on the mutant, GREEN on the real file
     --- FAIL: TestD71_UntickKeepsTheAccountAndItsRecord_ResetTakesItDown (0.05s)
     d71_offsite_account_record_test.go:89: the account's record did not survive the untick and two saves: <nil> in {"logging":{"level":"debug"}}

2 mutations, 0 not a red-proof
== MUTATION: RESET reads only the tick (an unticked account is skipped)
   RED on the mutant, GREEN on the real file
     --- FAIL: TestD71_UntickKeepsTheAccountAndItsRecord_ResetTakesItDown (0.05s)
     d71_offsite_account_record_test.go:107: the reset preview does not name the kept account u629193-sub1000: {"claim_present":false,"customer_id":"acme","dr_recipe_present":false,"escrow_ack_required":false,"host_count":0,"offsite_en
     d71_offsite_account_record_test.go:107: the delete preview does not name the kept account u629193-sub1000: {"claim_present":false,"cloudflare_manual":["the Cloudflare tunnel that serves acme.hu","the DNS records of acme.hu (the ap
     d71_offsite_account_record_test.go:123: after the RESET: 1 account(s) left (want 0), 0 purge(s) (want 1) — the unticked account was skipped

1 mutations, 0 not a red-proof
== MUTATION: the record is written once and lost at the next save
   RED on the mutant, GREEN on the real file
     --- FAIL: TestD71_UntickKeepsTheAccountAndItsRecord_ResetTakesItDown (0.04s)
     d71_offsite_account_record_test.go:89: the account's record did not survive the untick and two saves: <nil> in {"logging":{"level":"debug"}}
== MUTATION: a ticked tier keeps the old untick record
   *** NOT A RED-PROOF *** (mutant rc=0 built=True real rc=0)
== MUTATION: a tier that was never provisioned gets a record
   RED on the mutant, GREEN on the real file
     --- FAIL: TestKeepAccountRecord_FourCases (0.00s)
     account_record_test.go:38: ticked, never provisioned, then unticked: no account was made, no record: a record &{Type:shared User: Host: UntickedAt:2026-11-14T20:00:00Z}, want none ({"git":{"username":"x"},"offsite_account":{"type"
== MUTATION: the record outlives the account after a RESET
   RED on the mutant, GREEN on the real file
     --- FAIL: TestD71_UntickKeepsTheAccountAndItsRecord_ResetTakesItDown (0.05s)
     d71_offsite_account_record_test.go:131: the record outlived the account: {"logging":{"level":"debug"},"offsite_account":{"type":"shared","user":"u629193-sub1000","host":"u629193-sub1000.your-storagebox.de","unticked_at":"2026-11-1
== MUTATION: the kept record is written as an offsite block (the box would read it)
   RED on the mutant, GREEN on the real file
     --- FAIL: TestD71_UntickKeepsTheAccountAndItsRecord_ResetTakesItDown (0.05s)
     d71_offsite_account_record_test.go:89: the account's record did not survive the untick and two saves: <nil> in {"logging":{"level":"debug"}}

5 mutations, 1 not a red-proof
== MUTATION: a ticked tier keeps the old untick record (done again: the first run of this mutation was GREEN — the table had no case for it; the case was added)
   RED on the mutant, GREEN on the real file
     --- FAIL: TestKeepAccountRecord_FourCases (0.00s)
     account_record_test.go:40: a config that carries BOTH a ticked tier and a record: the record goes (the descriptor is the record): a record &{Type:shared User:u1-sub3 Host: UntickedAt:}, want none ({"offsite":{"enabled":true,"type"

1 mutations, 0 not a red-proof
== MUTATION: the hub's account record is merged into the box's config
   RED on the mutant, GREEN on the real file
     --- FAIL: TestGenerate_TheAccountRecordNeverReachesTheBox (0.00s)
     offsite_account_record_test.go:23: the box's config carries the hub's account record ("offsite_account"):

1 mutations, 0 not a red-proof
