jay
/
pi-remote-control
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
pi-remote-control/docs
History
jay f70fd02f08 T-1.0: server refactor scaffold 
- Move original server.ts → server/legacy-server.ts (with LEGACY comment)
- Create server/server.ts re-exporting legacy bootstrap (T-1.0 scaffold)
- Create server/routes/{stream,input,sessions,commands,side,health}.ts
  as empty placeholders for T-1.5/T-1.6/T-1.7
- Create server/upgrade.ts as placeholder (T-1.5/T-1.6)
- Update index.ts to import from ./server/server.js
- Tag auth.ts, config.ts, messages.ts with LEGACY comments
- Update SYNC.md: claim removed, History entry added
 		2026-05-15 06:36:02 +02:00
..
reference docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
NEXT-STEPS.md docs: incorporate Phase 0.5 verdict (Path B), prep Phase 1 2026-05-15 04:48:20 +02:00
PHASE-0-spike-stream.md docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
PHASE-0.5-spike-tmux-control-mode.md docs: add Phase 0.5 — spike tmux control mode 2026-05-15 04:06:25 +02:00
PHASE-1-sidecar.md docs: freeze interface contracts IC-1 through IC-4 2026-05-15 06:25:08 +02:00
PHASE-2-ios-mvp.md docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
PHASE-3-ios-augmentation.md docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
README.md docs: incorporate Phase 0.5 verdict (Path B), prep Phase 1 2026-05-15 04:48:20 +02:00
SYNC.md T-1.0: server refactor scaffold 2026-05-15 06:36:02 +02:00

README.md

Implementation Docs

This folder drives the implementation work for the pi-remote iOS app and its sidecar. Background / spec / audit material lives in reference/.

Start here when resuming work: NEXT-STEPS.md.

File Purpose
NEXT-STEPS.md Resume pointer — state of play, next orchestrator actions, open questions. Read first.
PHASE-0-spike-stream.md Stream PoC — verify tmux + pipe-pane + WebSocket. ~1 day, single agent. Done, see reference/PHASE-0-report.md.
PHASE-0.5-spike-tmux-control-mode.md Follow-up spike: tmux control mode (-CC) vs pipe-pane + watchdog. Decides Phase 1 streaming path. ~2h, single agent.
PHASE-1-sidecar.md Sidecar production-ready: all S-features, multi-agent parallel work. Blocked on Phase 0.5.
PHASE-2-ios-mvp.md iOS app MVP — Groups A, B, C-01/02, D, E, F. Multi-agent parallel.
PHASE-3-ios-augmentation.md iOS feature polish — slash palette, voice, thumbnails, search, etc.
SYNC.md Live multi-agent coordination — claims, file ownership, contract changes.

Order of work

  1. Phase 0 first, single agent.
  2. Phase 1 starts after Phase 0 green-lights; multi-agent parallel.
  3. Phase 2 starts after Phase 1 is production-ready; multi-agent parallel.
  4. Phase 3 is continuous after Phase 2 MVP ships.

See SYNC.md for the current state.