Client consistency audit: verify all clients use accelerated query endpoints

[aaronsb]

Context

ADR-201 Phase 5 introduced GraphFacade (topology acceleration) and batch hydration (grounding/confidence caching). The API routes now use these optimized paths, but four client applications need verification to ensure they're calling the right endpoints with the right parameters.

This is the biggest architectural change to the query layer so far. All clients should benefit from the acceleration without any client-side changes (the optimization is server-side), but we need to verify:

• Clients request include_grounding: true where appropriate
• Clients use the batch-enabled endpoints (not deprecated ones)
• Response shapes haven't changed in ways that break client parsing

Clients to Audit

Web workstation (web/src/api/client.ts)

• Inventory all query-related API calls
• Verify search, connect, related endpoints hit the accelerated routes
• Check response parsing for grounding/confidence fields

MCP server

• Inventory tool implementations that make graph queries
• Verify grounding parameters are passed through
• Check for any hardcoded endpoint paths

CLI (cli/src/)

• Inventory kg search, kg search connect, kg concept etc.
• Verify they request grounding and use batch-enabled endpoints
• Check response display code handles new fields

FUSE driver (fuse/)

• Inventory graph queries made by the filesystem layer
• Verify query patterns are consistent with API changes

Deliverable

• Document findings per client (what's correct, what needs updating)
• Apply fixes where needed
• Update .claude/todo-adr-201-graph-accel.md with results

References

• Phase 5g in .claude/todo-adr-201-graph-accel.md
• PR feat: unified GraphFacade with graph_accel integration (ADR-201 Phase 5b) #274 (GraphFacade), PR feat: generation-aware hydration caches (ADR-201 Phase 5f) #276 (batch hydration)

[aaronsb]

Audit Complete

No changes needed (correct)

• CLI: search, connect (both modes), concept details — all pass include_grounding: true
• MCP: search, concept details, connect-by-search — all pass include_grounding: true
• Web: concept details — passes include_grounding: true

Inconsistencies to fix

Client	Operation	Fix
CLI related	Missing include_grounding	Add to match search/connect behavior
MCP related	Missing include_grounding	Add to match search behavior
MCP connect (exact)	Missing include_grounding	Add to match connect-by-search behavior

Intentional design (no fix)

• Web search/related: Grounding disabled for performance — fetched on-demand when user clicks a concept for details. This is correct for the UI pattern.
• Web connect: Same on-demand pattern.
• FUSE: Presents data as files. Grounding isn't exposed in the filesystem interface. If FUSE adds grounding display in the future, it would be a feature, not a bug fix.

Response parsing

All clients parse grounding_strength, grounding_display, and epistemic status fields correctly where they exist. No schema mismatches found.

[aaronsb]

Reopening — the audit identified 3 fixes that were never applied:

Client	Operation	Fix
CLI related	Missing include_grounding	Add to match search/connect behavior
MCP related	Missing include_grounding	Add to match search behavior
MCP connect (exact)	Missing include_grounding	Add to match connect-by-search behavior

Picking this up now.