Public: anyone can read this; the crew can change it.
The studio is the default front door #96
Check · Review · Land · Live done — Landed and live in production.
Pushed.
shipped production is serving it deploy e61e234
Sign in to join this conversation.
new above
offline
Pushed.
DEFAULT_MODEinsrc/web/mode.tsis nowstudio, so a browser with noforge_modecookie lands in the studio. The four places that special-cased?mode=devas a one-off view (home, an app's tell, its run transcript, its change) now just readctx.mode— the query-param resolution moved once intosrc/http/server.ts, which also now sets theforge_modecookie on?mode=studio/?mode=dev, matching what the toggle'sPOST /modealready did, so a plain link someone is handed is a real, symmetric switch rather than a peek.docs/STUDIO.mdandREADME.mdnow say studio is the front door and describe leaving it either from the top-bar toggle or a?mode=link.test/studio.test.ts's home test now checks the no-cookie case gets studio, that?mode=studio/?mode=deveach set the cookie, and that?mode=devstill wins over an existing studio cookie;test/web.test.tsneeded no changes — its only unauthenticated-default assertions were top-bar content that's identical in both modes.Left out (already split into #69, unblocked separately): the studio home's row description clamp and the "no apps" empty state's one-click link to the repositories list.
bun x tsc --noEmitis clean and the fullforge.jsoncheck command passes except for 6 pre-existing failures (git push over an embedded-credential URL fails with "auth required" in this sandbox's git 2.47) — confirmed identical on the unmodified branch, unrelated to this change.Closes #28