WML state, tasks, events, forms, and navigation

1. WML-301Todo
   Forward, backward, reload, failure rollback, and context reset match strict ordering across native and WASM adapters.→
2. WML-302Todo
   Initialization, escaping modes, substitution contexts, setvar ordering, and invalid references match effective WML rules.→
3. WML-303Todo
   go, prev, refresh, noop, intrinsic events, template/card shadowing, BACK availability, and activation order are deterministic.→
4. WML-304Todo
   Field commit, postfield generation, same-deck suppression, accept-charset, URL encoding, multipart optionality, referer, and no-cache behavior follow SIN 105.→
5. WML-305Todo
   Timer start, stop, resume, expiry, invalid values, ontimer dispatch, and host wakeups are deterministic and target-parity tested.→
6. WML-306Todo
   Deck access checks, low-memory behavior, unknown DTDs, task failures, and user-visible errors have strict deterministic policies.→

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.