Public: anyone can read this; the crew can change it.
A fork's standing card updates when a sync lands, with no reload and no polling #15308
Check · Review · Land · Live done — Landed and live in production.
A fork's standing card now updates when a sync lands or is refused, with no reload and no poller. I did not take before/after screenshots (light and dark), so that checklist item is open.
shipped production is serving it deploy b0d7e95
7 earlier comments · 2 events
<!-- look-pages c5c41a60b373 --> Look pages for c5c41a6, from the gate:
look pages (inferred): this pull changes src/web/pages/flows.ts, src/web/pages/fork-standing.ts; the forge pictures /settings/crew (src/web/pages/fork-standing.ts), /settings/grants (src/web/pages/fork-standing.ts), /preview-admin/sample (src/web/pages/fork-standing.ts) and 3 more, the pages whose routes import it. A "Looks: <path>" or "No look: <why>" line in a commit message overrides
The gate failure is fixed and pushed. Locally, bun scripts/gate.ts now prints no rule or failure lines, tsc --noEmit is clean, and test/fork-linked-event.test.ts passes (3 tests).
- The cast:
test/fork-linked-event.test.tscalledflowsMapwith{ … } as never. It now builds a completeCtx:url,theme, and anauthwithscopeandvia: "session". The assertions are unchanged. - "Both doors" and "pipeline first": the check log listed these two rules too, so I added the override lines they accept to the commit message. The reasons are mine, so check them:
No door:says the link word only refreshes the existing flows card live, with no new verb or screen.Direction:says the card must stay true when a sync lands (#15305).- If you want a terminal screen or a
docs/features/how-to instead, say so.
- Gate similarity notes: I left the "one implementation?" notes alone.
flowsPageagainstweekPage, and the test helpersmkandcommitagainstundo-make-it-yours.test.ts#mkandapproval-moved-inbox.test.ts#put, are advisory and did not fail the check.
<!-- look-pages cc95d39085db --> Look pages for cc95d39, from the gate:
look pages (inferred): this pull changes src/web/pages/flows.ts, src/web/pages/fork-standing.ts; the forge pictures /settings/crew (src/web/pages/fork-standing.ts), /settings/grants (src/web/pages/fork-standing.ts), /preview-admin/sample (src/web/pages/fork-standing.ts) and 3 more, the pages whose routes import it. A "Looks: <path>" or "No look: <why>" line in a commit message overrides
I pushed fixes for six of the eight failing tests, and the other two (the main.ts boot tests) passed when I re-ran them here. Locally, tsc --noEmit is clean and gate.ts printed nothing, and following-cache, fork-standing-line, server-timing-sweep, fork-linked-event and boot-production all pass. I did not run the full suite.
- Extra git comparison:
following-cache("warm reads do not compare again…") and "an answer git failed to give is not remembered", which shared its file, failed because every landed sync madeannounceLinkcompare the fork and parent a second time.fastForwardForknow passesannounceLinkthe level standing when the branch actually moved, since the fork then sits at the parent's tip. Conflicts and other cases still compare. - Server-Timing:
/:owner/:name/flows/mapnow namessessionandrenderphases, asflowsPagedoes. That fixedserver-timing-sweep. - Standing-line tests: the card now shows the link word before the sentence, so the markup regex in
test/fork-standing-line.test.tsaccepts an optional<strong data-link-word>… ·ahead of the link. The test was out of date with a deliberate markup change; the expected sentences are unchanged. main.tsboot tests: the failures were at 0.41 ms and 0.24 ms, which looks like a runner problem rather than my change. If they fail again on the next check, send me the log.
The "No door" and "Direction" lines are repeated in the new commit message. Those reasons are mine, so check them.
<!-- look-pages 9ccf4086cd4f --> Look pages for 9ccf408, from the gate:
look pages (inferred): this pull changes src/web/pages/flows.ts, src/web/pages/fork-standing.ts; the forge pictures /settings/crew (src/web/pages/fork-standing.ts), /settings/grants (src/web/pages/fork-standing.ts), /preview-admin/sample (src/web/pages/fork-standing.ts) and 3 more, the pages whose routes import it. A "Looks: <path>" or "No look: <why>" line in a commit message overrides
<!-- look-pages 08f1b7b094c3 --> Look pages for 08f1b7b, from the gate:
look pages (inferred): "Looks: /trevato/forge/flows" is not a page of app.looks in forge.json; this pull changes src/web/pages/flows.ts, src/web/pages/fork-standing.ts; the forge pictures /settings/crew (src/web/pages/fork-standing.ts), /settings/grants (src/web/pages/fork-standing.ts), /preview-admin/sample (src/web/pages/fork-standing.ts) and 3 more, the pages whose routes import it. A "Looks: <path>" or "No look: <why>" line in a commit message overrides
I replaced my earlier Looks: /trevato/forge/flows line, which was wrong: the gate said that path isn't in app.looks in forge.json. The new line is No look: and is in an empty commit (7a386de4a); no code changed.
None of the pages in app.looks shows a fork's flows page or its home card. The pages the gate infers (/settings/crew, /settings/grants, /preview-admin/sample and the rest) don't render this change, so there's nothing useful to picture. test/fork-linked-event.test.ts and test/fork-standing-line.test.ts cover the change instead.
If you want a picture of it, a fork's flows path would need adding to app.looks in forge.json. I didn't do that, because the looks run against fixtures I can't see.
Mechanism is sound: the event carries only word, count and a sentence, it rides the existing /events stream under the reader audience, and /flows/map 404s to viewers who cannot read the repo. Changes needed, all in one round:
- Box 6 is open: no before/after screenshots (light and dark). Add the fork card and /flows to app.looks in forge.json, or attach the pictures. A 'No look:' line does not meet the box.
- Principle 1 (nothing explains itself twice): the card now prints the link word and then the sentence beside it, so 'behind 3 · 3 commits behind' says the same thing twice. Fold the word into the sentence, or drop one of the two.
- Tests: takeUpdates now announces on a merge and on a conflict, and no test fails without those two calls. The tests cover only fastForwardFork (move and refusal). Add the merge (keep-both) and conflict shapes, as test/sync-shapes.test.ts does.
- Both doors: the terminal's forks screen re-renders on fork.linked via STANDING_EVENTS, but it does not show the word. Show it there, and put the how-to in docs/features/. The paragraph in forge-origin.md is a long run-on and is not a how-to.
- Clean: flows.ts imports from ../layout.ts on two lines; merge them. view.ts keeps a re-export shim of STALE_MS, linkWord and LinkWord; point the importers at link_word.ts and delete it. In fastForwardFork the comments are stacked and contradict each other; keep one.
Nothing changed in the code since my last read (the head only adds a No look: commit), so the earlier asks stand as they were: the event, its audience, the flows live region and the rewritten docs paragraph are in and tested; fork.linked carries only word, count and says, and is reader-level, so a viewer who may not read the fork hears nothing (tested over the real stream). Non-blocking: no before/after screenshots (box 6 is left; design-lint passes); no terminal screen change, which I accept because the forks screen already reads the standing and this only refreshes an existing card; offer and keep-both are not exercised by a dedicated test case. Not blocking.
Left #15305 open: 1 unticked item remain (before/after screenshots of the card in light and dark; bun scripts/design-lint.ts passes).
A fork's standing card now updates when a sync lands or is refused, with no reload and no poller. I did not take before/after screenshots (light and dark), so that checklist item is open. I ran
bun x tsc --noEmit,bun scripts/gate.ts --fix,bun scripts/design-lint.ts(passes) and the tests that touch this change; they are green.scripts/fast.tscalled the diff too broad to name tests, so I picked the files myself and did not run the whole suite.What changed
fork.linkedevent on the fork, with only{word, behind, says}. It comes fromannounceLinkinsrc/core/following.ts, called fromfastForwardForkand fromtakeUpdateson a merge or a conflict./eventsstream, which sends events only to viewers who may read the fork.fork.linkedis registered as a reader-level kind insrc/core/event_audience.ts, and the event never names the parent.src/web/pages/fork-standing.ts) now listens forfork.linked. The first paint is server-rendered and includes the link word, which is swapped in place from/standing-line./flowsis now a live region,#flow-links, listening on the page's one stream. It re-renders from a new fragment route/:owner/:name/flows/map.linkWord,LinkWordandSTALE_MSmoved tosrc/flows/link_word.ts, so core can say the word without importing the flows view.src/flows/view.tsre-exports them.docs/features/forge-origin.mdis rewritten.test/fork-linked-event.test.tsruns real git between real repositories and covers three cases. It fails without the event.following, and the flows fragment has the live region.behind 1.Not done
Try it Fork a repo, open
/<fork>and/<fork>/flows, then push to the parent. The word moves frombehind Ntofollowing. For a diverged fork, commit on both sides and the word showsbehind Nwithout a reload.The first push was refused by the pre-push hook, which wants a "Try:" commit. The empty commit after the code commit is that line, so the "Try:" subject is the hook's, not a note to you.
🤖 Generated with Claude Code
Closes #15305