The map opens for its owner, signed in, in Safari, and shows the next few things first #8702

The signed-in /map no longer ships every lane's drawing. The first screen is now lane headers plus the 5 next things, and a lane's graph draws when you ask for it. I did not reproduce the failure in Safari, so the first box is only partly met.

Cause. The owner's page was /map, not one repository's map. Every lane was server-rendered with its full SVG graph, which is the 6.2 MB and 4.15 s you measured. Safari stalls on that many elements. I did not drive Safari from here, so the cause rests on that measurement and the code.

Change (src/web/pages/global-map.ts):

• A Next list now sits above the lanes. It shows the top 5 ready issues across the lanes, crew lanes first, each linking to its issue.
• Each lane is a folded header with a "Draw this map" link to /map?lane=owner/name. That page draws only that lane, still at the widest lane's width, so the scale is unchanged.
• Lane access checks are unchanged: a stranger asking for a private lane gets nothing drawn.

Tests.

• A new test in test/map.test.ts holds the first screen under 50 KB and 1 s, requires the Next list with at most 5 entries, and requires no map-canvas on the first screen.
• It also checks that ?lane= draws exactly one lane.
• I changed two existing tests to ask for lanes by ?lane=: the lane-drawing assertions in test/map.test.ts and the privacy checks in test/map-cache.test.ts.
• I ran the map tests plus the live-pages, guest-crawl, webspec, client-home, home-archive, idle-reason, web-budget, design-audit, never-lost and held-relieves-map tests, and all pass.
• tsc, scripts/gate.ts and scripts/design-lint.ts pass.
• scripts/fast.ts named 1064 test files for this change, so I picked the covering files by hand.

Left out.

• Lanes load by full page navigation, not in-page, so there is no new JavaScript.
• /api/v1/map is unchanged and still returns every lane.
• The per-repository /:owner/:name/map (364 KB for this forge) is untouched.
• I measured nothing on production or a preview after the change.

Try it. Sign in, open /map, then click "Draw this map" on a lane.

Closes #8693

The signed-in /map no longer ships every lane's drawing. The first screen is now lane headers plus the 5 next things, and a lane's graph draws when you ask for it. I did not reproduce the failure in Safari, so the first box is only partly met.

Cause. The owner's page was /map, not one repository's map. Every lane was server-rendered with its full SVG graph, which is the 6.2 MB and 4.15 s you measured. Safari stalls on that many elements. I did not drive Safari from here, so the cause rests on that measurement and the code.

Change (src/web/pages/global-map.ts):

• A Next list now sits above the lanes. It shows the top 5 ready issues across the lanes, crew lanes first, each linking to its issue.
• Each lane is a folded header with a "Draw this map" link to /map?lane=owner/name. That page draws only that lane, still at the widest lane's width, so the scale is unchanged.
• Lane access checks are unchanged: a stranger asking for a private lane gets nothing drawn.

Tests.

• A new test in test/map.test.ts holds the first screen under 50 KB and 1 s, requires the Next list with at most 5 entries, and requires no map-canvas on the first screen.
• It also checks that ?lane= draws exactly one lane.
• I changed two existing tests to ask for lanes by ?lane=: the lane-drawing assertions in test/map.test.ts and the privacy checks in test/map-cache.test.ts.
• I ran the map tests plus the live-pages, guest-crawl, webspec, client-home, home-archive, idle-reason, web-budget, design-audit, never-lost and held-relieves-map tests, and all pass.
• tsc, scripts/gate.ts and scripts/design-lint.ts pass.
• scripts/fast.ts named 1064 test files for this change, so I picked the covering files by hand.

Left out.

• Lanes load by full page navigation, not in-page, so there is no new JavaScript.
• /api/v1/map is unchanged and still returns every lane.
• The per-repository /:owner/:name/map (364 KB for this forge) is untouched.
• I measured nothing on production or a preview after the change.

Try it. Sign in, open /map, then click "Draw this map" on a lane.

Signed-in /map no longer ships every lane's drawing. The first screen is now lane headers plus the 5 next things, and a lane's graph draws when asked for at /map?lane=owner/name. Safari signed in was never reproduced from here, so that box is open. The cause is the measured 6.2 MB / 4.15 s page: every lane was rendered with its full SVG graph.

Why the check failed, and the fix. Two tests in test/snappy.test.ts ("a write is on the very next map…" and "a sealed issue the owner's map drew is not drawn for a member…") looked for issue titles in the drawn /map. Titles now appear in a lane's graph only when that lane is asked for, so they read /map?lane=owner/name instead. They still check what they did before: a write shows on the next map, and a sealed issue stays hidden from a member. The tests did not pass on the first push because they expected the old page; they pass after the edit.

Tests.

• test/snappy.test.ts, the map tests, tsc and the design lint pass here.
• The four crawl-budget failures in the check (the "past its deep budget" test and three others) don't touch the map. The file passes alone here (11 pass), so I took them for shard-load flakiness and left them. If they fail again on this push, that is worth a look.

Change. The page code is in src/web/pages/global-map.ts.

• A Next list above the lanes shows the top 5 ready issues across them, crew lanes first.
• Each lane is a folded header with a "Draw this map" link. Drawing keeps one scale across lanes, and private lanes stay hidden from strangers.
• A test in test/map.test.ts holds the first screen under 50 KB and 1 s and requires no graph drawn on it.
• Not changed: /api/v1/map still returns every lane, and the per-repository map is unchanged.

Try it. Sign in, open /map, and click "Draw this map" on a lane.

I addressed all seven points except the Safari reproduction and the preview measurement, which I couldn't do. Map, snappy, live-pages, guest-crawl and xss tests, tsc, the design lint and the gate all pass here, and I've pushed.

1. Closed lanes. Every lane row now carries "Draw N issues" in its own meta, so a folded idle lane is one tap from its drawing. The fold body adds "draw it here" and a link to the lane's own /owner/name/map.
2. Drawn lane. A drawn lane's row shows "Show fewer", which goes back to the light /map. The lane's own map link is there too.
3. Next list. Rows now show the lane, the issue number, how many are ready in that lane, and "crew working" when it is. I kept the plain <h2> because I found no section-heading component in DESIGN.md or ui.ts, and map.ts itself uses bare <h2> for its headings. If you mean a specific one, tell me which.
4. Other doors. The API, MCP and terminal map still return every lane, deliberately, because a program asks for data and not a first paint. docs/features/map.md says so and documents ?lane= and the Next list.
5. ?lane= validation. parseLane accepts owner/name only (letters, digits, ., _, -, each part at most 100 characters, the whole at most 200). Anything else draws nothing and returns the light page. Tests cover unknown, malformed, too-long and null-byte values.
6. Stranger test. A new test signs in as a user with no access and checks that neither /map nor a ?lane= ask for a private lane or someone else's lane names it, shows its issues, or draws a graph. It also checks that bob asking for ?lane=alice/engine never sees alice's issues.
7. Timing assert. I removed it and kept the byte cap.

Safari signed in is still not reproduced. The preview needs a signed-in session, so I couldn't measure /map there from this shell. An unauthenticated request to the preview returned 0 bytes in 1.0 s, which says nothing about the page you asked about. The cause named in the pull is from the measured 6.2 MB / 4.15 s and the code. Please measure the preview signed in.

Left #8693 open: 1 unticked item remain (The failure is reproduced signed in and named in the pull.).