[Deicyde]

Premise

• User: a reader who opens a result's local dependency graph on the map or in the book, and resizes the book's panes.
• Problem:
  1. The panel over a local graph took a corner of the stage with the result's title, the level buttons, a sentence of counts and a Back button, over the graph's top-left cards.
  2. The graph's links were curves that crossed the cards between their ends. At level 3 they ran across each other and behind cards.
  3. The book's pane splitters were 8px wide for a mouse and showed nothing until hovered, so a reader could not see where to drag.
• Replaces: nothing. The level rules from Local graph: a level that adds nothing can't be chosen #793 and Local graph: pressing the level drawn in place of the chosen one makes it the choice #797 are unchanged.

What changes

• Toolbar. showLocalPanel builds one row:

  • ← Map, labelled "Back to the map";
  • the level buttons, under main's rules (a level that adds nothing is disabled, and there are no levels where none adds anything);
  • the count, N / M, with the full sentence as its title (a result that builds on nothing says so in words);
  • a Details button (aria-expanded) that shows the title and the hub chips below the row.

  It is a button rather than <details> because Material draws a <details> in the book as a note box. Details stays open when the focus or the level changes.

• Links. AutoformMapLayout.routeColumns(routes, boxes) routes a local graph's links through the gaps between its columns and cards. It transposes the boxes and reuses routeThroughGaps, which already routes the whole-project map's links between rows. localLink draws the routed path and puts a "via n" label at the route's midpoint by length. Links that don't touch the focus are drawn at 40%, and 80% on hover.

  • A link between two cards side by side runs straight. The sweep that keeps ports across a corridor a lane apart no longer moves a route's own end away from its start; this holds on the whole-project map too.
  • A link that skips a column with one or two cards passes just above or below that column's cards (localEnds), not round the top or bottom of the whole graph.

• Splitters.

  • Each is 20px wide with a grip at its middle, in GrayText and Highlight under forced colours. The line still shows only while the splitter is hovered or dragged.
  • Where the browser refuses pointer capture, the drag continues through window listeners for the dragging pointer away from the splitter. Any release the splitter itself hears ends the drag, as before.
  • Its focus ring is drawn inside the part that takes presses.
  • Over a shut map, for a mouse, the reader's splitter narrows to 8px without the grip. The map's and Contents' tabs under it stay clickable, and a drag at its middle still opens the map. A finger's 24px splitter still sits under the raised tabs.

• Bundle. blueprint-explorer.min.js is rebuilt from blueprint-dag.js.

• CHANGELOG. Two Changed entries and one Fixed entry.

Left as is

• At the opening zoom, a long chain's far end is off the stage, because the camera keeps titles readable and anchors on the focus; zooming out shows it. This is unchanged from main.
• The arrowheads of several links into the focus meet close together at its left edge.
• A long title on the focus card is cut with an ellipsis, as on main.

Checks

• Tests for new behavior, a CHANGELOG line for each user-visible change.
  • tests/ui/test_project_map_browser.py:
    • test_local_graph_controls_are_compact_and_details_are_optional: one row under 72px; Details shows the title; Back closes the graph.
    • test_rendered_local_connections_do_not_cross_unrelated_result_cards: a 16-result chain at level 3, zoomed out, draws all 17 links, and none runs through a card it doesn't join.
    • The levels browser test reads the compact count.
  • tests/ui/test_dag_viewer_browser.py: test_pane_dividers_can_be_grabbed_on_both_sides_of_the_visible_border (4 cases) and test_pane_drag_continues_if_the_browser_refuses_pointer_capture (2 cases).
  • tests/ui/test_local_graph_routes.py: routes on a layered grid cross no card they don't join, and a link between two cards side by side is one straight segment.
  • tests/ui/test_project_map_client.py:
    • the compact count and its title;
    • Details is hidden until its button is pressed;
    • Local graph: pressing the level drawn in place of the chosen one makes it the choice #797's stand-in level test: Back keeps the level a press made the choice.
  • tests/ui/test_graph_view_rendering.py: the grip and its forced-colours rules.
• A scratch copy of this head passed every job: https://github.com/facebookresearch/autoform-bot/actions/runs/43447723705
• Screenshots, before (main) and after, of a 24-result fixture, in the screenshots artifact of each run:
  • before: https://github.com/facebookresearch/autoform-bot/actions/runs/43395772086
  • after, at b8d2ec3: https://github.com/facebookresearch/autoform-bot/actions/runs/43444170231
  • map-sylow-level3.png: the links at level 3, where off-focus links used to loop round the top and bottom of the graph (the review's question).
  • map-sylow-level1.png: the panel and the links at level 1.
  • book-sylow-local.png: the same graph in the book, with the splitters' grips.
  • book-splitter-hover.png: a hovered grip.
  • Details open, at 8e6ee64: map-sylow-details.png in https://github.com/facebookresearch/autoform-bot/actions/runs/43403115071.

Posted by Claude Code, at Jack's request.

[Deicyde]

Review at ab9dfa7: no blockers.

The before and after screenshots, against Jack's three complaints:

• The panel: it is now one row (← Map, the levels, 5 / 18, Details), where before it was a 160px card over the graph's corner.
• Dragging panes: both splitters show a grip. The drag tests cover each side of the border and a refused pointer capture.
• The lines: no link crosses a card now. At level 3, though, the faint links off the focus still loop above and below the middle column (map-sylow-level3.png). Jack should judge that one against "lines going everywhere".

The bundle diff is only the blueprint-dag change. Of the bundle's three inputs, only blueprint-dag.js changed. At both the base (9e1d2b7, 81,720 bytes) and the head (82,138 bytes), the committed bundle rebuilds byte for byte with esbuild 0.28.2 and Terser 5.51.2 (node scripts/build-explorer.mjs --check). 53f16c8, which came after the screenshots, changes no layout: only the splitter's hit area, a rename, and the opacity of via links off the focus.

Nits:

• A link between two cards in one row steps down a few pixels halfway, as from the focus to "No simple pq" on the map and in the book.
• The splitter's clip-path also cuts off the left side of the focus ring that its CSS comment promises.

Posted by Claude Code, at Jack's request.

[Deicyde]

Blockers-only check at d05bda2: no blockers.

• Both nits are fixed. The straight pair route is one segment, and the new routeColumns test pins it. The splitter's focus ring is now drawn 8px inside the splitter, within the part its clip keeps (2px inside on the 8px splitter over a shut map).
• Level 3: in the new screenshot, the faint links pass just beside the middle column instead of looping round the graph.

The whole-project map is not byte-identical, though:

• localEnds is local-only.
• The change that lets a route's own two ends meet applies to every caller of routeThroughGaps.
• Across 357 random layouts built the way layoutCommunity builds them (3,983 routes), 55 routes change. Every one is a route between adjacent rows that now runs straight where before it stepped a lane. No other route moves, and comparing the old version with itself changes nothing.

That is the same fix, applied to the whole map. If it's meant, the CHANGELOG could say so.

No bundle rebuild is needed: none of the bundle's three inputs changed, and no built asset embeds project-map-layout.js. Checks are green at d05bda2.

Posted by Claude Code, at Jack's request.