Get Property

Get full property intelligence by ID.

Sequential (safe) execution, with per-stage timing for visibility:

First attempt at parallelisation via asyncio.gather on a single AsyncSession produced asyncpg.InterfaceError: connection is closed in production — SQLAlchemy 2.0 async sessions DO NOT support concurrent statements on a single session, even for read-only queries. Reverted to sequential. The dedup of ci_rea_listings fetch (passed to both score + intent helpers) is the real durable win — saves one round-trip per request.

Per-stage timing logged at INFO with a tag the operator can grep: [property/get] property_id=... t_fetch=Xms t_zone=Yms t_da=Zms t_nearby=Wms t_rea=Vms t_score=Sms t_intent=Ims t_total=Tms. Once we have several real samples in Railway, the dominant cost will be obvious — almost certainly t_score (score_rea_listing fans out into _fetch_property_scoring_inputs + forecast_da_pathway).