WML state, tasks, events, forms, and navigation

1. WML-301In Progress
   Forward, backward, reload, failure rollback, context reset, and source-required table boundaries match strict ordering and layout across native and WASM adapters.→
2. WML-302Done
   Initialization, escaping modes, substitution contexts, setvar ordering, and invalid references match effective WML rules.→
3. WML-303Done
   go, prev, refresh, noop, intrinsic events, template/card shadowing, BACK availability, and activation order are deterministic.→
4. WML-304Done
   Field commit, postfield generation, same-deck suppression, accept-charset, URL encoding, multipart optionality, referer, and no-cache behavior follow SIN 105.→
5. WML-305Done
   Timer start, stop, resume, expiry, invalid values, ontimer dispatch, and host wakeups are deterministic and target-parity tested.→
6. WML-306Done
   Deck access checks, low-memory behavior, unknown DTDs, task failures, and user-visible errors have strict deterministic policies.→
7. WML-307Todo
   WML-C-05 and WML-C-06 receive complete source-derived encoding/entity evidence, and WBXML-C-001, WBXML-C-010, and WBXML-C-011 close non-WML token-table, implied-default, and generic-routing gaps without reopening WML-203.→
8. WML-308Todo
   Input, option, select, and optgroup presentation metadata and optional capability behavior are source-aligned without moving frame policy into the engine.→
9. WML-309Done
   Every active non-optional do is represented once with stable activation identity and best-effort authored labelling without assuming a vendor-specific physical widget.→

Exit contract

Evidence required to leave this sprint

• Mandatory WML runtime SCR lines are covered by deterministic tests.
• Form/network effects cross contracts without host-side semantic reimplementation.
• Native and WASM outcomes are equivalent.