The README opens on what this forge is now: apps, a crew, and the studio #110

README.md now opens on what the forge is: two paragraphs above the existing git-forge pitch say that the forge runs the apps it hosts, that a crew of agents builds them (a sentence becomes an issue, the assigned agent works it in its own fork and opens a pull, every push redeploys that pull's preview on its own copy of production's data, every deploy is the check, and only a person's merge reaches production), then name the studio as the front door with its five words — tell, working, look, shipped, asks you — linked to docs/STUDIO.md, with docs/APPS.md as the contract for apps and previews. The paragraph 280 lines down that used to be the only mention of the studio loses its duplicate word list and now points back at the frame, so the five words are named exactly once.

Nothing else moved: Run it, Live in the terminal, Origins, On your machine, Apps, The crew, Shape and What works today are byte-identical, and there is no new dependency and no change to forge.json, the workflow or the chart. Every claim in the new text was checked against the tree — forge_mode unset means studio (src/http/context.ts:29), the crew works from forks (src/crew/runner.ts:354), a preview starts from a copy of production's data (src/apps/data.ts) — and the new text adds no commands, so Run it is still the first thing you can paste.

Two things to look at. The doc links are ordinary relative markdown (docs/STUDIO.md), which resolves correctly on a file view and off-forge but not in the README card on /:owner/:name, where the forge's markdown renderer passes relative hrefs through without rebasing them — a renderer gap I left alone since this issue scopes to the README. And the check's git-over-HTTP tests (6 of 261: web.test.ts, pulls.test.ts, forks.test.ts, cross-repo-pull.test.ts, apps.test.ts, apps-adversarial.test.ts) fail in my sandbox with remote: auth required, because the sandbox forces http.extraheader with my own forge token onto every git call and it overrides the credentials the tests embed in their clone URLs; they fail identically with this change stashed, and bun x tsc --noEmit is clean.

🤖 Generated with Claude Code

Closes #78