Planning flood zones on the flood-risk point endpoint, and a closed field enum on property aggregate (v2.155.0)

Added

POST /v1/flood-risk/point now carries a planning block for England coordinates: the Environment Agency Flood Map for Planning zone (1, 2 or 3), resolved by point-in-polygon against the loaded flood-zone extents, together with the NPPF defaults a residential site at that zone faces: a flood risk assessment, the sequential test and the exception test.
Because the Flood Map for Planning only defines Zone 2 and Zone 3, the absence of any polygon at a point means Zone 1, so a point with no overlap is reported as Zone 1, never as missing data. The planning block is England-only, matching the source's coverage.
The climate2080 block is now always present when modelled, including when the 2080 direction is unchanged, so the response can state an honest "stable to 2080" instead of omitting the block.

Changed

The field parameter on POST /v1/property/aggregate is now a closed enum sourced from the engine's aggregation allowlist, so the valid values are discoverable directly in the OpenAPI specification and the generated SDK instead of being an opaque free-form string.
An unrecognised field now returns a precise 400 listing the allowed values. Valid requests are unaffected, since the engine already rejected unknown fields, and this simply surfaces the existing contract earlier and more clearly.

Planning flood zones on the flood-risk point endpoint, and a closed field enum on property aggregate