Beagle SCM

CI-004: v button — run the project's default build+test as a bg job

Local one-keystroke CI: the pager's v button detects the project's conventional build+test entry point ("default stuff": ./ci.sh, ./scripts/ci.sh, cmake+ninja+ctest, ./configure && make && make test, and the per-language equivalents), runs it as a detached background job in the worktree, and puts the verdict into the per-repo cache. Separate from the qemu runner fleet (CI-001/CI-003) — this is the local leg; the fleet can later reuse the same detector script inside its VMs.

Input

Context

• CI-001 covers remote per-commit runners; nothing runs the build/tests locally from the pager today — the user shells out by hand.
• Cache model updated by STATUS-019: the shared cache is now a per-dir REV TREE storing no values — the CI verdict is a CONSUMER memo keyed by the rev(wtDir) it ran at, so the first edit after the run stales it automatically, same property as the old bucket drop.
• RULING gritzko 2026-08-04: ci MUST BE A VIEW — a views/-tree read-only verb like status/log/todo (Views is the open category; only the mutation basis is closed). The ∞ click mints the normal view spell, the pager pushes the ci view like any other: it starts or attaches to the run and renders the log tail (TODOs 7-9). The _pagerSpell reserved-word interception built on 2026-08-04 is WRONG and must be removed — no pager-local dispatch, no special case. The extension-script entry (jab ci.js) stays for the CLI and the CI-001 fleet.

Goals

• v in the pager kicks off the detected default build+test for the current worktree as a background job; the pager stays interactive.
• Ruling gritzko 2026-08-04: the TODO BOARD grows a CI BUTTON per wt-having row — face [ ∞] (2-cell, frame conventions of TODO-005), tone #5883a7 (a new view/theme.js BTN slot; the ci name is taken by the commit ✓ — pick a fresh name, e.g. run).
• Placement, gritzko's lean: the ∞ goes at the END of the FILE panel (where the ✓ sits today) and the post ✓ MOVES to the END of the COMMIT panel — staging surface ends in "test it", history surface ends in "commit it"; frame widths shift 16/10 → 16/13.
• The button's click runs the CI-004 runner on the row's wt; while a job runs the face reads in-progress, and the landed verdict tints the button green/red off the consumer memo until rev(wtDir) moves.
• Ruling gritzko 2026-08-04: starting a run must SHOW the output, not just the badge — a CI LOG VIEW over the run's log file: render the LAST 4 KB, positioned at the END; r refreshes (re-reads the file, stays at the end while the job appends). The log already lands in a file, so the view is a tail over it, no second capture path.
• On exit the result — green/red, exit code, log path — lands in the per-repo cache so status/pager surface it until the tree changes.
• Detection ladder, first hit in the worktree root wins:
  1. ./ci.sh
  2. ./scripts/ci.sh
  3. CMakeLists.txt → cmake + ninja + ctest -j16
  4. ./configure && make && make test
  5. Makefile → make && make test
  6. Cargo.toml → cargo test; go.mod → go test ./...; package.json → npm test; pyproject.toml/setup.py → pytest

Constraints

• stdout+stderr captured to a log file; the cache row carries the log path, never the log body.
• No hand-rolled URI/path composition; resolution via the standard library (resolve_hash.js), paths via the worktree root only.
• The runner is arg-blind like any pager action: it acts on the current context worktree, no per-invocation configuration.

WIP

Design decisions

• One shared detector script (extension), so the CI-001 fleet runs the exact same "default stuff" inside its VMs later — no fleet-only logic.
• Result is cache-resident only: a stale verdict silently disappears with its bucket; no persisted CI history on this leg (that is the fleet's job).

TODOs

• 1. Detector script in be/: probe the ladder, print the chosen command line; exit distinct on "nothing detected".
• 2. Background execution: detached spawn in the worktree, log capture to a file, completion hook feeding the cache row.
• 3. Cache row shape: green/red, exit code, log path, keyed under the repo path bucket.
• 4. Pager v keybinding invoking the runner for the current context worktree; re-press while running reports "in progress".
• 5. Surface the verdict: status/pager banner reads the cache row.
• 6. Board button (ruling 2026-08-04): [ ∞] #5883a7 at the FILE panel's end, the post ✓ moved to the COMMIT panel's end; wire the click to the runner, the face to the verdict memo.
• 7. The ci VIEW (ruling 2026-08-04, gritzko's words): it FORKS whatever command (the detection ladder; attach if one already runs), REDIRECTS output to a file, and the view TRACKS THE TAIL of that file, tail capped at 4 KB, positioned at the end; r re-reads and re-tails.
• 8. A GENERAL per-view mark "refresh each ~1 s" that bro honors for the topmost view — the ci view sets it while the job runs; OTHER views will use the same mark later, so it is a pager mechanism, not ci code.
• 9. Verdict FOOTER under the tail — ── PASS rc=0 ── / ── FAIL rc=N ── in the verdict tone, ⋯ running mid-run; render-only, never written to the log file. The hunk BANNER stays the command line as-is.
• 10. Remove the _pagerSpell reserved-word layer; the ∞ mints the plain view spell and the pager pushes the ci view normally.
• 11. Verdict on the BOARD (ruling gritzko 2026-08-04): the ∞ button's COLOUR carries the last run's verdict — greyish for unknown/never-ran, #e1351e fail, #1fe033 ok. The status is REMEMBERED per wt in a {wt: status} map the runner writes at settle (beside the logs, outside every watched tree, so no self-staling rev bump); the board reads the map cold — no watcher needed to show the last verdict.

Blockers and bummers

• None known; independent of GIT-022 and the qemu track.
• TODO #6 edits views/todo/todo.js frames — land AFTER the in-flight TODO-006 r3 rework to avoid a two-writer collision on the file.

Outcome

r2, the ci VIEW (supersedes r1's reserved-word wiring):

• views/ci/ci.js — a views/-tree read-only verb: bare ci (context tree), ci //WT (the board's form), ci <path>; all ride shared/ci.js's ONE runner. The view forks-or-ATTACHES (CI.ensure — a fresh verdict replays, r re-runs), tails the log file (4 KB cap, positioned at the END), renders the ── PASS rc=0 ──/── FAIL rc=N ── footer in the verdict tones, ⋯ running mid-run; the banner stays the command line.
• shared/viewmark.js — the GENERIC per-view ~1 s tick (tick/end/take): only the topmost marked view re-runs, scroll pins to the last page until a scroll key, unmarked views never wake. loop.js also records the initial view's launch invocation (r/tick used to re-derive a spell from the banner — fatal for ci, whose banner is a command).
• TODO 11: settle writes the {wt: ok|fail} map to $TMP/be-ci/verdicts (temp+rename, outside every watched tree); the ∞ reads it COLD — greyish never-ran, #e1351e fail, #1fe033 ok (theme BTN_RUN; #5883a7 stays the in-flight tone) — and the verdict survives a fresh pager process.
• The _pagerSpell layer is DELETED (both call sites); the v key, status-bar badge, board layout, detection ladder, spawnFds capture and the rev-keyed memo survive.
• Suite 352/352 (orchestrator-verified); the pty case pins 17 legs (push-on-click, end-positioned tail, keyless growth, settle footer, tick stop, cold verdict colours, footer never on disk), three red-verifies.
• Smells parked: a killed job reads as ⋯ running forever (log without .rc); $TMP/be-ci has no reaper; the key wait is the pre-existing 100 ms VTIME spin; Enter on the ci banner row derives nonsense (refresh fixed, that path not); BTN_FACE_ASCII/PANELW dead wiring.
• Suggested commit: CI-004: ci as a view — log tail, 1s view tick, per-wt verdict map