Public: anyone can read this; the crew can change it.

First login to a spawned forge: the crew working right now in the feed, and three next steps #600

shipped production is serving it trevatoowner opened this 1mo ago

trevatoowner opened this 1mo ago

Pillar: P4 Forge in a link (umbrella #590). One run, started fresh from today's main.

Outcome (what a person sees). Someone follows the link to their new forge, sets a password, and lands on a home that shows their crew working right now and three next steps: make your everyday account, open your apps, tell the crew something.

Today. spawnForge makes the child; #575 writes its direction issue and claim link; nothing decides what the first screen says.

Acceptance.

[ ] After the claim, the home is the feed (#599) with the child's crew visible: its planner's run on the direction issue, queued or running, live.
[ ] Above it, one card with three steps that tick themselves done: Make your everyday account (the #596 flow), Open your apps (each app with its open link), Tell the crew something (the composer, focused).
[ ] Fits a 390 px phone with no sideways scroll.
[ ] The Link test, in the pull: a fresh child, a stranger's browser, and within a minute a crew working and a next step on screen.

Done means reachable (all four, or the pull says which one does not apply and why):

Page: the claim link lands here
MCP: forge returns next_steps with the same three items and their state
Test: spawn a child in the test, claim it, GET / shows the three steps and a crew item
Look: phone and desk, on the pull

Start from: src/actions/spawn.ts, src/spawn/, docs/SPAWN.md, src/web/pages/site.ts, src/web/studio/home.ts, src/web/studio/feed.ts, src/http/mcp.ts.

Depends on: #575 (first boot and claim link), #596 (everyday account), #599 (home is the feed).

Must not touch: the release workflow, the chart (charts/), other repositories. Do not change the spawn plan's validation or anything under the parent's data directory.

trevatoowner commented 1mo ago

Added acceptance (owner's contract rule, now in the direction and docs/VISION.md):

[ ] Contract: one interface per job. If this screen or control does a job another one already does, keep the better and delete the other in this same pull.
[ ] Minimal, not bare: every element earns its place on the path below; white space at every width; nothing shown the person does not need now.
[ ] One primary next action on the screen, and the pull's looks show the path below at phone and desktop widths.
[ ] The pull says what it removes for every screen or control it adds.

The path: someone new arrives from the claim link, to understand what they were given; the one primary action is the next unticked step; they go to their everyday account, their apps, or a tell.