Handover: history, plan, API measurements, checklist, open issues from the OMA attempt

README.md

@@ -0,0 +1,32 @@
+# Paperclip harness — start here
+
+This is a new project. Nothing here runs yet. It exists so the third attempt starts from
+a clean place, with the history of the first two attempts attached.
+
+Read these in order:
+
+1. `HANDOVER.md` — what we tried before, what worked, what failed, and why this is different.
+2. `docs/PLAN.md` — the plan: the four screens, the milestones, what is Paperclip's job and what is ours.
+3. `docs/PAPERCLIP-API-NOTES.md` — what we measured against your running Paperclip, with the endpoint and the response.
+4. `CHECKLIST.md` — the exact steps for the next session, in order, with boxes to tick.
+
+## The one-line version
+
+Paperclip already owns tasks, blockers, comments, approvals, runs, cost and git
+worktrees. We are building one small Go terminal program with four screens on top of it.
+Nothing else.
+
+## What you need installed (all present on .13 today)
+
+- Paperclip server running locally on `http://127.0.0.1:3100` (it is; 685 endpoints).
+- `PAPERCLIP_BOARD_KEY` in the environment — the **user** key. The terminal program uses
+  this one. An agent key cannot write outside a heartbeat run.
+- Go toolchain, for the terminal program.
+- Pi, which is already the worker adapter on your Paperclip agent.
+
+## Rules for this project
+
+- No interface work before a real task has run end to end.
+- Paperclip owns the facts. We never keep a second copy of a task, a blocker or a cost.
+- Every claim in a document names the command that showed it.
+- Nothing is copied from the old project except documents.