M5a plan: run tasks 16 to 20 on titan's own Ornith

Titan serves ornith-1.5-35b-a3b itself, so OpenCode there uses
titan/ornith-1.5-35b-a3b. The harness's device checks still use straylight.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-09-25 16:41:44 -07:00
committed by kyle
co-authored by Claude Opus 5.5
parent c55cffe884
commit 1dca52118d
+5 -2
View File
@@ -111,8 +111,11 @@ the gate at its end state on its own.
```sh
git switch m5a
OPENCODE_MODEL=straylight/ornith-1.5-35b-a3b tools/run-plan.sh docs/plans/M5a
# the review's follow-ups:
OPENCODE_MODEL=straylight/ornith-1.5-35b-a3b tools/run-plan.sh docs/plans/M5a 16
# the review's follow-ups, on titan, which serves Ornith itself (127.0.0.1:8081):
OPENCODE_MODEL=titan/ornith-1.5-35b-a3b tools/run-plan.sh docs/plans/M5a 16
```
The model the implementer runs on is separate from the one the harness serves: `make
verify-device` and the device checks still use straylight's `llama-server`.
Keep the OpenCode TUI closed while it runs.