hub v0.70.1: the ghost customer's Delete button must exist (Danger-zone render gate split)

2026-07-22 09:23:37 +02:00
parent 2cf37f263b
commit f4c2c4151b
7 changed files with 199 additions and 4 deletions
@@ -51,6 +51,11 @@ UI. Package map, helpers, seams, extension points: **`REUSE.md`** (e.g. new even
 - Add debug capabilities (logging, verbose output).
 - If you need more input or troubleshooting output, **ask first — don't guess**.
 - Testing doctrine (non-hollow tests, red-proofs, seams): use the `felhom-testing` skill.
+- **Seam-wiring rule — and it covers TEMPLATE GATES (fourth inert seam, hub v0.70.1):** a feature
+  is not shipped until its entry point is reachable. For UI, any conditional affordance
+  (`{{if .Flag}}` around a button/form/script) ships with a render test per branch of the gate —
+  handler tests that POST directly prove nothing about reachability. The v0.70.0 ghost-delete was
+  fully implemented server-side and fully dead UI because the button sat inside the wrong gate.
 - UI/design work (tokens, gates, copy rules): use the `felhom-ui-design` skill.
 - **Logging**: levels/English/no-secrets rules per `documentation/runbooks/logging-conventions.md`
  (DEBUG = flow detail, INFO = state change + duration; logs are operator-tier English; keys never