[stefan-jansen]

BarAggregator must retain the configured interval across hour and date boundaries. Align starts to fixed UTC intervals from the Unix epoch. The previous hour-based truncation split 90-minute OHLCV; a midnight-based repair still emitted overlapping 100-minute intervals when trades crossed a UTC date.

Closes #120. Resolves the aggregation part of #111. Retains the original 90-minute regression from #112 by quantum-like/Cursor Agent and completes the interval fix.

Public regression commands:

• uv run pytest -q tests/unit/test_bar_aggregator.py -k 'bar_windows or boundary_and_shutdown'
• uv run pytest -q tests/unit/test_bar_aggregator.py

Evidence:

• Producing base 2ad36a8 emits three hourly windows instead of the expected two 90-minute windows at 10:30 and 12:00, with incorrect OHLCV grouping.
• Partial producer 1af9309 passes the hour and shutdown controls but fails the unchanged midnight regression: its first bar ends at 01:00 while the next starts at 00:00. Valid typed trades drive the real public aggregator.
• Fix 69f3fa8 passes all 15 aggregator tests in 1.81s, including exact timestamps, non-overlapping metadata and OHLCV for both interval sizes. Ruff, formatting, ty and all commit hooks pass. The feed guide documents the UTC origin.
• Current head 462a163 integrates merged IB main. Its aggregation source, regressions and guide are identical to the tested fix. Full current-head stable, ecosystem and strict-docs qualification remains required before merge.

No release or credentialed provider qualification is included.

AI assistance: Cursor prepared the original contribution; Codex reproduced both boundary failures, completed the interval algorithm, documented its origin and ran verification.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[stefan-jansen]

Superseded by the combined maintainer-directed maintenance PR #121 to avoid qualifying and merging this queue separately. This PR head and its regression/documentation evidence are preserved in #121 and in a verified recovery archive. The accepted issue remains open until the combined fix lands; this closure does not claim the fix is merged. Follow-up work continues in #121.