The ORCH-01 one-command measurement pipeline.
Sequences the entire "run a round" interaction in the exact order:
next-round -> assets.build -> capture -> propose -> verify -> seal-round -> digestThis task is a thin orchestrator: it reimplements zero ratchet logic, it only
sequences System.cmd calls through a swappable Runner behaviour (twinning
mix accrue_admin.assets.build's Runner/ShellRunner idiom). It:
- reads the round number and final convergence status from the two marker
files
phase-ratchet-ledger.mjswrites (.round-next/.round-status) — it never re-derives the round number or the convergence status itself. - resolves
--slice NAMEby readinge2e/baseline-manifest.js'sSLICESmap DIRECTLY (via a capturednode -ecall) — the surface names live only in that JS single-source-of-truth, never as a hardcoded Elixir copy. - ALWAYS renders the digest before deciding whether to raise, so a maintainer gets a rendered digest even on the 6-round cap-reached escalation.
Examples
# Full configured surface set (unscoped)
mix accrue_admin.ui.round
# A named slice (surfaces read from baseline-manifest.js's SLICES)
mix accrue_admin.ui.round --slice foundation
# An explicit surface list (no slice-map lookup)
mix accrue_admin.ui.round --surface dashboard,subscriptions--slice and --surface are mutually exclusive.