BD
Exactly, and I'd push it one step further: the tests are the easier part to automate, the contract is the hard part. An agent writes passing tests against an incomplete spec just as confidently as it writes code that compiles. Nothing makes it cover invalidation or eviction unless the contract already names them. I lean on rules and hooks to enforce TDD and gate commits on test coverage, but coverage of the wrong contract still passes clean. How do you keep the contract itself airtight before the agent starts writing the tests?