Release actionable diagnostics in engine 0.2.0

[konojunya]

背景

Stack Web and future editor consumers need compiler-owned expected values and guidance at the browser boundary. The engine package must preserve the newly merged compiler diagnostic contract without requiring consumers to reconstruct it.

実装方法

• Pin stack-compiler to merged commit 3d2379483da1edaeb24a26d43743587a4f5bd645 and the specification suite to 7f9154d22702ddf02f2713bbc06dde7bdf635806.
• Carry ordered expected values through native engine diagnostics, serializable WASM diagnostics, JavaScript objects, and generated TypeScript declarations.
• Add a shared direction hoo fixture that verifies exact range, expected values, help, empty related information, and native/WASM parity.
• Bump the Rust facade, WASM adapter, workspace, and npm package to 0.2.0, update SVG metadata snapshots, package documentation, and dependency provenance.

テスト方法

• cargo +stable fmt --check
• cargo +stable test --workspace --locked
• canonical formatter and engine conformance against the pinned specification
• python3 scripts/validate-svg.py
• npm run build:wasm && npm test && npm run typecheck && npm run pack:check
• cargo +stable clippy --workspace --all-targets --all-features --locked -- -D warnings
• RUSTDOCFLAGS="-D warnings" cargo +stable doc --workspace --no-deps --locked
• coverage gates: line 97.21%, function 97.11%, region 95.53%
• Rust 1.85 tests and Clippy

Review 視点 / 懸念点

This is a minor-version public package change because Diagnostic gains a required expected array. Renderer-owned warnings intentionally emit an empty array. Local WASI parity could not run because Wasmtime is not installed on this host; the unchanged CI job installs Wasmtime 48.0.1 and remains the release gate.