flutter3d_cpu 0.4.0

A software backend for flutter3d_hardware: no GPU, no shading language, and therefore the sharpest test of whether the interface is an interface.

0.4.0

• CpuFrame disposes its images. It had no dispose at all — one leaked ui.Image per presented frame — and two in-flight decodes could finish out of order. The previous image is disposed when a new one lands, the fresh one when the widget is already gone, and a sequence number keeps a stale frame from overwriting a newer one.

0.3.0

• The composite pass mirrors the grading, vignette, grain and dispersion the hardware backends apply, so the two reference sets stay comparable.
• Cube texture uploads validate each mip level's size rather than accepting anything that fits.

0.2.0

• flutter3d_hardware rasterised in Dart with no GPU under it: what the golden images are drawn with, and what a test renders a whole frame through.
• Deliberately shares nothing with either hardware backend — no driver, no shading language, no command buffer — which is what makes agreeing with them mean something.