[ItIsUday]

Why

The CLI resolves JUnit <testsuite timestamp> timezones itself with a blanket tzlocal(). That's correct for offset-aware and genuinely-local frameworks, but wrong for "looks-naive-but-UTC" runners (jest, cypress), corrupting test_cases.created_at on non-UTC agents and breaking cross-machine elapsed-time aggregation (AIENG-379). Mirroring the framework-timezone policy in every client is unmaintainable.

What

Move timezone resolution to the server (single source of truth). The CLI now:

• sends the raw <testsuite timestamp> string as suiteTimestamp (unresolved);
• sends the agent's UTC offset once per record tests request (agentUtcOffset), which only the client knows and the server needs to resolve naive local timestamps.

_timestamp()/tzlocal() and the framework-TZ imports are removed — the CLI holds zero timezone knowledge. Requires the paired mothership change that accepts these fields and resolves them.

Tests

Full suite green except the pre-existing, unrelated subset failure test_maven.test_scan_test_compile_lst. Updated golden payloads to the raw-passthrough format; comparator excludes the machine-dependent agentUtcOffset.

v1-first per the two-branch process; will be forward-ported to main.

[ono-max]

@ItIsUday

Let's merge the PR in mothership first and merge one in CLI later.