Bug: Scheduled session timezone/utc does not appear to be correct

[bhavenst]

🐛 Bug Description

Summary:

The timezone/utc calculation for scheduled sessions does not appear to be correct.

The time is entered as 8 (presumably in my timezone of MDT) and the interpretation text shows this as 2 PM UTC, 8AM MDT). However the job actually runs at 2AM MDT.

Expected Behavior:
The cron specifier and the utc/timezone interpretation to agree.

Actual Behavior:
They do not seem to agree.

🔄 Steps to Reproduce

1. Create a schedule for a particular time
2. See that it runs not when shown in the schedule screen.

🖼️ Screenshots

See above

🌍 Environment

N/A

Component: [RAT System / Ambient Agentic Runner / vTeam Tools]

Version/Commit: [e.g. v1.2.3 or commit hash]

Operating System: [e.g. macOS 14.0, Ubuntu 22.04, Windows 11]

Browser: [if applicable - Chrome 119, Firefox 120, Safari 17]

Python Version: [if applicable - e.g. 3.11.5]

Kubernetes Version: [if applicable - e.g. 1.28.2]

📋 Additional Context

Error Messages: [Paste any error messages or logs]

[Error logs here]

Configuration: [Any relevant configuration details]

Recent Changes: [Any recent changes that might be related]

🔍 Possible Solution

[If you have suggestions on how to fix the bug]

✅ Acceptance Criteria

• Bug is reproduced and root cause identified
• Fix is implemented and tested
• Regression tests added to prevent future occurrences
• Documentation updated if needed
• Fix is verified in staging environment

🏷️ Labels

• Priority: [low/medium/high/critical]
• Complexity: [trivial/easy/medium/hard]
• Component: [frontend/backend/operator/tools/docs]