Follow-up from review
The Versioned Dataset Contract accepts 15m, but the collector/export path is still hard-coded around ES RTH 5-minute datasets.
What to build
Add end-to-end support for 15-minute ES RTH datasets as the secondary comparison interval described in the PRD.
Acceptance criteria
Context
Review finding: the contract validator accepts 15m, but buildEsRth5mDataset / collectEsRth5mDataset and the example command are 5m-specific.
Related PRD story: "I want 15-minute bars supported as a secondary comparison interval."
Follow-up from review
The Versioned Dataset Contract accepts
15m, but the collector/export path is still hard-coded around ES RTH 5-minute datasets.What to build
Add end-to-end support for 15-minute ES RTH datasets as the secondary comparison interval described in the PRD.
Acceptance criteria
bar.intervalas15mand keeps the same symbol/session/continuous futures metadata expectations as the 5m path.Context
Review finding: the contract validator accepts
15m, butbuildEsRth5mDataset/collectEsRth5mDatasetand the example command are 5m-specific.Related PRD story: "I want 15-minute bars supported as a secondary comparison interval."