feat(workspace): manage raw pnpm workspaces with Bit

[zkochan]

Proposed changes

• add bit pnpm sync, which adopts a regular pnpm workspace directly from pnpm-workspace.yaml
• map every pnpm project to a Bit component and assign unclaimed repository files to a root component
• persist version-free path-to-component identity while keeping .bitmap as generated checkout state
• migrate local workspace: dependencies to portable catalog references
• make ordinary bit import add project roots, reconcile catalogs, and switch exact snap fallbacks to workspace:* when a dependency component becomes local
• preserve lockfile-derived component dependency graphs and mark only components using a changed catalog entry as modified
• record one exact workspace toolchain profile and component compatibility requirements, including aggregate toolchains such as Bit, Bun, Deno, Vite+, or Nub
• retain the validated root-first, lane-aware bootstrap primitives for future Bit-native clone UX
• use ordinary bit status, bit snap, bit lane, bit import, and bit export; pnpm is not a VCS wrapper

Design: pnpm/rfcs#33
Generic pnpm catalog support: pnpm/pnpm#14332

The topology and catalog bridge use ordinary Bit component objects. No bit.cloud server change is required.

Validation

• Prettier and oxlint on all changed TypeScript files
• affected-component compilation for tracker and importer
• tracker tests: 14 passed
• Git-free raw pnpm workspace adoption, install, status, and snap
• direct selective bit import with exact catalog fallback and later local rebinding
• root-first and lane-aware bootstrap exercised against bit.cloud during prototype validation

---

Written by an agent (Codex, GPT-5).