Ogg-01184 Expected 4 Bytes But Got 0 Bytes In Trail [extra Quality]

Suggested feature: Robust OGG packet-trail length validation with informative error handling

Summary

Add a validation and recovery feature that detects OGG error cases like "expected 4 bytes but got 0 bytes in trail" and handles them gracefully: validate packet-trail lengths on read, log structured diagnostics, optionally attempt soft-repair, and surface a clear, actionable error to callers.

Expected 3,number,0 bytes, but got 4,number,0 bytes, in trail 0, seqno 1,number,0, reading record trailer token at RBA {2, Oracle Help Center Extract & Pump Abends — oracle-mosc ogg-01184 expected 4 bytes but got 0 bytes in trail

2. Symptom

Replicat process fails with the following in the error log: log structured diagnostics

"No," Maya said. "It's not missing. It was never written." optionally attempt soft-repair