Summary

apps/ ships inside the jspod package and seedPodFiles() copies it into the pod on first run — offline, no git, no network. It already bundled pilot; this adds profile and home.

Why

For git-less / single-process embedders — especially nodejs-mobile (the Android app, js-pod/android) via the in-process start() in #58 / #59 — the bundled apps/ is the offline-first install path. A pod boots with a useful curated set already installed, with no jsDelivr/git network round-trip. The network install (#60) stays as the path for arbitrary/extra apps and no-release updates.

What

Vendored snapshots of each app's gh-pages deployable files (README/LICENSE excluded), matching how apps/pilot is structured:

• apps/profile/ — app.js, index.html, style.css, xlogin.js, manifest.json, favicon.svg, icons
• apps/home/ — home.js, index.html, manifest.json, favicon.svg, icons, og.png

Tradeoffs

• ✅ offline, instant first run, no git
• ⚠️ updating these apps needs a jspod release (bundled copy is pinned to the jspod version)
• ⚠️ grows the package by a few small static sites

Notes

• No code change — seedPodFiles() already copies the whole apps/ dir on first run.
• Pairs with Embeddable in-process start (no spawn) so jspod can wrap JSS on mobile/single-process runtimes #58/feat(start): in-process mode (createServer, no jss spawn) — embeddable jspod #59 (in-process start) and Git-less install path so embedders inherit bundling in single-process / no-git runtimes #60 (git-less network install).