[Feature] Make timestamp timezone configurable in CaptureConfig

[southpy]

Feature Description

TDAI stores (L0) and (L1) timestamps using which always outputs UTC. These timestamps should respect a configurable timezone.

Motivation

Timestamps in local time are more useful for debugging, user-facing display, and data analysis. UTC is correct for storage but the system should allow users to configure which timezone is used when generating these timestamps. Currently already has a helper with a hardcoded offset — the natural next step is to expose this as a config field.

Proposed Solution

Add a field to (in ):

Default to (CST) to match the existing behavior. Users in other timezones can override.

The three hardcoded UTC sites are:

• — →
• — →
• — →

These would read from instead of using UTC directly.

Alternatives Considered

1. **Environment variable ** — Node.js respects this but requires system-level config, not user-configurable per-deployment.
2. Hard-coding into the three sites — what the existing helper already does, but not configurable.

Additional Context

The file already contains a function (with ) that could serve as the basis for the implementation. This would be a minimal, low-risk addition with a clear default.

[Maxwell-Code07]

Thanks for the well-thought-out proposal! This is a reasonable enhancement. We'll evaluate internally and get back to you.