Timezone is unclear in campaign date inputs and displays

[Alive24]

Observed behavior

During campaign creation and campaign-date display, the UI does not identify
whether entered and rendered dates are UTC or local time. An operator cannot
tell which exact instant a campaign begins or ends.

Expected diagnostic outcome

Determine where the current source establishes—or fails to establish—the
timezone contract, distinguish storage/parsing behavior from a display-only
labeling gap, and recommend the smallest evidence-backed remediation.

Reproduction

Inspect the campaign date input and display paths at
a2f98850862a8bc9ef9bb08c364ef6e8f03461a0, then run only focused,
non-mutating checks needed to verify the current behavior.

This is a disposable diagnostic fixture. Do not implement or route a change.

[Alive24]

FailureReport update

• Report: failure-report/Alive24-CKBoost-62
• Stage: Active diagnosis
• Status: investigating
• Severity: medium
• Repository: Alive24/CKBoost
• Immutable target revision: a2f98850862a8bc9ef9bb08c364ef6e8f03461a0
• Workpad revision: 0
• Diagnostic session: not started
• Logical session: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62
• Authoritative entry: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-0
• Issue: Alive24/CKBoost#62
• Canonical representation: inline folded snapshot

Active diagnosis

Current facts and evidence

• evidence-reported-timezone-ambiguity [reported] — The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time. Interpretation: The source paths must be inspected before distinguishing a data-semantics defect from a display-labeling gap. Public evidence: Timezone is unclear in campaign date inputs and displays #62.

Current hypotheses

• hypothesis-display-only [open] — Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.
• hypothesis-semantics-ambiguous [open] — Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.

Remaining unknowns

• Whether campaign dates are parsed and stored with consistent UTC or local-time semantics.
• Whether the defect is limited to missing display/input labeling.
• Which smallest remediation follows from the source behavior.

Canonical context — complete FailureReport snapshot

{
  "entry": {
    "schema_version": "failure-report-workpad-entry/v2",
    "producer": {
      "id": "failure-report-local",
      "github_actor_id": "20827211"
    },
    "logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
    "entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-0",
    "revision": 0
  },
  "failure_report": {
    "id": "failure-report/Alive24-CKBoost-62",
    "schema_version": "failure-report/v1",
    "status": "investigating",
    "created_at": "2026-07-30T14:43:58Z",
    "updated_at": "2026-07-30T14:46:02.359Z",
    "shared_context": {
      "provider": "github_issue",
      "repository": "Alive24/CKBoost",
      "issue_number": 62,
      "issue_url": "https://github.com/Alive24/CKBoost/issues/62",
      "workpad_marker": "<!-- failure-report-workpad -->",
      "workpad_revision": 0,
      "workpad_logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
      "workpad_entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-0",
      "workpad_producer_id": "failure-report-local",
      "synced_at": "2026-07-30T14:46:02.359Z"
    },
    "origin": {
      "source": "github_issue",
      "reporter": "issue-author",
      "related_work": [
        {
          "kind": "github_issue",
          "ref": "https://github.com/Alive24/CKBoost/issues/62"
        }
      ]
    },
    "target": {
      "repository": "Alive24/CKBoost",
      "revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
      "components": [
        "campaign date input",
        "campaign date display"
      ],
      "environment": [
        {
          "name": "diagnostic_mode",
          "value": "focused non-mutating source inspection at bound revision"
        }
      ]
    },
    "severity": "medium",
    "symptom": {
      "observed_behavior": [
        "Campaign date inputs do not identify whether entered dates are UTC or local time.",
        "Campaign date displays do not identify whether rendered dates are UTC or local time.",
        "An operator cannot determine the exact campaign start or end instant from the UI."
      ],
      "expected_behavior": [
        "The timezone contract for campaign date entry, parsing/storage, and display is explicit.",
        "The UI communicates enough timezone information for an operator to determine exact campaign instants."
      ],
      "raw_error_summary": "Timezone is unclear in campaign date inputs and displays.",
      "first_seen_at": null,
      "reproduction": {
        "preconditions": [
          "Inspect repository revision a2f98850862a8bc9ef9bb08c364ef6e8f03461a0."
        ],
        "steps": [
          "Locate campaign date input and display paths.",
          "Trace parsing, serialization or storage, and rendering behavior.",
          "Run only focused non-mutating checks needed to verify current behavior."
        ],
        "frequency": "Reported as present in the current campaign creation and date-display paths."
      }
    },
    "inputs": [
      {
        "id": "input-issue-62",
        "kind": "github_issue",
        "artifact": {
          "ref": "https://github.com/Alive24/CKBoost/issues/62",
          "media_type": "text/markdown",
          "sensitivity": "public",
          "retention": "durable"
        },
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        }
      }
    ],
    "evidence": [
      {
        "id": "evidence-reported-timezone-ambiguity",
        "kind": "reported_observation",
        "observed_fact": "The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time.",
        "interpretation": "The source paths must be inspected before distinguishing a data-semantics defect from a display-labeling gap.",
        "epistemic_status": "reported",
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/issues/62",
            "media_type": "text/markdown",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      }
    ],
    "hypotheses": [
      {
        "id": "hypothesis-display-only",
        "statement": "Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.",
        "status": "open",
        "supporting_evidence": [],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "Plausible from the reported UI ambiguity, but no repository evidence has yet been collected.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          }
        ]
      },
      {
        "id": "hypothesis-semantics-ambiguous",
        "statement": "Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.",
        "status": "open",
        "supporting_evidence": [],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "The reported behavior does not establish whether the ambiguity is display-only or exists in the data path.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          }
        ]
      }
    ],
    "decisions": [
      {
        "id": "decision-diagnostic-only",
        "kind": "scope",
        "statement": "Perform one focused, non-mutating diagnosis; do not implement or route a change.",
        "status": "accepted",
        "authority": "human",
        "rationale": "The Issue defines this as a disposable diagnostic fixture and explicitly excludes implementation and routing.",
        "evidence_refs": [
          "evidence-reported-timezone-ambiguity"
        ],
        "provenance": {
          "phase": "human_decision",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "issue scope readback"
        }
      }
    ],
    "experiments": [],
    "conclusion": {
      "diagnosis": "Diagnosis pending focused inspection of campaign date input, parsing/storage, and display paths at the bound revision.",
      "confidence": {
        "level": "low",
        "basis": "Only the Issue's reported observation is currently available; no repository or runtime evidence has been collected."
      },
      "remaining_uncertainty": [
        "Whether campaign dates are parsed and stored with consistent UTC or local-time semantics.",
        "Whether the defect is limited to missing display/input labeling.",
        "Which smallest remediation follows from the source behavior."
      ],
      "recommended_remediation": []
    },
    "handoff": {
      "todo_status": "not_ready",
      "gate_decision": "Blocked",
      "uat_required": false,
      "goal": "Diagnose the campaign timezone contract without implementing or routing a change.",
      "why_now": "Operators reportedly cannot determine exact campaign start and end instants from current date entry and display behavior.",
      "scope_in": [
        "Inspect campaign date input, parsing/serialization or storage, and display paths at the immutable target revision.",
        "Run focused non-mutating checks needed to distinguish timezone semantics from a display-only gap."
      ],
      "scope_out": [
        "Code changes, commits, pull requests, or implementation routing.",
        "Broad unrelated application review."
      ],
      "guardrails": [
        "Use only the immutable target revision.",
        "Keep the diagnostic worktree clean.",
        "Treat Issue claims as reported until verified in repository or test evidence."
      ],
      "required_outcomes": [
        "Identify the current timezone contract or absence of one.",
        "Distinguish parsing/storage behavior from display labeling.",
        "Recommend the smallest evidence-backed remediation."
      ],
      "verification": {
        "automated": [
          "Run focused existing tests or non-mutating checks relevant to campaign date handling when available."
        ],
        "uat": [],
        "context": [
          "Cite source paths and focused check results in diagnostic evidence."
        ]
      },
      "residual_risks": []
    },
    "domain": {
      "pack_id": "failure-report/generic",
      "pack_version": "1",
      "schema_ref": "failure-report/v1",
      "extension_data": {}
    }
  }
}

FailureReport update

• Report: failure-report/Alive24-CKBoost-62
• Stage: Active diagnosis
• Status: investigating
• Severity: medium
• Repository: Alive24/CKBoost
• Immutable target revision: a2f98850862a8bc9ef9bb08c364ef6e8f03461a0
• Workpad revision: 1
• Diagnostic session: active
• Logical session: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62
• Authoritative entry: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-1
• Issue: Alive24/CKBoost#62
• Diagnostic session identity: diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec
• Canonical representation: inline folded snapshot

Active diagnosis

Current facts and evidence

• evidence-reported-timezone-ambiguity [reported] — The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time. Interpretation: The source paths must be inspected before distinguishing a data-semantics defect from a display-labeling gap. Public evidence: Timezone is unclear in campaign date inputs and displays #62.

Current hypotheses

• hypothesis-display-only [open] — Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.
• hypothesis-semantics-ambiguous [open] — Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.

Remaining unknowns

• Whether campaign dates are parsed and stored with consistent UTC or local-time semantics.
• Whether the defect is limited to missing display/input labeling.
• Which smallest remediation follows from the source behavior.

Canonical context — complete FailureReport snapshot

{
  "entry": {
    "schema_version": "failure-report-workpad-entry/v2",
    "producer": {
      "id": "failure-report-local",
      "github_actor_id": "20827211"
    },
    "logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
    "entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-1",
    "revision": 1
  },
  "failure_report": {
    "id": "failure-report/Alive24-CKBoost-62",
    "schema_version": "failure-report/v1",
    "status": "investigating",
    "created_at": "2026-07-30T14:43:58Z",
    "updated_at": "2026-07-30T14:46:20.692Z",
    "shared_context": {
      "provider": "github_issue",
      "repository": "Alive24/CKBoost",
      "issue_number": 62,
      "issue_url": "https://github.com/Alive24/CKBoost/issues/62",
      "workpad_marker": "<!-- failure-report-workpad -->",
      "workpad_comment_ref": "5132323099",
      "workpad_revision": 1,
      "workpad_logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
      "workpad_entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-1",
      "workpad_producer_id": "failure-report-local",
      "synced_at": "2026-07-30T14:46:20.692Z"
    },
    "diagnostic_session": {
      "lifecycle": "active",
      "domain_extensions": [],
      "backend_id": "codex_app_server",
      "worktree": {
        "identity": "diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec",
        "base_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "head_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0"
      },
      "diagnostic_branch_slug": "timezone-is-unclear-in-campaign-date-inputs-and-displays"
    },
    "origin": {
      "source": "github_issue",
      "reporter": "issue-author",
      "related_work": [
        {
          "kind": "github_issue",
          "ref": "https://github.com/Alive24/CKBoost/issues/62"
        }
      ]
    },
    "target": {
      "repository": "Alive24/CKBoost",
      "revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
      "components": [
        "campaign date input",
        "campaign date display"
      ],
      "environment": [
        {
          "name": "diagnostic_mode",
          "value": "focused non-mutating source inspection at bound revision"
        }
      ]
    },
    "severity": "medium",
    "symptom": {
      "observed_behavior": [
        "Campaign date inputs do not identify whether entered dates are UTC or local time.",
        "Campaign date displays do not identify whether rendered dates are UTC or local time.",
        "An operator cannot determine the exact campaign start or end instant from the UI."
      ],
      "expected_behavior": [
        "The timezone contract for campaign date entry, parsing/storage, and display is explicit.",
        "The UI communicates enough timezone information for an operator to determine exact campaign instants."
      ],
      "raw_error_summary": "Timezone is unclear in campaign date inputs and displays.",
      "first_seen_at": null,
      "reproduction": {
        "preconditions": [
          "Inspect repository revision a2f98850862a8bc9ef9bb08c364ef6e8f03461a0."
        ],
        "steps": [
          "Locate campaign date input and display paths.",
          "Trace parsing, serialization or storage, and rendering behavior.",
          "Run only focused non-mutating checks needed to verify current behavior."
        ],
        "frequency": "Reported as present in the current campaign creation and date-display paths."
      }
    },
    "inputs": [
      {
        "id": "input-issue-62",
        "kind": "github_issue",
        "artifact": {
          "ref": "https://github.com/Alive24/CKBoost/issues/62",
          "media_type": "text/markdown",
          "sensitivity": "public",
          "retention": "durable"
        },
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        }
      }
    ],
    "evidence": [
      {
        "id": "evidence-reported-timezone-ambiguity",
        "kind": "reported_observation",
        "observed_fact": "The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time.",
        "interpretation": "The source paths must be inspected before distinguishing a data-semantics defect from a display-labeling gap.",
        "epistemic_status": "reported",
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/issues/62",
            "media_type": "text/markdown",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      }
    ],
    "hypotheses": [
      {
        "id": "hypothesis-display-only",
        "statement": "Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.",
        "status": "open",
        "supporting_evidence": [],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "Plausible from the reported UI ambiguity, but no repository evidence has yet been collected.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          }
        ]
      },
      {
        "id": "hypothesis-semantics-ambiguous",
        "statement": "Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.",
        "status": "open",
        "supporting_evidence": [],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "The reported behavior does not establish whether the ambiguity is display-only or exists in the data path.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          }
        ]
      }
    ],
    "decisions": [
      {
        "id": "decision-diagnostic-only",
        "kind": "scope",
        "statement": "Perform one focused, non-mutating diagnosis; do not implement or route a change.",
        "status": "accepted",
        "authority": "human",
        "rationale": "The Issue defines this as a disposable diagnostic fixture and explicitly excludes implementation and routing.",
        "evidence_refs": [
          "evidence-reported-timezone-ambiguity"
        ],
        "provenance": {
          "phase": "human_decision",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "issue scope readback"
        }
      }
    ],
    "experiments": [],
    "conclusion": {
      "diagnosis": "Diagnosis pending focused inspection of campaign date input, parsing/storage, and display paths at the bound revision.",
      "confidence": {
        "level": "low",
        "basis": "Only the Issue's reported observation is currently available; no repository or runtime evidence has been collected."
      },
      "remaining_uncertainty": [
        "Whether campaign dates are parsed and stored with consistent UTC or local-time semantics.",
        "Whether the defect is limited to missing display/input labeling.",
        "Which smallest remediation follows from the source behavior."
      ],
      "recommended_remediation": []
    },
    "handoff": {
      "todo_status": "not_ready",
      "gate_decision": "Blocked",
      "uat_required": false,
      "goal": "Diagnose the campaign timezone contract without implementing or routing a change.",
      "why_now": "Operators reportedly cannot determine exact campaign start and end instants from current date entry and display behavior.",
      "scope_in": [
        "Inspect campaign date input, parsing/serialization or storage, and display paths at the immutable target revision.",
        "Run focused non-mutating checks needed to distinguish timezone semantics from a display-only gap."
      ],
      "scope_out": [
        "Code changes, commits, pull requests, or implementation routing.",
        "Broad unrelated application review."
      ],
      "guardrails": [
        "Use only the immutable target revision.",
        "Keep the diagnostic worktree clean.",
        "Treat Issue claims as reported until verified in repository or test evidence."
      ],
      "required_outcomes": [
        "Identify the current timezone contract or absence of one.",
        "Distinguish parsing/storage behavior from display labeling.",
        "Recommend the smallest evidence-backed remediation."
      ],
      "verification": {
        "automated": [
          "Run focused existing tests or non-mutating checks relevant to campaign date handling when available."
        ],
        "uat": [],
        "context": [
          "Cite source paths and focused check results in diagnostic evidence."
        ]
      },
      "residual_risks": []
    },
    "domain": {
      "pack_id": "failure-report/generic",
      "pack_version": "1",
      "schema_ref": "failure-report/v1",
      "extension_data": {}
    }
  }
}

FailureReport update

• Report: failure-report/Alive24-CKBoost-62
• Stage: Active diagnosis
• Status: investigating
• Severity: medium
• Repository: Alive24/CKBoost
• Immutable target revision: a2f98850862a8bc9ef9bb08c364ef6e8f03461a0
• Workpad revision: 2
• Diagnostic session: active
• Logical session: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62
• Authoritative entry: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-2
• Issue: Alive24/CKBoost#62
• Diagnostic session identity: diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec
• Canonical representation: inline folded snapshot

Active diagnosis

Current facts and evidence

• evidence-reported-timezone-ambiguity [reported] — The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time. Interpretation: The source paths must be inspected before distinguishing a data-semantics defect from a display-labeling gap. Public evidence: Timezone is unclear in campaign date inputs and displays #62.

Current hypotheses

• hypothesis-display-only [open] — Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.
• hypothesis-semantics-ambiguous [open] — Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.

Remaining unknowns

• Whether campaign dates are parsed and stored with consistent UTC or local-time semantics.
• Whether the defect is limited to missing display/input labeling.
• Which smallest remediation follows from the source behavior.

Canonical context — complete FailureReport snapshot

{
  "entry": {
    "schema_version": "failure-report-workpad-entry/v2",
    "producer": {
      "id": "failure-report-local",
      "github_actor_id": "20827211"
    },
    "logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
    "entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-2",
    "revision": 2
  },
  "failure_report": {
    "id": "failure-report/Alive24-CKBoost-62",
    "schema_version": "failure-report/v1",
    "status": "investigating",
    "created_at": "2026-07-30T14:43:58Z",
    "updated_at": "2026-07-30T14:46:46.323Z",
    "shared_context": {
      "provider": "github_issue",
      "repository": "Alive24/CKBoost",
      "issue_number": 62,
      "issue_url": "https://github.com/Alive24/CKBoost/issues/62",
      "workpad_marker": "<!-- failure-report-workpad -->",
      "workpad_comment_ref": "5132323099",
      "workpad_revision": 2,
      "workpad_logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
      "workpad_entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-2",
      "workpad_producer_id": "failure-report-local",
      "synced_at": "2026-07-30T14:46:46.323Z"
    },
    "diagnostic_session": {
      "lifecycle": "active",
      "domain_extensions": [],
      "backend_id": "codex_app_server",
      "codex_thread_id": "019fb37d-f822-7482-a0c0-50ee203c8358",
      "worktree": {
        "identity": "diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec",
        "base_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "head_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0"
      },
      "diagnostic_branch_slug": "timezone-is-unclear-in-campaign-date-inputs-and-displays"
    },
    "origin": {
      "source": "github_issue",
      "reporter": "issue-author",
      "related_work": [
        {
          "kind": "github_issue",
          "ref": "https://github.com/Alive24/CKBoost/issues/62"
        }
      ]
    },
    "target": {
      "repository": "Alive24/CKBoost",
      "revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
      "components": [
        "campaign date input",
        "campaign date display"
      ],
      "environment": [
        {
          "name": "diagnostic_mode",
          "value": "focused non-mutating source inspection at bound revision"
        }
      ]
    },
    "severity": "medium",
    "symptom": {
      "observed_behavior": [
        "Campaign date inputs do not identify whether entered dates are UTC or local time.",
        "Campaign date displays do not identify whether rendered dates are UTC or local time.",
        "An operator cannot determine the exact campaign start or end instant from the UI."
      ],
      "expected_behavior": [
        "The timezone contract for campaign date entry, parsing/storage, and display is explicit.",
        "The UI communicates enough timezone information for an operator to determine exact campaign instants."
      ],
      "raw_error_summary": "Timezone is unclear in campaign date inputs and displays.",
      "first_seen_at": null,
      "reproduction": {
        "preconditions": [
          "Inspect repository revision a2f98850862a8bc9ef9bb08c364ef6e8f03461a0."
        ],
        "steps": [
          "Locate campaign date input and display paths.",
          "Trace parsing, serialization or storage, and rendering behavior.",
          "Run only focused non-mutating checks needed to verify current behavior."
        ],
        "frequency": "Reported as present in the current campaign creation and date-display paths."
      }
    },
    "inputs": [
      {
        "id": "input-issue-62",
        "kind": "github_issue",
        "artifact": {
          "ref": "https://github.com/Alive24/CKBoost/issues/62",
          "media_type": "text/markdown",
          "sensitivity": "public",
          "retention": "durable"
        },
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        }
      }
    ],
    "evidence": [
      {
        "id": "evidence-reported-timezone-ambiguity",
        "kind": "reported_observation",
        "observed_fact": "The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time.",
        "interpretation": "The source paths must be inspected before distinguishing a data-semantics defect from a display-labeling gap.",
        "epistemic_status": "reported",
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/issues/62",
            "media_type": "text/markdown",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      }
    ],
    "hypotheses": [
      {
        "id": "hypothesis-display-only",
        "statement": "Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.",
        "status": "open",
        "supporting_evidence": [],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "Plausible from the reported UI ambiguity, but no repository evidence has yet been collected.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          }
        ]
      },
      {
        "id": "hypothesis-semantics-ambiguous",
        "statement": "Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.",
        "status": "open",
        "supporting_evidence": [],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "The reported behavior does not establish whether the ambiguity is display-only or exists in the data path.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          }
        ]
      }
    ],
    "decisions": [
      {
        "id": "decision-diagnostic-only",
        "kind": "scope",
        "statement": "Perform one focused, non-mutating diagnosis; do not implement or route a change.",
        "status": "accepted",
        "authority": "human",
        "rationale": "The Issue defines this as a disposable diagnostic fixture and explicitly excludes implementation and routing.",
        "evidence_refs": [
          "evidence-reported-timezone-ambiguity"
        ],
        "provenance": {
          "phase": "human_decision",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "issue scope readback"
        }
      }
    ],
    "experiments": [],
    "conclusion": {
      "diagnosis": "Diagnosis pending focused inspection of campaign date input, parsing/storage, and display paths at the bound revision.",
      "confidence": {
        "level": "low",
        "basis": "Only the Issue's reported observation is currently available; no repository or runtime evidence has been collected."
      },
      "remaining_uncertainty": [
        "Whether campaign dates are parsed and stored with consistent UTC or local-time semantics.",
        "Whether the defect is limited to missing display/input labeling.",
        "Which smallest remediation follows from the source behavior."
      ],
      "recommended_remediation": []
    },
    "handoff": {
      "todo_status": "not_ready",
      "gate_decision": "Blocked",
      "uat_required": false,
      "goal": "Diagnose the campaign timezone contract without implementing or routing a change.",
      "why_now": "Operators reportedly cannot determine exact campaign start and end instants from current date entry and display behavior.",
      "scope_in": [
        "Inspect campaign date input, parsing/serialization or storage, and display paths at the immutable target revision.",
        "Run focused non-mutating checks needed to distinguish timezone semantics from a display-only gap."
      ],
      "scope_out": [
        "Code changes, commits, pull requests, or implementation routing.",
        "Broad unrelated application review."
      ],
      "guardrails": [
        "Use only the immutable target revision.",
        "Keep the diagnostic worktree clean.",
        "Treat Issue claims as reported until verified in repository or test evidence."
      ],
      "required_outcomes": [
        "Identify the current timezone contract or absence of one.",
        "Distinguish parsing/storage behavior from display labeling.",
        "Recommend the smallest evidence-backed remediation."
      ],
      "verification": {
        "automated": [
          "Run focused existing tests or non-mutating checks relevant to campaign date handling when available."
        ],
        "uat": [],
        "context": [
          "Cite source paths and focused check results in diagnostic evidence."
        ]
      },
      "residual_risks": []
    },
    "domain": {
      "pack_id": "failure-report/generic",
      "pack_version": "1",
      "schema_ref": "failure-report/v1",
      "extension_data": {}
    }
  }
}

FailureReport update

• Report: failure-report/Alive24-CKBoost-62
• Stage: Active diagnosis
• Status: investigating
• Severity: medium
• Repository: Alive24/CKBoost
• Immutable target revision: a2f98850862a8bc9ef9bb08c364ef6e8f03461a0
• Workpad revision: 3
• Diagnostic session: active
• Logical session: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62
• Authoritative entry: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-3
• Issue: Alive24/CKBoost#62
• Diagnostic session identity: diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec
• Canonical representation: inline folded snapshot

Active diagnosis

Current facts and evidence

• evidence-reported-timezone-ambiguity [reported] — The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time. Interpretation: The source paths must be inspected before distinguishing a data-semantics defect from a display-labeling gap. Public evidence: Timezone is unclear in campaign date inputs and displays #62.

Current hypotheses

• hypothesis-display-only [open] — Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.
• hypothesis-semantics-ambiguous [open] — Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.

Remaining unknowns

• Whether campaign dates are parsed and stored with consistent UTC or local-time semantics.
• Whether the defect is limited to missing display/input labeling.
• Which smallest remediation follows from the source behavior.

Canonical context — complete FailureReport snapshot

{
  "entry": {
    "schema_version": "failure-report-workpad-entry/v2",
    "producer": {
      "id": "failure-report-local",
      "github_actor_id": "20827211"
    },
    "logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
    "entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-3",
    "revision": 3
  },
  "failure_report": {
    "id": "failure-report/Alive24-CKBoost-62",
    "schema_version": "failure-report/v1",
    "status": "investigating",
    "created_at": "2026-07-30T14:43:58Z",
    "updated_at": "2026-07-30T14:51:37.401Z",
    "shared_context": {
      "provider": "github_issue",
      "repository": "Alive24/CKBoost",
      "issue_number": 62,
      "issue_url": "https://github.com/Alive24/CKBoost/issues/62",
      "workpad_marker": "<!-- failure-report-workpad -->",
      "workpad_comment_ref": "5132323099",
      "workpad_revision": 3,
      "workpad_logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
      "workpad_entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-3",
      "workpad_producer_id": "failure-report-local",
      "synced_at": "2026-07-30T14:51:37.401Z"
    },
    "diagnostic_session": {
      "lifecycle": "active",
      "domain_extensions": [],
      "backend_id": "codex_app_server",
      "codex_thread_id": "019fb37d-f822-7482-a0c0-50ee203c8358",
      "worktree": {
        "identity": "diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec",
        "base_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "head_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0"
      },
      "diagnostic_branch_slug": "timezone-is-unclear-in-campaign-date-inputs-and-displays",
      "last_diagnosed_at": "2026-07-30T14:51:37.401Z"
    },
    "diagnostic_completions": [
      {
        "schema_version": "failure-report/diagnostic-completion/v1",
        "completion_id": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
        "report_id": "failure-report/Alive24-CKBoost-62",
        "target_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "diagnostic_session_identity": "diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec",
        "codex_thread_id": "019fb37d-f822-7482-a0c0-50ee203c8358",
        "observed_worktree_head": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "outcome": {
          "evidence": [],
          "operation_evidence": [],
          "hypotheses": [],
          "experiments": []
        },
        "metadata": {
          "completed_at": "2026-07-30T14:51:37.401Z",
          "owner": "root",
          "provider": "codex_app_server",
          "provider_finish_reason": "completed"
        }
      }
    ],
    "origin": {
      "source": "github_issue",
      "reporter": "issue-author",
      "related_work": [
        {
          "kind": "github_issue",
          "ref": "https://github.com/Alive24/CKBoost/issues/62"
        }
      ]
    },
    "target": {
      "repository": "Alive24/CKBoost",
      "revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
      "components": [
        "campaign date input",
        "campaign date display"
      ],
      "environment": [
        {
          "name": "diagnostic_mode",
          "value": "focused non-mutating source inspection at bound revision"
        }
      ]
    },
    "severity": "medium",
    "symptom": {
      "observed_behavior": [
        "Campaign date inputs do not identify whether entered dates are UTC or local time.",
        "Campaign date displays do not identify whether rendered dates are UTC or local time.",
        "An operator cannot determine the exact campaign start or end instant from the UI."
      ],
      "expected_behavior": [
        "The timezone contract for campaign date entry, parsing/storage, and display is explicit.",
        "The UI communicates enough timezone information for an operator to determine exact campaign instants."
      ],
      "raw_error_summary": "Timezone is unclear in campaign date inputs and displays.",
      "first_seen_at": null,
      "reproduction": {
        "preconditions": [
          "Inspect repository revision a2f98850862a8bc9ef9bb08c364ef6e8f03461a0."
        ],
        "steps": [
          "Locate campaign date input and display paths.",
          "Trace parsing, serialization or storage, and rendering behavior.",
          "Run only focused non-mutating checks needed to verify current behavior."
        ],
        "frequency": "Reported as present in the current campaign creation and date-display paths."
      }
    },
    "inputs": [
      {
        "id": "input-issue-62",
        "kind": "github_issue",
        "artifact": {
          "ref": "https://github.com/Alive24/CKBoost/issues/62",
          "media_type": "text/markdown",
          "sensitivity": "public",
          "retention": "durable"
        },
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        }
      }
    ],
    "evidence": [
      {
        "id": "evidence-reported-timezone-ambiguity",
        "kind": "reported_observation",
        "observed_fact": "The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time.",
        "interpretation": "The source paths must be inspected before distinguishing a data-semantics defect from a display-labeling gap.",
        "epistemic_status": "reported",
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/issues/62",
            "media_type": "text/markdown",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      }
    ],
    "hypotheses": [
      {
        "id": "hypothesis-display-only",
        "statement": "Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.",
        "status": "open",
        "supporting_evidence": [],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "Plausible from the reported UI ambiguity, but no repository evidence has yet been collected.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          }
        ]
      },
      {
        "id": "hypothesis-semantics-ambiguous",
        "statement": "Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.",
        "status": "open",
        "supporting_evidence": [],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "The reported behavior does not establish whether the ambiguity is display-only or exists in the data path.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          }
        ]
      }
    ],
    "decisions": [
      {
        "id": "decision-diagnostic-only",
        "kind": "scope",
        "statement": "Perform one focused, non-mutating diagnosis; do not implement or route a change.",
        "status": "accepted",
        "authority": "human",
        "rationale": "The Issue defines this as a disposable diagnostic fixture and explicitly excludes implementation and routing.",
        "evidence_refs": [
          "evidence-reported-timezone-ambiguity"
        ],
        "provenance": {
          "phase": "human_decision",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "issue scope readback"
        }
      }
    ],
    "experiments": [],
    "conclusion": {
      "diagnosis": "Diagnosis pending focused inspection of campaign date input, parsing/storage, and display paths at the bound revision.",
      "confidence": {
        "level": "low",
        "basis": "Only the Issue's reported observation is currently available; no repository or runtime evidence has been collected."
      },
      "remaining_uncertainty": [
        "Whether campaign dates are parsed and stored with consistent UTC or local-time semantics.",
        "Whether the defect is limited to missing display/input labeling.",
        "Which smallest remediation follows from the source behavior."
      ],
      "recommended_remediation": []
    },
    "handoff": {
      "todo_status": "not_ready",
      "gate_decision": "Blocked",
      "uat_required": false,
      "goal": "Diagnose the campaign timezone contract without implementing or routing a change.",
      "why_now": "Operators reportedly cannot determine exact campaign start and end instants from current date entry and display behavior.",
      "scope_in": [
        "Inspect campaign date input, parsing/serialization or storage, and display paths at the immutable target revision.",
        "Run focused non-mutating checks needed to distinguish timezone semantics from a display-only gap."
      ],
      "scope_out": [
        "Code changes, commits, pull requests, or implementation routing.",
        "Broad unrelated application review."
      ],
      "guardrails": [
        "Use only the immutable target revision.",
        "Keep the diagnostic worktree clean.",
        "Treat Issue claims as reported until verified in repository or test evidence."
      ],
      "required_outcomes": [
        "Identify the current timezone contract or absence of one.",
        "Distinguish parsing/storage behavior from display labeling.",
        "Recommend the smallest evidence-backed remediation."
      ],
      "verification": {
        "automated": [
          "Run focused existing tests or non-mutating checks relevant to campaign date handling when available."
        ],
        "uat": [],
        "context": [
          "Cite source paths and focused check results in diagnostic evidence."
        ]
      },
      "residual_risks": []
    },
    "domain": {
      "pack_id": "failure-report/generic",
      "pack_version": "1",
      "schema_ref": "failure-report/v1",
      "extension_data": {}
    }
  }
}

[Alive24]

FailureReport update

• Report: failure-report/Alive24-CKBoost-62
• Stage: Completed diagnosis
• Status: diagnosed
• Severity: medium
• Repository: Alive24/CKBoost
• Immutable target revision: a2f98850862a8bc9ef9bb08c364ef6e8f03461a0
• Workpad revision: 4
• Diagnostic session: active
• Logical session: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62
• Authoritative entry: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-4
• Issue: Alive24/CKBoost#62
• Diagnostic session identity: diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec
• Canonical representation: inline folded snapshot

Completed diagnosis

Diagnosis

The campaign admin flow has a real timezone semantic bug: it hydrates datetime-local inputs with UTC ISO clock text and reparses that zone-less text as browser-local time, so an unchanged save shifts stored instants for non-UTC operators. Separately, campaign read views render viewer-local dates without a timezone label, creating display ambiguity and possible neighboring-day output.

Confidence

high — The diagnosis is supported by line-specific source evidence and a deterministic non-UTC round-trip reproduction with a zero-drift UTC control.

Key evidence

• evidence-reported-timezone-ambiguity [reported] — The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time. Interpretation: The report prompted inspection of both mutation and presentation paths. Public evidence: Timezone is unclear in campaign date inputs and displays #62.
• evidence-admin-utc-hydration [verified] — The campaign admin path hydrates existing start and end timestamps using toISOString() and truncates them for form input. Interpretation: UTC clock text is placed into a field whose semantics are local wall-clock time. Public evidence:

  CKBoost/dapp/app/campaign-admin/[campaignTypeId]/page.tsx

  Lines 766 to 771 in a2f9885

  	startDate: campaignData.starting_time
  	? new Date(Number(campaignData.starting_time) * 1000)
  	.toISOString()
  	.slice(0, 16)
  	: "",
  	endDate: campaignData.ending_time

  .
• evidence-local-input-and-save [verified] — The form uses input type datetime-local, while the save path converts its zone-less string with new Date(...).getTime(). Interpretation: The save path interprets the displayed clock value in the browser's local timezone. Public evidence:

  CKBoost/dapp/components/campaign-admin/campaign/campaign-form.tsx

  Line 387 in a2f9885

  <Label htmlFor="startDate">Start Date</Label>

  ,

  CKBoost/dapp/app/campaign-admin/[campaignTypeId]/page.tsx

  Line 1083 in a2f9885

  starting_time: campaignData.startDate

  .
• evidence-roundtrip-drift [verified] — Under TZ=America/Los_Angeles, stored 2025-01-01T00:00:00.000Z hydrates as 2025-01-01T00:00 and reparses as 2025-01-01T08:00:00.000Z, a +28800-second shift; the UTC control has zero shift. Interpretation: The admin edit round-trip mutates the stored instant for non-UTC operators even with no intentional date change.
• evidence-display-local-unlabeled [verified] — Campaign read paths produce UTC ISO values, but display paths use local calendar getters or toLocaleDateString without a timezone label. Interpretation: The display contract is viewer-local and unlabeled, so midnight-UTC instants can appear on a neighboring calendar date. Public evidence:

  CKBoost/dapp/lib/utils/campaign-utils.ts

  Line 107 in a2f9885

  const startDate = new Date(startTimestampMs).toISOString();

  ,

  CKBoost/packages/ssri-ckboost/src/logging/index.ts

  Line 274 in a2f9885

  export const formatDateConsistent = (dateString: string | Date): string => {

  ,

  CKBoost/dapp/components/campaign-card.tsx

  Lines 361 to 378 in a2f9885

  	Started: {formatDateConsistent(campaign.startDate)}
  	</span>
  	<span>Ends: {formatDateConsistent(campaign.endDate)}</span>
  	</div>
  	</div>
  	{/* Stats */}
  	<div className="grid grid-cols-2 gap-4 text-sm">
  	<div className="flex items-center gap-2 text-black dark:text-white">
  	<Users className="w-4 h-4 text-blue-400" />
  	<span>
  	{Number(campaign.total_completions || 0)} completions
  	</span>
  	</div>
  	<div className="flex items-center gap-2 text-black dark:text-white">
  	<Calendar className="w-4 h-4 text-orange-400" />
  	<span>
  	Ends {new Date(campaign.endDate).toLocaleDateString()}

  .
• evidence-no-targeted-tests [observed] — No targeted repository test coverage was found for campaign date timezone round-trips or the date display contract. Interpretation: Regression coverage should be added if implementation is ever authorized.

Remaining uncertainty

• Product policy does not state whether campaign displays should be explicitly viewer-local or consistently UTC; this does not change the confirmed mutation-path diagnosis.

Residual risks

• No targeted repository tests currently lock the timezone contract.
• Any future implementation must obtain a product decision on UTC versus explicitly viewer-local display.

Recommended remediation

• Hydrate datetime-local fields with local YYYY-MM-DDTHH:mm values rather than UTC toISOString().slice(0,16), while retaining local parsing on save.
• Apply the same local-wall-clock conversion to create defaults and edit hydration.
• Choose and document either explicit viewer-local or consistent UTC display semantics, then route all campaign date rendering through one formatter.
• Add timezone-sensitive regression tests for unchanged admin round-trips and displayed calendar dates.

Canonical context — complete FailureReport snapshot

{
  "entry": {
    "schema_version": "failure-report-workpad-entry/v2",
    "producer": {
      "id": "failure-report-local",
      "github_actor_id": "20827211"
    },
    "logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
    "entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-4",
    "revision": 4,
    "predecessor_comment_ref": "5132323099",
    "continuation_kind": "capacity"
  },
  "failure_report": {
    "id": "failure-report/Alive24-CKBoost-62",
    "schema_version": "failure-report/v1",
    "status": "diagnosed",
    "created_at": "2026-07-30T14:43:58Z",
    "updated_at": "2026-07-30T15:06:09.405Z",
    "shared_context": {
      "provider": "github_issue",
      "repository": "Alive24/CKBoost",
      "issue_number": 62,
      "issue_url": "https://github.com/Alive24/CKBoost/issues/62",
      "workpad_marker": "<!-- failure-report-workpad -->",
      "workpad_revision": 4,
      "workpad_logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
      "workpad_entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-4",
      "workpad_producer_id": "failure-report-local",
      "workpad_predecessor_comment_ref": "5132323099",
      "synced_at": "2026-07-30T15:06:09.405Z"
    },
    "diagnostic_session": {
      "lifecycle": "active",
      "domain_extensions": [],
      "backend_id": "codex_app_server",
      "codex_thread_id": "019fb37d-f822-7482-a0c0-50ee203c8358",
      "worktree": {
        "identity": "diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec",
        "base_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "head_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0"
      },
      "diagnostic_branch_slug": "timezone-is-unclear-in-campaign-date-inputs-and-displays",
      "last_diagnosed_at": "2026-07-30T14:51:37.401Z"
    },
    "diagnostic_completions": [
      {
        "schema_version": "failure-report/diagnostic-completion/v1",
        "completion_id": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
        "report_id": "failure-report/Alive24-CKBoost-62",
        "target_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "diagnostic_session_identity": "diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec",
        "codex_thread_id": "019fb37d-f822-7482-a0c0-50ee203c8358",
        "observed_worktree_head": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "outcome": {
          "evidence": [],
          "operation_evidence": [],
          "hypotheses": [],
          "experiments": []
        },
        "metadata": {
          "completed_at": "2026-07-30T14:51:37.401Z",
          "owner": "root",
          "provider": "codex_app_server",
          "provider_finish_reason": "completed"
        }
      }
    ],
    "origin": {
      "source": "github_issue",
      "reporter": "issue-author",
      "related_work": [
        {
          "kind": "github_issue",
          "ref": "https://github.com/Alive24/CKBoost/issues/62"
        },
        {
          "kind": "commit",
          "ref": "https://github.com/Alive24/CKBoost/commit/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0"
        }
      ]
    },
    "target": {
      "repository": "Alive24/CKBoost",
      "revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
      "components": [
        "campaign admin date hydration and save",
        "campaign date formatting and display"
      ],
      "environment": [
        {
          "name": "diagnostic_mode",
          "value": "focused non-mutating source inspection at bound revision"
        },
        {
          "name": "timezone_repro",
          "value": "America/Los_Angeles with UTC control"
        }
      ]
    },
    "severity": "medium",
    "symptom": {
      "observed_behavior": [
        "Campaign admin date fields can shift a stored instant when a non-UTC operator opens and saves without intentionally changing the date.",
        "Campaign date displays use viewer-local calendar formatting without identifying the timezone.",
        "An operator cannot reliably infer exact campaign start and end instants from the UI."
      ],
      "expected_behavior": [
        "Opening and saving unchanged campaign dates preserves the stored instants in every browser timezone.",
        "The timezone contract for campaign date entry and display is explicit and consistently applied."
      ],
      "raw_error_summary": "UTC ISO text is truncated into datetime-local fields and then reparsed as local time, causing timezone-dependent instant drift; read views also omit timezone labeling.",
      "first_seen_at": null,
      "reproduction": {
        "preconditions": [
          "Use revision a2f98850862a8bc9ef9bb08c364ef6e8f03461a0.",
          "Evaluate the date round-trip in a non-UTC timezone such as America/Los_Angeles."
        ],
        "steps": [
          "Start with stored epoch 1735689600, equal to 2025-01-01T00:00:00.000Z.",
          "Hydrate the form as new Date(stored*1000).toISOString().slice(0,16), producing 2025-01-01T00:00.",
          "Reparse the datetime-local string with new Date(input).getTime() as the save path does.",
          "Compare the resaved epoch and rendered local calendar date with the original."
        ],
        "frequency": "Deterministic for non-UTC browser timezones whose offset differs from UTC; the magnitude follows the applicable timezone offset."
      }
    },
    "inputs": [
      {
        "id": "input-issue-62",
        "kind": "github_issue",
        "artifact": {
          "ref": "https://github.com/Alive24/CKBoost/issues/62",
          "media_type": "text/markdown",
          "sensitivity": "public",
          "retention": "durable"
        },
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        }
      },
      {
        "id": "input-target-revision",
        "kind": "git_commit",
        "artifact": {
          "ref": "https://github.com/Alive24/CKBoost/commit/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "media_type": "text/html",
          "sensitivity": "public",
          "retention": "durable"
        },
        "provenance": {
          "phase": "investigation",
          "source_type": "repository",
          "source_ref": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "validated diagnostic session at immutable revision"
        }
      }
    ],
    "evidence": [
      {
        "id": "evidence-reported-timezone-ambiguity",
        "kind": "reported_observation",
        "observed_fact": "The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time.",
        "interpretation": "The report prompted inspection of both mutation and presentation paths.",
        "epistemic_status": "reported",
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/issues/62",
            "media_type": "text/markdown",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      },
      {
        "id": "evidence-admin-utc-hydration",
        "kind": "repository_fact",
        "observed_fact": "The campaign admin path hydrates existing start and end timestamps using toISOString() and truncates them for form input.",
        "interpretation": "UTC clock text is placed into a field whose semantics are local wall-clock time.",
        "epistemic_status": "verified",
        "provenance": {
          "phase": "investigation",
          "source_type": "repository",
          "source_ref": "dapp/app/campaign-admin/[campaignTypeId]/page.tsx:766-771@a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "diagnostic source inspection"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/app/campaign-admin/%5BcampaignTypeId%5D/page.tsx#L766-L771",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      },
      {
        "id": "evidence-local-input-and-save",
        "kind": "repository_fact",
        "observed_fact": "The form uses input type datetime-local, while the save path converts its zone-less string with new Date(...).getTime().",
        "interpretation": "The save path interprets the displayed clock value in the browser's local timezone.",
        "epistemic_status": "verified",
        "provenance": {
          "phase": "investigation",
          "source_type": "repository",
          "source_ref": "campaign-form.tsx:387 and page.tsx:1083@a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "diagnostic source inspection"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/components/campaign-admin/campaign/campaign-form.tsx#L387",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          },
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/app/campaign-admin/%5BcampaignTypeId%5D/page.tsx#L1083",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      },
      {
        "id": "evidence-roundtrip-drift",
        "kind": "tool_observation",
        "observed_fact": "Under TZ=America/Los_Angeles, stored 2025-01-01T00:00:00.000Z hydrates as 2025-01-01T00:00 and reparses as 2025-01-01T08:00:00.000Z, a +28800-second shift; the UTC control has zero shift.",
        "interpretation": "The admin edit round-trip mutates the stored instant for non-UTC operators even with no intentional date change.",
        "epistemic_status": "verified",
        "provenance": {
          "phase": "investigation",
          "source_type": "test",
          "source_ref": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "focused Node timezone reproduction with America/Los_Angeles and UTC control"
        },
        "artifacts": []
      },
      {
        "id": "evidence-display-local-unlabeled",
        "kind": "repository_fact",
        "observed_fact": "Campaign read paths produce UTC ISO values, but display paths use local calendar getters or toLocaleDateString without a timezone label.",
        "interpretation": "The display contract is viewer-local and unlabeled, so midnight-UTC instants can appear on a neighboring calendar date.",
        "epistemic_status": "verified",
        "provenance": {
          "phase": "investigation",
          "source_type": "repository",
          "source_ref": "campaign-utils.ts:107, logging/index.ts:274, campaign-card.tsx:361,378@a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "diagnostic source inspection and focused display reproduction"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/lib/utils/campaign-utils.ts#L107",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          },
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/packages/ssri-ckboost/src/logging/index.ts#L274",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          },
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/components/campaign-card.tsx#L361-L378",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      },
      {
        "id": "evidence-no-targeted-tests",
        "kind": "tool_observation",
        "observed_fact": "No targeted repository test coverage was found for campaign date timezone round-trips or the date display contract.",
        "interpretation": "Regression coverage should be added if implementation is ever authorized.",
        "epistemic_status": "observed",
        "provenance": {
          "phase": "investigation",
          "source_type": "agent",
          "source_ref": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "focused repository test search"
        },
        "artifacts": []
      }
    ],
    "hypotheses": [
      {
        "id": "hypothesis-display-only",
        "statement": "Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.",
        "status": "rejected",
        "supporting_evidence": [
          "evidence-display-local-unlabeled"
        ],
        "contradicting_evidence": [
          "evidence-admin-utc-hydration",
          "evidence-local-input-and-save",
          "evidence-roundtrip-drift"
        ],
        "history": [
          {
            "status": "open",
            "rationale": "Plausible from the reported UI ambiguity before source inspection.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          },
          {
            "status": "rejected",
            "rationale": "The display gap exists, but focused reproduction proves the admin edit path also changes the stored instant outside UTC.",
            "provenance": {
              "phase": "investigation",
              "source_type": "test",
              "source_ref": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
              "collector": "root",
              "collected_at": "2026-07-30T15:00:45Z",
              "method": "hypothesis update from source and focused repro"
            }
          }
        ]
      },
      {
        "id": "hypothesis-semantics-ambiguous",
        "statement": "Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.",
        "status": "confirmed",
        "supporting_evidence": [
          "evidence-admin-utc-hydration",
          "evidence-local-input-and-save",
          "evidence-roundtrip-drift"
        ],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "The reported behavior did not establish whether ambiguity extended into the mutation path.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          },
          {
            "status": "confirmed",
            "rationale": "The edit path combines UTC-formatted hydration with local-time parsing, and the non-UTC reproduction verifies deterministic instant drift.",
            "provenance": {
              "phase": "investigation",
              "source_type": "test",
              "source_ref": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
              "collector": "root",
              "collected_at": "2026-07-30T15:00:45Z",
              "method": "hypothesis update from source and focused repro"
            }
          }
        ]
      }
    ],
    "decisions": [
      {
        "id": "decision-diagnostic-only",
        "kind": "scope",
        "statement": "Perform one focused, non-mutating diagnosis; do not implement or route a change.",
        "status": "accepted",
        "authority": "human",
        "rationale": "The Issue defines this as a disposable diagnostic fixture and explicitly excludes implementation and routing.",
        "evidence_refs": [
          "evidence-reported-timezone-ambiguity"
        ],
        "provenance": {
          "phase": "human_decision",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "issue scope readback"
        }
      }
    ],
    "experiments": [
      {
        "id": "experiment-timezone-roundtrip",
        "question": "Does unchanged admin hydration and save preserve the stored instant outside UTC?",
        "proposed_action": "Apply the source's ISO truncation and local Date parsing sequence to a fixed epoch under America/Los_Angeles, with UTC as a control.",
        "approval": {
          "required": false,
          "status": "not_required"
        },
        "baseline_evidence": [
          "evidence-admin-utc-hydration",
          "evidence-local-input-and-save"
        ],
        "result_evidence": [
          "evidence-roundtrip-drift"
        ],
        "outcome": "confirmed",
        "interpretation": "The path shifts the instant by the browser timezone offset outside UTC, proving a semantic round-trip defect."
      },
      {
        "id": "experiment-display-calendar-date",
        "question": "Can the shared local display behavior show a different calendar day than the UTC instant?",
        "proposed_action": "Format 2025-01-01T00:00:00.000Z under America/Los_Angeles using the observed local-date behavior.",
        "approval": {
          "required": false,
          "status": "not_required"
        },
        "baseline_evidence": [
          "evidence-display-local-unlabeled"
        ],
        "result_evidence": [
          "evidence-display-local-unlabeled"
        ],
        "outcome": "confirmed",
        "interpretation": "The instant displays as 12/31/2024 without a timezone label, confirming the separate presentation ambiguity."
      }
    ],
    "conclusion": {
      "diagnosis": "The campaign admin flow has a real timezone semantic bug: it hydrates datetime-local inputs with UTC ISO clock text and reparses that zone-less text as browser-local time, so an unchanged save shifts stored instants for non-UTC operators. Separately, campaign read views render viewer-local dates without a timezone label, creating display ambiguity and possible neighboring-day output.",
      "confidence": {
        "level": "high",
        "basis": "The diagnosis is supported by line-specific source evidence and a deterministic non-UTC round-trip reproduction with a zero-drift UTC control."
      },
      "remaining_uncertainty": [
        "Product policy does not state whether campaign displays should be explicitly viewer-local or consistently UTC; this does not change the confirmed mutation-path diagnosis."
      ],
      "recommended_remediation": [
        "Hydrate datetime-local fields with local YYYY-MM-DDTHH:mm values rather than UTC toISOString().slice(0,16), while retaining local parsing on save.",
        "Apply the same local-wall-clock conversion to create defaults and edit hydration.",
        "Choose and document either explicit viewer-local or consistent UTC display semantics, then route all campaign date rendering through one formatter.",
        "Add timezone-sensitive regression tests for unchanged admin round-trips and displayed calendar dates."
      ]
    },
    "handoff": {
      "todo_status": "not_ready",
      "gate_decision": "Blocked",
      "uat_required": false,
      "goal": "Record a complete diagnostic result without initiating implementation.",
      "why_now": "The operator requested one real diagnosis for a disposable fixture and explicitly excluded implementation or downstream routing.",
      "scope_in": [
        "Preserve the verified diagnosis, source evidence, focused reproductions, and smallest remediation recommendations."
      ],
      "scope_out": [
        "Implementation, commits, pull requests, handoff delivery, or tracker routing.",
        "Choosing product policy for UTC versus explicitly viewer-local display."
      ],
      "guardrails": [
        "Keep the diagnostic snapshot clean and diagnostic-only.",
        "Do not treat the diagnostic branch as a coding branch.",
        "Do not route this fixture into an implementation lane."
      ],
      "required_outcomes": [
        "Persist the semantic round-trip diagnosis and the separate display ambiguity.",
        "Finalize the clean diagnostic snapshot only after the diagnosis is durable."
      ],
      "verification": {
        "automated": [
          "Focused America/Los_Angeles round-trip reproduction shows +28800 seconds; UTC control shows zero.",
          "Focused display reproduction shows a midnight UTC instant as the prior local calendar date."
        ],
        "uat": [],
        "context": [
          "Source references identify hydration, datetime-local input, save parsing, and display formatting paths."
        ]
      },
      "residual_risks": [
        "No targeted repository tests currently lock the timezone contract.",
        "Any future implementation must obtain a product decision on UTC versus explicitly viewer-local display."
      ]
    },
    "domain": {
      "pack_id": "failure-report/generic",
      "pack_version": "1",
      "schema_ref": "failure-report/v1",
      "extension_data": {}
    }
  }
}

[Alive24]

FailureReport update

• Report: failure-report/Alive24-CKBoost-62
• Stage: Completed diagnosis
• Status: diagnosed
• Severity: medium
• Repository: Alive24/CKBoost
• Immutable target revision: a2f98850862a8bc9ef9bb08c364ef6e8f03461a0
• Workpad revision: 5
• Diagnostic session: finalized
• Logical session: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62
• Authoritative entry: github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-5
• Issue: Alive24/CKBoost#62
• Diagnostic session identity: diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec
• Canonical representation: inline folded snapshot

Completed diagnosis

Diagnosis

The campaign admin flow has a real timezone semantic bug: it hydrates datetime-local inputs with UTC ISO clock text and reparses that zone-less text as browser-local time, so an unchanged save shifts stored instants for non-UTC operators. Separately, campaign read views render viewer-local dates without a timezone label, creating display ambiguity and possible neighboring-day output.

Confidence

high — The diagnosis is supported by line-specific source evidence and a deterministic non-UTC round-trip reproduction with a zero-drift UTC control.

Key evidence

• evidence-reported-timezone-ambiguity [reported] — The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time. Interpretation: The report prompted inspection of both mutation and presentation paths. Public evidence: Timezone is unclear in campaign date inputs and displays #62.
• evidence-admin-utc-hydration [verified] — The campaign admin path hydrates existing start and end timestamps using toISOString() and truncates them for form input. Interpretation: UTC clock text is placed into a field whose semantics are local wall-clock time. Public evidence:

  CKBoost/dapp/app/campaign-admin/[campaignTypeId]/page.tsx

  Lines 766 to 771 in a2f9885

  	startDate: campaignData.starting_time
  	? new Date(Number(campaignData.starting_time) * 1000)
  	.toISOString()
  	.slice(0, 16)
  	: "",
  	endDate: campaignData.ending_time

  .
• evidence-local-input-and-save [verified] — The form uses input type datetime-local, while the save path converts its zone-less string with new Date(...).getTime(). Interpretation: The save path interprets the displayed clock value in the browser's local timezone. Public evidence:

  CKBoost/dapp/components/campaign-admin/campaign/campaign-form.tsx

  Line 387 in a2f9885

  <Label htmlFor="startDate">Start Date</Label>

  ,

  CKBoost/dapp/app/campaign-admin/[campaignTypeId]/page.tsx

  Line 1083 in a2f9885

  starting_time: campaignData.startDate

  .
• evidence-roundtrip-drift [verified] — Under TZ=America/Los_Angeles, stored 2025-01-01T00:00:00.000Z hydrates as 2025-01-01T00:00 and reparses as 2025-01-01T08:00:00.000Z, a +28800-second shift; the UTC control has zero shift. Interpretation: The admin edit round-trip mutates the stored instant for non-UTC operators even with no intentional date change.
• evidence-display-local-unlabeled [verified] — Campaign read paths produce UTC ISO values, but display paths use local calendar getters or toLocaleDateString without a timezone label. Interpretation: The display contract is viewer-local and unlabeled, so midnight-UTC instants can appear on a neighboring calendar date. Public evidence:

  CKBoost/dapp/lib/utils/campaign-utils.ts

  Line 107 in a2f9885

  const startDate = new Date(startTimestampMs).toISOString();

  ,

  CKBoost/packages/ssri-ckboost/src/logging/index.ts

  Line 274 in a2f9885

  export const formatDateConsistent = (dateString: string | Date): string => {

  ,

  CKBoost/dapp/components/campaign-card.tsx

  Lines 361 to 378 in a2f9885

  	Started: {formatDateConsistent(campaign.startDate)}
  	</span>
  	<span>Ends: {formatDateConsistent(campaign.endDate)}</span>
  	</div>
  	</div>
  	{/* Stats */}
  	<div className="grid grid-cols-2 gap-4 text-sm">
  	<div className="flex items-center gap-2 text-black dark:text-white">
  	<Users className="w-4 h-4 text-blue-400" />
  	<span>
  	{Number(campaign.total_completions || 0)} completions
  	</span>
  	</div>
  	<div className="flex items-center gap-2 text-black dark:text-white">
  	<Calendar className="w-4 h-4 text-orange-400" />
  	<span>
  	Ends {new Date(campaign.endDate).toLocaleDateString()}

  .
• evidence-no-targeted-tests [observed] — No targeted repository test coverage was found for campaign date timezone round-trips or the date display contract. Interpretation: Regression coverage should be added if implementation is ever authorized.

Remaining uncertainty

• Product policy does not state whether campaign displays should be explicitly viewer-local or consistently UTC; this does not change the confirmed mutation-path diagnosis.

Residual risks

• No targeted repository tests currently lock the timezone contract.
• Any future implementation must obtain a product decision on UTC versus explicitly viewer-local display.

Recommended remediation

• Hydrate datetime-local fields with local YYYY-MM-DDTHH:mm values rather than UTC toISOString().slice(0,16), while retaining local parsing on save.
• Apply the same local-wall-clock conversion to create defaults and edit hydration.
• Choose and document either explicit viewer-local or consistent UTC display semantics, then route all campaign date rendering through one formatter.
• Add timezone-sensitive regression tests for unchanged admin round-trips and displayed calendar dates.

Diagnostic snapshot

• Branch: diagnostic/62-timezone-is-unclear-in-campaign-date-inputs-and-displays (diagnostic_snapshot_only)
• Immutable snapshot revision: a2f98850862a8bc9ef9bb08c364ef6e8f03461a0

Canonical context — complete FailureReport snapshot

{
  "entry": {
    "schema_version": "failure-report-workpad-entry/v2",
    "producer": {
      "id": "failure-report-local",
      "github_actor_id": "20827211"
    },
    "logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
    "entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-5",
    "revision": 5,
    "predecessor_comment_ref": "5132581225",
    "continuation_kind": "capacity"
  },
  "failure_report": {
    "id": "failure-report/Alive24-CKBoost-62",
    "schema_version": "failure-report/v1",
    "status": "diagnosed",
    "created_at": "2026-07-30T14:43:58Z",
    "updated_at": "2026-07-30T15:06:35.661Z",
    "shared_context": {
      "provider": "github_issue",
      "repository": "Alive24/CKBoost",
      "issue_number": 62,
      "issue_url": "https://github.com/Alive24/CKBoost/issues/62",
      "workpad_marker": "<!-- failure-report-workpad -->",
      "workpad_revision": 5,
      "workpad_logical_session_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62",
      "workpad_entry_id": "github-issue/Alive24/CKBoost/62/failure-report/Alive24-CKBoost-62/revision-5",
      "workpad_producer_id": "failure-report-local",
      "workpad_predecessor_comment_ref": "5132581225",
      "synced_at": "2026-07-30T15:06:35.661Z"
    },
    "diagnostic_session": {
      "lifecycle": "finalized",
      "domain_extensions": [],
      "backend_id": "codex_app_server",
      "codex_thread_id": "019fb37d-f822-7482-a0c0-50ee203c8358",
      "worktree": {
        "identity": "diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec",
        "base_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "head_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0"
      },
      "diagnostic_branch_slug": "timezone-is-unclear-in-campaign-date-inputs-and-displays",
      "diagnostic_branch": {
        "name": "diagnostic/62-timezone-is-unclear-in-campaign-date-inputs-and-displays",
        "head_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "remote_name": "origin",
        "remote_ref": "refs/heads/diagnostic/62-timezone-is-unclear-in-campaign-date-inputs-and-displays",
        "remote_url": "https://github.com/Alive24/CKBoost/tree/diagnostic/62-timezone-is-unclear-in-campaign-date-inputs-and-displays",
        "pushed_at": "2026-07-30T15:06:32.379Z",
        "finalized_at": "2026-07-30T15:06:32.379Z",
        "reuse_policy": "diagnostic_snapshot_only"
      },
      "last_diagnosed_at": "2026-07-30T14:51:37.401Z"
    },
    "diagnostic_completions": [
      {
        "schema_version": "failure-report/diagnostic-completion/v1",
        "completion_id": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
        "report_id": "failure-report/Alive24-CKBoost-62",
        "target_revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "diagnostic_session_identity": "diagnostic-failure-report-Alive24-CKBoost-62-8598506d5dec",
        "codex_thread_id": "019fb37d-f822-7482-a0c0-50ee203c8358",
        "observed_worktree_head": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
        "outcome": {
          "evidence": [],
          "operation_evidence": [],
          "hypotheses": [],
          "experiments": []
        },
        "metadata": {
          "completed_at": "2026-07-30T14:51:37.401Z",
          "owner": "root",
          "provider": "codex_app_server",
          "provider_finish_reason": "completed"
        }
      }
    ],
    "origin": {
      "source": "github_issue",
      "reporter": "issue-author",
      "related_work": [
        {
          "kind": "github_issue",
          "ref": "https://github.com/Alive24/CKBoost/issues/62"
        },
        {
          "kind": "commit",
          "ref": "https://github.com/Alive24/CKBoost/commit/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0"
        }
      ]
    },
    "target": {
      "repository": "Alive24/CKBoost",
      "revision": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
      "components": [
        "campaign admin date hydration and save",
        "campaign date formatting and display"
      ],
      "environment": [
        {
          "name": "diagnostic_mode",
          "value": "focused non-mutating source inspection at bound revision"
        },
        {
          "name": "timezone_repro",
          "value": "America/Los_Angeles with UTC control"
        }
      ]
    },
    "severity": "medium",
    "symptom": {
      "observed_behavior": [
        "Campaign admin date fields can shift a stored instant when a non-UTC operator opens and saves without intentionally changing the date.",
        "Campaign date displays use viewer-local calendar formatting without identifying the timezone.",
        "An operator cannot reliably infer exact campaign start and end instants from the UI."
      ],
      "expected_behavior": [
        "Opening and saving unchanged campaign dates preserves the stored instants in every browser timezone.",
        "The timezone contract for campaign date entry and display is explicit and consistently applied."
      ],
      "raw_error_summary": "UTC ISO text is truncated into datetime-local fields and then reparsed as local time, causing timezone-dependent instant drift; read views also omit timezone labeling.",
      "first_seen_at": null,
      "reproduction": {
        "preconditions": [
          "Use revision a2f98850862a8bc9ef9bb08c364ef6e8f03461a0.",
          "Evaluate the date round-trip in a non-UTC timezone such as America/Los_Angeles."
        ],
        "steps": [
          "Start with stored epoch 1735689600, equal to 2025-01-01T00:00:00.000Z.",
          "Hydrate the form as new Date(stored*1000).toISOString().slice(0,16), producing 2025-01-01T00:00.",
          "Reparse the datetime-local string with new Date(input).getTime() as the save path does.",
          "Compare the resaved epoch and rendered local calendar date with the original."
        ],
        "frequency": "Deterministic for non-UTC browser timezones whose offset differs from UTC; the magnitude follows the applicable timezone offset."
      }
    },
    "inputs": [
      {
        "id": "input-issue-62",
        "kind": "github_issue",
        "artifact": {
          "ref": "https://github.com/Alive24/CKBoost/issues/62",
          "media_type": "text/markdown",
          "sensitivity": "public",
          "retention": "durable"
        },
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        }
      },
      {
        "id": "input-target-revision",
        "kind": "git_commit",
        "artifact": {
          "ref": "https://github.com/Alive24/CKBoost/commit/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "media_type": "text/html",
          "sensitivity": "public",
          "retention": "durable"
        },
        "provenance": {
          "phase": "investigation",
          "source_type": "repository",
          "source_ref": "a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "validated diagnostic session at immutable revision"
        }
      }
    ],
    "evidence": [
      {
        "id": "evidence-reported-timezone-ambiguity",
        "kind": "reported_observation",
        "observed_fact": "The issue reports that campaign creation inputs and campaign-date displays do not state whether dates are UTC or local time.",
        "interpretation": "The report prompted inspection of both mutation and presentation paths.",
        "epistemic_status": "reported",
        "provenance": {
          "phase": "intake",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "read_shared_context"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/issues/62",
            "media_type": "text/markdown",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      },
      {
        "id": "evidence-admin-utc-hydration",
        "kind": "repository_fact",
        "observed_fact": "The campaign admin path hydrates existing start and end timestamps using toISOString() and truncates them for form input.",
        "interpretation": "UTC clock text is placed into a field whose semantics are local wall-clock time.",
        "epistemic_status": "verified",
        "provenance": {
          "phase": "investigation",
          "source_type": "repository",
          "source_ref": "dapp/app/campaign-admin/[campaignTypeId]/page.tsx:766-771@a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "diagnostic source inspection"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/app/campaign-admin/%5BcampaignTypeId%5D/page.tsx#L766-L771",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      },
      {
        "id": "evidence-local-input-and-save",
        "kind": "repository_fact",
        "observed_fact": "The form uses input type datetime-local, while the save path converts its zone-less string with new Date(...).getTime().",
        "interpretation": "The save path interprets the displayed clock value in the browser's local timezone.",
        "epistemic_status": "verified",
        "provenance": {
          "phase": "investigation",
          "source_type": "repository",
          "source_ref": "campaign-form.tsx:387 and page.tsx:1083@a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "diagnostic source inspection"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/components/campaign-admin/campaign/campaign-form.tsx#L387",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          },
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/app/campaign-admin/%5BcampaignTypeId%5D/page.tsx#L1083",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      },
      {
        "id": "evidence-roundtrip-drift",
        "kind": "tool_observation",
        "observed_fact": "Under TZ=America/Los_Angeles, stored 2025-01-01T00:00:00.000Z hydrates as 2025-01-01T00:00 and reparses as 2025-01-01T08:00:00.000Z, a +28800-second shift; the UTC control has zero shift.",
        "interpretation": "The admin edit round-trip mutates the stored instant for non-UTC operators even with no intentional date change.",
        "epistemic_status": "verified",
        "provenance": {
          "phase": "investigation",
          "source_type": "test",
          "source_ref": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "focused Node timezone reproduction with America/Los_Angeles and UTC control"
        },
        "artifacts": []
      },
      {
        "id": "evidence-display-local-unlabeled",
        "kind": "repository_fact",
        "observed_fact": "Campaign read paths produce UTC ISO values, but display paths use local calendar getters or toLocaleDateString without a timezone label.",
        "interpretation": "The display contract is viewer-local and unlabeled, so midnight-UTC instants can appear on a neighboring calendar date.",
        "epistemic_status": "verified",
        "provenance": {
          "phase": "investigation",
          "source_type": "repository",
          "source_ref": "campaign-utils.ts:107, logging/index.ts:274, campaign-card.tsx:361,378@a2f98850862a8bc9ef9bb08c364ef6e8f03461a0",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "diagnostic source inspection and focused display reproduction"
        },
        "artifacts": [
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/lib/utils/campaign-utils.ts#L107",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          },
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/packages/ssri-ckboost/src/logging/index.ts#L274",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          },
          {
            "ref": "https://github.com/Alive24/CKBoost/blob/a2f98850862a8bc9ef9bb08c364ef6e8f03461a0/dapp/components/campaign-card.tsx#L361-L378",
            "media_type": "text/plain",
            "sensitivity": "public",
            "retention": "durable"
          }
        ]
      },
      {
        "id": "evidence-no-targeted-tests",
        "kind": "tool_observation",
        "observed_fact": "No targeted repository test coverage was found for campaign date timezone round-trips or the date display contract.",
        "interpretation": "Regression coverage should be added if implementation is ever authorized.",
        "epistemic_status": "observed",
        "provenance": {
          "phase": "investigation",
          "source_type": "agent",
          "source_ref": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
          "collector": "root",
          "collected_at": "2026-07-30T15:00:45Z",
          "method": "focused repository test search"
        },
        "artifacts": []
      }
    ],
    "hypotheses": [
      {
        "id": "hypothesis-display-only",
        "statement": "Campaign instants have consistent timezone semantics internally, but the UI omits an explicit timezone label.",
        "status": "rejected",
        "supporting_evidence": [
          "evidence-display-local-unlabeled"
        ],
        "contradicting_evidence": [
          "evidence-admin-utc-hydration",
          "evidence-local-input-and-save",
          "evidence-roundtrip-drift"
        ],
        "history": [
          {
            "status": "open",
            "rationale": "Plausible from the reported UI ambiguity before source inspection.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          },
          {
            "status": "rejected",
            "rationale": "The display gap exists, but focused reproduction proves the admin edit path also changes the stored instant outside UTC.",
            "provenance": {
              "phase": "investigation",
              "source_type": "test",
              "source_ref": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
              "collector": "root",
              "collected_at": "2026-07-30T15:00:45Z",
              "method": "hypothesis update from source and focused repro"
            }
          }
        ]
      },
      {
        "id": "hypothesis-semantics-ambiguous",
        "statement": "Campaign date parsing, serialization, or storage has no consistent timezone contract, so remediation must extend beyond display labeling.",
        "status": "confirmed",
        "supporting_evidence": [
          "evidence-admin-utc-hydration",
          "evidence-local-input-and-save",
          "evidence-roundtrip-drift"
        ],
        "contradicting_evidence": [],
        "history": [
          {
            "status": "open",
            "rationale": "The reported behavior did not establish whether ambiguity extended into the mutation path.",
            "provenance": {
              "phase": "intake",
              "source_type": "issue",
              "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
              "collector": "root",
              "collected_at": "2026-07-30T14:43:58Z",
              "method": "intake hypothesis formation"
            }
          },
          {
            "status": "confirmed",
            "rationale": "The edit path combines UTC-formatted hydration with local-time parsing, and the non-UTC reproduction verifies deterministic instant drift.",
            "provenance": {
              "phase": "investigation",
              "source_type": "test",
              "source_ref": "diagnostic-completion/56c2e3c759d28d2db4d78602f0cb1fea59946238d9763d6942e0df64aa533e73",
              "collector": "root",
              "collected_at": "2026-07-30T15:00:45Z",
              "method": "hypothesis update from source and focused repro"
            }
          }
        ]
      }
    ],
    "decisions": [
      {
        "id": "decision-diagnostic-only",
        "kind": "scope",
        "statement": "Perform one focused, non-mutating diagnosis; do not implement or route a change.",
        "status": "accepted",
        "authority": "human",
        "rationale": "The Issue defines this as a disposable diagnostic fixture and explicitly excludes implementation and routing.",
        "evidence_refs": [
          "evidence-reported-timezone-ambiguity"
        ],
        "provenance": {
          "phase": "human_decision",
          "source_type": "issue",
          "source_ref": "https://github.com/Alive24/CKBoost/issues/62",
          "collector": "root",
          "collected_at": "2026-07-30T14:43:58Z",
          "method": "issue scope readback"
        }
      }
    ],
    "experiments": [
      {
        "id": "experiment-timezone-roundtrip",
        "question": "Does unchanged admin hydration and save preserve the stored instant outside UTC?",
        "proposed_action": "Apply the source's ISO truncation and local Date parsing sequence to a fixed epoch under America/Los_Angeles, with UTC as a control.",
        "approval": {
          "required": false,
          "status": "not_required"
        },
        "baseline_evidence": [
          "evidence-admin-utc-hydration",
          "evidence-local-input-and-save"
        ],
        "result_evidence": [
          "evidence-roundtrip-drift"
        ],
        "outcome": "confirmed",
        "interpretation": "The path shifts the instant by the browser timezone offset outside UTC, proving a semantic round-trip defect."
      },
      {
        "id": "experiment-display-calendar-date",
        "question": "Can the shared local display behavior show a different calendar day than the UTC instant?",
        "proposed_action": "Format 2025-01-01T00:00:00.000Z under America/Los_Angeles using the observed local-date behavior.",
        "approval": {
          "required": false,
          "status": "not_required"
        },
        "baseline_evidence": [
          "evidence-display-local-unlabeled"
        ],
        "result_evidence": [
          "evidence-display-local-unlabeled"
        ],
        "outcome": "confirmed",
        "interpretation": "The instant displays as 12/31/2024 without a timezone label, confirming the separate presentation ambiguity."
      }
    ],
    "conclusion": {
      "diagnosis": "The campaign admin flow has a real timezone semantic bug: it hydrates datetime-local inputs with UTC ISO clock text and reparses that zone-less text as browser-local time, so an unchanged save shifts stored instants for non-UTC operators. Separately, campaign read views render viewer-local dates without a timezone label, creating display ambiguity and possible neighboring-day output.",
      "confidence": {
        "level": "high",
        "basis": "The diagnosis is supported by line-specific source evidence and a deterministic non-UTC round-trip reproduction with a zero-drift UTC control."
      },
      "remaining_uncertainty": [
        "Product policy does not state whether campaign displays should be explicitly viewer-local or consistently UTC; this does not change the confirmed mutation-path diagnosis."
      ],
      "recommended_remediation": [
        "Hydrate datetime-local fields with local YYYY-MM-DDTHH:mm values rather than UTC toISOString().slice(0,16), while retaining local parsing on save.",
        "Apply the same local-wall-clock conversion to create defaults and edit hydration.",
        "Choose and document either explicit viewer-local or consistent UTC display semantics, then route all campaign date rendering through one formatter.",
        "Add timezone-sensitive regression tests for unchanged admin round-trips and displayed calendar dates."
      ]
    },
    "handoff": {
      "todo_status": "not_ready",
      "gate_decision": "Blocked",
      "uat_required": false,
      "goal": "Record a complete diagnostic result without initiating implementation.",
      "why_now": "The operator requested one real diagnosis for a disposable fixture and explicitly excluded implementation or downstream routing.",
      "scope_in": [
        "Preserve the verified diagnosis, source evidence, focused reproductions, and smallest remediation recommendations."
      ],
      "scope_out": [
        "Implementation, commits, pull requests, handoff delivery, or tracker routing.",
        "Choosing product policy for UTC versus explicitly viewer-local display."
      ],
      "guardrails": [
        "Keep the diagnostic snapshot clean and diagnostic-only.",
        "Do not treat the diagnostic branch as a coding branch.",
        "Do not route this fixture into an implementation lane."
      ],
      "required_outcomes": [
        "Persist the semantic round-trip diagnosis and the separate display ambiguity.",
        "Finalize the clean diagnostic snapshot only after the diagnosis is durable."
      ],
      "verification": {
        "automated": [
          "Focused America/Los_Angeles round-trip reproduction shows +28800 seconds; UTC control shows zero.",
          "Focused display reproduction shows a midnight UTC instant as the prior local calendar date."
        ],
        "uat": [],
        "context": [
          "Source references identify hydration, datetime-local input, save parsing, and display formatting paths."
        ]
      },
      "residual_risks": [
        "No targeted repository tests currently lock the timezone contract.",
        "Any future implementation must obtain a product decision on UTC versus explicitly viewer-local display."
      ]
    },
    "domain": {
      "pack_id": "failure-report/generic",
      "pack_version": "1",
      "schema_ref": "failure-report/v1",
      "extension_data": {}
    }
  }
}