Use a workflow to close the gaps in docs/commercial-readiness.md. Create a branch named readiness/close-gaps from the current branch and do all of the work there. Phases and gates:

1. Blockers. One agent per gap whose metadata line says Severity: Blocker. Each agent reads only its own gap and closing brief, makes the change, runs that gap's Verify line, and commits with the gap ID first in the subject. Gate: every Blocker's Verify line passes and the project's test command is green.

2. 30-day. The same, one agent per gap whose metadata line says Severity: 30-day. Gate: the same.

3. Review. One agent re-reads every closed gap against its closing brief and reverts any change that does not match the brief. Gate: the reviewer lists each gap as closed or reverted.

4. Re-run. Run the commercial-readiness skill again and write the new report over docs/commercial-readiness.md, so closed gaps move to the Closed table. Gate: zero Blockers remain.

5. Pull request. Open a pull request against the branch I started from, with the Closed table and the reverted list in the description.

Rules for every agent: no deploys, no database migrations, no billing or payment commands, and no new paid service without naming its monthly cost in the pull request. Gaps marked Later stay open. Keep every gap ID unchanged.
