[joeblau]

The docs site depended on four unpublished HIG 0.1 packages (@bloxwap/hig-tokens, @bloxwap/hig-contracts, @bloxwap/hig-react, and @bloxwap/hig-og-fonts). Those registry URLs 404, so a clean install cannot fetch them.

This replaces them with the published @bloxwap/hig@0.2.0 package and points every live import, CSS @import, and script at its subpath exports (/tokens, /tokens/css, /react/*, /react/css, /og-fonts/node). Next lists @bloxwap/hig in transpilePackages. bun.lock and package-lock.json both resolve https://registry.npmjs.org/@bloxwap/hig/-/hig-0.2.0.tgz. Historical adoption dumps under docs/hig-adoption/ are left as evidence of the earlier steps.

The published 0.2.0 tarball requires @bloxwap/chart@^0.3.0. This workspace is @bloxwap/chart@0.4.0, which is outside that range (later HIG source accepts ^0.3.0 || ^0.4.0, but that widening is not in the published tarball). bun install and npm ci keep node_modules/@bloxwap/chart linked to packages/chart and do not fetch chart 0.3.0. A resolving npm install stops with ERESOLVE; --force can replace the workspace link with the registry package, so the lockfile was updated in place instead.

Verified locally with Bun 1.4.2 and Node 24:

• bun install --frozen-lockfile from an empty node_modules
• npm ci
• node apps/docs/scripts/hig-tokens.mjs --check
• NEXT_PUBLIC_BASE_PATH=/chart bun run docs:build (30 HTML pages, 25 social cards, docs typecheck)
• bun run lint

The static export still emits the existing Fumadocs ::highlight(fd-search) CSS optimizer warnings. Not merged.