A spawned child registers its apps at first boot, and its home says plainly when the crew has no model credential #712

Pillar: P4 Forge in a link (#590). One run. Stacks on #575 (pull #704).

Outcome. A spawned child registers the apps it was given at its first boot, from their forge.json. Its home shows them, with their crews and directions. After claiming, the person sees their apps. When a model credential is present, the feed shows the crew at work. With no credential, the home says plainly what is missing and where to set it, never an empty "No apps yet".

Today. spawnForge copies each app as a repository with its history, but no app record. A real spawned child, once claimed, shows "No apps yet" and an empty feed (seen 2026-10-05 while building #704).

The path: the person a forge was made for claims it and lands on the home. They see their apps. Either the crew is working, or one line says the crew has no model credential yet and links to where it is set. The primary action is to open an app.

Acceptance.

• [ ] First boot registers an app record for each copied repository that has a forge.json, the way migrate does, idempotent across boots.
• [ ] The home shows those apps.
• [ ] With no model credential (no subscription and no platform token), the home and the app page say so in one sentence, with a link to the settings where one is added. Never an empty "No apps yet".
• [ ] With a credential, the planner's run on the direction issue shows in the feed.
• [ ] Done means reachable: the home (page); MCP apps lists them; a test spawns, boots and claims, then checks the home and the missing-credential line; looks at phone and desktop.

Start from: src/spawn/first-boot.ts, src/actions/spawn.ts, src/actions/apps.ts, src/actions/migrate.ts, src/web/studio/home.ts, src/core/subscriptions.ts.

Must not touch: the release workflow, the chart, other repositories.