paperclip: ops review loop and end-to-end smoke test #65

New issue

Open

opened 2026-10-25 12:06:21 +00:00 by lab · 0 comments

lab commented

2026-10-25 12:06:21 +00:00

Owner

Context

Agent-to-agent evaluation happens at the PR, because Paperclip approvals are
human-only.

Steps

Add a lxc/paperclip/agents/review.md playbook for ops: read the diff,
check for secrets and :latest tags, check the deploy agent's claimed
verification, then approve or request changes.
Give deploy a branch naming convention (paperclip/<issue>-<slug>) and a
PR body template with a verification section.
Create one throwaway issue (docs typo) and let both agents work it end to
end.

Done when

deploy opens a PR with a filled-in verification section
ops leaves an approving PR review
a human merges and the existing Forgejo workflow applies it
neither agent has merge rights

## Context Agent-to-agent evaluation happens at the PR, because Paperclip approvals are human-only. ## Steps 1. Add a `lxc/paperclip/agents/review.md` playbook for `ops`: read the diff, check for secrets and `:latest` tags, check the deploy agent's claimed verification, then approve or request changes. 2. Give `deploy` a branch naming convention (`paperclip/<issue>-<slug>`) and a PR body template with a verification section. 3. Create one throwaway issue (docs typo) and let both agents work it end to end. ## Done when - `deploy` opens a PR with a filled-in verification section - `ops` leaves an approving PR review - a human merges and the existing Forgejo workflow applies it - neither agent has merge rights