Evening 2026-10-18: fresh install proven (R-1148), OnlyOffice walk (R-1018), one-sign-in spike (R-1100 READY), Redis volumes (R-1117), CI rows, golden 0.331.0 baked; register 168 -> 168 (closed 6, opened R-1149..R-1154)

2026-10-18 23:12:21 +02:00
parent b9b56c47c0
commit e4f022a0d9
90 changed files with 1634 additions and 22 deletions
@@ -203,6 +203,10 @@ produced a false "unreachable" verdict (standing rule 2).
 Create and destroy freely **on a Tier 0 host**. Two exceptions: **`drill-r50`** is a fixture, not
 scratch; and scratch **customers** outlive their VMs in the hub — delete those too, or they accumulate
 (`sess-c` and `sess-d` were both left behind before anyone noticed).
+**One standing exception (operator, 2026-10-18): customer `Tester4` is KEPT** as the fresh-install customer
+(domain `tester4.test`, mail `tester4@felhom.eu` — the Gmail catch-all). Before each new install with it, the operator
+deletes its OLD host record on the Hosts page: an enroll that finds the customer's old host reuses it and skips the claim
+and off-site re-issues in silence.

 **The hub-side teardown waits for the stale threshold — plan for it (R-599).** After the VM is destroyed
 the hub still reads its host as ONLINE until the last report is older than `alerting.stale_threshold`