chore: bump AILANG WASM pin → v0.33.1

[github-actions]

Automated AILANG WASM pin bump

From: v0.30.0
To: v0.33.1

Release notes: https://github.com/sunholo-data/ailang/releases/tag/v0.33.1

This PR was opened automatically by the weekly refresh-ailang-wasm.yml
workflow. It is not auto-merged — CI runs the full suite including
the wasm-smoke Playwright job, which loads the new bundle in a
real browser and parses a fixture document. Merge only if green.

This PR self-supersedes. It lives on a fixed branch
(chore/bump-ailang-wasm), so when a newer AILANG release lands the
workflow force-updates this same PR rather than opening another one.
There should never be more than one open bump PR. Don't let it sit:
a pin left behind the ailang = ">=X.Y.Z" floor in ailang.toml
silently breaks the in-browser demo (see the pin-floor CI guard).

Review checklist

• check job (type-check + bindings) passes
• wasm-smoke job (Playwright) passes
• AILANG release notes don't flag any breaking change relevant to docparse
• Optional: spot-check the deployed Pages preview if your fork supports it

If the smoke test fails, do not merge — the new AILANG release
has likely regressed something. Open an issue against sunholo-data/ailang
with the smoke-test output and pin to the previous version.

[sunholo-voight-kampff]

⚠️ Do not merge — v0.33.0 is broken for this bundle.

Tested on #15: the v0.33.0 WASM runtime fails the Browser WASM Smoke Test exactly as v0.31.0 does — the bundle loads 5 modules (document, format_router, zip_extract, omml, docx_parser) then stalls, and DocParseEngine.isReady() never returns true. 60s timeout, no console error.

CI history shows the smoke test passing on v0.30.0 across six consecutive commits with identical module sources, so this is a runtime regression spanning v0.31.0 → v0.33.0, not a change in this repo.

v0.30.0 is the correct pin today — it is the newest runtime that boots. Reported upstream; leave this open until there is a release that passes.