Purpose
Disposable operator-approved fixture for the FailureReport real
Root-to-Codex trace-capture UAT required before starting FailureReport #46.
Diagnostic observation
During campaign creation and campaign-date display, the UI does not clearly
identify whether entered and rendered dates are UTC or local time. An operator
cannot tell from the visible fields which exact instant a campaign begins or
ends.
Determine where the current revision establishes—or fails to establish—the
timezone contract, what evidence distinguishes storage/parsing behavior from a
display-only labeling gap, and what the smallest evidence-backed remediation
would be. This is a diagnostic exercise only; do not implement the change.
Binding
- Repository revision:
a2f98850862a8bc9ef9bb08c364ef6e8f03461a0
- Flow: one existing-Issue FailureReport diagnostic turn
- Expected public mutation: FailureReport-managed append-only workpad activity
only
Boundaries
- This Issue is not a production incident or implementation request.
- Do not route it to implementation.
- Raw traces, prompts, model/tool payloads, credentials, endpoints, and host
paths must remain local and must not be posted here.
Purpose
Disposable operator-approved fixture for the FailureReport real
Root-to-Codex trace-capture UAT required before starting FailureReport #46.
Diagnostic observation
During campaign creation and campaign-date display, the UI does not clearly
identify whether entered and rendered dates are UTC or local time. An operator
cannot tell from the visible fields which exact instant a campaign begins or
ends.
Determine where the current revision establishes—or fails to establish—the
timezone contract, what evidence distinguishes storage/parsing behavior from a
display-only labeling gap, and what the smallest evidence-backed remediation
would be. This is a diagnostic exercise only; do not implement the change.
Binding
a2f98850862a8bc9ef9bb08c364ef6e8f03461a0only
Boundaries
paths must remain local and must not be posted here.