chore(packages): bump @plannotator/ui to 0.33.0

[backnotprop]

Version bump, lockfile refresh, and docs for the npm release of @plannotator/ui 0.33.0, carrying the HTML viewer bridge as an asset (#1398) and the 0.32.0 adoption feedback (#1399). @plannotator/core stays at 0.25.0: git diff bafd1f5f..HEAD -- packages/core is empty, so this is a ui-only release on the already published core 0.25.0 and there is no lockstep or core-first ordering this time. Three commits, matching #1396: the bump, the lockfile refresh (bun pm pack stamps the core dependency from bun.lock), and a docs consistency pass.

Docs pass. The "Lazy renderers and eager entries" list in HANDOFF.md now describes the 0.33.0 state once: item 2 names the utils/math-default-loader split with its version, the adoption paragraph is labeled 0.33.0 instead of "post-0.32.0", and item 4 states what 0.32.0 left out, what 0.33.0 ships (the bridge asset and the loader split), and what is still open (the lazy table popout). "Publishing & versioning" names the pair as ui 0.33.0 on core 0.25.0 with no lockstep, lists the recent pairs, and notes that prepack now generates the two bridge files the exports map points at. README's publishing note says the same. The parity-seam edits from #1399 are clarifications of 0.32.0 behavior and carry no new version label.

Tarball verification. bun pm pack from packages/ui at this branch: 365 files, 2.65 MB packed, 4.98 MB unpacked, shasum f9bb4d551068c168d9d55ee9f22ed9f3b94cf29f. Prepack ran (styles.css, bridge-script.asset.js and bridge-script.lite.ts all carry the pack timestamp; the tree stays clean since they are gitignored). Checked on the extracted tarball: bridge-script.asset.js is byte-for-byte equal to BRIDGE_SCRIPT from the packed source module (186,803 bytes) and embeds protocol version 1; the lite module matches the CSS, protocol version and live bootstrap with an empty BRIDGE_SCRIPT; utils/math-default-loader.ts, HANDOFF.md, README.md, styles.css, theme.css, print.css and plannotator.webp are present; every file the 0.32.0 files globs covered at bafd1f5 (358) still ships; no test files ship; all 13 literal exports subpaths resolve inside the tarball and the 10 glob subpaths point at existing directories; package.json shows version 0.33.0 and @plannotator/core 0.25.0. tsc --noEmit -p packages/ui/tsconfig.strict-consumer.json passes as part of bun run typecheck, and bun test packages/ui is 739 pass, 0 fail.

Registry-shape smoke. A throwaway project installed @plannotator/core@0.25.0 from the registry plus the ui tarball by path, with @types/react and @types/react-dom, and compiled a strict TSX (moduleResolution bundler) that renders HtmlViewer with bridgeScriptUrl, bridgeReadyTimeoutMs, onBridgeUnavailable, scrollBehavior and maxAdditionalTargets, uses useHtmlRefresh and HtmlSurfaceControls, calls configurePlannotatorUI with mathRendererLoader and identityGenerator, projects rows with projectHostThreads, and imports both @plannotator/ui/components/html-viewer/bridge-script.asset.js (side-effect form) and the ?url form. tsc exits 0, and --traceResolution shows the asset and lite subpaths resolving through the exports map to the installed tarball files.

Publish, after merge, from the scratch directory that holds the verified tarball:

npm publish plannotator-ui-0.33.0.tgz --access public

Core is not republished. --provenance is dropped because it only works from CI OIDC and there is no CI publish job for these packages yet (see HANDOFF.md "Publishing & versioning"). Not published and not merged by this PR.

AI-assisted (Claude) under maintainer direction.