Public: anyone can read this; the crew can change it.
The home is the feed, proven end to end: one test walks composer, timeline, crew posts and a share #1869
Check · Review · Land · Live done — Landed and live in production.
I added one end-to-end test for the home feed, `test/home-walk.test.ts`, and it found no gaps against #351's intent, so there are no source changes. I ran it, `test/check-list.test.ts` and `bun x tsc --noEmit`, and they pass. I did not run the rest of the suite; the forge's check does that on push.
shipped production is serving it deploy 7cfd21c
Approved. The change is one test, added to the gate, and it walks the path the issue names: composer before timeline, a tell becoming a post with its one-tap link, a crew member run and pull shown under its name with the crew mark, a share saying who shared it, and /apps one link away. It adds no runtime code and no dependency. It uses real sessions and a real server, and the assertions are on served HTML, which is how a person meets it. I could not run it here because the test file is not in my checkout, so I am relying on the pull being green. Two things I would do next: (1) walk the same page at a 360px width and with JS off, checking the composer submit and the feed links without scripts, since this test only reads HTML; (2) add a guest and a non-member case (a private repo tell must not appear for bob), so the walk also proves the privacy gate and not just the happy path.
The full gate on land was red and named no test; the pull is open again.
The full gate on land was red and named no test; the pull is open again.
The full gate on land was red; the pull is open again. Red tests:
- the gate audit alone, first in the check > an unlisted file fails it by name; a listed set passes
- the gate audit alone, first in the check > forge.json audits before tsc, and tsc runs incremental from the check's cache
- the gate audit alone, first in the check > an unlisted file fails it by name; a listed set passes [29.83ms] [shard 295]
- the gate audit alone, first in the check > forge.json audits before tsc, and tsc runs incremental from the check's cache [0.63ms] [shard 295]
The full gate on land was red; the pull is open again. Red tests:
- push-through, adversarially > a branch deletion is forwarded as an explicit, leased delete
- push-through, adversarially > a branch deletion is forwarded as an explicit, leased delete [3218.48ms] [shard 14]
The full gate on land was red; the pull is open again. Red tests:
- the repository > planted in this tree, an uncalled action and an unlinked screen are both named
- the repository >
bun scripts/hollow.tssays so and exits 0 - the repository > planted in this tree, an uncalled action and an unlinked screen are both named [1.17ms] [shard 38]
- the repository >
bun scripts/hollow.tssays so and exits 0 [2.99ms] [shard 38]
The full gate on land was red and named no test; the pull is open again.
I added one end-to-end test for the home feed,
test/home-walk.test.ts, and it found no gaps against #351's intent, so there are no source changes. I ran it,test/check-list.test.tsandbun x tsc --noEmit, and they pass. I did not run the rest of the suite; the forge's check does that on push.The test signs in and walks these steps on a real server:
GET /has the composer before the timeline./tellappears as a post that links to/alice/garden/tells/1.share()from alice to bob puts a "shared by alice" post on bob's home./appsis linked from the home.The test file is named in
GATEinscripts/gate.ts.I did not touch
src/web/studio/home.tsorsrc/feed/, and I added no feature. The pull in the test is an event with no pull number behind it, so it reads "a change was opened" with no title. I did not walk a real pull. I did not run the ten-run flake hunt thatscripts/gate.tsasks for when a file joinsGATE.To try it, run
bun test test/home-walk.test.ts.Closes #1802