runward 0.42.3
What the tool prints, records and asks for now holds: a row counts as ratified only as currently written, and an agent may ratify under its own name, for a named person.
What changes
- Under the regulated tier (
"regulated": true), a decided row counts only when it was ratified as it is written today: rewritten since, it must be ratified again. runward ratify --agent <name> --for <person>lets an agent ratify under its own name, for the person accountable for it: never under a person’s name, never a row either of them proposed.- Around a red verdict, no message reads as green any more: the “Next” line names the check that said no.
- Four commands no longer write past what they were asked:
report -o, for one, replaces only a previous delivery report and refuses a path outside the project. - Six more commands answer in JSON (
--json) for an agent that reads them, and an error says which case it was. - The example (
init --example) is green as the package ships it: from 0.40.0 to 0.42.2, it was not.
Source
This note restates the section “0.42.3” of runward’s CHANGELOG, at the tag v0.42.3, and nothing else. The detail, and what it leaves out, is in the release notes on GitHub.