pi-remote-control/docs
jay a7dad86901 feat(t-1.0a): smoke test harness MVP
- scripts/smoke/helpers.mjs — spawn-pi (via python3 pty.spawn), wait-for-port,
  fetch, WebSocket helpers; createSmokeHome/removeSmokeHome for isolated HOME
- scripts/smoke/smoke.mjs — 6 node:test assertions:
    GET /manifest.json → 200 + JSON shape
    GET /icon.svg → 200 + <svg body
    GET / (with token) → 302→200 + HTML marker
    GET / (no token) → 403
    WS /ws (with token) → 101 upgrade
    pi process alive check
- scripts/smoke/README.md — usage, design notes, extension guide
- package.json: add 'smoke' script
- docs/SYNC.md: add scripts/smoke/** ownership row + History entry

All 6 tests pass in ~1.4 s locally.

Key finding: pi requires a PTY to enter interactive mode and fire
session_start. Spawning without a TTY causes immediate exit. Workaround:
python3 pty.spawn() — allocates a PTY with no additional deps.
2026-05-15 11:18:20 +02:00
..
reference docs: reorganise — implementation plans + sync, archive spec to reference/ 2026-05-15 03:33:51 +02:00
NEXT-STEPS.md docs: resolve OQ-4 — T-1.0 worker = sonnet-4-6 2026-05-15 10:51:27 +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 chore: freeze IC-1..IC-4 interface contracts 2026-05-15 06:56:38 +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 feat(t-1.0a): smoke test harness MVP 2026-05-15 11:18:20 +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.