docs: single Gates home and honest UX ownership

Move Gate A/B/C meanings to IMPL-PLAN. List UX-DESIGN as non-normative with
signed UX.md winning conflicts. List INVENTORY in AGENTS §0.

docs/IMPL-PLAN.md

@@ -18,6 +18,18 @@ Ground rules (from AGENTS.md):
 
 Test specification: `docs/TEST-SPEC.md` — pyramid cases, phased by gate, affirmative only.
 
+## Gates (human map)
+
+This file is the only place that defines Gate meanings and how they map onto phases. Other docs may name a gate; they must not restate this table.
+
+| Label | Human name | What it means |
+|---|---|---|
+| Gate A | Docs freeze | Product locks written into the repo |
+| Gate B | Run-host setup | Inventory the real host, deploy skeleton (`frontend/` + `backend/` + compose targets) |
+| Gate C | First draft listing | One Woo draft listing with inference OFF |
+
+**Phase 0 = Gates A+B.** **Gate C = early Phase 1** claimable publish slice. Call 1/2 after Gate C is green, still inside POC. Phase 2 is a deferred stub; do not build it next after Phase 1.
+
 ---
 
 ## Phase 0 — Hybrid skeleton and client deterministic core (= Gates A+B)

docs/UX-DESIGN.md

@@ -1,7 +1,8 @@
-# UX Design — SlabUploader Phone App
+# UX Design — wireframes (non-normative)
 
-Status: DESIGN · 2026-09-03 · SlabUploader
-Screens for the online-only POC flow. Mobile-first, 375px viewport.
+Status: DESIGN · non-normative · 2026-09-03 · SlabUploader
+
+**Not normative.** Signed presentation SoT is `docs/UX.md` (phone and PC browsers). If a wireframe here disagrees with `docs/UX.md`, AGENTS, or TECH-SPEC, follow those and ignore the wireframe. These ASCII screens are layout sketches for discussion, drawn at a 375px phone width; they do not lock mobile-only or override the phone+PC matrix.
 
 Functional rules live in `docs/UX.md`. Confidence gating: `AGENTS.md` §6.
 Data model and status machine: `docs/DATA-MODEL.md`.