coxswain 0.35.0

0.35.0

Cut on 2026-10-06. Status: beta. Lands no longer drop work: a phase land includes every approved task of the
phase or stops and says which one is missing, and a quarantine raised while merging a phase reaches the store. A
land that turns main red is reverted and its initiative quarantined. Each release now proves a clean install and an
upgrade from the tap before the tap pull request merges (coxswain #248, coxswain #249, coxswain #251), and a cut
pushes a notification when one is configured (coxswain #252).

Lands that never drop work. A phase land gathers every task approved for the phase, from this run or an
earlier one, and refuses to squash a phase branch that is missing one; a task is marked done only once its commit
is on main. Every quarantine in an epic run reaches the store, a conflicting phase merge included. A task approved
and then quarantined for its code or its ticket no longer blocks its own relaunch. A timed-out post-land smoke
check is inconclusive rather than a red main.

A red main is reverted. After a land, the chair watches main's checks; when they fail, it opens a revert pull
request for that land and quarantines the initiative, and two reverts in a row stop its relaunches.

towpath. The runs pane shows the project as its own column, the queue groups by project, towpath --version and cox --version
print their versions without starting a screen, and the spend detail charts the real week and a rolling five-hour
window.

Started, not yet wired. The Forgejo forge client and its operations are on main and selectable with
forge: forgejo; detecting a Forgejo origin automatically lands in 0.36. The notifier's events and cards are on
main; the chair loop starts sending them in 0.36. The chair's ticket widening has its rules and ticket text but
not its handoff wiring. The release tool can write a towpath download into the formula, and the tap step starts
passing it in 0.36.

Upgrading from 0.34.0. Nothing migrates and the store schema is unchanged. Restart the chair loop to pick up
the new land and revert rules.

coxswain-cartridges

• The workstore knows the quarantined state (cartridges #184).

coxswain-dash

• Each row names its project and the queue groups by project (dash #94, dash #95, dash #97).
• towpath --version prints its version and exits before any terminal setup (dash #96).
• The runs pane shows the project as its own column under a PROJECT header, and keeps room for the widest status
  chip (dash #98).

coxswain-graphs

• Every quarantine in an epic run reaches the store, a conflicting phase merge included (graphs #702).
• A decompose that splits an interface across repositories emits a shared contract task, and a lint rule checks
  it (graphs #701, graphs #703).
• A landing check can carry its own timeout (graphs #705).

coxswain-tools

• A phase land gathers every approved task of the phase and marks a task done only once it is merged
  (tools #1454, tools #1457).
• A land that turns main red is reverted and its initiative quarantined (tools #1445, tools #1450, tools #1452).
• A code or ticket quarantine supersedes a task's earlier approval (tools #1451); a timed-out post-land smoke is
  inconclusive (tools #1449); a dry-run tick makes no host probes or fetches (tools #1453).
• An intake whose decompose wrote nothing twice is held for the chair (tools #1447); a phase land rebuilds its own
  leftover local pr branch instead of refusing every tick (tools #1458).
• Route reads the unindented block lists the store's export writes (tools #1442); usage reads every run's start
  time in one query, so cox route context takes about 2 s (tools #1440).
• cox --version prints its version (tools #1443); the feed names each row's project (tools #1446); the spend
  detail charts the real week and a rolling five-hour window (tools #1441).
• The Forgejo forge client and operations (tools #1444, tools #1448), the notifier's dispatch, events and cards
  (tools #1439, tools #1455) and the ticket-widening rules (tools #1456), not yet wired.

coxswain (umbrella)

• Each release proves a clean install and an upgrade from the tap before the tap merges, and the release docs
  name the proof (coxswain #248, coxswain #249, coxswain #251).
• A release cut pushes a notification when a channel is configured (coxswain #252).
• The release tool can write the towpath download into the formula (coxswain #250).