chore(#1193): repin harness images to fullsend 0.42.0 digests

[fullsend-ai-coder]

Summary

• Repin all seven harness/*.yaml image digests from the previous release to the fullsend 0.42.0 release
• fullsend-code (code, fix, review) → sha256:623fc74588876062f12f40690ee759c6134ba516fabdd36e6dcfc4eeb9cd1d0b
• fullsend-sandbox (prioritize, retro, scribe, triage) → sha256:259605fea321353552fdefd3a6a55e8b5c260998dfc5a622ed143e41a429995a

Digest table

Image	Digest	Files
ghcr.io/fullsend-ai/fullsend-code:0.42.0	sha256:623fc74588876062f12f40690ee759c6134ba516fabdd36e6dcfc4eeb9cd1d0b	harness/code.yaml, harness/fix.yaml, harness/review.yaml
ghcr.io/fullsend-ai/fullsend-sandbox:0.42.0	sha256:259605fea321353552fdefd3a6a55e8b5c260998dfc5a622ed143e41a429995a	harness/prioritize.yaml, harness/retro.yaml, harness/scribe.yaml, harness/triage.yaml

Both digests resolved from GHCR (Docker-Content-Digest for the 0.42.0 tag); both images carry org.opencontainers.image.revision = 4665685a1d9d471a7a044908a68f00bed78caba7.

What the new image ships

• pi 0.85.0, xai-vertex 0.2.1, Claude Code 2.1.260
• fullsend anthropic-vertex extension
• Runner-side persona routing (feat(runtime): per-persona model configuration for pi sub-agents (#7031) fullsend#7038)
• Hook fix (fix(#7043): keep analysis_incomplete blocking and fail closed on malformed tirith output fullsend#7044)

Validation

$ grep -h '^image:' harness/*.yaml | sort -u
image: ghcr.io/fullsend-ai/fullsend-code@sha256:623fc74588876062f12f40690ee759c6134ba516fabdd36e6dcfc4eeb9cd1d0b
image: ghcr.io/fullsend-ai/fullsend-sandbox@sha256:259605fea321353552fdefd3a6a55e8b5c260998dfc5a622ed143e41a429995a

Related

• release: open the agents harness image-digest repin PR from the tag build instead of by hand (and tag agents after it lands) fullsend#7048 (automate this)
• chore(harness): repin sandbox and code images to the 0.40.0 release digests #1160 (previous repin for 0.40.0)

---

Closes #1193

Post-script verification

• Branch is not main/master (agent/1193-repin-images-042)
• Secret scan passed (gitleaks — ec2f8a5b4369b844323ee1ee87c1d4a599a42817..HEAD)
• PR body secret scan passed (gitleaks — no-git)

[waynesun09]

/fs-fix-stop

[github-actions]

Fix agent disabled for this PR. Remove the fullsend-no-fix label or use /fs-fix to re-engage.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 8:54 PM UTC · Completed 9:06 PM UTC

Commit: 7bb0eab · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.60

[fullsend-ai-review]

Risk Assessment: moderate (2/5)

Details

A surgical, bot-authored config-only PR repinning image digests in 7 harness YAML files per a well-scoped issue; the mechanical nature and reversibility of the change offset the high churn, multi-author contention, and regression history observed in these frequently-touched files.

[fullsend-ai-review]

Review

Findings

Medium

• [protected-path] harness/ — This PR modifies 7 files under protected paths: harness/code.yaml, harness/fix.yaml, harness/prioritize.yaml, harness/retro.yaml, harness/review.yaml, harness/scribe.yaml, harness/triage.yaml. The PR links to issue harness: repin sandbox and code images to the 0.42.0 release digests #1193 and explains the rationale (repinning image digests to fullsend 0.42.0). Human approval is always required for protected-path changes, regardless of context.