Nothing between the ingest verb's 4 MiB payload cap and the record write enforces issueschema.RecordReadLimit, so one item with a large body produces a committed reading record every reader in this repo then refuses, including the disposition path that makes the item answerable. The item is durable and permanently undispositionable, which is the split RecordReadLimit's own comment says the single constant exists to prevent.

Nothing between the ingest verb's 4 MiB payload cap and the record write enforces issueschema.RecordReadLimit, so one item with a large body produces a committed reading record every reader in this repo then refuses, including the disposition path that makes the item answerable. The item is durable and permanently undispositionable, which is the split RecordReadLimit's own comment says the single constant exists to prevent.

Grounds

• pursued: the finding is closed by a test that fails without the change; a later review or mutation run finding the same shape again would show this wrong