⭐ Known Gaps

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

• 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.
• blackbox.yml/e2e.yml steps gated if: false — tests/blackbox/tests/e2e are manifest-only, nothing real to run yet. Re-enable condition is written directly in each workflow's comment, and tracked as its own card so it doesn't get forgotten once the source lands: Issue #30 — see CI and Docker.
• CI secrets not yet configured — Check now installs cleanly (see Yarn Migration for the isolated-vm fix), but workflows depending on unconfigured secrets (Docker Hub, release PAT, etc.) will keep failing until those are set — see CI and Docker.
• Neither Dockerfile has been build-tested end-to-end — blocked on the real source trees 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.

Real bugs found and fixed

• isolated-vm@5.0.3 incompatible with Node 26. Failed to compile identically on Windows and the GitHub Actions Ubuntu runner — real compiler output (gh run view --log-failed) showed the native addon calling V8 APIs Node 26's bundled V8 has since removed or changed (Template::SetAccessor, Object::GetIsolate/GetPrototype, internal-field accessor signatures, a Maybe<T>/cppgc header restructuring). Not a missing-toolchain problem — every other native module in the dependency graph built cleanly. Fixed by bumping to 7.0.1 (latest, engines.node: ">=24.0.0"), verified with a real yarn install. Issue #26.