Map products had no matching product type: "GIS dashboard web map"
routed to Analytics Dashboard, "geospatial analytics platform" to
Podcast Platform, and "satellite imagery earth observation viewer"
returned nothing, so --design-system fell back to a landing-page
pattern for a map tool.
Add two product types with matching rows in products.csv, colors.csv
and ui-reasoning.csv (No 193-194):
- GIS / Web Map Dashboard: map-first layout with layer panel and linked
list, muted basemap, one UI accent, colorblind-safe data ramps.
- Earth Observation / Satellite Imagery Viewer: imagery-first layout,
neutral dark-grey chrome so imagery colors read true, date timeline,
before/after compare, perceptual index ramps.
Reasoning rows require map attribution, a legend and a text
alternative, and list rainbow ramps, hidden attribution, glass panels
over the map and raw-count choropleths as anti-patterns, in line with
the Maps rows in ux-guidelines.csv. Color tokens pass the existing
contrast contract. Provenance records cover both reasoning rows.
The product, palette and reasoning sets grow from 192 to 194, so the
row-count contract in validate_data.py, test_data_contracts.py and the
published counts move to 194. Neighbouring product queries (analytics
dashboard, delivery tracking, public transit, drone fleet, podcast
platform) keep their product type; relevance metrics are unchanged.
Co-authored-by: Khanhle19 <201531944+Khanhle19@users.noreply.github.com>