bazi-compatibilitylisted

# BaZi Compatibility Compare two validated sources, write `bazi_compatibility_<name-a>_<name-b>.json` plus data-only Markdown, then invoke `bazi-compatibility-reading` automatically. ## Route first - One raw birth record belongs to `bazi-chart`. - One existing chart needing meaning belongs to `bazi-reading`. - An existing compatibility artifact needing meaning belongs to `bazi-compatibility-reading`. - Luck cycles, dated predictions, and event timing are outside this release. ## Accepted source combinations Accept chart + chart, raw birth + raw birth, or chart + raw birth. Prefer reusable chart JSON when available; never recalculate a valid existing chart. A chart source must be schema `chinese-metaphysics.bazi-chart`, version 1, with a valid checksum and complete primary facts and score ledgers. If it declares a boundary alternate, that alternate must also be complete. A raw source has the same exact requirements as `bazi-chart`: name, unambiguous place, exact date and minute, declared Gregorian or lunar calendar, IANA zone, latitude, longitude, and an explicit leap-month flag for lunar input. Resolve ambiguous places before running. Never infer a minute, place, leap month, gender, DST fold, or historical offset. Birth data and chart artifacts are sensitive. Keep them in the user-selected output directory and do not transmit them elsewhere. ## Relationship context Default to a relationship-neutral general comparison. Set a context only when the user states one clea