Task · GHC-0004

Fleet campaign: roll the justfile task surface out to every repo

Description

Parent tracking item for the fleet-wide justfile migration. This repo is the fleet hub, so the campaign is tracked here; the per-repo work lives on each repository’s own Migrate the repo task surface to just task.

Run artefacts

Shape

One Codex parent owns the whole wave as DESIGN+INTEGRATION on gpt-5.6-sol/high, and fans the implementation out one lane per repository as JUDGMENT+EXECUTION on gpt-5.6-terra at max reasoning effort. Lanes are deliberately given latitude to fix what they find rather than park on it.

The pool is ten child threads excluding the root, so ~39 lanes run as a rolling pool of ten, not all at once.

Scope, verified 2026-08-29

42 tasks were filed; the wave commissions fewer. 3 are already Done (TSO-0025, BMC-0169, BKP-0252), 2 are In Progress and are a resume rather than a restart (BMA-0070, MSS-0349), 37 are To Do.

Supersedes the wave labels

Every commissioned task carries a wave: label from the original ordering. Rob paused all other work so the fleet could run as one campaign, so the ordering is superseded and the goal says so. The hazard behind wave:3-last survives as a per-lane constraint in the goal rather than as an order.

Why the parent lives here

There was no parent task before this one. The campaign was coordinated only by wave labels spread across 42 boards, which is not a queryable state. This repo already holds the fleet’s shared workflows and the repo-settings audit, so it is where a fleet-level item belongs.

Acceptance Criteria

Definition of Done

View the source file on GitHub