claude-smoke: sandbox issue for @claude handler smoke check

[izzywdev]

This is a dedicated sandbox issue for the claude-smoke workflow (guardrail #4 from #169).\n\nThe smoke check workflow posts @claude here on a weekly schedule (Mondays 08:00 UTC) and asserts the handler produces a real, non-"0s" response — catching the exact regression that caused #169 (bad SHA → e2e suite → 0s no-op).\n\nDo not close this issue. It is used as a stable target for automated mentions.\n\nRefs: #169

[claude]

Claude finished @izzywdev's task in 16s —— View job

---

✅ claude-smoke: handler is alive

This is the dedicated sandbox issue for the claude-smoke guardrail (#4 from #169). The @claude handler received this mention, executed with a real model turn, and is posting a genuine (non-0s no-op) response — which is exactly what the weekly smoke check asserts.

• Read the issue and understood it's a smoke target (not an implementation/review request)
• Confirmed no code changes are required — this issue is intentionally left open as a stable mention target
• Produced a real handler response so the smoke assertion passes

Handler status: healthy — mention processed, model turn ran, comment updated. No files changed and this issue will not be closed.

Refs: #169

[github-actions]

@claude smoke check — please reply 'ack' with a one-line status. (run 29244045830)