The map, lightly (#8693)
/map is every app you can see, one lane each. The first screen is light:
- Next: the top 5 ready issues across your lanes, crew lanes first, each with its lane, its number and how many are ready there.
- Lanes: one folded row per app with its counts. The row carries a link,
Draw N issues, that opens/map?lane=owner/name: that lane's graph, drawn at the same scale as all lanes, withShow fewerto go back. Each lane also links its own map,/owner/name/map.
?lane= is owner/name made of letters, digits, ., _ and -, at most 200 characters; anything else, an unknown lane, or one you may not see draws nothing and the page is the light one. The test in test/map.test.ts holds the first screen under 50 KB.
The other doors keep the whole graph: /api/v1/map, the MCP map tools and the terminal map return every lane, since a program asks for data, not a first paint.
Keyboard and screen reader (#12755)
Focus a map (click it or Tab to it) and it answers keys, only while focus is inside that map and not in a field, and never with Ctrl, ⌘ or Alt held:
- Arrow keys pan the drawing by 80 px per press, at any zoom.
+(or=) zooms in,-zooms out,0fits the drawing again.
A polite live line under the map (data-map-live) says what is on screen after the view settles (400 ms after the last key): Showing 3 of 12 issues, counting the cards that overlap the visible frame. The focused map has an accent outline. The table of keys is src/web/map_keys.ts; the page script embeds its functions, so the tests run the same code.