WML parse/error taxonomy

Generated from canonical repository manifests. Do not edit this note directly.

Relationships

• contains ← [[sprints/WML-2|WML-2]]
• covers-family → [[source-families/wml|wml]]
• owned-by → [[owner-layers/browser|browser]]
• owned-by → [[owner-layers/engine-wasm|engine-wasm]]
• owned-by → [[owner-layers/qa|qa]]
• planned-by ← [[clauses/WML-CL-ERROR-ENFORCEMENT|WML-CL-ERROR-ENFORCEMENT]]
• planned-by ← [[clauses/WML-CL-ERROR-NO-INTENT-INFERENCE|WML-CL-ERROR-NO-INTENT-INFERENCE]]
• planned-by ← [[clauses/WML-CL-TASK-FAILURE-ATOMICITY|WML-CL-TASK-FAILURE-ATOMICITY]]
• relates-to → [[legacy-tickets/R0-07|R0-07]]

Data

{
  "status": "done",
  "ownerLayers": [
    "engine-wasm",
    "browser",
    "qa"
  ],
  "sourceFamilies": [
    "wml"
  ],
  "notes": [
    "The direct graph slice maps WML-CL-ERROR-ENFORCEMENT, WML-CL-ERROR-NO-INTENT-INFERENCE, and WML-CL-TASK-FAILURE-ATOMICITY.",
    "Native invalid-load tests cover an invalid form of all 36 declared WML elements plus source-defined case, literal, length, table, task, event, variable, prologue, and structural failures.",
    "The executable production-WASM story proves both fetch failure and access denial preserve the invoking state and pending external intent while surfacing a stable host notification. The host remains responsible for fetching; WBXML decoding remains in transport.",
    "WML-205 closes only the bounded error-handling slice. Broader task, variable, timer, rendering, sendreferer, low-memory, and optional-capability work remains additive under WML-3 and later slices."
  ],
  "existingTickets": [
    "R0-07"
  ],
  "outputs": [
    "WML parse/error taxonomy",
    "Exhaustive declared-element invalid-WML enforcement",
    "Atomic host fetch/access-control failure notification"
  ],
  "acceptance": [
    "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."
  ],
  "evidence": [
    "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"
  ],
  "source": "docs/waves/wap-1.2.1-compliance-program.json"
}