Repository guards
This codebase has no CI. What protects it instead is a set of small, fast checks wired into paths nobody can skip: the prebuild, the gate, the deploy build, and the git pre-push hook. Every guard below exists because something broke once. Read the full reference or the tutorial on writing one.
Loading the guard registry.
Adding a guard
A guard that is not wired into an unavoidable path protects nothing, and a guard nobody has proven
still catches anything protects nothing either. Write the checker, give it an npm script, register it
in data/guards.json with the violation it must reject, and wire it into a stage.
npm run audit:guards tells you if the registry and the chains disagree;
npm run prove:guards runs each guard against its declared violation and tells you whether
it still fires.