fix(gateway): support Windows drive-letter paths and GIS extensions in MEDIA: regex

[liuhao1024]

What does this PR do?

The MEDIA: tag extractor in gateway/platforms/base.py (extract_media) fails on Windows absolute paths containing spaces (e.g. C:\Users\Foo\OneDrive\My Folder\file.pdf). The path is silently truncated at the first whitespace because the spaced-path branch only matches POSIX paths starting with ~/ or /.

Additionally, common GIS/structured-data extensions (kmz, kml, geojson, gpx, json, xml, html) are absent from the spaced-path extension allowlist, so even POSIX-style spaced paths fail for those file types.

Root Cause

The media_pattern regex at line 2066 has a spaced-path branch anchored to (?:~/|/), which only matches POSIX-style paths. Windows drive-letter paths (C:\...) and UNC paths (\\server\share\...) fall through to the \S+ fallback branch, which stops at the first whitespace.

The extension allowlist also omits GIS and structured-data formats, causing .kmz, .kml, .geojson, .gpx, .json, .xml, and .html files to fail the spaced-path match even on POSIX systems.

Related Issue

N/A

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)

Changes Made

• See commit messages for detailed changes

How to Test

1. Run pytest tests/ -q — all tests should pass
2. Verify the specific scenario described above is resolved

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: macOS 26.4.1

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture and workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A

[teknium1]

Thanks for identifying the Windows spaced-path and extension-list issues. The Windows drive-letter portion has already landed separately in 51d165a8e and current extraction uses the shared matcher at gateway/platforms/base.py:1468-1473.

Problems

• The PR's inline regex allowlist (gateway/platforms/base.py:2067 in this diff) is superseded by the shared MEDIA_DELIVERY_EXTS design at gateway/platforms/base.py:1432-1457, consumed by both extract_media() (:3622) and extract_local_files() (:3722). Reintroducing a local list would restore the drift fixed in 781604ce4.
• The changed [A-Za-z]: prefix does not match the UNC paths mentioned in the PR body.
• Current MEDIA_DELIVERY_EXTS already contains .json, .xml, .html, and .htm, but not .kmz, .kml, .geojson, or .gpx (gateway/platforms/base.py:1432-1449).

Suggested changes

• Salvage the remaining GIS support by adding only those four extensions to MEDIA_DELIVERY_EXTS, with unquoted spaced-path regressions for each.
• Drop or separately implement and test the UNC claim.

Automated hermes-sweeper review.

[teknium1]

This adds drive-letter matching but does not match the UNC paths described in the PR body: \\server\share\file.pdf has no [A-Za-z]: prefix. Either remove the UNC claim or add dedicated support and regression coverage.