Resolve committed byte overlaps before replaying telemetry

When an append-only telemetry replay is rejected for overlapping committed ranges, inspect the authoritative delivery ledger before retrying. An extended queued range may contain both an already uploaded prefix and a missing tail. Verify committed hashes against saved bytes, subtract that coverage, and upload only uncovered ranges at native record boundaries with the original stream, generation, and absolute offsets. Preserve original queued envelopes with a reconciliation record linking their coverage to actual committed batches; do not fabricate a whole-envelope receipt or change generations merely to evade overlap checks. If overlapping bytes cannot be verified, retain the conflict rather than declare completion.

Applies when: Immutable byte-range ingestion rejects a replay while its queued source still contains uncovered bytes. Keywords: telemetry replay overlap receipt hash byte range ingestion reconciliation