[fullsend-ai-coder]

Summary

Repins the seven image: lines under harness/ from the fullsend v0.52.0-rc.1 builds to the v0.53.0-rc.1 multi-arch index digests, so the v0.53.0 agents tag ships with current images. The image sources did not change in this release; only the build revision differs. This PR changes only the digest and keeps the @sha256: index form.

Image	Harness files	New digest
ghcr.io/fullsend-ai/fullsend-sandbox	prioritize.yaml, retro.yaml, scribe.yaml, triage.yaml	sha256:c0fe76a6e59dbdf77871ee7a8caa98f784ec163320b49f7ee7160f5f58cbd60e
ghcr.io/fullsend-ai/fullsend-code	code.yaml, fix.yaml, review.yaml	sha256:1f5b5d40a6ee3a5a9e51ff6d1e602c9ff71571aa5f6f14913cc53153348caff9

Verification

• In the GitHub packages API, both digests are the package versions tagged 0.53.0-rc.1 and 25811c9. The fullsend v0.53.0-rc.1 annotated tag points at commit 25811c9a815e2c27d397d41e45c59819b1302f54.
• grep -rn 'image:.*fullsend-\(sandbox\|code\)' harness/ prints exactly the 7 lines, all with the new digests. The old digests appear nowhere else in the repo.

Testing

• pre-commit could not fetch its remote hook repos in the sandbox (TLS verification failure). I ran the applicable hooks directly and they passed: the pre-commit-hooks 6.0.0 file checks, lint-agent-docs and lint-release-cases. gitleaks ran through scan-secrets and passed.
• skillsaw 0.18.0 --strict (make lint): passed.
• scripts/harness-jira-test.sh and the harness/triggertest Go tests: passed. make cannot spawn /bin/sh in the sandbox, so the full script-test suite was not run.

🤖 Generated with Claude Code

---

Closes #1852

Post-script verification

• Branch is not main/master (agent/1852-repin-v0-53-0-rc-1-images)
• Secret scan passed (gitleaks — 2bde087e7b90e6078ce3afdb373473e606914771..HEAD)
• PR body secret scan passed (gitleaks — no-git)
• Final PR description secret scan passed (gitleaks — no-git)

[fullsend-ai-review]

🤖 Review · ⚠️ Cancelled · Ended 5:31 PM UTC

Commit: c1424f6 · View workflow run →

Automated review did not complete for this commit. Check the latest review status before merging. If no review is queued or running, comment /fs-review to retry.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 5:32 PM UTC · Completed 5:38 PM UTC

Commit: c1424f6 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $0.64

[fullsend-ai-review]

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine bot-authored repin of seven harness image digests with exact issue scope match, moderated to score 2 due to protected harness paths and high churn in touched files.

[fullsend-ai-review]

Review

Findings

Medium

• [protected-path] harness/code.yaml, harness/fix.yaml, harness/prioritize.yaml, harness/retro.yaml, harness/review.yaml, harness/scribe.yaml, harness/triage.yaml — This PR modifies governance/infrastructure files under the protected harness/ path (seven image: digest lines). The PR links Repin fleet harness images to the v0.53.0-rc.1 release builds #1852 and explains the rationale, and the diff matches the issue exactly (digest-only, @sha256: form kept, correct image-to-file mapping). Human approval is always required for protected-path changes, regardless of context.

[waynesun09]

Release repin for v0.53.0-rc.1, verified: exactly the 7 harness image lines, both digests are the multi-arch index digests of the 0.53.0-rc.1 tags (revision 25811c9a8), functional tests green for all agents.