pi-remote-control

Commit Graph

Author	SHA1	Message	Date
jay	b2b82c82ce	docs: incorporate Phase 0.5 verdict (Path B), prep Phase 1 - PHASE-1-sidecar.md - Note at top: streaming primitive decided as tmux control mode - Architecture sketch: tmux/pipe.ts → tmux/control.ts - T-1.1 description updated to reference control mode + spike-cc.ts - Risks R4 (parser throughput) and R5 (tmux ≥2.5 required) added - SYNC.md - File ownership map: tmux/** note about control mode - Frozen Interface Contracts table: added Status + Frozen-at columns so contracts can be tracked from draft → frozen with date stamp - Freeze protocol prose - NEW: NEXT-STEPS.md — single resume pointer for the next session. Lists what's done, what's draft, the orchestrator todo list (freeze contracts → dispatch T-1.0 → plan fan-out), open questions, and things explicitly NOT to do tomorrow. - README.md: NEXT-STEPS.md added at top of the docs index.	2026-05-15 04:48:20 +02:00
jay	307417b392	docs: add Phase 0.5 — spike tmux control mode Phase 0 found that tmux pipe-pane is unreliable across alternate-screen transitions. Before Phase 1 commits to a streaming primitive, a short follow-up spike evaluates tmux control mode (`tmux -CC`) as an alternative to pipe-pane + watchdog. Verdict drives T-1.1 design.	2026-05-15 04:06:25 +02:00
jay	f6cbf17078	docs: reorganise — implementation plans + sync, archive spec to reference/ - docs/ now holds only implementation drivers: - PHASE-0-spike-stream.md (single agent, ~1 day PoC) - PHASE-1-sidecar.md (multi-agent, sidecar production-ready) - PHASE-2-ios-mvp.md (multi-agent, iOS app MVP) - PHASE-3-ios-augmentation.md (multi-agent, iOS polish) - SYNC.md (live coordination: claims, ownership, CCRs) - README.md (folder guide) - docs/reference/ holds background: - SPEC-ios-app.md (final v3 spec) - EXTENSION-API-AUDIT.md (audit result) - SPEC-ios-app-review-v1.md (archived review thread) - ARCHITECTURE.md (original extension architecture) - README.md (folder guide) Each phase plan defines: goal, acceptance criteria, file layout, explicit task table with parallelisable tasks, interface contracts, branching strategy, risks, exit criteria. SYNC.md provides the multi-agent coordination protocol: active claims table, file ownership map, frozen contracts, and contract change requests (CCR) workflow.	2026-05-15 03:33:51 +02:00

Author

SHA1

Message

Date

jay

b2b82c82ce

docs: incorporate Phase 0.5 verdict (Path B), prep Phase 1

- PHASE-1-sidecar.md
  - Note at top: streaming primitive decided as tmux control mode
  - Architecture sketch: tmux/pipe.ts → tmux/control.ts
  - T-1.1 description updated to reference control mode + spike-cc.ts
  - Risks R4 (parser throughput) and R5 (tmux ≥2.5 required) added

- SYNC.md
  - File ownership map: tmux/** note about control mode
  - Frozen Interface Contracts table: added Status + Frozen-at columns
    so contracts can be tracked from draft → frozen with date stamp
  - Freeze protocol prose

- NEW: NEXT-STEPS.md — single resume pointer for the next session.
  Lists what's done, what's draft, the orchestrator todo list (freeze
  contracts → dispatch T-1.0 → plan fan-out), open questions, and
  things explicitly NOT to do tomorrow.

- README.md: NEXT-STEPS.md added at top of the docs index.

2026-05-15 04:48:20 +02:00

jay

307417b392

docs: add Phase 0.5 — spike tmux control mode

Phase 0 found that tmux pipe-pane is unreliable across alternate-screen
transitions. Before Phase 1 commits to a streaming primitive, a short
follow-up spike evaluates tmux control mode (`tmux -CC`) as an
alternative to pipe-pane + watchdog. Verdict drives T-1.1 design.

2026-05-15 04:06:25 +02:00

jay

f6cbf17078

docs: reorganise — implementation plans + sync, archive spec to reference/

- docs/ now holds only implementation drivers:
  - PHASE-0-spike-stream.md (single agent, ~1 day PoC)
  - PHASE-1-sidecar.md (multi-agent, sidecar production-ready)
  - PHASE-2-ios-mvp.md (multi-agent, iOS app MVP)
  - PHASE-3-ios-augmentation.md (multi-agent, iOS polish)
  - SYNC.md (live coordination: claims, ownership, CCRs)
  - README.md (folder guide)

- docs/reference/ holds background:
  - SPEC-ios-app.md (final v3 spec)
  - EXTENSION-API-AUDIT.md (audit result)
  - SPEC-ios-app-review-v1.md (archived review thread)
  - ARCHITECTURE.md (original extension architecture)
  - README.md (folder guide)

Each phase plan defines: goal, acceptance criteria, file layout,
explicit task table with parallelisable tasks, interface contracts,
branching strategy, risks, exit criteria.

SYNC.md provides the multi-agent coordination protocol: active claims
table, file ownership map, frozen contracts, and contract change
requests (CCR) workflow.

2026-05-15 03:33:51 +02:00

3 Commits