hub v0.70.1: the ghost customer's Delete button must exist (Danger-zone render gate split)
This commit is contained in:
+12
@@ -3,6 +3,18 @@
|
||||
> Created with the REUSE.md rollout (2026-07-03). Authoritative history: `hub/CHANGELOG.md` (hub),
|
||||
> `website/CHANGELOG.md`, `scripts/CHANGELOG.md`; end-of-task detail in `REPORT.md`.
|
||||
|
||||
- **2026-07-22 — hub v0.70.1: the ghost customer's Delete button exists now.** The v0.70.0
|
||||
ghost-delete path was fully implemented and fully unreachable — the **fourth inert-seam defect**,
|
||||
this time a TEMPLATE GATE: the Danger-zone card (and the `customerDeleteOpen` script) sat inside
|
||||
`{{if .HasConfig}}`, so a ghost rendered no Delete button (found live on `demo-vm-felhom`).
|
||||
Fix: `Deletable` page flag = the exact negation of the delete preview's 404 predicate; RESET
|
||||
stays HasConfig-gated, Block/Unblock config-only. Render tests per branch + 2 red-proofs.
|
||||
**The seam-wiring rule now covers template gates** (see CLAUDE.md) — handler tests that POST
|
||||
directly prove nothing about reachability. **Operator live leg PENDING: the demo-vm-felhom ghost
|
||||
delete click** (doubles as v0.70.0+v0.70.1 live validation). Same day: **agent 0.93.0 published
|
||||
+ deployed fleet-wide** (`pilot/RUNBOOK-publish-agent-0.93-2026-07-22.md`), **R-17 CLOSED**
|
||||
(u629193-sub1 deleted at the console).
|
||||
|
||||
- **2026-07-21 — THE FLEET IS TWO HOSTS.** A second Proxmox node exists: **`demo-hp-bb76ea`**, an
|
||||
**HP t740 Thin Client** (Ryzen V1756B, 30 GiB, PVE node `felhom-host`, customer `demo-hp`), installed
|
||||
from the armed universal ISO the same day. Both hosts run **agent 0.92.1**; the N100 is
|
||||
|
||||
Reference in New Issue
Block a user