bazi-chartlisted

# BaZi Chart Calculate one static natal chart, write `bazi_<name>.json` and `bazi_<name>.md`, then hand the verified JSON to `bazi-reading` automatically. The artifacts contain calculation data only; never interpret the chart here. ## Route before calculating - If the user supplied two people and wants to know whether they match, route to `bazi-compatibility`. - If the user supplied an existing chart and wants meaning, route to `bazi-reading` without recalculating. - If they ask for Da Yun, annual luck, event dates, or forecasts, state that this first release is natal-only and do not improvise those calculations. ## Require one resolved birth record Collect these fields without guessing: - `name`: display identity for the artifact. - `birth_place`: unambiguous city/region/country. - `birth_date`: exact `YYYY-MM-DD` in the declared calendar. - `birth_time`: exact `HH:MM` in 24-hour form. Refuse an hour-only or approximate time. - `calendar`: `gregorian` or `lunar`. A lunar date also requires explicit `leap_month: true|false`. - `timezone`: historical IANA zone such as `Asia/Shanghai`. - `latitude` and `longitude`: decimal degrees for the birthplace. - `utc_offset_minutes` only when an authoritative historical source must override IANA data. - `fold: 0|1` only to resolve a repeated DST wall time. - `gender` is optional. Never infer it from a name, relationship, or pronoun. Resolve a place through an available geocoder or map source. If multiple places match, stop for a l