@codex review

Closing this PR because the author has more than 10 active PRs in this repo. Please reduce the active PR queue and reopen or resubmit once it is back under the limit. You can close your own PRs to get back under the limit.

Greptile Summary

This PR adds a targeted defensive guard in app-render.ts against cron jobs with missing/undefined payloads that previously caused the Control UI render path to throw. The fix extracts job.payload into a local variable and uses optional chaining (payload?.kind) before the existing kind-check, so malformed entries short-circuit to "" and are filtered out of the model-suggestions set. A jsdom regression test in app-render.test.ts locks in the no-throw behavior.

• Changed job.payload.kind → payload?.kind to guard against undefined payloads before property access
• Extracted job.payload into a const payload for clarity (consistent with the existing typeof job.agentId === "string" defensive pattern nearby)
• Added a Vitest/jsdom unit test that injects a cron job with payload: undefined and asserts renderApp does not throw

Confidence Score: 5/5

• This PR is safe to merge — the fix is minimal, correct, and fully covered by a regression test.
• The change is a single-line defensive guard using optional chaining (payload?.kind), which is the idiomatic pattern already used elsewhere in the same function for job.agentId. The logic is straightforward: an undefined payload causes payload?.kind !== "agentTurn" to evaluate to true, returning "" which is then filtered out — exactly the desired behavior. A jsdom regression test directly covers the crash scenario. No unintended side effects are introduced.
• No files require special attention.

_{Reviews (1): Last reviewed commit: "fix(ui): tolerate malformed cron payload..." | Re-trigger Greptile}

Codex Review: Didn't find any major issues. Bravo.