EPIC: ADR-0003 — Advisor → Query Planner direct retrieval

[bjagg]

Implement ADR-0003: internal programmatic consumers (the Advisor, via the semantic-search MCP server) retrieve LIF data from the Query Planner directly, and GraphQL is retained as a peer external facade — not a mandatory internal waypoint. This is the enabling topology for the Advisor's partial-result / progress ("Regime B") work.

Plan: docs/operations/proposals/advisor-qp-direct-retrieval.md (PR #1104) — grounded in a file:line map of the current code. Spike: #1053.

Regime-A-first: in-turn token streaming (Regime A, #970 / advisor-streaming.md) ships independently with no data-layer change and is not part of this epic — only the reframe concurrency fix (A) is shared. This epic is the retrieval rewire + the QP partial-result subsystem + Advisor Regime B.

Sequencing:

1. Foundation / topology: B → C → D → E — Advisor retrieves from the QP directly; GraphQL becomes a peer consumer. Shippable without partial results.
2. QP net-new: F → G → H — durable job store, partial results, completion propagation.
3. Regime B: I.

• A = shared concurrency precursor.

See the plan for full detail, per-item dependencies, and the current-state code map. Sub-issues below roll up automatically.