[Fixture] FailureReport Root-to-Codex diagnostic trace smoke

[Alive24]

Purpose

This is a disposable, operator-approved fixture for one FailureReport
Root-to-Codex diagnostic trace smoke used by the Shea Halo OpenSourceIRL
demonstration.

It is not a request to implement or merge a CKBoost product change.

Controlled symptom

A campaign start or end timestamp can appear as the wrong calendar day when the
stored value is UTC and the viewer is in a negative UTC offset.

Diagnose the current CKBoost date-rendering path and determine:

• where storage, parsing, and display timezone semantics are selected;
• whether the behavior is a formatting-only problem or changes campaign
  eligibility logic;
• what focused regression test would distinguish UTC storage from local display;
• the smallest safe implementation handoff, if the symptom is supported by the
  current source.

Fixture boundaries

• Diagnose only; do not implement the change or open a pull request.
• Use the immutable repository revision supplied by the operator at runtime.
• It is acceptable for FailureReport to append its managed workpad comments and
  create its diagnostic-only snapshot according to its normal contract.
• Do not publish credentials, private Nostr content, host paths, raw model/tool
  payloads, or trace contents.
• If current source disproves the symptom, record that result rather than
  forcing a remediation.

Completion

The fixture is complete when FailureReport reaches a deterministic diagnostic
handoff or a precise human-input request and the accompanying local native trace
is finalized. The Issue should not enter CKBoost implementation work.