v0.7.0: manual verify fails a run that could read nothing

deploylog manual verify now fails a run that could not read a single claim. Update with npm i -g deploylog; 0.7.0 reached npm on 2026-09-26.

Changed

A run that reads claims and cannot read any of them exits 2 at every --fail-on except none. Before 0.7.0 it exited 0 under the default, drift.
This affects anyone who runs manual verify in CI or a git hook at the default, from 0.7.0 on. If a run that used to pass now exits 2, read the reasons it prints, or pass --fail-on none to report without failing.
The summary line prints vouched N: the claims the run read and stood behind. One unreadable claim among readable ones still exits 0 under drift; pass --fail-on any to fail on it.

Fixed

Claims that cite a second repository can now be read. Generating a chapter records the commit of the repository it read. Until a server fix on 2026-09-18, only the repository a run was in had a commit on record, so every claim citing another repository was unreadable. Regenerate a chapter that cites another repository to record its commit.
deploylog --version prints the installed version. 0.6.0 printed 0.5.0.
A key in .deploylog.yml that the CLI does not know is reported on stderr, with the closest real key when there is one, such as default_type. The file still loads.