2011 Chrysler 200 Brake Rotors in Albuquerque, NM

• vehicle.real_rotor_price_range_usd — exact price range for rotors (per axle), e.g. "150-320" (USD) so the FAQ can cite per-axle pricing.
• vehicle.oem_rotor_life_miles — OEM expected rotor life in miles (number) to cite lifespan precisely.
• service.duration_minutes — typical labor time to replace rotors (minutes) per axle at the dealership.
• vehicle.rotor_specs — front and rear nominal thickness and minimum thickness specs and OEM part numbers (if available) for the Rotor Specifications section.
• vehicle.common_issues — any known rotor/brake TSBs or common issues for the 2011 Chrysler 200 (text list) to reference in specs section.
• rooftop.warranty_terms.brakes — exact warranty language/term for brake parts/service (or state it is not covered) so the FAQ about warranty is accurate.
• rooftop.scheduler_url — full or relative URL to link the "schedule service" anchor (you provided /service/schedule-service.htm; confirm if that exact relative path should be used).
• rooftop.service_specials_url — URL for "service specials" (you listed /specials/service.htm; confirm if to link that path).
• rooftop.neighborhoods_served — neighborhoods or nearby areas to list in the local-service paragraph (optional but recommended).
• rooftop.climate_context — brief local driving/climate notes (e.g., canyon descents, winter salt) — you provided some context; confirm exact phrasing to use.
• rooftop.years_in_operation and rooftop.certified_tech_count — numeric values to cite service center experience and tech count (if available).

If you prefer, I can proceed using conservative, typical industry values (clearly marked as estimates) — say to show a draft — but your rules require avoiding invented prices and specs, so I recommend providing the exact fields above. Reply with the missing values and I will return the full JSON output with the requested HTML content and a 150–160 character meta description.