WAE, caching, formats, and content behavior

1. WAE-601In Progress
   WAE requirements come from WAP-190 plus SINs, with WAP-236 used only for explicit successor deltas.→
2. WAE-602Todo
   Accepted content, character decoding, language/capability headers, URI limits, and unsupported content outcomes match the selected profile.→
3. WAE-603In Progress
   All five mandatory WAPCachingMod:MCF rows map to exact source IDs, implementation status, open work, and direct tests; zero-byte mode is explicit; both must-revalidate history branches, intra-resource behavior, and cache security are deterministic.→
4. WAE-604Todo
   Mandatory WBMP decode/display and fallback behavior are capability-tested without relying on modern browser image semantics.→
5. WAE-605Todo
   Content, script, navigation, access, memory, and unsupported-feature errors have strict observable behavior and diagnostic-only enhancements.→
6. WAE-606In Progress
   Each current WAP 2.0-derived behavior is confirmed compatible, changed for strict mode, or isolated behind a successor/extension profile.→
7. WAE-607Todo
   The browser and transport implement deterministic Basic challenge parsing, credential acquisition/storage policy, Authorization retry behavior, cancellation, and user-visible failure without treating header token registration as conformance.→

Exit contract

Evidence required to leave this sprint

• Class C browser/WAE mandatory groups resolve to tested behavior.
• Cache and media behavior are independent of modern DOM assumptions.
• WAP 2.0 successor behavior cannot silently leak into strict mode.