Release v0.6.0 · morzecrew/torve

Changelog

An attempt that writes ignored files outside the toolchain caches gets an
ignored-writes shadow result naming them, in its record and in torve why. It changes
no verdict.
An opt-in verifier, verify.enabled in the runner configuration, off by default. A
feature or fix phase that touches source gets a verify task first: an agent on the
verify seat writes the phase's tests from its decision rows. The implement task must
pass them and cannot edit them.
A verifier can also write held-out tests that never enter the implementer's sandbox.
The held-out gate runs them in the gate checkout and reports only the failing row and
message. When the document's last phase lands, the lane commits them to its branch.
The verify-tests gate rejects a verify candidate whose tests do not collect, leave a
settled decision row without a test citing it, or already pass before the
implementation exists.
torve eval --task <id> --verifier replays a task with and without its verifier, and
--oracle records which arm let a known bug through.
torve doctor fails when the verifier is on and its seat runs the executor seat's own
model.
torve init --starter writes a verify agent profile beside the implement, revert and
review ones.

Every gate battery judges a standalone checkout of what the attempt would commit,
inside a sandbox. Ignored files, the attempt's .venv among them, no longer reach a
gate, so a gate that leaned on one the attempt built now fails.

A gate whose output is not valid UTF-8 reports its own verdict when it runs in a
sandbox. It was recorded as an infrastructure error, with its output lost.
A shell gate that runs git, such as coverage-delta's diff-cover --compare-branch,
judges the candidate in the sandbox. The battery's checkout is a repository of its own
whose history reaches the attempt's base.
A run whose attempt raises, such as a seat image that does not start, ends escalated
instead of running. Requeueing the escalation now dispatches the task again, without a
torve reap first.
A served night records on the board a candidate the lane escalates, such as one red
again at the same base and head. The board no longer shows it as ready while the
night waits on it, and torve manager resolve can answer it.

The lane's re-gate of a rebased candidate and the whole-document battery run their
shell gates in a gates sandbox under the default executor seat's image. They ran the
candidate's tests on the host, in the manager's environment.