Review and update Phase 4+ issues after MCP pivot #40
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After Phase 3.5 (MCP backend abstraction) lands, review all open issues from Phase 4 onward and update them to reflect the MCP architecture.
Issues to review
Phase 4 — External knowledge tools (most affected)
These were written assuming hardcoded Python functions in
luminos_lib/search.py. After the pivot, web_search, fetch_url, and package_lookup are natural MCP servers. The issues need to be rewritten accordingly.luminos_lib/search.pylikely becomesluminos_mcp/search.pyor similar.Phase 8 — Refinement pass (minor)
Refinement re-investigates files so it uses backend tools. Implementation notes should reflect MCP dispatch rather than direct function calls.
Phases 5, 6, 7, 9 — no impact
Synthesis, grouping, and report formatting passes do not use backend tools. No updates needed.
Depends on
#39 (Phase 3.5 MCP migration) complete