Home is the living pipeline: KPIs, what is moving, what shipped, your apps, and one box to tell the crew #8050

Home is now the living pipeline, and the feed has moved to /feed. I couldn't take the before and after screenshots at either width, so those are not on this pull.

Tests: bun x tsc --noEmit, scripts/gate.ts, scripts/design-lint.ts and the new test/home-living.test.ts pass, as do the existing suites that touch home and the feed. A broader sweep had one red test I couldn't run here: the composer-draft real-browser test, which needs Chromium and failed with "chromium did not offer a DevTools endpoint". I didn't compare it against main.

What home holds when signed in:

• The box: a one-line "Tell the crew…" form that posts to /tell and is filled by a phone's share sheet. It becomes the /talk entry (#7652) when that lands.
• KPIs: the tile row for admins with any alarm as one calm line; everyone else gets the live-version line. I didn't give the tiles a design pass; they are unchanged.
• Now: check › review › land › live. Each count is the sum of the /boards stages it names, so it matches the boards. It links to /boards only for viewers who may open it; otherwise it is plain text.
• Being built / Just shipped: three rows each, always six, so nothing shifts. Each row links to its issue or pull, and rows are read per viewer, so a private repo or sealed report is never named.
• Your apps: a chip per app and a "+". Both this and the lists above redraw over the existing stream, from /live/moving and /live/chips.
• Feed link: a small "The feed" link goes to /feed.

A stranger still gets the door, unchanged.

Feed page: /feed is what home used to be, with the composer, timeline, "since you were here", pinned panels and stalled-step cards. The "Newest" and "Older posts" links now point to /feed.

Speed: the two list scans are read once per write (keyed on writeStamp), because the cold pull scan had moving at about 23 ms on the realistic fixture. A warm home is tested to answer in under 50 ms.

Left out on purpose:

• Removed from home: the "waiting on you" line, the clog text, the vitals and keeper lines. The boards and the Flow dialog still show them.
• "Slowest right now" needs a timing read home doesn't have.
• The .moving and .tell-box styles are named in docs/design/areas/home.md, and the notes are in docs/features/living-home.md.

Existing tests changed: about 30 files that fetched / and expected the feed now fetch /feed, as the move requires. Four tests asserted the clog, vitals and keeper lines on home; I changed them to assert those lines are gone from home. I added a /feed entry to docs/design/audit.md.

Try it: sign in and open /, then /feed. Start a run or merge a pull and the lists redraw without moving anything below them.

Closes #8015

Home is now the living pipeline, and the feed has moved to /feed. I couldn't take the before and after screenshots at either width, so those are not on this pull.

Tests: bun x tsc --noEmit, scripts/gate.ts, scripts/design-lint.ts and the new test/home-living.test.ts pass, as do the existing suites that touch home and the feed. A broader sweep had one red test I couldn't run here: the composer-draft real-browser test, which needs Chromium and failed with "chromium did not offer a DevTools endpoint". I didn't compare it against main.

What home holds when signed in:

• The box: a one-line "Tell the crew…" form that posts to /tell and is filled by a phone's share sheet. It becomes the /talk entry (#7652) when that lands.
• KPIs: the tile row for admins with any alarm as one calm line; everyone else gets the live-version line. I didn't give the tiles a design pass; they are unchanged.
• Now: check › review › land › live. Each count is the sum of the /boards stages it names, so it matches the boards. It links to /boards only for viewers who may open it; otherwise it is plain text.
• Being built / Just shipped: three rows each, always six, so nothing shifts. Each row links to its issue or pull, and rows are read per viewer, so a private repo or sealed report is never named.
• Your apps: a chip per app and a "+". Both this and the lists above redraw over the existing stream, from /live/moving and /live/chips.
• Feed link: a small "The feed" link goes to /feed.

A stranger still gets the door, unchanged.

Feed page: /feed is what home used to be, with the composer, timeline, "since you were here", pinned panels and stalled-step cards. The "Newest" and "Older posts" links now point to /feed.

Speed: the two list scans are read once per write (keyed on writeStamp), because the cold pull scan had moving at about 23 ms on the realistic fixture. A warm home is tested to answer in under 50 ms.

Left out on purpose:

• Removed from home: the "waiting on you" line, the clog text, the vitals and keeper lines. The boards and the Flow dialog still show them.
• "Slowest right now" needs a timing read home doesn't have.
• The .moving and .tell-box styles are named in docs/design/areas/home.md, and the notes are in docs/features/living-home.md.

Existing tests changed: about 30 files that fetched / and expected the feed now fetch /feed, as the move requires. Four tests asserted the clog, vitals and keeper lines on home; I changed them to assert those lines are gone from home. I added a /feed entry to docs/design/audit.md.

Try it: sign in and open /, then /feed. Start a run or merge a pull and the lists redraw without moving anything below them.

I've pushed fixes for the 36 failing tests. I ran the failing test files locally and they pass, along with tsc, scripts/gate.ts and scripts/design-lint.ts. I haven't run the full check, so I don't know what else it will flag. The earlier summary of what home holds and what moved to /feed still applies; the changes since are below.

What I fixed in the code:

• Offline: home no longer registered the service worker, since that code lived only in the feed's script. I pulled out registerWorkerJs in feed.ts and home now includes it. The worker still caches /, but the cached home no longer carries the "this is old" note, because that note lives on the feed page.
• Tabs: the Feed / Your apps / Asked tabs now point Feed at /feed.
• Reserved name: feed is now reserved in core/reserved.ts.
• /feed as a look: it is listed in forge.json app.looks.
• Server-Timing: /live/moving now names its render phase.
• Wall clock: the cache in flow/moving.ts took its time from Date.now() inside the function body, which the flow-clock rule forbids. It's now a default parameter.

What I changed in the tests:

• Feed content: about 20 tests looked for feed content on /. I pointed them at /feed, including the browser tests home-buttons-rest and composer-draft.
• Speed test: my own wall-clock bound is gone. The test now counts statements (a warm home costs at most 40) and checks that the two list scans are read once per write.
• Releases test: releases-page asserted the text live:, which no longer appears on home for an admin. It now accepts the plain live line or the admin's "Live version" tile.
• Audit: I added a /feed entry to docs/design/audit.md.

Not run here: the browser tests need Chromium, which the sandbox doesn't have. I changed their URLs to /feed but haven't run them, and there may be other browser tests that still expect the feed on /.

Screenshots are still not on the pull, for the same reason: I have no browser here.

Two of the eight failures were stale tests, and I fixed them. The other six I couldn't reproduce here, so I didn't change anything for them. I pushed the fix, but I haven't seen the forge's check run on it yet.

What I fixed. Both failures came from the feed having moved to /feed:

• home is the feed: the Feed tab now links to /feed, but the test still looked for /. It now expects /feed. That test passes locally.
• Composer draft browser test: the draft is saved under a key that includes the page path, so it is now draft.<id>/feed. The test still looked for draft.<id>/. I updated the key in two places. Chromium won't start in this sandbox, so I couldn't run this test; the forge's check will be its first real run.

What I didn't fix.

• Unreproduced: the "egress grants in the terminal" tests and the sentinel tests ("a clean forge" and "the faults of the day") pass here, so I left them alone. The checks test about the newest queued check running first is also untouched; I didn't run it, so I can't say whether it fails here.
• Likely load-related: I suspect load in the sharded run, but I haven't confirmed that. If those still fail on the next check, it needs a closer look.

scripts/gate.ts and tsc --noEmit ran clean.

🤖 Generated with Claude Code

Parked by the crew: the check stayed red through 2 automatic tries

Home is now the living pipeline, and the feed has moved to /feed. I haven't seen the earlier check log or the preview, so I can't say why the check went red before. In this sandbox, scripts/gate.ts, bun x tsc --noEmit and scripts/design-lint.ts are clean.

I merged current main into the branch; it merged without conflicts. The last push is a962f2d3. I couldn't take before/after screenshots.

What home holds:

• Tell the crew: a one-line form that posts to /tell, for signed-in viewers. It becomes the /talk entry (#7652) when that lands.
• KPIs: admins get the tile row, with any alarm as one calm line. Everyone else gets the live-version line.
• Now: the check › review › land › live counts, each the sum of the /boards stages it names. It links to /boards only for viewers who may open them.
• Being built / Just shipped: three rows each, always six, so nothing shifts.
• Your apps.

Tests changed, as the owner asked: the tests that asserted the old feed on home now follow it to /feed. That is 58 test files, among them the home-, feed-, flow-, studio, web-, live, offline, page-text, ssh-site and xss-everywhere suites. I also added test/home-living.test.ts for the new behaviour. I changed assertions only where they expected the old feed on /.

Test results here:

• The test files changed on this branch: 493 pass, 1 fail. The failure is the composer-draft real-browser test, which needs Chromium ("chromium did not offer a DevTools endpoint"). I didn't compare it against main.
• The other test files that request /: 427 pass, 4 fail. Three failures are the real-browser look captures, which need /usr/bin/chromium. The fourth, ssh-port-taken, passes when run alone.
• After the merge, the home and feed tests plus the newly merged main tests that mention the feed or /: all pass.

I didn't run the full suite. The forge's check does that on push, and it runs the Chromium and unix-socket suites this sandbox can't.

I fixed the likely cause of the failing browser test and pushed it, but I couldn't run that test here to confirm. Chromium won't start in my sandbox ("did not offer a DevTools endpoint"). The forge's check is the real verdict.

What changed

• The composer now lives on /feed, while / is the living home. Sending a tell from the composer redirected to /, which has no #composer. In the browser test, the step that sends to the forge and waits for the reloaded page timed out.
• The composer form on /feed now carries a hidden back=/feed.
• composerSubmit in src/web/studio/actions.ts sends the person back to that path, or to / when none is given. It does this for a tell to an app, a tell to the forge, and its refusals. backTo only accepts local paths, so this is not an open redirect.
• I added a Chromium-free test in test/composer-draft.test.ts. It checks that /feed carries back=/feed, and that both a forge tell and an app tell redirect to /feed.

What I didn't do

• The tell-box on home still returns to /, which is right for it.

Checks I ran: tsc --noEmit and scripts/gate.ts are clean. The changed tests, plus the neighbouring steering-four-places and home-living tests, pass except the Chromium one.

The branch already held the home work. The head you reviewed looks wrong, or a different pull's head: my diff against main touched none of the org-teams files (#7997).

main had since gained the org-teams commit. Against that newer main, my branch showed those files as removed, so I merged main in. The diff against main is now 60 files and has nothing from org-teams. Please re-review from the new head, 07709685.

What this pull does

• / is now the living pipeline home, built in src/web/studio/home.ts and src/web/studio/living.ts:

- the forge's KPIs for admins; - a "what is moving" region, drawn alone by /live/moving; - your apps as chips, drawn alone by /live/chips; - one box to tell the crew.

• The old home, with the composer and the single timeline, moved to /feed. The links, tests and service-worker registration that pointed at / for it now point at /feed. That is the roughly 30 moved files and 58 rewritten tests you mentioned.
• The tell box posts to /tell, the same endpoint the composer uses. It gets the same-origin check and the signed-in identity as the composer.
• A tell from the feed's composer now returns to /feed. This is the earlier fix for the failing browser test, which timed out because the redirect landed on /.
• I did not touch your point 3 about the weak "not offered" check, because that test belongs to the org-teams pull and isn't in this diff. Please raise it on that pull.

Checks I ran

• tsc and scripts/gate.ts are clean.
• composer-draft, home-living, feed-page and tui-org-teams pass, except the Chromium test, which can't start in my sandbox. The forge's check is the real verdict for it.

I fixed the two composer test failures and pushed. I did not touch the third, the MCP backups_test timeout. The change is in src/web/studio/feed.ts.

• Cause: the feed composer's hidden back input sat between the <form> tag and <div class="card-body">. The test "the composer is a §5 card" expects the form to open straight onto its card body, so it failed. I moved the input inside the card body. The /tell request still carries back=/feed.
• Checks: test/home-feed.test.ts and test/composer-draft.test.ts pass, including the test that a tell sent from the composer comes back to the feed, the forge's too. bun x tsc --noEmit is clean.
• Still failing here: the real-browser test in test/composer-draft.test.ts fails in this sandbox with "chromium did not offer a DevTools endpoint". It wasn't in the forge's failure list, so the forge's check should be able to run it.
• Not touched: MCP backups_test ("an unreachable one says why, and never echoes a secret") timed out at 20 s. I didn't reproduce it here, so I can't say if it's a flaky timeout or caused by this pull. If it fails again on the next check, it needs its own look.
• Not run: bun scripts/gate.ts and bun scripts/design-lint.ts were not run for this fix.

Home becomes the living pipeline. Signed in, / holds the tell box, the figures (site admins only), Now, Being built / Just shipped and your apps. The composer and the timeline move to /feed, which home links to. Both doors carry the change. This push answers @sentinel's review:

• The Now line leaked forge-wide counts. It is now shown to site admins only, on the page and in /live/moving, in src/web/studio/living.ts. Admins can read every repository, so the counts' single cache can't leak; a comment on the cache says so. I dropped the line for everyone else rather than counting per viewer, because every stage query in src/flow/pipeline.ts would need a per-repo read check. A new test proves the counts reach root and never reach alice or bob, through either route; it would fail on the old code.
• The terminal had no matching home. A new src/tui/screens/moving.ts (movingLines) gives the terminal the same lines: Now for a site admin, then Being built and Just shipped, filtered by the same reads the web home uses. Control characters are stripped from titles. The dashboard draws them as a muted strip above the figures and refreshes them with the figures. The terminal home's existing tell plays the box's part. A test drives the headless terminal as alice, bob and root.
• Code with no caller. vitalsRow and clogRow are gone, along with imports nothing else used. keeperRow stays, because the boards' Flow panel still draws it. The registerWorkerJs doc comment now sits above its own export, and dayKeepJs has its doc block back.
• Inverted assertions. Each line those tests used to check on home still has a positive test at another door:

- keeper: flow-keeper.test.ts again checks id="keeper" and "Binding landings:", now on /boards. - clog: the terminal's Flow lines (flowLines). - vitals: the MCP flow report (flowFor). - figures: the positive data-refresh="/live/home/kpis" check on an admin's home still stands, as does the new Now test for root.

• Docs. docs/features/living-home.md now names the terminal door and says why only site admins see Now.

Verification: the gate, bun x tsc --noEmit and design-lint are clean. scripts/fast.ts couldn't name tests (exit 2, forge.json is in the diff), so I picked them: home-living, flow-keeper, ten home, flow, client-home and XSS suites, and every test file that drives the terminal (197 files, 1,258 passing, none failing, 8 skipped). There are still no screenshots at either width, and no browser ran the composer test here; the forge check is the verdict on both.

To try it, open / on the preview as an admin and as a non-admin; only the admin sees the Now line. Then open the terminal home as each.

🤖 Generated with Claude Code

Home becomes the living pipeline. Signed in, / holds the tell box, the figures (site admins only), Now, Being built / Just shipped, and your apps. The composer and the timeline move to /feed, which home links to.

• Now line, site admins only. Its counts include private repositories, so nobody else sees it, on the page or in /live/moving. A test proves it reaches root and never reaches alice or bob, by either route.
• The terminal home matches the web home. It shows Now for a site admin, then Being built and Just shipped, filtered to what the viewer can read (src/tui/screens/moving.ts). Its existing tell plays the box's part. A test drives the headless terminal as each viewer.
• Removed: vitalsRow and clogRow, which no longer had callers. keeperRow stays because the boards' Flow panel still draws it, and flow-keeper.test.ts again checks the keeper there.
• Merge with main: the only conflict was test/home-frame.test.ts. It keeps main's repeated-sample median against the 50 ms budget, and this branch's region list without kpis, since the KPIs are on / and that test reads /feed. Their refresh is still checked on /.

Checks: the gate, bun x tsc --noEmit and design-lint are clean. home-frame, home-living, home-feed, home-kpis, flow-keeper, home-since and home-cache pass. The composer's real-browser test in composer-draft.test.ts fails here because Chromium can't start in this sandbox ("chromium did not offer a DevTools endpoint"); the forge check is its verdict. There are still no screenshots at either width.

To try it, open / on the preview as an admin and as a non-admin; only the admin sees the Now line. Then open the terminal home as each.

🤖 Generated with Claude Code

Home becomes the living pipeline. Signed in, / holds the tell box, the figures (site admins only), Now, Being built / Just shipped, and your apps. The composer and the timeline move to /feed, which home links to.

There was nothing new to merge this time: main is still 9adec1ad, and the merge commit 2dcf73ad already on this branch contains it. This notice looks like a repeat of the last one.

• Now line, site admins only. Its counts include private repositories, so nobody else sees it, on the page or in /live/moving. A test proves it reaches root and never reaches alice or bob, by either route.
• The terminal home matches the web home. It shows Now for a site admin, then Being built and Just shipped, filtered to what the viewer can read (src/tui/screens/moving.ts). Its existing tell plays the box's part. A test drives the headless terminal as each viewer.
• Removed: vitalsRow and clogRow, which no longer had callers. keeperRow stays because the boards' Flow panel still draws it, and flow-keeper.test.ts again checks the keeper there.
• Merge with main: the only conflict was test/home-frame.test.ts. It keeps main's repeated-sample median against the 50 ms budget, and this branch's region list without kpis, since the KPIs are on / and that test reads /feed. Their refresh is still checked on /.

Checks: the gate, bun x tsc --noEmit and design-lint are clean. home-frame, home-living, home-feed, home-kpis, flow-keeper, home-since and home-cache pass. The composer's real-browser test in composer-draft.test.ts fails here because Chromium can't start in this sandbox ("chromium did not offer a DevTools endpoint"); the forge check is its verdict. There are still no screenshots at either width.

To try it, open / on the preview as an admin and as a non-admin; only the admin sees the Now line. Then open the terminal home as each.

🤖 Generated with Claude Code

Home becomes the living pipeline. Signed in, / holds the tell box, the figures (site admins only), Now, Being built / Just shipped, and your apps. The composer and the timeline move to /feed, which home links to.

• Now line, site admins only. Its counts include private repositories, so nobody else sees it, on the page or in /live/moving. A test proves it reaches root and never reaches alice or bob, by either route.
• The terminal home matches the web home. It shows Now for a site admin, then Being built and Just shipped, filtered to what the viewer can read (src/tui/screens/moving.ts). Its existing tell plays the box's part. A test drives the headless terminal as each viewer.
• Removed: vitalsRow and clogRow, which no longer had callers. keeperRow stays because the boards' Flow panel still draws it, and flow-keeper.test.ts again checks the keeper there.
• Merges with main: the only conflict was test/home-frame.test.ts. It keeps main's repeated-sample median against the 50 ms budget, and this branch's region list without kpis, since the KPIs are on / and that test reads /feed. Their refresh is still checked on /. The latest main (e4107b40) merged without conflicts.

Fix for the failed check: in test/composer-draft.test.ts, "a tell sent from the feed's composer comes back to the feed, the forge's too" now makes its own session. It shared one with the real-browser test before it, which ends by signing out. Where Chromium runs, as on the forge, the tell was then redirected to sign-in, which is why it passed here. This was a fault in the test, not the code. The other failure, shard 1 killed at 5 s in test/webspec.test.ts, doesn't reproduce: that file passes in 138 ms here, so it reads as load on the check machine.

Checks: the gate and bun x tsc --noEmit are clean after the merge, and home-living, home-frame and the rest of composer-draft pass. The real-browser composer test can't run here because Chromium doesn't start in this sandbox, so this fix is only confirmed by reading the test; the forge check will run it. There are still no screenshots at either width.

To try it, open / on the preview as an admin and as a non-admin; only the admin sees the Now line. Then open the terminal home as each.

🤖 Generated with Claude Code