stado change

Invocation

stado change <COMMAND>

Purpose

The submit queue, one per repository: queue a commit to land on its main, run the queue, read and withdraw candidates

Required inputs and options

This command has no command-specific inputs or options.

Output and state effect

This command group selects one of the subcommands listed below; use its exact child invocation to perform an operation.

Refusals

Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.

Subcommands

submit — Queue a commit to land on its repository's main: the commit is written again on the remote main, checked with the product's declared gates, reviewed as its risk requires and pushed by `stado change run`. A commit that changes more lines than its product's catalog `submit.max_changed_lines` is refused here, to be split, and so is a high-risk one that names no `--defect`
run — Run one pass of the checkout's repository's queue, or, without a checkout, of every repository with a candidate waiting for a pass, each from the checkout its candidate was submitted from (the resident pass the installation declares as a host routine): carry every queued candidate, and every running one whose pass is gone (its repository's pass lock is free), in the queue's order (those `stado change prioritize` moved ahead, then oldest first), to landed, refused or repaired (its review before landing repaired it, or recorded no round over what its reviewer left: what the review left is queued at the tail). Exits 0 when every candidate reached a verdict; a candidate the pass could not judge (the remote or the fleet did not answer, Oko's admission did not answer or did not admit its gates, the harsh review could not be run) stays queued with what it waits on, and the pass exits non-zero with the cause. A pass under no agent session asks Oko's admission first as the fleet's daily build, then as each candidate's submitter
status — Read one candidate by its id or a unique prefix of it
list — List the candidates of the checkout's repository, or of every repository without one, in the queue's order: those moved ahead with `stado change prioritize` first, then oldest first
cancel — Withdraw a candidate: a queued one at once, a running one before its pass takes the next step. A landed, refused, repaired or cancelled candidate is refused
prioritize — Move a queued candidate ahead of every candidate not moved ahead (after those moved ahead before it), so the next pass takes it first; the reason, the session that moved it and when are kept beside it and shown by `status` and `list`. A candidate stacked on another that still waits and was not moved ahead is refused: move the one below first
review — Record a review round over a queued or running candidate by the agent session this command runs in, as its harness names it (`tama sessions self`, else the transcript `PI_SESSION_FILE` names); the session that submitted the candidate is refused, and so is a command no session runs. The round is over the commit the next pass lands (the candidate written again on `main` by the last pass, else its own commit) and that commit's tree: its findings and improvements, each a file holding a JSON array. At the review before landing, each reviewer's newest round over the same tree counts: any finding refuses the candidate naming it, rounds that all found nothing admit it. Tama's harsh review runs only when no round over the tree is recorded