Back to feed

mirror-smoke-1774018845

sledtools/pika · branch #9 · target master · updated 2026-03-20 15:02:02

branch: merged tutorial: ready ci: success

CI

Run #12 · success · 0 lane(s)

head 5da8fdda672247932a46e9511331014fec15d822 · queued 2026-03-20 15:01:33

finished 2026-03-20 15:01:33

No lanes were selected for this branch head.

merge commit b8ab90193931e84e5477da7e5733d8587d5aa289

Summary

This branch removes the living planning document todos/pikaci-apple-remote-plan.md, a 342-line specification that defined the phased roadmap for running Apple-host CI (pikaci) on owned hardware via SSH/Tailscale, with GitHub kept as a thin outer trigger. The deleted document covered eight phases — from scope lock and safety gates, through a thin remote wrapper, GitHub trigger wiring, advisory iOS simulator coverage, fixture-backed E2E, cleanup/retention on a 250 GB host, isolation re-evaluation (Tart), and finally reducing GitHub to a replaceable shell. Removing this file signals either that the plan has been fully absorbed into implementation, superseded by a different strategy, or intentionally cleaned up as part of a repository hygiene pass on the mirror-smoke-1774018845 branch.

Tutorial Steps

Delete the Apple remote CI planning document

Intent: Remove the canonical living plan for Apple-host `pikaci` execution from the repository. This document governed the phased rollout of remote Apple CI — covering architecture decisions, lane ordering, safety constraints, network isolation requirements, and a planner/implementer contract. Its deletion cleans the `todos/` directory of this specification.

Affected files: todos/pikaci-apple-remote-plan.md

Evidence 
@@ -1,342 +0,0 @@
-## Spec
-
-This is the canonical living plan for Apple-host `pikaci` execution on owned hardware, with GitHub kept as a temporary outer trigger rather than the long-term CI platform.
@@ -1,342 +0,0 @@
-## Current Phase (2026-03-15)
-
-1. The current target architecture should be:
-   - GitHub-hosted Linux runner as temporary trigger only
-   - checked-in Apple remote wrapper script as the execution entrypoint
-   - Mac mini or rented Apple host does the real work over SSH/Tailscale
-   - the Apple host is not treated as a self-hosted GitHub runner
@@ -1,342 +0,0 @@
-## Phase 1: Thin Apple Remote Wrapper
-...
-## Phase 7: Reduce GitHub To A Replaceable Shell

The entire file todos/pikaci-apple-remote-plan.md is deleted (342 lines, deleted file mode 100644).

What the document contained

The plan defined:

  1. Architecture — GitHub-hosted Linux runner as a temporary trigger; a checked-in Apple remote wrapper script as the real entrypoint; Mac mini or rented Apple host doing actual work over SSH/Tailscale; the Apple host explicitly not a self-hosted GitHub runner.
  2. Lane ordering — Blocking: pre-merge-pikachat-apple-followup; advisory: ios-ui-test; later advisory: ios-ui-e2e-local; Tart intentionally deferred.
  3. Safety constraints — No reliance on same-LAN trust; network separation or relocation required before treating the Mac as an active CI host; preference for checked-in CLI/script contracts over GitHub YAML as source of truth.
  4. Eight phases — Phase 0 (scope lock & safety gate) through Phase 7 (reduce GitHub to a replaceable shell), each with explicit scope, acceptance criteria, review focus, and land-to-master guidance.
  5. Planner/implementer contract — A coordination model where a planning agent maintains the document and an implementation agent takes one narrow slice at a time, with review cycles after each slice.

Why this matters

Removing this document means the branch no longer carries the planning artifact. Downstream consumers that referenced this file for architectural guidance, lane ordering, or safety requirements will need to consult whatever has replaced it — whether that is implemented code, a different planning document, or institutional knowledge.

Key deleted sections at a glance

SectionPurpose
Spec / Working assumptionsArchitectural principles and constraints
Current Phase (2026-03-15)Snapshot of active decisions and policy biases
Target OutcomeDefinition of the first steady state
Phases 0–7Incremental delivery plan with acceptance criteria
Suggested First Implementation SliceConcrete next-action guidance
Review NotesInitial review state and identified risks

Diff