3D Scanner Match - same bounds, different file contents
Original synthetic geometry, bitmap, code and records: CC0 1.0 Universal.
https://creativecommons.org/publicdomain/zero/1.0/

WHAT TO TRY
All six authored import cases use the same eight corner positions. Declare
millimeters at import and check 100 x 40 x 20 mm. This is not automatic unit discovery.
1. box.stl: twelve triangular faces, no material/color in this file.
2. box.obj + box.mtl + checker.png: twelve faces, UVs and original 16 x 16 checker.
3. missing-material.obj: names an MTL that was deliberately never supplied.
4. missing-texture.obj + missing-texture.mtl: names a PNG deliberately not supplied.
5. colored-mesh.ply: eight colored vertices connected into twelve faces.
6. colored-points.ply: eight colored vertices, no face element.
The last two files use point colors, not a photograph texture. Missing companions
are intentional practice faults; no existing file was deleted to create them.

RECEIVING CHECKS
Unpack all 14 members to one directory. Keep companion filenames unchanged. Use
separate imports/projects or unique material names so a prior loaded material
does not conceal a missing companion. Check faces, attributes and image data,
not only the apparent outline or overall dimensions. A point-only file may
need a point/vertex display; vertex colors may need a material/display setup.
Repeat the check in the application/version that will use your real delivered file.

ACTUAL RUN
October 19, 2026 UTC: Blender 5.2.2 LTS build d13f752e3b9c, Windows background mode,
factory startup, offline, no automatic script execution. Six imports and 18 checks.
Scene METRIC, scale_length 0.001, MILLIMETERS; numeric import scale 1, Y forward/Z up.
STL/PLY use_scene_unit=false. OBJ uses its explicit scale/axis options. PLY colors
imported as sRGB, with attributes enabled and vertex merging disabled.
Image.size is queried before testing loaded pixels, allowing native lazy decoding.
Missing MTL/PNG messages in the console are intentional expected observations.

REPRODUCE
Use your legal Blender installation, not ordinary Python. PowerShell example:
$env:SCANNER_FORMAT_INPUT='C:\your-files\format-handoff'
$env:SCANNER_FORMAT_OUTPUT='C:\your-files\format-result-fresh'
& 'C:\Blender\blender.exe' --background --factory-startup --disable-autoexec --offline-mode --python 'C:\your-files\format-handoff\reproduce.py'
Use a new output directory. Code reads source inputs and creates a fresh report;
it does not repair, overwrite, remove or upload source files. CSV/JSON contain
native counts, dimensions, material/image/color data and source hashes.

LIMITS
Synthetic boxes, not scans. Native file data inspected; no shaded GUI/render,
other importer, physical scanner, reconstructed CAD solid or history was tested.
Counts/bounds do not certify geometry validity, printability or physical accuracy.
Our checker bitmap is an authored test pattern, not captured color or photography.
Format definitions do not guarantee a scanner's installed exporter supports them.
Primary format records read October 19, 2026:
STL https://www.loc.gov/preservation/digital/formats/fdd/fdd000504.shtml
OBJ https://www.loc.gov/preservation/digital/formats/fdd/fdd000507.shtml
PLY https://www.loc.gov/preservation/digital/formats/fdd/fdd000501.shtml
