WSP session, connectionless, headers, and host fetch

1. WSP-801In Progress
   All 109 WSP rows retain exact source disposition and the eight-row selected connectionless path maps to implementation evidence or corrective work.→
2. WSP-802In Progress
   Known tokens, code pages, text fallbacks, unknown policy, encoding versions, and round trips match the WAP 1.2.1 effective set.→
3. WSP-803Todo
   Connect, capability bounds, suspend/resume, disconnect, re-establishment, and overage behavior are deterministic.→
4. WSP-804In Progress
   Browser mode selection, native fetch, fallback policy, error mapping, and Kannel smoke behavior preserve the generated transport contract.→
5. WSP-805In Progress
   Effective WML form data crosses engine, host, connectionless WSP, and WDP with exact method/content/request-policy semantics; WTP is activated only for connection-oriented WSP.→
6. WSP-806Todo
   WAP-230-derived behavior is classified as compatible, strict correction, or successor-only.→

Exit contract

Evidence required to leave this sprint

• The eight-row selected connectionless WSP path has executable evidence.
• Connection-oriented WSP and WTP remain separately capability-gated.
• Desktop GET and POST use the native stack with explicit fallback.
• Generated Rust/TypeScript transport contracts have no drift.