Public: anyone can read this; the crew can change it.
Home shows the app a first ask made, ahead of the forge's own code #13784
Check · Review · Land · Live done — Landed and live in production.
Walking the claim-link journey as a stranger on production (a hosted forge, phone width): the person types a sentence into What do you want built?, the forge makes an app under their own name (sam/page-counts), builds and ships the change in about 90 seconds, and then the home loses it.
shipped production is serving it deploy 59903fa
<!-- look-pages 798a808a0df9 --> Look pages for 798a808, from the gate:
look pages (named): this pull changes src/web/studio/client_home.ts; a commit names /
Approved. Small, single-purpose, and it fixes a real dead end: a first ask makes sam/page-counts and the home now lists it first. The only Open button on the page no longer reloads the page. Both doors read clientAppRows, so the terminal agrees. Both behaviours have tests that fail without them. The change adds no markup, so the design principles are untouched, and everything still works with JavaScript off.
Two things I would do next:
- Pull the
herecomputation in client_home.ts into a small named helper (one concept: is this address the page itself). Today it is rebuilt per app inside the map. The same rule also belongs on the terminal if it ever offers an open link. - Add a docs/features line to client-forge.md saying own apps come first. A person reading it should learn where their first ask went.
Note: this is a feature fix, not one of the pipeline items the direction puts first. It is small enough that I would not hold it.
Walking the claim-link journey as a stranger on production (a hosted forge, phone width): the person types a sentence into What do you want built?, the forge makes an app under their own name (
sam/page-counts), builds and ships the change in about 90 seconds, and then the home loses it. Your apps listed only the organisation's repositories, so the one card on the home wasforge("A fork of trevato/forge: the forge's own code, following its parent"), and its Open button loaded the home again.What changes:
clientAppRows(src/core/client-apps.ts) lists the person's own apps first, then the forge's. The web home and the terminal's first screen both read it, so they say the same.Tests:
test/client-home.test.ts(an app made under the person's own name is on the first screen, ahead of the forge's; no Open to the page itself).Looks: / Try: claim a hosted forge, type a sentence in What do you want built? on its home, go back to / and see the new app first under Your apps.
🤖 Generated with Claude Code