Static guards instead of endless tests

More than 120 check:* scripts hold module boundaries, contracts and documentation in CI. A module naming another module, a table without its module’s prefix, or a document pointing at a file that does not exist is refused before merge.

A pragmatic testing doctrine

Only the business-critical paths get Pest tests: payment, sign-in and the panel’s daily screens. Whatever a static guard holds needs no test of its own.

Why it matters for agents

An agent never gets tired, but it does not know a rule nobody wrote down. A guard is that rule, in a language CI understands.