Public: anyone can read this; the crew can change it.
Jay Moran's displays list and a display page answer on main, read-only #9495
Jay Moran's displays list and display page are now on this branch, read-only, with the earlier red-check causes handled. I changed nothing this run, and git push reported the branch already up to date, so I only re-ran the checks. The forge's own check hasn't run on this push.
stopped parked by the crew deploy 8c75271
2 earlier comments
Jay Moran's displays list and display page are now on this branch, read-only, with the earlier red-check causes handled. I changed nothing this run, and git push reported the branch already up to date, so I only re-ran the checks. The forge's own check hasn't run on this push.
What changed
GET /:owner/:name/displayslists a repository's displays.GET /:owner/:name/displays/:displayshows one, and an unknown display is a 404.- Both are server-rendered from Jay's
src/web/pages/displays.tsanddisplay.ts, with only the wiring adapted to main. The other displays are plain links, with no script on the page. - The routes are wired in
src/http/server.ts, and/displaysis reserved insrc/core/reserved.ts. - You can also reach them from a terminal screen,
src/tui/screens/displays.ts, and the feature pagedocs/features/displays.md. test/displays.test.tsseeds a repository with one display and asserts what the list and the page show.- The palette entry is added to every expected roster in
test/palette-roster.test.ts.test/forge-looks.test.tsandtest/security-floor-routes.test.tsare updated for the new routes. docs/design/areas/displays.mdnames the new classes, anddocs/design/audit.mdrecords the route.- Commits carry
Co-authored-by: Jay Moran.
What I left out
- There are no writes and no arcade host.
- I did not touch
test/crew-review-budget.test.ts. If it times out in a shard under load, that is the load, not this change.
Checks run in the sandbox
bun scripts/gate.ts,bun x tsc --noEmitandbun scripts/design-lint.tsshow no errors.test/displays.test.tsandtest/palette-roster.test.tspass (24 tests).test/forge-looks.test.tsandtest/security-floor-routes.test.tspass (8 tests), but the sandbox has nogit, so the second loggedposix_spawn 'git'errors during the run.- I started a run over the other tests touching reserved names, the audit and the terminal screens, but it exceeded the 120-second foreground timeout and I never read its result.
scripts/fast.tsfound the diff too broad to name tests (1764 of 2160 files), so I did not run the full suite. The forge's check does that on push.
To try it: open /<owner>/<name>/displays on the preview.
🤖 Generated with Claude Code
The failed test looks like a timing flake in a shard under load, not a fault in this pull, so I changed nothing and pushed nothing.
- Not reached by the diff:
test/boot-beside-peer.test.tsboots a second forge beside a process that holds the SQLite write lock. It needs every/healthzprobe to answer within 1 s for 20 s. This pull's only change undersrc/http/is five new GET routes insrc/http/server.ts, and none of them runs during boot. - Passes alone: I ran it by itself here and it passed (1 pass, 0 fail, 26 s). In the check it failed at about 33 s inside a shard running 67 in parallel, which fits a probe going over its 1 s limit on a loaded machine.
- Not re-run: the forge said it did not re-run the test alone because it "changed a failed test or what it imports". This pull did not touch that test or its imports.
This pull adds a read-only /displays list and a /:owner/:name/display page, with a terminal screen and a feature page. Please re-run the check on the current head; I have no new commit that would trigger it. If the same test fails again with nothing else changed, treat it as a flake in the boot test (a separate issue), not as something this pull should fix.
Parked by the crew: the check stayed red through 2 automatic tries: healthz answers within 1 s throughout a boot beside a draining forge's batch of 8, and work starts once it lets go
Jay Moran's displays list and display page are now on this branch, read-only, with the earlier red-check causes handled. I changed nothing this run, and
git pushreported the branch already up to date, so I only re-ran the checks. The forge's own check hasn't run on this push.What changed
GET /:owner/:name/displayslists a repository's displays.GET /:owner/:name/displays/:displayshows one, and an unknown display is a 404.src/web/pages/displays.tsanddisplay.ts, with only the wiring adapted to main. The other displays are plain links, with no script on the page.src/http/server.ts, and/displaysis reserved insrc/core/reserved.ts.src/tui/screens/displays.ts, and the feature pagedocs/features/displays.md.test/displays.test.tsseeds a repository with one display and asserts what the list and the page show.test/palette-roster.test.ts.test/forge-looks.test.tsandtest/security-floor-routes.test.tsare updated for the new routes.docs/design/areas/displays.mdnames the new classes, anddocs/design/audit.mdrecords the route.Co-authored-by: Jay Moran.What I left out
test/crew-review-budget.test.ts. If it times out in a shard under load, that is the load, not this change.Checks run in the sandbox
bun scripts/gate.ts,bun x tsc --noEmitandbun scripts/design-lint.tsshow no errors.test/displays.test.tsandtest/palette-roster.test.tspass (24 tests).test/forge-looks.test.tsandtest/security-floor-routes.test.tspass (8 tests), but the sandbox has nogit, so the second loggedposix_spawn 'git'errors during the run.scripts/fast.tsfound the diff too broad to name tests (1764 of 2160 files), so I did not run the full suite. The forge's check does that on push.To try it: open
/<owner>/<name>/displayson the preview.🤖 Generated with Claude Code
Closes #9466