feat: publish marknest-wasm to npm via release workflow

[developer0hye]

Summary

• Add WASM build and npm publish to the existing release workflow
• Bundle runtime assets (mermaid, mathjax) within the wasm crate for self-contained builds
• Publish marknest-wasm npm package on every tagged release

Key changes

• crates/marknest-wasm/runtime-assets/: Bundled mermaid.min.js and tex-svg.js
• crates/marknest-wasm/src/lib.rs: Fix include_bytes! paths to use crate-local assets
• .github/workflows/release.yml: New build-wasm and publish-wasm-npm jobs

Usage after publish

import init, { analyze_zip, render_zip_preview } from 'marknest-wasm';

await init();
const index = analyze_zip(zipBytes);

Test plan

• cargo check -p marknest-wasm --target wasm32-unknown-unknown passes
• All 12 WASM tests pass
• Verify wasm-pack build in CI after merge

🤖 Generated with Claude Code