docs(#2880): add sandbox image topology section to AGENTS.md#2881
Conversation
Document which container images exist (fullsend-sandbox vs fullsend-code), which agent types use each, and their relative run frequencies. This gives the review agent discoverable context when reviewing CI infrastructure changes to action.yml or sandbox image configuration. The mapping is derived from the harness definitions in internal/scaffold/fullsend-repo/harness/*.yaml: - fullsend-sandbox: triage, prioritize, retro (high frequency) - fullsend-code: code, fix, review (lower frequency) Includes a "When reviewing CI changes" callout so agents consider blast radius when evaluating image optimization PRs. Note: pre-commit could not run (shellcheck download blocked by sandbox network policy). Manual verification required. Closes #2880
Site previewPreview: https://4a1a317e-site.fullsend-ai.workers.dev Commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
🤖 Finished Retro · ✅ Success · Started 7:00 AM UTC · Completed 7:09 AM UTC |
Retro: PR #2881 — docs(#2880): add sandbox image topology section to AGENTS.mdWorkflow quality: Good. This was a clean end-to-end autonomous workflow: the retro agent identified a knowledge gap from PR #2796, filed issue #2880, the code agent produced accurate documentation in one shot (29 lines to AGENTS.md), and human Key observation: review agent was not dispatchedThe review agent never ran on this PR. The dispatch logic calls This is already tracked as #2674 — "dispatch: ADR 0054 authorization gate blocks review dispatch for coder-bot PRs." No new proposal needed. Other observations (already tracked)
No new proposalsAll improvement opportunities identified are already covered by existing open issues. The workflow executed efficiently with good output quality. |
Document which container images exist (fullsend-sandbox vs fullsend-code), which agent types use each, and their relative run frequencies. This gives the review agent discoverable context when reviewing CI infrastructure changes to action.yml or sandbox image configuration.
The mapping is derived from the harness definitions in internal/scaffold/fullsend-repo/harness/*.yaml:
Includes a "When reviewing CI changes" callout so agents consider blast radius when evaluating image optimization PRs.
Note: pre-commit could not run (shellcheck download blocked by sandbox network policy). Manual verification required.
Closes #2880
Post-script verification
agent/2880-sandbox-image-topology-docs)603d68159336c07b35789beb00e45758950aaea5..HEAD)