0.7.1

Two fixes from the pre-release audit of 0.7.0, both present in earlier releases,
and the Argleton run scored against trap 024's corrected truth, which arrived
after the 0.7.0 tag: that release's PyPI page still quotes the recount of the
old run. No answer 0.7.0 got right changes, and no manifest key moves: records
declare spec_version 1.0.0-draft.8, as in 0.7.0.

Fixed

• An output that is one of the inputs, or has an extension its writer cannot
  honour, is refused before anything is written
  (#31). zonal_statistics
  with output_path equal to its weights raster replaced the raster with a
  directory of shapefiles — a vector writer given .tif falls back to the
  Shapefile driver — and failed before writing a manifest. The dedicated tools
  now refuse both at the boundary, as run_operation already refused the
  collision; and the plan validator turns an extension no writer can honour from
  a warning into an error (OUTPUT_EXTENSION_REFUSED), keeping the warning for
  writable but non-canonical ones such as .geojson.

• A spacing could ask for any number of points. elevation_profile and
  points_along_lines materialised every point before looking at how many
  there were: a spacing of 1e-6 on a 90 m line is ninety million. Both now
  count the points from the line lengths and refuse above
  MAPSMITH_MAX_SAMPLES (default 1 000 000), an environment variable of the
  server that no tool argument can move; SECURITY.md says what is and is not
  limited. points_along_lines also refuses a NaN or infinite spacing, which
  spacing <= 0 let through.