Wrap overlay text instead of cutting it; the project check is a regression check, renamed check.sh; concrete Headroom steps; Mouse-1 measured

docs/NEXT.md

@@ -104,9 +104,21 @@ step; a switch is only worth adding after one agent has been run both ways and m
 
 ## 9. MOUSE-1
 
-Corrected: Mouse-1 is a hosted API, not software to install. `MOUSE_API_KEY` is present; what is
-missing is a client call from our side. The old project's policy stands: triage only, never a
-gate, never a permit — it could order `Board>needs`, never decide a merge.
+It is a hosted API, not software: `POST https://api.mouse.dev/v1/decisions` with the key already
+in the environment. Measured facts are in `docs/MOUSE-1-NOTES.md` and summarised in
+`docs/PLAN-INTERFACE.md`: cold start of minutes, ~490 ms warm, stable answers at high
+confidence, and four proven uses — failure routing first among them.
+
+The one place it would earn its keep here: a failed run in `Agents>agents` offers `f`, which
+asks "what does this failure need" with four options and records the answer, the confidence and
+the options on the task. A person still decides, and it never decides a merge.
+
+## Done: Headroom
+
+A provider entry in `~/.pi/agent/settings.json` pointing at `http://192.168.20.13:8787/v1`, and
+an agent's model set to `headroom/<model>`. Per agent, because the model is per agent; per
+project is not possible. The exact steps and the one unknown to measure are in
+`docs/PLAN-INTERFACE.md`.
 
 ## Unproven, and worth a test