cubs-halogen-probe-1: campaign kit for the gpu-worker row (FRONT-12 bootstrap proof)

[mecattaf]

Tracks the dotfiles side of the 7-day Halogen Flash capability probe on the CUBS tree, run as a serial backlog of ~40-minute iterations admitted by the rewrite kernel on the gpu-worker row. PR: #402 (draft: cubs-iteration executable, build:CUBS-1..40 kit entries, hermetic probe, docs/local-ai/cubs-campaign.md, DECISIONS 2026-09-16, DEFERRED DF-CUBS-1..5).

The three orchestrator defaults (Tom may flip any)

1. Executor review routing. The campaign's cards say executor: review and repo: mecattaf/dotfiles, because the deployed lake floor (apps/worker/src/floor.ts:87-125) routes class execute to gpu-coordinator only; review is the class that lands on gpu-worker without a Worker redeploy. An execute member on gpu-worker is DF-CUBS-2.
2. Envelope-pass semantics. With no --evaluator-lock on the served kernel (DF-U-D13-2), every item that finishes inside its 2400 s lease closes pass on the lake regardless of exit code. The campaign's proof is the commit on campaign/cubs-halogen-probe-1/<id> + ~/.local/state/cubs-campaign/tasks/<id>/receipt.json + the usage line under <rewrite state>/uplink/usage/, never the lake verdict. The executable never fabricates a pass (a dead Halogen is an outage receipt, exit 69; a red gate is fail, exit 1; the fuse is exit 2).
3. Level 1. Armed with --level 1 (WIP cap 1): strictly serial, one of the 3N cells in flight; all items minted in ONE parallel(), no later await, services.tally-uplink.plan stays null (DF-U-D14-3).

The two operator acts left to Tom

1. The coordinator switch from the merged branch, so the kit with the 120 entries is live BEFORE the first proposal arrives (an unresolvable argv_ref is a KitError that ends the wake with the item left released, kit.mjs:56, uplink.mjs:616).
2. The non-dry arm: tally-plan-arm cubs-campaign.js --args … --level 1 --dry | jq '.plan.counts, .plan.items[].needs' first (expect needs: review, 3N items, pending: null), then non-dry with --endpoint https://tally-lake.thomasmecattaf.workers.dev and LAKE_TOKEN read from ~/.local/state/tally-rewrite/lake-token in the shell, never echoed.

Before either: ~/mecattaf/cubs-campaign must carry worklists/current.jsonl (the kit's stdin pointer names it), pi/models.json (provider halogen, model halogen-qwen3.8-flash-next, thinkingFormat "qwen", supportsReasoningEffort true) and the day-01 bundles; the executable exits 78 naming whichever is missing.

MEASURED today

• rendered kit 123 entries; tally-uplink-topology check rc 0; probe-cubs-iteration.sh PASS; one real env -i run of the built executable against live Halogen on a scratch repo: pass first try in 17 s, 4 tool calls, prompt 12337 / completion 405 / reasoning 74 tokens.
• nix flake check --offline --no-build is red on the untouched main today (a source.drv that cannot be built offline), which is why probe-FT-3-kit.sh K7 is red on both; pre-existing.

🤖 Generated with Claude Code