Public: anyone can read this; the crew can change it.
A wave's page links the wave before it and the wave after it, by name, so the story reads in order #14573
Check · Review · Land · Live — No review yet.
A wave's page now ends with Earlier: and Later: links to the neighbouring waves in release order, built on the existing wave page route. The oldest wave has no Earlier link and the newest has no Later link. The new test/wave-neighbours.test.ts (middle, oldest, newest, and a file that isn't a wave skipped) passes.
waiting waiting for sentinel's review deploy 4df70eb
Check passeddeploy 4df70eb
Website spec: 26 findings (report only)
- /board http://127.0.0.1:40643/board answered 303 — https://specification.website/
- /notes http://127.0.0.1:40643/notes answered 303 — https://specification.website/
- /review http://127.0.0.1:40643/review answered 303 — https://specification.website/
- /releases http://127.0.0.1:40643/releases answered 303 — https://specification.website/
- /system http://127.0.0.1:40643/system answered 303 — https://specification.website/
- /admin/limits http://127.0.0.1:40643/admin/limits answered 404 — https://specification.website/
- /maintenance http://127.0.0.1:40643/maintenance answered 303 — https://specification.website/
- /talk http://127.0.0.1:40643/talk answered 303 — https://specification.website/
- /flow http://127.0.0.1:40643/flow answered 303 — https://specification.website/
- /resilience http://127.0.0.1:40643/resilience answered 303 — https://specification.website/
- /boards?help http://127.0.0.1:40643/boards?help answered 303 — https://specification.website/
- /settings/crew http://127.0.0.1:40643/settings/crew answered 303 — https://specification.website/
- /settings/crew?help http://127.0.0.1:40643/settings/crew?help answered 303 — https://specification.website/
- /settings/security/controls http://127.0.0.1:40643/settings/security/controls answered 303 — https://specification.website/
- /settings/grants http://127.0.0.1:40643/settings/grants answered 303 — https://specification.website/
- /preview-admin/sample expected exactly one <h1>, found 2 — headings
- /preview-admin/sample/drop http://127.0.0.1:40643/preview-admin/sample/drop answered 303 — https://specification.website/
- /preview-admin/sample/data-move http://127.0.0.1:40643/preview-admin/sample/data-move answered 303 — https://specification.website/
- /preview-admin/sample/cut-over http://127.0.0.1:40643/preview-admin/sample/cut-over answered 303 — https://specification.website/
- /preview-admin/sample/next?pick expected exactly one <h1>, found 2 — headings
- /preview-admin/sample/bets expected exactly one <h1>, found 2 — headings
- /preview-admin/sample/waves expected exactly one <h1>, found 2 — headings
- /preview-admin/sample/space the first focusable element is not a skip link (an in-page #target link) — skip-link
- /looks/missing http://127.0.0.1:40643/looks/missing answered 404 — https://specification.website/
- /looks/failed http://127.0.0.1:40643/looks/failed answered 500 — https://specification.website/
- /nope/nothing http://127.0.0.1:40643/nope/nothing answered 404 — https://specification.website/
This pull asks to reach lab--forge-trevato-apps.open-platform.sh. Its preview and check reach what main reaches; the new host opens when the pull lands.
Look
10 pages beside main · 0 new to this pull
/apps
In the dark
at 4df70eb ·
/docs
In the dark
at 4df70eb ·
/explore
In the dark
at 4df70eb ·
/looks/failed
In the dark
at 4df70eb ·
/looks/missing
In the dark
at 4df70eb ·
/nope/nothing
In the dark
at 4df70eb ·
/notes
In the dark
at 4df70eb ·
/releases
In the dark
at 4df70eb ·
/review
In the dark
at 4df70eb ·
/security
In the dark
at 4df70eb ·
3 earlier comments
A wave's page now ends with Earlier: <name> and Later: <name> links to the neighbouring waves in release order, built on the existing wave page route. The oldest wave has no Earlier link and the newest has no Later link.
The new test/wave-neighbours.test.ts (middle, oldest, newest, and a file that isn't a wave skipped) passes. So do the existing wave page tests I ran: wave-standing, wave-page-timing, waves-page, wave-page-pulls and waves-fit. tsc --noEmit and gate.ts --fix are clean. I did not run the full suite: scripts/fast.ts said the diff was too broad to name, so I picked the wave page tests myself.
- What changed:
waveNeighbours()insrc/story/waves.tsis new. It listswaves/once, finds the page's wave, and reads only as many files as it takes to find the nearest wave that parses on each side.wavePageinsrc/web/pages/waves.tsrenders the links server-side with the headline escaped, and aneighboursphase now shows in Server-Timing. - "Private wave" has no meaning here: a wave is a file in one repository, so the repository's visibility is the only gate and a private repository's waves aren't reachable at all. I treated the issue's "private wave is skipped" as any file that doesn't parse, or is too large or unreadable. Those are skipped and never named.
- Two commits beyond the change: the pre-push hook asked for a "Try:" commit, so the branch carries an empty one saying how to try this.
- Not done: the page still parses only the neighbours it needs, not the whole archive, to stay inside the page's time budget. The wave list and the Atom feed are untouched.
- How to try it: open
/<owner>/<repo>/waves/<version>on a repository with several waves and follow the links at the foot of the page. - Desk note: I saw the note "production is rolling, hold changes" and it did not touch this change.
🤖 Generated with Claude Code
<!-- look-pages 24192bc59cbf --> Look pages for 24192bc, from the gate:
look pages (inferred): this pull changes src/web/pages/waves.ts; the forge pictures /preview-admin/sample/waves (src/web/pages/waves.ts), the pages whose routes import it. A "Looks: <path>" or "No look: <why>" line in a commit message overrides
The preview failed because my earlier merge commit still had conflict markers in src/web/pages/waves.ts. I've resolved them, and the wave tests I ran pass. The fix is pushed as 12277434b.
- Resolution: the import now keeps both sides, so the page has the
?app=filter helpers from main andwaveNeighboursandwavePathfrom this change. - Checks:
tsc --noEmitis clean. 40 tests acrosswave-neighbours,waves-page,wave-standing,wave-page-timingandwaves-fitpass. I did not run the full suite. - Gate notes: the gate's "both doors" rule wanted a terminal change or a doc. I added a
No door:line to the commit instead, since these links are page navigation and the terminal already reaches each wave from its list. I also added aNo look:line, because the inferred/wavespicture doesn't show the foot of a wave page. - Long comment lines: the gate reports comment lines over 100 columns in
src/story/waves.ts. It says the nightly rewrap on main will fix them, so I left them.
I merged main into the branch and pushed it. The only conflict was the import block in src/web/pages/waves.ts.
- Conflict: I kept
waveNeighboursfrom this branch. I tookmain's words import, which no longer exportsFIRST_WAVE_BUTTONorNO_WAVES, so the old import would have broken the build. - Checks:
tsc --noEmitis clean, and the 216 tests in the wave, empty-state and story-words files pass.bun scripts/fast.tsfound the diff too broad to name, so I ran those files myself rather than the whole suite. - Gate:
scripts/gate.ts --fixreports only thatsrc/story/waves.tshas a comment line over 100 columns. It says the nightly rewrap fixes that onmain, so I left it.
The forge will run its full check on the push.
A wave's page now ends with
Earlier: <name>andLater: <name>links to the neighbouring waves in release order, built on the existing wave page route. The oldest wave has no Earlier link and the newest has no Later link.The new
test/wave-neighbours.test.ts(middle, oldest, newest, and a file that isn't a wave skipped) passes. So do the existing wave page tests I ran:wave-standing,wave-page-timing,waves-page,wave-page-pullsandwaves-fit.tsc --noEmitandgate.ts --fixare clean. I did not run the full suite:scripts/fast.tssaid the diff was too broad to name, so I picked the wave page tests myself.waveNeighbours()insrc/story/waves.tsis new. It listswaves/once, finds the page's wave, and reads only as many files as it takes to find the nearest wave that parses on each side.wavePageinsrc/web/pages/waves.tsrenders the links server-side with the headline escaped, and aneighboursphase now shows in Server-Timing./<owner>/<repo>/waves/<version>on a repository with several waves and follow the links at the foot of the page.🤖 Generated with Claude Code
Closes #14554