feat: graph management UI — admin page, picker, delete, member search

[charlie83Gs]

Summary

Implements #168 — comprehensive graph management UI improvements:

• Graph-switch reactivity fix: All data-fetching hooks (useNodeList, useEdgeList, useFactList, useSourceList, useSeedList, useGraphExplorer) now refetch when the active graph changes via switchGeneration. Pages (/investigate, /grow-graph) also react to switches.
• Synthesis API bug fix: createSynthesis() and createSuperSynthesis() now use graphRequest() instead of plain request(), ensuring syntheses are created in the correct graph.
• Sidebar admin link: Added "Graphs" nav item with Layers icon to the admin section.
• Org-style graph picker: Replaced plain <select> with a Popover+Command switcher — always visible, searchable, shows node counts per graph, with a "Manage graphs" link for superusers.
• Delete graph: New DeleteGraphDialog with "type slug to confirm" safety pattern. Wired into list page (hover icon) and detail page (danger zone section).
• Member invite by email: New MemberSearch component replaces raw UUID input with email autocomplete using GET /api/v1/members.
• Role tooltips: Hovering "Role" column header shows reader/writer/admin permission descriptions.
• Backend: DB connections endpoint: New GET /api/v1/graphs/database-connections (superuser-only) lists available database connections.
• Backend: GraphResponse enhancement: Added database_connection_name field, batch-fetched in list/detail endpoints.
• DB connection picker: Graph creation form shows a database connection selector when storage_mode=database.
• List page polish: Search/filter by name + database, empty states with CTAs, created_at display, database_connection_name on cards.
• Detail page polish: Extended stats grid, database_connection_name, created_at, BYOK status, member count.

Test plan

• pnpm lint — passes clean
• pnpm type-check — passes clean
• pnpm test — 123/123 tests pass
• Manual: switch graphs via picker → verify all list pages show correct data
• Manual: create graph with DB connection picker
• Manual: delete graph via list page and detail page danger zone
• Manual: invite member by email search
• CI pipeline checks

🤖 Generated with Claude Code

[charlie83Gs]

PR #169 Review

Nice feature set — the graph picker, delete dialog, and member search are well-built. A few things to address:

---

Blocking: Merge conflicts with main

The PR currently shows CONFLICTING merge status. Needs a rebase/merge from main. The conflicting files appear to be across both frontend and backend (GraphPicker.tsx, edges.py, facts.py, graphs.py, main.py, nodes.py, research.py, seeds.py).

---

Issues to fix

1. DB connection fetch can infinite-loop on error — frontend/src/app/graphs/page.tsx:50-58

When the listDatabaseConnections() call fails, the catch sets dbLoaded back to false, which changes the dependency array and re-triggers the effect, which fails again, ad infinitum. Either use a ref to track the attempt, or don't reset dbLoaded on failure (set an error state instead).

// Current (loops on error):
.catch(() => setDbLoaded(false));

// Fix: keep dbLoaded=true and track the error separately
.catch(() => setDbError("Failed to load connections"));

2. MemberSearch: 403 error causes retry on every open — frontend/src/components/graphs/MemberSearch.tsx:47-55

When the API returns 403, loaded is never set to true, so every subsequent popover open retries the failing request. Set setLoaded(true) in the .finally() block or move it out of the .then().

// Fix: move setLoaded(true) to .finally()
.then((data) => {
  setMembers(data);
})
.catch((err) => { ... })
.finally(() => {
  setLoading(false);
  setLoaded(true);  // prevent retries on persistent errors
});

3. Node count queries open N connections for N graphs — services/api/src/kt_api/graphs.py:199-214

_count_nodes resolves a new GraphSessions and opens a new DB session per graph via asyncio.gather. For a user with many graphs, this fans out to N concurrent DB connections on every list call. Consider capping concurrency with a semaphore, or storing node counts as a materialized counter (similar to NodeCounter in write-db) to avoid the fan-out.

Not blocking, but worth a TODO comment at minimum.

4. import asyncio inside function body — services/api/src/kt_api/graphs.py:193

Minor: move import asyncio to the top of the file with other stdlib imports.

---

Observations (non-blocking)

• switchGeneration pattern: The eslint-disable comments with switchGeneration in deps across 7+ hooks work correctly but are fragile. Consider extracting a useGraphScopedFetch(fetchFn, deps) hook that encapsulates this — would eliminate the repeated disable comments and make the pattern self-documenting.

• DeleteGraphDialog HTML entity: Line 67 uses “ — works fine in JSX but \u201c / \u201d is more idiomatic React.

• Access control looks solid: _require_graph_access with role hierarchy, WITH FOR UPDATE locking for last-admin protection, superuser bypass — all well-implemented. The default graph open-read / superuser-write policy is clearly documented.

• Synthesis API fix: createSynthesis and createSuperSynthesis now correctly use graphRequest — good catch and fix.

---

Summary

Fix #1 and #2 (both quick), resolve merge conflicts, and this is good to merge. #3 is worth tracking but not blocking.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}