Likely duplicate of #14307 (merged) — same change: extending MEDIA: regex with document extensions in gateway/platforms/base.py. The extensions added here (json, xml, md, html, js, py, sh, yaml, yml, toml) may partially overlap with what #14307 already added. Please verify which extensions are actually missing before merging.

Likely duplicate of #14307 (merged) — same change: extending MEDIA: regex with document extensions in gateway/platforms/base.py.

This PR adds support for GIS and code/document extensions that are not covered by any of the similar open PRs:

New MIME types (not in #24049 or #24217):

• .gpx, .kml, .geojson — GPS/GIS file formats that users can produce and send via
• .html, .htm, .js — web artifacts that skills generate and should deliver as native documents

**Extended to recognize: gpx|kml|geojson|html|htm|js|py|sh|json|xml|yaml|yml|toml|md

Real-world use case: I use Hermes to generate GPX files from my travels — asking it for points of interest in a city, restaurants, or landmarks, then rendering the output as .gpx with waypoints to import into map apps like HERE WeGo, Organic Maps, etc. Without these extensions in the MIME dict and the the gateway couldn't recognize and deliver these files natively.

PRs #24049 (Windows drive letters + GIS extensions by another author) and #24217 (spaced paths) don't overlap with the actual MIME type additions or the full extension list in the regex. This PR provides the complete set needed for the GPS/map workflow.

Superseded by #34844, which consolidates this cluster.

This PR widens the extract_media extension allowlist, which is the right direction — but on its own it leaves the unconditional MEDIA:\s*\S+ strip in place, so a MEDIA: tag with any extension still outside the (now wider) list keeps getting deleted from the body before extract_local_files can pick up the bare path. #34844 fixes both halves: it unifies the two extractors onto a single shared extension set (MEDIA_DELIVERY_EXTS) AND replaces the loose strip with an extension-anchored one, so an unknown-extension path survives in the text instead of vanishing.

Closing as superseded — thanks for surfacing and helping pin down this bug; it was part of getting the full fix right. See #34844.