Inspect Import

Row caps the client renders and gates on — served here so the numbers have exactly one home (the server) and can't drift across surfaces.

Detected route plus the address-like columns that motivated it. The route is a heuristic first offer — the card's manual override is the escape hatch, so a wrong guess costs one click.

County derivation for geometry files: per-county feature counts and the dominant (modal) county to pre-select. derivable is False when no feature landed in any county. located_count counts rows carrying ANY geometry — it can exceed sum(breakdown) when points fall outside every county, and those rows are still fenced (dropped) at upload, so clients must predict fence outcomes from it, never from the breakdown sum. The scope counts are present only when the inspect ran against an existing project (Door 2), fencing against that project's county.