FE-704: Sync planning after multi-chat substrate + V2 plumbing

[kostandinang]

Summary

Planning PR to reconcile memory/PLAN.md after FE-697 (multi-chat substrate + reconciliation_need queue) and FE-673 (side-chat V2 plumbing) reached completion. Drift surfaced by /ln-sync on 2026-05-07 — the file had FE-697 listed simultaneously as Active and as Recently Completed, no entry for FE-673, and the dependency diagram still showed multi-chat substrate as (next scope) in Track A while Track B already marked it (completed). Linear: FE-704.

What changed

• memory/PLAN.md
  • Narrative: substrate landed; V2 branch-complete with known UI-trigger gap; live frontier shifts to continuous workspace.
  • Active: promoted Continuous workspace from Next → Active.
  • Next: added Side-chat V2 UI trigger (closes the orphan gap from FE-673 where side-chat-popover.tsx:472-481 stayed stubbed disabled), and Side-chat V3 hard-impact + cascade preview (uses the reconciliation_need queue).
  • Recently Completed: added FE-673 V2 plumbing entry with explicit watch on the disabled Edit-mode button.
  • Dependency diagram: Track A multi-chat substrate now (completed) with side-chat V2/V3 sub-tree; Track B continuous-workspace flipped from (next) to (active); orphan revisit / edit-mode horizon line retired (subsumed by V3).
• docs/archive/PLAN_HISTORY.md
  • Rotated three older completions (FE-639 relation-first observer capture, FE-616 workflow ownership extraction, runtime JSON payload hardening) under a new ## 2026-05-07 Sync Archive heading per the rolling-frontier rule.

memory/SPEC.md untouched — no embedded historical detail to prune. A79 / A80 stay marked validated since they still constrain forward work (legacy pointer cleanup, patch-ledger extensibility).

Intent

This is a planning/scope merge point, not a feature change. Land it on main first so downstream feature branches (ka/fe-697-decouple-turns-from-specs and any new work) rebase onto a shared planning baseline rather than fight over the same paragraphs. Follows the convention codified in .agents/skills/planning-pr (FE-703, PR #99) and previously demonstrated by FE-698 (PR #98).

Test plan

• CI passes (no code touched)
• PR merges to main before downstream stack work resumes
• Downstream gt restack on open feature branches is conflict-free on memory/PLAN.md and docs/archive/PLAN_HISTORY.md

[cursor]

PR Summary

Medium Risk
Doc-only changes, but memory/PLAN.md currently contains unresolved merge-conflict markers in the Recently Completed section, which could break tooling that parses the plan.

Overview
Updates planning docs to reflect FE-697 multi-chat substrate and FE-673 side-chat V2 plumbing as completed, promoting continuous workspace to the single Active frontier and adding follow-up Next items for a V2 UI trigger and V3 hard-impact/cascade work.

Rotates older completed items out of memory/PLAN.md into a new 2026-05-07 Sync Archive section in docs/archive/PLAN_HISTORY.md, and refreshes the dependency diagram/horizon notes to match the new sequencing. Note: memory/PLAN.md includes <<<<<<</=======/>>>>>>> conflict markers that should be resolved before merge.

^{Reviewed by Cursor Bugbot for commit 42c109e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[kostandinang]

• FE-674: Sync planning for V3 cascade through reconciliation_need #110
• FE-704: Sync planning after multi-chat substrate + V2 plumbing #100 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[augmentcode]

🤖 Augment PR Summary

Summary: Planning-doc sync after FE-697 (multi-chat substrate + reconciliation_need) and FE-673 (side-chat V2 plumbing) landed.

Changes:

• Promotes Continuous workspace from Next to Active as the current execution frontier.
• Adds Next items for the missing Side-chat V2 UI trigger and a V3 hard-impact + cascade preview driven by reconciliation_need.
• Updates Recently Completed to capture FE-673/FE-697 status and explicitly calls out the remaining disabled Edit-mode button gap.
• Refreshes the dependency diagram to reflect the completed substrate and the V2/V3 subtree.
• Archives older completed entries into docs/archive/PLAN_HISTORY.md under a new 2026-05-07 Sync heading.

Technical Notes: memory/SPEC.md remains unchanged; A79/A80 stay validated constraints.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 88d2252. Configure here.}

[graphite-app]

Merge activity

• May 8, 1:28 PM UTC: Graphite rebased this pull request, because this pull request is set to merge when ready.