Bug: Panic when fetching

Describe the bug

{"level":"error","ts":"2025-03-31T13:37:46.153Z","message":"internal error: fetch panicked on fraction seq-db-01JQEBHMXQQPYMNFCBS6NN0G6H: runtime error: index out of range [4294943512] with length 4096"}
goroutine 121941 [running]:
runtime/debug.Stack()
    runtime/debug/stack.go:26 +0x5e
runtime/debug.PrintStack()
    runtime/debug/stack.go:18 +0x13
gitlab.ozon.ru/sre/seq-db/util.Recover({0xf7f4e8?, 0xc000130c60?}, {0xf72340, 0xdfe6a78e20})
    gitlab.ozon.ru/sre/seq-db/util/err.go:43 +0x65
gitlab.ozon.ru/sre/seq-db/fetch.fetchMultiWithRecover.func1()
    gitlab.ozon.ru/sre/seq-db/fetch/fetcher.go:97 +0x113
panic({0xdc6cc0?, 0xcec17f4a38?})
    runtime/panic.go:785 +0x132
gitlab.ozon.ru/sre/seq-db/frac.(*SealedIDs).GetDocPosByLIDs(0xc00124b980, {0xf242388060, 0x3, 0x3?})
    gitlab.ozon.ru/sre/seq-db/frac/sealed_ids.go:183 +0xf0
gitlab.ozon.ru/sre/seq-db/frac.(*SealedDataProvider).Fetch(0xd4ede59e40, {0xd0886e2b10, 0x3, 0x3})
    gitlab.ozon.ru/sre/seq-db/frac/sealed.go:209 +0x25f
gitlab.ozon.ru/sre/seq-db/fetch.fetchMultiWithRecover({0xf7bd70?, 0xcefe7000f0?}, {0xf7f2d8?, 0xc0012389c0?}, {0xd0886e2b10, 0x3, 0x3})
    gitlab.ozon.ru/sre/seq-db/fetch/fetcher.go:107 +0xe2
gitlab.ozon.ru/sre/seq-db/fetch.(*Fetcher).fetchDocsAsync.func1()
    gitlab.ozon.ru/sre/seq-db/fetch/fetcher.go:46 +0x94
created by gitlab.ozon.ru/sre/seq-db/fetch.(*Fetcher).fetchDocsAsync in goroutine 121696
    gitlab.ozon.ru/sre/seq-db/fetch/fetcher.go:45 +0x105

Start with frac/sealed_ids.go at GetDocPosByLIDs, especially line 183, then follow the call chain through frac/sealed.go and fetch/fetcher.go. Investigate the reported out-of-range index and identify a reproducible fetch case. Done means fetching no longer panics for the affected data and the behavior is covered by an appropriate test if one exists.