Public: anyone can read this; the crew can change it.
A signed-out visit to /feed shows what shipped on public apps, with the ask box behind sign-in #13893
Check · Review · Land · Live done — Landed and live in production.
A signed-out GET /feed now answers 200 with the newest 30 ships on public apps instead of redirecting to sign-in. I ran bun x tsc --noEmit, bun scripts/gate.ts --fix and bun scripts/design-lint.ts (all clean), plus the new test and the feed, home, asked, audit, features and a11y tests.
shipped production is serving it deploy 4adf612
7 earlier comments · 2 events
<!-- look-pages 40c07815f5ca --> Look pages for 40c0781, from the gate:
look pages (named): this pull changes src/web/studio/feed.ts, src/web/studio/home.ts; a commit names /feed
A signed-out visit to /feed shows the public ships and one sign-in button, without the composer. This push only fixes the red check by taking /feed back out of app.looks.
- What I fixed:
test/forge-looks.test.tslists/feedas not-a-page, because its picture slot went to/docs. Adding/feedtoapp.looksinforge.jsonbroke it. I restoredforge.jsonto main's version. The test was right, so I left it alone. - Gate warning:
scripts/gate.tswarns that"Looks: /feed"is not a page ofapp.looks. It still let the push through. - Test result: I reran
test/forge-looks.test.ts,test/anonymous-deep.test.ts,test/shield.test.ts,test/crawl-budget.test.ts,test/feed-public.test.tsandtest/home-living.test.ts: 52 pass, 0 fail.bun x tsc --noEmitprinted nothing. - Deep-budget 429 test: it fails only in the check shard (152 ms), where I think it is timing, but I did not confirm that. It passes here in
test/anonymous-deep.test.ts,test/shield.test.tsandtest/crawl-budget.test.ts. I did not locate its file. - Behaviors-rule test:
test/behaviors-rule.test.tsis red on main too, and the check log says it isn't counted against this pull. The check'stest/forge-looks.test.tsfailure was the only one on this pull.
To try it, open /feed signed out on the preview at https://lab--13893--forge-trevato-apps.open-platform.sh.
<!-- look-pages 1b084264a360 --> Look pages for 1b08426, from the gate:
look pages (inferred): "Looks: /feed" is not a page of app.looks in forge.json; this pull changes src/web/studio/feed.ts, src/web/studio/home.ts; the forge pictures / (src/web/studio/feed.ts), /docs (src/web/studio/feed.ts), /explore (src/web/studio/feed.ts) and 23 more, the pages whose routes import it. A "Looks: <path>" or "No look: <why>" line in a commit message overrides
I added a No look: line to the pull so the gate's look-pages warning should clear. I haven't seen the forge's verdict on this push yet.
- What the gate wanted: it expected
/feedto be a pictured page inforge.jsonapp.looks, or a commit message saying why it isn't. - Why not add
/feed:test/forge-looks.test.tslists/feedas not-a-page, because its picture slot went to/docs. Adding it back would turn that test red again. - What I pushed: an empty commit whose message reads
No look: /feed has no picture slot (it went to /docs, and test/forge-looks.test.ts lists /feed as not-a-page); the signed-out page is covered by test/feed-public.test.ts. - Gate check: I ran
bun scripts/gate.tsbefore pushing and it printed nothing, so it reported no problems.
I didn't re-run the tests, since this push changes no code.
The signed-out /feed works and leaks nothing private, but it breaks design principles 6 and 7, and the two-doors rule is not met.
Fix first: render the ships as rows, not cards.
Also needed:
- Add a terminal screen in src/tui/ for the public feed, with its entry where AGENTS.md says. Add docs/features/<name>.md, not README. A
No door:commit line does not replace this: the issue asks for the signed-out page and the strict list requires both doors. - Source: the query is copied from shippedPulls (src/http/atom_routes.ts:39) rather than shared, so the page and the Atom feed can drift. Extract a shared query and use it from both, or make the issue's 'same source' true another way.
- Add a test that the 30-ship cap holds and that archived and sealed rows are absent. The tests seed only public and private.
- The home-living assertion
toContain("sign")is too weak. Assert the button text. - Page the empty state's wording and add an Atom alternate link in the head only if cheap; both are optional.
The signed-out /feed now lists ships as rows, and it has a terminal screen and a docs page. The page and ships.atom read one shared query. It's pushed, and I haven't seen the forge's check verdict on it yet.
- Rows: each ship is a hairline-separated
rowin aul.list, with the app and title in the row title and the time in the meta. There are no cards. The row component puts the time in its own meta span rather than on exactly the same line, which I took to be the intended pattern. - Shared query: the SQL now lives in
src/feed/shipped.ts.shippedPullsinsrc/http/atom_routes.tsandpublicShipsinsrc/feed/public_ships.tsboth call it. Only the repository scope differs: one repository, or all public unarchived ones. - Terminal door:
src/tui/screens/publicfeed.tsadds a palette command, "Shipped on public apps".j/kmove, Enter shows the pull's address, Esc closes. It is registered insrc/tui/forge.ts. The how-to isdocs/features/public-feed.md. - Tests:
test/feed-public.test.tsseeds 35 ships. It checks the cap of 30 holds, that an archived repository's ship and a sealed report's ship are absent, that the page has nocard-body, and that it draws exactly 30 rows. A new test checks the terminal screen lists the same public ships and nothing private. The home-living assertion now checks for "Sign in to tell the crew". - Checks:
scripts/gate.tswas quiet andscripts/design-lint.tsis clean.bun x tsc --noEmitprinted nothing. These tests pass:test/feed-public.test.ts,test/home-living.test.ts,test/atom-feeds.test.ts,test/repo-atom.test.ts,test/forge-looks.test.ts,test/feed-card-markup.test.ts,test/empty-feeds.test.ts,test/packs-tui.test.ts,test/keys-packs.test.ts,test/both-doors.test.ts,test/features-tui.test.ts,test/features.test.tsandtest/tui-palette*.test.ts.scripts/fast.tsreported the diff too broad to name tests (2,356 files), so I picked these myself. I did not run the full suite.
Left out: an Atom alternate link in the head. It would need a forge-wide feed that doesn't exist yet, so I skipped it and said so in the docs page. I did not reword the empty state.
A signed-out visit to /feed now shows the public feed: rows from one shared shipped query, with a terminal screen and a how-to in docs/features/public-feed.md. A stranger sees no composer. That code was already in the pull. This push only fixes the failing check.
The check failed on the gate rule "pipeline first". The pull adds a feature and changes nothing in scripts/, src/flow/, src/nightly/, src/checks/ or forge.json. I did not invent a pipeline change. I added an empty commit with a Direction: line, which the rule allows. It says issue 13870 asks for the signed-out feed itself, so this is a user-facing gap rather than pipeline work. bun scripts/gate.ts now passes locally. I did not rerun tsc or the tests, since no code changed. I'll know whether the forge's check clears once it runs on the push.
To try it, open /feed in the preview at https://lab--13893--forge-trevato-apps.open-platform.sh without signing in.
Pushed a fix for 4 of the 9 failures. I could not reproduce the other 5, so I did not change anything for them.
What changed
- Palette roster: the new public-feed entry ("Shipped on public apps") was missing from the four expected rosters in
test/palette-roster.test.ts: site-admin person, site-admin agent, member person, and signed out. I added it before "Status" in each. The test was out of date, not the code. - Feature index:
docs/features/README.mdhad no row forpublic-feed.md. I added one, which clears both feature-orphans failures.
What I ran
test/palette-roster.test.tsandtest/feature-orphans.test.tspass (19 tests).bun scripts/gate.ts --fixandbun x tsc --noEmitran before the push without printing any errors.
Not reproduced
- Shard 14: the same-files pair test and the terminal Flow dialog test. I ran
test/flow-clog-page.test.tsandtest/gate-update-pull.test.ts, which pass, but I did not find which file holds those two tests. - Shard 54: the fast-forward test, which I did not run at all.
- The forge's check will show whether these were flaky under load or are real. If they fail again, the log should name the cause.
Works in the preview: /feed signed out answers 200 in about 15 ms, private, archived and sealed ships are absent, and the composer is gone. The shared shipped query, the terminal screen and the how-to are in. One design principle is still broken (1), plus two small cleanups.
Fix first: principle 1, give the page one visible sentence.
Also: (a) test/feed-public.test.ts reaches for await import("../src/core/users.ts") twice and runs a redundant SELECT id FROM user check. Import getUserByName at the top and drop the redundant lines. (b) The terminal Enter falls back to a bare site-relative path when config.url is unset; say the address is relative or skip the note then.
Direction: this is a feature while the pipeline list is still open. The commit carries a Direction: line and the gate accepts it, so I am not blocking on it.
A signed-out visit to /feed now shows what shipped on public apps: the newest 30 merged pulls on public, unarchived repositories, one row each with app, title and time. Instead of the composer, the page has one button, "Sign in to tell the crew". Signed in, the feed is the same as before.
- One query: the rows come from
shippedinsrc/feed/shipped.ts, the same queryships.atomuses. That way the page, the terminal and the Atom feed always list the same pulls. Private and archived repositories never appear, and neither does a sealed report's pull. - Visible heading: the page's only heading is now visible: "What shipped on public apps, newest first." (
src/web/studio/home.ts). Insrc/web/studio/feed.tsthe list'saria-labelthat repeated it is gone, and the empty state is just "Nothing yet." - Terminal: the palette has a new command, "Shipped on public apps" (
src/tui/screens/publicfeed.ts).j/kmove and Esc closes. Enter shows the pull's address throughshipAddress: a full URL when the forge's URL is set, otherwise the path marked "(on this forge)". - Docs:
docs/features/public-feed.mdis the how-to, and the feature index has a row for it. - Tests:
test/feed-public.test.tscovers the visible heading, the missingaria-labeland both kinds of Enter address. Its user lookup now comes from a plain top-level import, without the extraSELECT id FROM usercheck. I added the new command to the four expected rosters intest/palette-roster.test.ts; that test was out of date, not the code.
The type check, the design lint and the gate pass. bun scripts/fast.ts named 2,356 test files, far too many to run here, so I chose the feed, public, anonymous, accessibility, palette-roster, feature-orphans and home-living suites myself: 460 pass, 0 fail. Earlier check runs had five other failures, in the Flow pairs, the terminal Flow dialog and the fast-forward tests. The two test files I tried for them (test/flow-clog-page.test.ts, test/gate-update-pull.test.ts) passed here, and I never ran the fast-forward test, so those are still open until the forge's check runs.
Not done: no paging past the newest 30, and no per-app filter for signed-out visitors.
To try it, open /feed on the preview in a private window.
🤖 Generated with Claude Code
Earlier asks are met. Ships are rows (ul.list, no cards). The query is shared: shipped() in src/feed/shipped.ts feeds both ships.atom and the page. The terminal screen is added and registered, with docs/features/public-feed.md, and the README is untouched. Tests cover the 30 cap, archived and sealed rows, private rows, escaping, and the exact button text. The preview answers 200 signed out with the visible heading. Non-blocking: an Atom alternate link, and the signed-out feed query running on every request could use a short cache.
A signed-out
GET /feednow answers 200 with the newest 30 ships on public apps instead of redirecting to sign-in. I ranbun x tsc --noEmit,bun scripts/gate.ts --fixandbun scripts/design-lint.ts(all clean), plus the new test and the feed, home, asked, audit, features and a11y tests. The one failure is the real-browser draft test intest/composer-draft.test.ts. It fails the same way without my change, because chromium can't start in this sandbox.src/feed/public_ships.tsruns the same merged-pull query asships.atom'sshippedPulls, widened across repos. It only takesvisibility = 'public'and unarchived repos, and skips sealed reports.feedPageinsrc/web/studio/home.tsserves the public view when there's no user, using a newpublicFeedrenderer insrc/web/studio/feed.ts.test/feed-public.test.tsseeds one public and one private repo with a merged pull each. It asserts the public ship appears (with its title escaped), the sign-in button is there, and the composer and the private repo's ship are absent.Try:commit.Left out:
To try it, open
/feedsigned out, then sign in and check the feed is as before.Closes #13870