Streaming encoders leave Frame_Content_Size out unless told the size up front,
and their readers often can't know it either: every zstd frame in an Anki
package (its collection, its media list, each media file) is written that way.
Such a frame needed the exact size passed as expectedSize, and anything else
was refused.
Now it gets the most its blocks can hold, Block_Maximum_Size (128 KiB) each,
found by walking the block headers alone, and the output is trimmed to what
the blocks held. The output is still allocated once. expectedSize keeps its
exact check when given, and maxOutputSize bounds the allocation as before.
Checked against libzstd (python-zstandard) on Anki 26.09.3's exports: a small
package's four frames and a 30 MB collection decode byte for byte the same.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
description, repository, issue_tracker and topics, plus a changelog,
which between them are most of a package's discoverability. The
repository URLs are a guess at the new home and want checking before the
first publish.
publish_to stays none so an accidental publish from inside this checkout
cannot succeed. Remove it in the new repository.
Version 0.1.0 rather than 0.0.1: a published version can be retracted
but never deleted, so the first one should mean something.
