All issues

Smaller findings from the five user tests: lint offline, status precedence, snapshot silence, and friends

#43

· jordonpeterson opened

on Aug 17, 2026

The repo owner receiving a rollout has no veto, and no way to attribute what turned their CI red

#42

· jordonpeterson opened

on Aug 17, 2026

--summary-out puts skip reasons in the `proven` column

#41

· jordonpeterson opened

on Aug 17, 2026

verify shouts INVARIANT VIOLATED when the user simply passed too few --scope flags

#40

· jordonpeterson opened

on Aug 17, 2026

A CODEOWNERS symlinked to a file inside the repo is written through and claimed proven, while snapshot and audit see no ownership at all

#39

· jordonpeterson opened

on Aug 17, 2026

declare yields divergent ownership across a fleet, and the fleet-level consequence is undocumented

#38

· jordonpeterson opened

on Aug 17, 2026

docs/FLEET.md's resumable script retires exception repos permanently

#37

· jordonpeterson opened

on Aug 17, 2026

An invalid --on-empty value exits 0 or 2, never 3 — unlike its policy-file twin

#36

· jordonpeterson opened

on Aug 17, 2026

The R-8 refusal hands the operator a copy-pasteable instruction into an unguarded destructive run

#35

· jordonpeterson opened

on Aug 17, 2026

--repo "" silently targets the working directory and writes to it

#34

· jordonpeterson opened

on Aug 17, 2026

The stale-comment warning is gated on the run having changed something, so it is silent in the repos where it is the only signal

#33

· jordonpeterson opened

on Aug 17, 2026

sync never reports that owners LOST access — the artifact a fleet collects cannot distinguish co-owning from displacing

#32

· jordonpeterson opened

on Aug 17, 2026