Environment guards now exit 69 rather than 1, so a caller can tell a suite
that could not start from one that ran and failed. The first toj test sweep
reported "3 repositories failed" and none of the three had executed a test —
two could not find go, one had no venv. That points the reader at the tests
when the fault is in the environment.
Only the environment guards change. A gitleaks finding, a failed test run and
a vulncheck hit still exit 1, because those did run and did fail.
Co-Authored-By: Claude <noreply@anthropic.com>
The suite reported 26 passed and 17 failed, which reads as broken tests and
was actually a missing build step. *.freezed.dart and lib/**/*.g.dart are
gitignored, so a fresh tree has none of them and most of the suite fails to
compile rather than to assert. After running build_runner the same suite is
452 passed, unchanged.
setup now runs pub get then generate, and generate exists on its own for after
a model change. test guards on a known generated file and says which command
fixes it, because "cannot compile" and "assertion failed" are different
problems and the runner presents them identically.
Co-Authored-By: Claude <noreply@anthropic.com>
Every repo gets one at the root: help, plus test and lint where those exist.
The point is that a target name means the same thing in every repo, so an
agent or a person can act without reading the repo first.
Paths resolve here rather than in callers (D-10). python3 on this host is 3.8
and cannot parse these sources, and a bare pytest or ruff resolves only in a
login shell — so both are named explicitly through the venv, and a missing
venv fails with the command to fix it rather than a bare no-such-file.
Co-Authored-By: Claude <noreply@anthropic.com>
jpmschweitzerandClaude