jay
/
pi-remote-control
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: mark IC-1..IC-4 frozen in NEXT-STEPS, resolve OQ-1/OQ-2

This commit is contained in:
Johannes Merz 2026-05-15 10:48:38 +02:00
parent c9bdfce890
commit 07522e5974
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/NEXT-STEPS.md
View File

@ -1,8 +1,8 @@
# Next Steps — Resume Pointer
> **Last updated:** 2026-05-15, end of day.
> **Where we are:** Phase 0 + 0.5 done. Phase 1 doc updated for Path B.
> **Where we go next:** Freeze interface contracts, then T-1.0.
> **Last updated:** 2026-05-15.
> **Where we are:** Phase 0 + 0.5 done. Phase 1 doc updated for Path B. Interface contracts IC-1..IC-4 frozen (commit 7c40c49).
> **Where we go next:** Dispatch T-1.0 — Server Refactor.
This document is the "where did I leave off" anchor. Read this first when
resuming work. The rest of `docs/` is reference.
@ -16,7 +16,7 @@ resuming work. The rest of `docs/` is reference.
| Phase 0 — Stream Spike | ✅ done. Verdict GREEN with caveat (pipe-pane unreliable). Branch `feat/spike-stream` kept. |
| Phase 0.5 — Control-Mode Spike | ✅ done. Verdict: **Path B — tmux control mode**. Branch `feat/spike-tmux-cc` kept. |
| Phase 1 plan | ✅ updated to Path B. T-1.1 now specifies control mode + `%output` parser. Architecture diagram, risks (R4 + R5) added. |
| Interface Contracts (IC-1..IC-4) | ⚠️ **draft**. Need orchestrator sign-off before T-1.5 / fan-out. |
| Interface Contracts (IC-1..IC-4) | ✅ **frozen** 2026-05-15. See SYNC.md. |
| Phase 1 implementation | ⛔ not started. T-1.0 is the next dispatch. |
| iOS work | blocked, untouched. |
@ -111,9 +111,9 @@ T-1.5, T-1.6, T-1.7 follow as their deps come in.
## Open questions for next session
- **OQ-1.** Drop the `tree` event from IC-1 ServerToClient, or keep reserved? (Recommendation: drop.)
- **OQ-2.** Resize message in IC-1? (Recommendation: defer.)
- **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.
- ~~**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-4.** Worker for T-1.0: same `anthropic/claude-sonnet-4-5`, or escalate to a higher-context model since the refactor touches multiple files? (Recommendation: sonnet-4-5 with `context: fresh` is fine for ~500 LoC refactor.)
---