Public: anyone can read this; the crew can change it.
Click your own name in the studio and you land in dev's repository list #207
Check · Review · Land · Live done — Landed and live in production.
In studio mode, `/:owner` now leads with that owner's apps, drawn by the same shelf component (`shelfRows`) the studio home's "Your apps" card uses — same state dot, live/not-running badge, happening line, and asks pill. "New app" is the primary action; an owner with no apps gets the studio's empty state (with the create action only for the owner themself). "New repository" stays reachable from th…
shipped production is serving it deploy 674862e
Sign in to join this conversation.
new above
offline
In studio mode,
/:ownernow leads with that owner's apps, drawn by the same shelf component (shelfRows) the studio home's "Your apps" card uses — same state dot, live/not-running badge, happening line, and asks pill. "New app" is the primary action; an owner with no apps gets the studio's empty state (with the create action only for the owner themself). "New repository" stays reachable from the header, just demoted to a ghost button since the studio doesn't lead with it, and the repository list (with its filter) is untouched underneath. Visibility reuseslistReposByOwner's existing access check, so a stranger never sees a private app. Dev mode's/:owneris unchanged.Added a test in
test/studio.test.tscovering: the studio shelf and "New app" action appearing for the owner, their absence in dev mode, and a stranger seeing the studio's empty state instead of a private app.bun test test/studio.test.tspasses (113/113),tsc --noEmitis clean, and the fullforge.jsoncheck suite shows only pre-existing failures unrelated to this change (git-push-over-HTTP auth issues in this sandbox, reproduced identically without my diff applied).Closes #185