chore(spec): auto-polish area-mountain-panorama (#9539)

Automated spec polish from `daily-regen` pre-flight.

**Spec:** `area-mountain-panorama`

## What changed
- Moved `geospatial` tag from `features` to `data_type` (describes data
structure, not visualization feature)
- Replaced generic `spatial` tag with more specific `geospatial` for
accurate geographic/topographic data classification

## Why
Per the tag guidelines, `geospatial` describes the **nature of input
data** (geographic coordinates, topographic positioning), not a
visualization feature. It should be classified in `data_type` alongside
the other data-shape descriptors. This makes the tag dimension alignment
clearer and more discoverable for users with geographic/topographic
datasets.

## Hard guarantees from the prompt
- `id`, `issue`, `created` unchanged
- No semantic changes (data shape, plot type, requirements identical)
- `updated` bumped to current UTC

Auto-merge enabled — will merge once required checks pass. The skip-gate
in `daily-regen` prevents stacking polish PRs for this spec.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>

Author: 3 people

plots/area-mountain-panorama/specification.yaml

@@ -6,7 +6,7 @@ title: Mountain Panorama Profile with Labeled Peaks
 
 # Specification tracking
 created: 2026-04-24T21:39:00Z
-updated: 2026-04-25T00:00:00Z
+updated: 2026-06-30T21:43:15Z
 issue: 5365
 suggested: MarkusNeusinger
 
@@ -19,7 +19,7 @@ tags:
   data_type:
     - numeric
     - continuous
-    - spatial
+    - geospatial
   domain:
     - general
     - science
@@ -28,4 +28,3 @@ tags:
     - annotated
     - silhouette
     - jagged
-    - geospatial