@codex review

Greptile Summary

This PR adds a targeted null-safety guard in app-render.ts to tolerate cron jobs whose payload field is undefined (or otherwise malformed). Previously, accessing job.payload.kind on such a job would throw a TypeError and crash the Control UI render path. The fix introduces optional chaining (payload?.kind) so malformed jobs are silently skipped instead of surfacing as exceptions.

• app-render.ts: Extracts job.payload into a local variable and uses payload?.kind to short-circuit safely when the payload is absent, matching the existing filter(Boolean) sentinel-return pattern already used throughout the same pipeline.
• app-render.test.ts: New jsdom regression test that constructs an OpenClawApp with a deliberately undefined payload and asserts renderApp does not throw, locking in the no-crash guarantee.

Confidence Score: 5/5

• Safe to merge — the change is a one-line defensive guard with a dedicated regression test and no behavioral impact on well-formed data.
• The fix is minimal, correct, and consistent with patterns already used in the same code block (e.g., job.delivery?.to on line 364). The regression test directly exercises the crash path and will catch any reversion. No unrelated code is touched.
• 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. Keep them coming!

Quick note on the remaining Windows shard:

• checks-windows (node, test, 8, 9, pnpm test) is currently showing as failed, but the job log itself completed the test run successfully.
• The shard finished with 126 passed test files / 1002 passed tests and every recorded step in the Actions job completed with success.
• GitHub currently reports the job conclusion as cancelled, so this looks like CI/job bookkeeping noise rather than a failure in the files touched by this PR.

This PR still only changes:

• ui/src/ui/app-render.ts
• ui/src/ui/app-render.test.ts

@Takhoffman when you have a moment, could you take a quick look?

This is back to a very small web-ui fix: a null-safe guard plus one focused regression test. The only remaining non-green signal is a Windows shard that GitHub recorded as cancelled, but that job log itself finished with 126 passed test files / 1002 passed tests and all recorded steps succeeding.

Thanks!

@BunsDev when you have a moment, could you take a quick look?

This is a very small web-ui regression fix for #54439: one null-safe guard plus one focused jsdom regression test.

All substantive checks are green. The only non-green signal is checks-windows (node, test, 8, 9, pnpm test), which GitHub recorded as cancelled even though that shard's log completed with 126 passed test files / 1002 passed tests and all recorded steps succeeding.

Thanks!

Closing this to free active PR slots and refocus on fresher post-update issues. This stayed blocked behind noisy CI / reviewer attention rather than the small web-ui fix itself.