Gud Boi
eed5856622
A one-day MNQ schedule reply can start in the next session, leaving the gap's earlier trading hours uncovered. Widen `Client.history_schedule()` lookbacks up to 31 days, keeping the requested end fixed and sharing one timeout across attempts. Preserve unknown coverage when widening cannot cover the range. Share `SECONDS_PER_DAY` between query and reservation arithmetic, with one explanation of elapsed versus calendar/session days. Replay the captured MNQ replies through the allocator: reserve 51,824 candidate slots while excluding the maintenance closure. Cover bounded retries and timeout cancellation, and document the query contract. This does not repair existing SHM or parquet. Prompt-IO: ai/prompt-io/codex/20260924T232405Z_441358e2_schedule_coverage_prompt_io.md (this patch was generated in some part by `codex` using `gpt-6` (`openai`)) |
||
|---|---|---|
| .. | ||
| claude | ||
| codex | ||
| opencode | ||