What's next after v0.3

[addisdev]

v0.3.0 took the fleet from one Mac to several. Here is the work that is already tracked or waiting on something, as a starting point. Reply with what you would want next, or 👍 the replies you agree with.

Tracked and open to contributors

• Tests for the parts that only had indirect coverage: failure classification (Add unit tests for failure annotation classification #20), the workflow YAML parser (Add unit tests for the workflow YAML parser #82) and the capacity headroom gate (Add unit tests for the capacity headroom gate #83)
• The hook install suite in CI (Run the hook install suite in CI #21)
• A dead docs link in the cockpit release workflow (Fix the docs/cockpit.md path in the cockpit release workflow #84)

Built, waiting on a gate

• Signed, notarized Fleet Cockpit builds. The release workflow exists (cockpit-v* tags) and skips cleanly until Developer ID secrets are set. Until then, the cockpit builds from source; see Install and set up.
• Pre-warming runners before a burst. The forecast runs in shadow mode, and pre-warming stays off until it scores precision ≥ 0.70 and recall ≥ 0.50 over at least 20 windows (capacity design).

Out of scope

Intel Macs, Linux and Windows hosts, and cloud autoscaling. For cloud autoscaling, actions-runner-controller is the right tool.