Ten fixture archives carried the `.shp.xml` sidecar that ArcGIS writes beside an export. It describes the workstation that produced the file rather than the shapefile itself, which is not something a fixture in a public repository needs to carry.
Nothing reads these files. The importer selects archive members by a `.shp` extension anchored at the end of the name, so a `.shp.xml` sibling has never matched, and no spec refers to one.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Ten of the shapefile fixture archives carried the .shp.xml sidecar that ArcGIS writes alongside an export. That file describes the workstation and toolchain that produced the shapefile rather than the shapefile itself, and it is not something a fixture in a public repository needs to carry.
Nothing reads them. Unzip.paths selects archive members with a .shp extension anchored at the end of the name, so a .shp.xml sibling has never matched, and no spec refers to one. The .shp, .dbf, .shx and .prj components are untouched, so every fixture still exercises exactly what it did before.
Full suite is green locally: 266 examples, 0 failures.
🤖 Generated with Claude Code
https://claude.ai/code/session_017uHh49RG66T3qNFNRnPY6s