Agent-Readiness

Make a repo ready for autonomous agent work by adding mechanical proof: boot scripts, smoke checks, CI/hooks, observable signals, and isolation where needed. Add the smallest useful layer first; stop once the repo is reliably verifiable.

Boundaries

• Existing code, diff, branch, or PR review is out of scope.
• Completed product changes need their own runtime proof pass.
• AGENTS.md, README.md, specs, or repo docs are documentation work unless they support readiness infrastructure.
• Mock-only tests, docs-only cleanup, and builder self-evaluation are not readiness proof.

The 7-Layer Stack