feat: integrate framework files into monorepo #344
Reference in New Issue
Block a user
Delete Branch "feat/framework-into-monorepo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Moves all Mosaic framework runtime files into the monorepo as canonical source. Previously these lived in a separate
mosaic/bootstraprepo and were only on the local filesystem at~/.config/mosaic/. Now@mosaic/mosaicships everything needed for standalone installation vianpm install.What Moved
framework/bin/mosaic,mosaic-doctor, etc.)framework/runtime/framework/tools/framework/templates/framework/defaults/framework/install.shframework/remote-install.shTotal: 251 files, 278KB compressed in npm tarball.
Why This Matters
All Pi runtime support, the
mosaic pilauncher,mosaic doctor --fix, skill wiring fixes, and runtime adapters were only on the local filesystem — not tracked in any repo. A fresh install ormosaic-release-upgradewould overwrite them with the old bootstrap versions that had none of these changes.Key Files with Recent Changes
bin/mosaic:launch_pi()function, skills-local loopbin/mosaic-doctor:--fixauto-wiring for all 4 harnessesbin/mosaic-sync-skills: Pi as 4th link target, symlink-aware findbin/mosaic-link-runtime-assets: Pi settings.json patchingruntime/pi/RUNTIME.md+mosaic-extension.tsTesting
pnpm typecheck— 36/36 passpnpm pack— 251 framework files in tarballframework/dir