fix: scan all events for first non-None timestamp in session_start fallback (#1182)

[microsasa]

Closes #1182

Problem

In render_session_detail, when summary.start_time is None and events[0].timestamp is None, the fallback was datetime.now(tz=UTC). This caused all past event timestamps to display +0:00 in the relative-time column — a silent data-loss bug.

Fix

Replace the events[0]-only check with next() to scan all events for the first non-None timestamp:

session_start = (
    ensure_aware(summary.start_time)
    if summary.start_time is not None
    else next(
        (ensure_aware(ev.timestamp) for ev in events if ev.timestamp is not None),
        datetime.now(tz=UTC),
    )
)

datetime.now(tz=UTC) remains the final fallback only when no event has a timestamp.

Test

Adds TestRenderSessionDetailFirstNoneTimestampFallback with a 3-event scenario:

• events[0].timestamp = None
• events[1].timestamp = T
• events[2].timestamp = T + 5min

Asserts +5:00 and +0:00 appear in the rendered output, confirming events[1] anchors the timeline.

Warning

⚠️ Firewall blocked 3 domains

The following domains were blocked by the firewall during workflow execution:

• astral.sh
• pypi.org
• releaseassets.githubusercontent.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "astral.sh"
    - "pypi.org"
    - "releaseassets.githubusercontent.com"

See Network Configuration for more information.

Generated by Issue Implementer · ● 9.5M · ◷

[Copilot]

Pull request overview

Fixes a rendering bug in copilot_usage session detail output where, if SessionSummary.start_time is None and the first event has timestamp=None, the timeline anchor incorrectly fell back to datetime.now(tz=UTC), causing past events’ relative-time deltas to clamp to +0:00.

Changes:

• Update render_session_detail to scan all events for the first non-None timestamp (via next(...)) before falling back to datetime.now(tz=UTC).
• Add a regression test covering the “first event timestamp is None, later events have timestamps” scenario to ensure +5:00 renders correctly.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/copilot_usage/render_detail.py	Fixes session_start fallback to use the first available event timestamp (not just events[0]).
tests/copilot_usage/test_render_detail.py	Adds regression coverage to confirm relative-time anchoring uses the first non-None event timestamp.