Clarify HTTP candleSnapshot response timestamps and candle completion #333

Hello maintainers,

Could you point me to the public contract for HTTP POST /info with type: "candleSnapshot", specifically its response fields? The intended use is 15-minute candles requested with coin: "BTC".

1. Response timestamps: What units and epoch do t and T use? Does t identify the interval start, and does T identify an inclusive end or the exclusive next boundary? I would like to distinguish response definitions from the request's time parameters.

2. Candle completion: Can a response include a candle that is still forming? What documented flag or observable rule distinguishes a completed interval from an in-progress one? If no explicit completion signal is exposed, please clarify that limitation.

3. Later revisions: After an interval is considered complete, can its previously returned contents be corrected? If so, are there documented conditions or a revision indicator? Completion and immunity to later corrections are separate questions; I am not assuming the latter.

Please identify the applicable HTTP/mainnet product and schema/version scope, or any limits on that scope.

Reference: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint

This is separate from #330 (public trade identity/replay), #331 (book ordering/aggregation), and #332 (product/account-mode applicability). It is a documentation question, not a report of an observed malfunction or a request for account-specific information.

Thank you.