⭐ Known Gaps

The honest list — tracked here and in todo.md's "Still to do" table, not buried in chat history.

• isolated-vm native build failure. Fails to compile during yarn install's Link step (exit code 1) on the current Windows dev machine. Needs a working native build toolchain (MSVC + Python for node-gyp) investigated. Everything else in the ~2,150-package dependency graph installs cleanly — this is the one hard failure.
• vitest 3.2.7→4.1.10 compatibility unverified. Bumped to latest across all 32 consuming packages by deliberate choice, but no package's vitest.config.ts has been copied over yet — real config compatibility with the breaking 4.x line is genuinely unconfirmed, not just assumed fine.
• packages/release-notes-generator's pnpm-internals rewrite still owed. Its package.json no longer lists @pnpm/workspace.find-packages/@pnpm/workspace.pkgs-graph/@pnpm/logger, but the actual source file that imports them (src/utils/process-packages.ts) hasn't been copied/rewritten yet. Planned replacement: read each workspace's package.json directly and build the internal dependency graph from workspace:* references — no package-manager-specific API needed at all.
• CI not yet exercised against the live repo, and several workflows depend on secrets that aren't configured yet — see CI and Docker.
• Neither Dockerfile has been build-tested end-to-end — blocked on the real source trees, the isolated-vm fix, and a real run of scripts/deploy-production.mjs.
• 41 of 42 workspace packages have no real source yet — see Architecture Overview. This is the main body of remaining work, not a footnote.