## Parent - #7 — Integrate Study Plans across Now, Web architect, and MCP ## What to build Add a Plan with architect journey to the Plans view using the existing live console, while retaining the complete manual form as a fallback. ## Acceptance criteria - [ ] The Plans view exposes a clear Plan with architect action. - [ ] Successful launch navigates to the existing live console and labels planning purpose correctly. - [ ] The architect receives interview questions, evidence seeds, existing-plan summaries, and optional brain dump. - [ ] Refresh and reconnect preserve planning-purpose context. - [ ] The manual create/edit/checkpoint interface remains fully functional. - [ ] Exactly one addressed console and WebSocket handle the planning session. ## Blocked by - #13 — Plan integration 6: Launch planning-purpose agent sessions ## Definition of Done - [ ] Browser tests cover launch, fallback, conflict, reconnect, cancellation, and structured errors. - [ ] A representative journey proves that no plan exists before the interview creates one. - [ ] Accessibility, loading, empty, and failure states follow existing Web conventions. - [ ] No duplicate terminal, ACP listener, or WebSocket is mounted. - [ ] Web UI documentation and normative requirements are updated.
Parent
What to build
Add a Plan with architect journey to the Plans view using the existing live console, while retaining the complete manual form as a fallback.
Acceptance criteria
Blocked by
Definition of Done