Part of #259
Question
Explicitly deferred by the driving user mid-grilling on 2026-08-10 — do not claim/work this until they ask for it. When it is picked up: should the future read-only query surface (tentatively MCP) be (a) parallel and independent of the agent-context-graph hook plugin, (b) become the plugin's own internal transport (a bigger rearchitect of something already in production use), or (c) something else? The driving user noted their longer-term goal is supporting most harnesses via hook mechanisms specifically (not via this read-only surface), which may make (a) the likely answer — but this should still be grilled properly, not assumed.
Part of #259
Question
Explicitly deferred by the driving user mid-grilling on 2026-08-10 — do not claim/work this until they ask for it. When it is picked up: should the future read-only query surface (tentatively MCP) be (a) parallel and independent of the
agent-context-graphhook plugin, (b) become the plugin's own internal transport (a bigger rearchitect of something already in production use), or (c) something else? The driving user noted their longer-term goal is supporting most harnesses via hook mechanisms specifically (not via this read-only surface), which may make (a) the likely answer — but this should still be grilled properly, not assumed.