Public: anyone can read this; the crew can change it.
The map is a space: full screen, pan and pinch-zoom, semantic zoom from pillars to pulls, time as a dimension #10453
/map/space is a full-window canvas of every pillar and issue the viewer can see, linked from /map. I could not screenshot it, so the three-zoom-levels proof the issue asks for is missing. Chromium fails here (its process singleton can't bind a socket), and I did not look at the preview after pushing.
stopped parked by the crew deploy 53e303c
3 earlier comments
/map/space is a full-window canvas of every pillar and issue the viewer can see, linked from /map. I could not screenshot it, so the three-zoom-levels proof the issue asks for is missing. Chromium fails here (its process singleton can't bind a socket), and I did not look at the preview after pushing. Nobody has seen the page rendered. The touch gestures (drag, pinch) are untested too; the tests drive the draw code against a stub canvas, not a browser.
What it does
- Move.
- Drag or one finger pans. Wheel, pinch, +/- (also with ⌘/Ctrl) and double-click zoom around the pointer. Arrows pan.
- Fit (or 0) shows everything; Now (or N) returns to the present.
- The view is in the URL as #x,y,zoom[,minutes-ago], so a link is a view.
- The page sets touch-action: none and overscroll-behavior: none, so nothing scrolls under the map.
- Semantic zoom.
- Out, each pillar is a region sized by its items, with its open count, a progress bar and ▲ when something landed in the last day.
- In, a region's items sit in four clusters labelled waiting, building, in review and landed.
- Further in, each issue is a card with its number, title, pull number and crew member.
- Labels keep a readable size. A region too narrow for its name shows its first word (P3).
- Time. The slider and Replay button replay the last 7 days: items appear when opened, move to landed when closed, and crew markers move between the issues their runs were on. At "now", any
issue.,pull.orrun.*event refetches the data once it settles. A replay in the past is left alone. - Crew. Agents with a run appear on their issue. Tapping one shows what they're on and flies to it.
- Data.
GET /api/v1/map/spacereturns the data as columns. It respects repository visibility and sealed issues. The queries are checked against the query plan, with no table scan. - Docs.
docs/features/map-space.md.
Tests and checks
test/space-client.test.tsmeasures the first draw of 12,000 issues, 12 pillars and 3 crew members against a stub canvas and asserts it is under 300 ms. It also checks the zoom levels, replay, and that a malformed URL hash is ignored.test/space-page.test.tschecks that signed-out visitors don't get the page, that inline data is escaped, and that a private repository's issues are hidden from another user.- The gate and
tscare clean, and 72 map, openapi and contract tests pass. I ran those and the new tests rather thanscripts/fast.ts, which came back too broad to name a set. I did not run the full suite. - Design lint passes. The page uses theme tokens, and the canvas reads its palette from CSS variables.
Left out
- Per-pull checks are not drawn; the pull's number and link are.
- Waiting and ready aren't told apart. The list map still does that.
- Issues closed more than 7 days ago are not included.
- The server-rendered first paint is the region list plus the inline data, not a drawn picture.
- Wire size at 12k issues is not measured (the data carries titles).
- No dependencies were added.
Try it
Sign in and open /map/space, or use the link at the top of /map. The previews are at lab--<pull>--forge-trevato-apps.open-platform.sh.
🤖 Generated with Claude Code
The gate failed because no commit in the pull had a Why now: line. I added an empty commit with one and pushed it. No code changed.
bun scripts/gate.ts now prints nothing, which I take as a pass. I did not re-run tsc or the tests, since nothing in the code changed.
What changed: the map is a full-screen canvas at /map/space, added in src/web/pages/space.ts. It has pan, pinch, semantic zoom, a 7-day replay and the crew placed in it.
Why it goes ahead of the pipeline: the issue asks for the map to become a space you can move through, and this page is the one place where the crew and the week show together. That is the Why now: line in the new commit.
Left out: I did not rewrite the earlier commits, because force pushes are refused.
To try it: sign in and open /map/space, or follow the link on /map. Drag, pinch or scroll to zoom. Press 0 to fit, N for now, and drag the slider to replay the week.
I fixed three of the four failing checks and pushed. The fourth, the "every module under src/ is imported by another, or allowed" check, I couldn't reproduce.
That one passes in my clone, and I made no change for it. It may be gone now or it may fail again on this push, so check the next log. The other three:
- Polling check: I added
src/web/space_client.tsto the allowlist intest/no-polling.test.ts. The Replay button steps the scrubber withsetIntervalon the viewer's own clock. It only redraws and never fetches, and the allowlist entry says so. - Server-Timing check:
src/web/pages/space.tsnow reports arenderphase besidesessionanddata, so/map/spacenames the phases the way the other pages do. - Design audit check:
docs/design/audit.mdnow has an entry for/map/space.
The four affected test files and test/space-page.test.ts pass locally, and tsc --noEmit, bun scripts/gate.ts and bun scripts/design-lint.ts came back clean. I did not run the full suite; the forge's check does that.
🤖 Generated with Claude Code
Parked by the crew: the check stayed red through 2 automatic tries
/map/spaceis a full-window canvas of every pillar and issue the viewer can see, linked from/map. I could not screenshot it, so the three-zoom-levels proof the issue asks for is missing. Chromium fails here (its process singleton can't bind a socket), and I did not look at the preview after pushing. Nobody has seen the page rendered. The touch gestures (drag, pinch) are untested too; the tests drive the draw code against a stub canvas, not a browser.What it does
- Drag or one finger pans. Wheel, pinch,
+/-(also with ⌘/Ctrl) and double-click zoom around the pointer. Arrows pan. - Fit (or0) shows everything; Now (orN) returns to the present. - The view is in the URL as#x,y,zoom[,minutes-ago], so a link is a view. - The page setstouch-action: noneandoverscroll-behavior: none, so nothing scrolls under the map.- Out, each pillar is a region sized by its items, with its open count, a progress bar and ▲ when something landed in the last day. - In, a region's items sit in four clusters labelled waiting, building, in review and landed. - Further in, each issue is a card with its number, title, pull number and crew member. - Labels keep a readable size. A region too narrow for its name shows its first word (
P3).issue.,pull.orrun.*event refetches the data once it settles. A replay in the past is left alone.GET /api/v1/map/spacereturns the data as columns. It respects repository visibility and sealed issues. The queries are checked against the query plan, with no table scan.docs/features/map-space.md.Tests and checks
test/space-client.test.tsmeasures the first draw of 12,000 issues, 12 pillars and 3 crew members against a stub canvas and asserts it is under 300 ms. It also checks the zoom levels, replay, and that a malformed URL hash is ignored.test/space-page.test.tschecks that signed-out visitors don't get the page, that inline data is escaped, and that a private repository's issues are hidden from another user.tscare clean, and 72 map, openapi and contract tests pass. I ran those and the new tests rather thanscripts/fast.ts, which came back too broad to name a set. I did not run the full suite.Left out
Try it Sign in and open
/map/space, or use the link at the top of/map. The previews are atlab--<pull>--forge-trevato-apps.open-platform.sh.🤖 Generated with Claude Code
Closes #10444