Enrich property assessor with CAD detail data

skills/property-assessor/SKILL.md

@@ -113,6 +113,7 @@ scripts/property-assessor render-report --input "<report-payload-json>" --output
 - require the assessment purpose
 - treat the assessment purpose as missing unless it is present in the current request or explicitly confirmed as unchanged from earlier context
 - resolve official public-record jurisdiction automatically from the address
+- keep CAD discovery jurisdiction-specific from the address; do not hardcode one county CAD for every property
 - try to discover Zillow and HAR listing URLs from the address when no listing URL is provided
 - run the approval-safe Zillow/HAR photo extractor chain automatically
 - build a purpose-aware report payload
@@ -180,11 +181,13 @@ This command currently:
 - returns county/state/FIPS/GEOID context
 - for Texas, resolves the official Texas Comptroller county directory page
 - returns the county appraisal district and tax assessor/collector links when available
+- when a supported official CAD detail host is found, retrieves subject-property facts from that county CAD and includes them in the assessment payload
 
 Important rules:
 - listing-site geo IDs are hints only; do **not** treat them as assessor record keys
 - parcel/APN/account identifiers from Zillow/HAR/Redfin are much stronger keys than listing geo IDs
 - if a direct public-record property page is available, use its data in the assessment and link it explicitly
+- when the helper exposes official CAD owner, legal-description, property-ID/account, value, or exemption data, treat those as primary-source facts in the model's assessment
 - if the jurisdiction can be identified but the property detail page is not directly retrievable, still link the official jurisdiction page and say what could not be confirmed
 - a host approval prompt triggered by an ad hoc shell snippet is workflow drift; return to `locate-public-records`, `assess`, `web_fetch`, or a file-based helper instead of approving the inline probe by default