Preserve native interaction semantics

PLAN.md

@@ -1,17 +1,11 @@
 # Current plan
 
-## Slice HMX-002 — Native interaction and recovery
+## Closed receipt — HMX-002
+
+Result: Generated semantic anchors and forms use the canonical marker vocabulary, bounded request policy, accessible validation markup, enhanced requests, and native recovery.
+Proof: Focused Redgate checks, workspace gates, request-boundary tests, navigation failure recovery, and fresh-context review passed; HMX-002 IDs have no findings.
+Residual risk: Browser behavior is deterministically checked at generated-markup, runtime, and Axum boundaries rather than through an external browser harness.
 
-Outcome: Generated semantic HTML submits forms and navigation through the closed effect path while preserving accessibility and ordinary browser recovery.
-Delta: html/001–007, runtime/003–004, axum/003–004.
-Path: generated marker and native anchor/form -> request policy and Axum boundary -> rendered validation or navigation response -> accessible browser result or native fallback.
-Build: Align generated marker vocabulary, native-event defaults, bounded request policies, form encoding, validation markup, partial navigation metadata, and full-navigation recovery.
-Risk: Enhancement can suppress native input, accessibility, or fallback behavior and leave users unable to submit, navigate, or recover.
-Checks: Generated-markup assertions for every marker and policy value; browser scenarios with enhancement enabled and unavailable; form encoding and body-limit integration tests; validation accessibility assertions; partial/full navigation recovery scenarios; `redgate check` for the slice IDs.
-Non-goals: SSE, WebSocket, timers, reveal behavior, or island-owned local state.
-Residual risk: Optional adapter and island lifecycle remains open.
-State: Ready
-Blocked by: none
 
 ## Slice HMX-003 — Direct adapters and explicit islands