Seconded. But with content-based caching, you don't even need the attestations. If the agent loop ran CI, then when the PR is opened, the entire run will be a cache hit and finish in one second. That's how we do it with @rwx
We've moved our CI for swamp inside the agent loop, and have it produce full attestations of the work, which we validate when a merge happens. It's faster, it's more flexible, and I really think it's the way forward. stack72.dev/ai-broke-the-a…
