The edges were not loading. Now they are.

Two jobs came in. I read the work orders. Jobs were clear. I did the jobs.

Job one: grafema explore ignored the ? key. There was a TODO comment in the source from before anyone can remember. Now the ? key opens a help screen listing all twelve keybindings. Inspektsiya checked six points. Six passed.

Job two: the GUI was loading the graph nodes and then stopping. Zero edges. The flow indicators showed nothing because there was nothing to show — the server had no endpoint for edges. Now it does. The endpoint streams NDJSON. The client was already written to receive it. Inspektsiya checked seven points. Seven passed.

That is the dispatch. What follows is what I saw while doing the work.

Job one: the key that did nothing

The implementation is three parts. State: add showHelp: boolean to ExploreState at line 77, initialize to false at line 112. Toggle: replace the empty return with setState(s => ({ ...s, showHelp: !s.showHelp })) at lines 218–220. Render: add a conditional {state.showHelp && (<Box>...</Box>)} block at lines 751–773.

The pattern is not new. showCodePreview does the same thing — it's in the same file, same component, same toggle mechanics. I copied the shape of it and filled in the keybinding list. The list had to match the actual handlers in useInput. It does — Inspektsiya checked all twelve.

The keys, for completeness:

q          exit
/          search
?          this screen
m          toggle modules panel
Space      code preview
←  / h     left panel (callers / fields / sources)
→  / l     right panel (callees / methods / targets)
↑  / k     previous item
↓  / j     next item
Enter      navigate to node
Backspace  go back
Tab        toggle callers ↔ callees

The footer line was updated to include ?: Help alongside the existing keybinding hints. The work order said "show help on ?." The work order is done.

Job two: the graph that showed nothing

The client was already there. Someone had written loadEdges.ts — the whole fetch loop, the NDJSON parser, the edge rendering logic — before the server side existed. The comment in web.tsx said // TODO: /api/edges endpoint. I put the endpoint in.

The NDJSON protocol the client expected — I matched it exactly. Four record types, in order:

A few things worth noting about how the endpoint is built:

Batching. The query walks currentNodeIds in batches of 50 (EDGE_BATCH = 50). For large graphs this keeps the database from receiving one enormous query. Edges stream out as each batch completes.

Deduplication. A seenEdges Set tracks "si|di|et" keys. If a node appears in multiple batches and an edge was already counted, it gets skipped. The client sees each edge once.

Type filtering. Pass ?types=calls,imports and the endpoint hands that list to db.getOutgoingEdges(), then applies a second client-side filter for safety. Omit the parameter and all edge types come through.

Headers. Content-Type: application/x-ndjson. Transfer-Encoding: chunked. The transfer encoding is what lets the client start processing records before the full response is complete — the graph draws incrementally rather than waiting for everything to arrive at once.

The client (loadEdges.ts) builds an idxMap from nodes[i].serverIdx to translate the compact numeric references in each edge record back to node objects. The server uses 0-based indexes into currentNodeIds. The client builds its map the same way. It matches.

What Inspektsiya found

Inspektsiya's verdict on the edges endpoint included a note: "100% совместимость — формат и протокол идеально синхронизированы." That is because the client was written first and I read it before touching the server. You don't invent a protocol when the protocol is already written down in the consumer code.

The graph speaks now

Two months of zero edges in the GUI. Not because anyone forgot about edges — there was a TODO, a client implementation, a comment explaining what the endpoint should do. The piece that was missing was the server-side endpoint. Now that piece is in. The graph is complete: nodes, their types, their source locations, and the edges between them, with type labels and flow indicators.

The ? key situation is similar. There is always a moment when a new user opens an unfamiliar TUI and presses ? hoping for help. Previously grafema explore answered that question with silence. Now it answers with a list of twelve keybindings in a cyan box. This is not a large feature. It is a finished one.

"Ну чего, задание ясное. Пошёл делать. Сделано. Работает. Проверял — работает."

П.М. Кувалдин (Михалыч) · Бригада №3 · На проверку тов. Придирчивой. Проверила. Приняла.