FE-709: Planning sync — Conversational Workspace Runtime umbrella frontier decomposition

[kostandinang]

Summary

Planning baseline that decomposes the Conversational Workspace Runtime umbrella (docs/design/CONVERSATIONAL_WORKSPACE_RUNTIME.md) into frontier items in memory/PLAN.md. Drafted off ln/fe-705-extensions so the diff inherits Lu's new PLAN.md format and shows only the umbrella additions (not the format migration).

Replaces closed PR #135 (closed due to a branch rename that GitHub didn't migrate cleanly).

Why this is a separate planning PR

Per the planning-pr skill convention:

• Edit establishes a planning baseline that several implementation branches should rebase onto before continuing.
• Frontier Definitions migration (three new frontier definitions added).
• Sequencing reshuffle (continuous-workspace done; Track 2/3/5 inserted; v4a retired).

Changes

• Context paragraph: names the umbrella + its 5 sub-tracks.
• Sequencing:
  • Active: continuous-workspace removed (done as FE-709).
  • Next: chat-runtime-threads (Track 2), thread-context-provision (Track 5), reconciliation-runtime (Track 3) inserted at appropriate positions.
  • Horizon: side-chat-persistence-v4a removed (superseded by Track 2).
• Three new frontier definitions added:
  • chat-runtime-threads — Track 2; thread substrate + in-stream rendering.
  • reconciliation-runtime — Track 3; async-by-default classifier with in-stream thread.
  • thread-context-provision — Track 5; TOON serializer, `#` mention, turn-zero.
• `continuous-workspace` frontier: Linear=FE-709, Status=done.
• Recently Completed: FE-709 entry for the workspace shell.
• Dependencies block: TRACK A restructured as the umbrella; `side-chat-persistence-v4a` moved to new RETIRED section.

Status

Draft. Will be promoted to ready-for-review once Lu's #132 + #133 land on main, at which point this PR's base can be retargeted to `main`.

Open questions still inherited from the umbrella

• Thread substrate shape: (p) `parent_chat_id` on `chat` / (q) new `thread` table / (r) UI-only rendering. Sub-RFC under Track 2 will decide.
• Reconciliation thread lifecycle, direct-edit thread-opening UX, TOON library choice. Deferred to per-track design.

Test plan

• PR base updates cleanly when Lu's stack merges.
• No SPEC.md edits in this PR.
• No code edits in this PR.
• After merge, downstream branches restack onto the new main.

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Low risk: documentation-only planning changes with no runtime/code modifications, but it may affect coordination if downstream branches rebase on the new sequencing.

Overview
Introduces the Conversational Workspace Runtime umbrella in memory/PLAN.md, splitting it into five tracks and reshuffling sequencing so continuous-workspace is marked done (FE-709) and chat-runtime-threads becomes the next major runtime unblocker.

Adds three new frontier definitions—chat-runtime-threads, reconciliation-runtime, and thread-context-provision—and updates dependencies to reflect the new Track 1–5 flow, while explicitly retiring side-chat-persistence-v4a in favor of thread-based in-stream history.

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

[augmentcode]

🤖 Augment PR Summary

Summary: Updates the planning baseline to decompose the Conversational Workspace Runtime umbrella into concrete frontier items in memory/PLAN.md.
Changes: Marks continuous-workspace (Track 1) as done (FE-709) and reshuffles sequencing to prioritize Track 2 (chat-runtime-threads) and align Tracks 3/5 behind it.
Adds three new frontier definitions: chat-runtime-threads, reconciliation-runtime, and thread-context-provision.
Retires the side-chat-persistence-v4a horizon in favor of collapsed in-stream threads.
Extends the Dependencies block to reflect the umbrella’s track graph and updates “Recently Completed” with the FE-709 entry.
Keeps agent-fixture-substrate (FE-705) as the active reconciliation item before higher-coordination semantic work proceeds.

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

[augmentcode]

Review completed. 1 suggestion posted.

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

[augmentcode]

memory/PLAN.md:106 — The thread kind is written as QA here, but chat-runtime-threads defines the kind as qa (see memory/PLAN.md:82); consider standardizing the casing so the plan’s thread-kind lexicon stays unambiguous.

Severity: low

Other Locations

• memory/PLAN.md:82

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}