Cross-layer parity and interoperability closure

1. INT-901Todo
   Every mandatory selected-profile feature participates in at least one unit, boundary, integration, or end-to-end evidence path.→
2. INT-902Todo
   Deck load, navigation, focus, render output, scripts, timers, effects, and traces are byte/semantic equivalent across targets.→
3. INT-903Todo
   Selected WAP transactions interoperate with Kannel and replay deterministically without allowing implementation behavior to override normative sources.→
4. INT-904Todo
   A real WAP deck can traverse the entire strict stack with deterministic session history, form submission, script effects, and rendered output.→
5. INT-905Todo
   Malformed source, constrained payloads, timeouts, duplicate packets, memory pressure, and script limits never crash or produce nondeterministic state.→
6. INT-906Todo
   A release candidate can be independently audited without inferring coverage from ticket status or source-file count.→

Exit contract

Evidence required to leave this sprint

• Cross-layer strict scenarios pass with native/WASM parity.
• Interop evidence supplements rather than replaces normative evidence.
• Every known deviation is explicit and ticketed.