refactor(core): centralize FFI option-key manifest (TS/napi/wasm/Python)

[dean0x]

Summary

Create a normative, single-source-of-truth option-key registry spanning the four FFI surfaces (TypeScript, napi, WASM, Python). Currently, four independently hardcoded key lists are reconciled only by prose comments, and the WASM-vs-napi parser naming needs a private rename.

Deferred Issues

From review [wave-v0.4.0-wave1/2026-08-19_1216]:

Finding	File:Line	Reason
architecture-02	packages/mds/src/util/options.ts:100	Cross-language generated key manifest spanning 4 FFI surfaces.
consistency-20	crates/mds-wasm/src/lib.rs:413	All private, zero semver cost; rename alongside architecture-02.

Acceptance Criteria

• Define canonical option-key registry (single JSON or Rust data structure)
• Generate TS, napi, WASM, and Python from the registry
• All four surfaces verify against the registry in tests
• WASM parser naming renamed (private only, no semver impact)
• Prose comments replaced by generated code

Related

• PR v0.4.0 Wave 1: breaking changes, live-bug fixes, and release-safety gates #308 (wave/v0.4.0-wave1)

For v0.5.0