From 4f6fa0e83b7484e354e7cde5c6ccb2d64aed9242 Mon Sep 17 00:00:00 2001 From: jay Date: Fri, 15 May 2026 11:25:16 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20resolve=20OQ-3=20=E2=80=94=20tmux=20con?= =?UTF-8?q?trol-mode=20per-session?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/NEXT-STEPS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/NEXT-STEPS.md b/docs/NEXT-STEPS.md index d462720..98ddfe2 100644 --- a/docs/NEXT-STEPS.md +++ b/docs/NEXT-STEPS.md @@ -113,7 +113,7 @@ T-1.5, T-1.6, T-1.7 follow as their deps come in. - ~~**OQ-1.** Drop the `tree` event from IC-1 ServerToClient~~ — **resolved**: dropped. IC-1 frozen 2026-05-15. - ~~**OQ-2.** Resize message in IC-1?~~ — **resolved**: deferred, fixed 120×40 for v1. -- **OQ-3.** Should `tmux/manager.ts` use a single long-lived control-mode connection per **server**, or per **session**? The spike used per-session for simplicity. Per-server scales better but is more code. Decide before T-1.1 starts. (Not an IC question — T-1.1 implementation detail.) +- ~~**OQ-3.** tmux control-mode connection per-server vs per-session?~~ — **resolved**: per-session (like the spike). Simpler, spike reference code exists, isolates parser state per session. Refactor to per-server later if scale demands it. - ~~**OQ-4.** Worker model for T-1.0?~~ — **resolved**: `anthropic/claude-sonnet-4-6` with `context: fresh`. Haiku rejected: previous swarm attempt produced broken imports across `index.ts`/`html.ts`/`messages.ts` even on a stronger model (see deleted `feat/p1-t1-0-server-refactor` branch). T-1.0 is the blocker for all parallel fan-out — reliability over cost. ---