Get Da Precedent Conditions

Surface the categorical breakdown of DA conditions for the property's (LGA, zone_code) cohort — what conditions actually get attached to approved DAs at sites like this.

Response shape: { "property_id": "...", "lga": "Brisbane", "zone_code": "LMR", "sample_size": 142, # DAs with categorised conditions "top_categories": [ {"category": "infrastructure_charges", "frequency": 0.87, "da_count": 124, "median_charge": 18450.0, "typical_measurement": null, "measurement_unit": null}, {"category": "setback", "frequency": 0.62, "da_count": 88, "median_charge": null, "typical_measurement": 6.0, "measurement_unit": "m"}, ... ], "infrastructure_charge": { "median": 17500.0, "average": 19340.0, "min": 4200.0, "max": 152000.0, "sample_size": 67 }, "data_available": true, "message": null }

When the cohort is too sparse (no rows for this LGA+zone), returns a "data_available": false response so the caller can render an empty- state card rather than raise.