[jacksteamdev]

Summary

- First-party runtime, tools, and examples: MPL-2.0
+ First-party runtime, tools, and examples: MIT
  Third-party dependencies: retain their existing licenses and notices

Update LICENSE, metadata, SPDX headers, documentation, and generated distribution notices. Preserve MPL dependency source links, upstream attribution, source archives, and data terms. No calculation or API changes.

Evidence

• Before: First-party package metadata and notice validation required MPL-2.0.
  After: MIT metadata is accepted; stale MPL first-party metadata is rejected. All 9 notice tests pass; regenerated bundles verify and both MPL dependency source downloads are accessible.
• Before: Distribution bundles identify the project as MPL-2.0.
  After: Native builder, browser, and Worker distributions identify project code as MIT while preserving third-party license sections and dependency inventories byte-for-byte.
• Workspace tests, Clippy, formatting, boundary checks, TypeScript checks, 11 CI tooling tests, Python verification checks, Cargo packaging, and browser build passed. Local Worker Wasm harness passed 6 structural cases and adapter checks. No hosted deployment or full dataset regeneration performed.

Merge Danger

Door: one-way

Future code changes can be reverted, but MIT permissions already granted to recipients cannot be withdrawn. Historical releases remain unchanged.

Blast Radius: licensing

Affects first-party reuse terms and distribution notices across the runtime, tools, and examples. Dependency licenses and calculation behavior are unchanged.