[Fix] Custom automation cards show cadence in the wrong timezone

[roomote-roomote]

​Opened on behalf of @daniel-lxs. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Saved custom-automation cron cards now parse and label cadence with the deployment's effective scheduling timezone instead of UTC.
• The card reuses the same timezone suffix formatter as the custom-automation editor and preserves Custom schedule when timezone data is unavailable or the saved cron cannot be parsed.
• Regression coverage exercises non-UTC, UTC, unavailable-timezone, invalid-cron, editor-summary, and server occurrence behavior.

Why this change was made

The custom-automation editor, save validation, and scheduled execution already use the resolved deployment timezone, but saved cards independently passed UTC to the cron parser and omitted the timezone from their visible cadence. This made the persisted summary ambiguous and inconsistent with when the automation actually runs.

Impact

A saved 0 9 * * * automation in America/New_York now displays Daily at 09:00 AM (America/New York), matching its editor preview and the server's 9 AM local execution semantics. UTC deployments remain explicitly labeled (UTC), while unavailable or invalid schedule data continues to degrade safely to Custom schedule.

The focused component, client cron, and server schedule suites pass, as do web and SDK type checks, web lint, full repository lint and type checks, knip, the full repository test suite, and pre-push gates. Desktop and mobile captures were taken from the exact shipped diff using genuine UI-created deployment and automation state.

Screenshots

Desktop

Mobile

[roomote-community]

No code issues found. See task

_{Reviewed 37870fc}