WAP LabsProject atlas

Work item · WML parser, deck model, and validation baseline

WML-205

Malformed XML, invalid WML, unsupported optional constructs, and recoverable content errors have spec-shaped deterministic outcomes.

Done

Definition of done

  • Malformed XML, invalid WML, unsupported optional constructs, and recoverable content errors have spec-shaped deterministic outcomes.
  • Every declared WML element has a rejected invalid form, and literal, length, table, task, event, variable, prologue, structural, and case-sensitive constraints fail atomically without intent inference.
  • Fetch and destination access-control failures notify the user while preserving the invoking card, context, pending external intent, event/focus state, committed session metadata, and history across the native/WASM host boundary.

Artifacts to create or change

  • WML parse/error taxonomy
  • Exhaustive declared-element invalid-WML enforcement
  • Atomic host fetch/access-control failure notification

How closure is proven

  • cargo test --manifest-path engine-wasm/engine/Cargo.toml wml_205
  • pnpm --dir browser/frontend test
  • pnpm test:story WML-205
  • node scripts/check-wap-selected-normative-clauses.mjs
  • node scripts/check-wap-knowledge-graph.mjs