Upstream watch: GAMDL next-tag (3.7.4?) — m3u8 master URL default-variant rewrite (zero-surface admission)

[Salem874]

Summary

Upstream GAMDL (main branch) is one commit ahead of the most recent tag 3.7.3 as of 2026-06-07. The single in-flight commit is a pure HTTP-layer fix that rewrites Apple Music's m3u8 master URLs from codec-specific variants to the _default variant.

This issue is the pre-emptive watch: get the audit done, confirm zero MeedyaDL surface change, pre-stage the support-window bump, and pre-write the per-workflow release-notes line so the moment upstream tags (probably 3.7.4) we can ship a follow-up MeedyaDL pre-release on the alpha channel with one-line PR.

In-flight commit

• a9e75384 — "Add method to switch m3u8 master URL to default and update playback handling" — touches gamdl/interface/song.py only (1 file, +27/-10).

What the change does

Adds _switch_m3u8_master_url_to_default():

def _switch_m3u8_master_url_to_default(self, m3u8_master_url: str) -> str:
    return re.sub(
        r"(P\d+)_[^/]+(\.m3u8)",
        r"\1_default\2",
        m3u8_master_url,
    )

The regex matches Apple's CDN m3u8 master URL pattern and rewrites the codec-specific middle segment to default. Examples:

• Input: https://…/P12345_aac_HE_4_44100.m3u8
• Output: https://…/P12345_default.m3u8

Applied at both extraction sites in song.py:

1. _get_m3u8_from_playback() — when the URL comes from playback.songList[0].hls-playlist-url
2. _get_m3u8_master_url_from_metadata() — when the URL comes from song_metadata.attributes.extendedAssetUrls.enhancedHls

Pattern is identical to the user-facing fix in v3.5.2 (play-edge.itunes.apple.com → play.itunes.apple.com host migration) and v3.5.1 (m3u8 403 error fix) — Apple silently shifts what URL shapes work, and GAMDL adapts.

Why MeedyaDL surface is unaffected

Audit-grep run 2026-06-07:

Surface	Hit count	Verdict
MeedyaDL parses m3u8 URL shape (`rg 'm3u8	hls-playlist	enhancedHls'`)
MeedyaDL regex matching P\d+_* pattern	0	No collision
MeedyaDL emits CLI flags affected by this change	0	This is pure HTTP-layer internal
MeedyaDL stdout/stderr parsing affected (process::classify_error, TRACK_INFO_V2_REGEX, ERROR_PREFIX_REGEX)	0	The new log.debug calls are gated behind --log-level DEBUG which MeedyaDL never sets

Confirmed: this matches the same zero-code-change admission shape as v3.3 (playlist fix) / v3.5 (iTunes lookup fix) / v3.5.1 (MV 403 fix) / v3.5.2 (host migration) / v3.5.x and v3.7.1 trailing audits.

Plan

Tracked as a 4-step pre-release prep (all read-only / non-blocking on upstream):

• Step 1 — Diagnostic audit. Fetch + analyze the in-flight commit (this issue body).
• Step 2 — Audit doc draft. Pre-write .github/audits/gamdl-vNEXT-audit.md with the analysis. Once upstream tags, rename file + fill in the tag.
• Step 3 — Pre-stage tool-versions.toml bump. Comment block + audit note ready for the version-ceiling flip.
• Step 4 — Release notes line. Pre-write the one-liner for the next .github/release-notes/v1.10.0-alpha.NN.md (or whichever pre-release lands first after the upstream tag) so it's drop-in ready.

Anticipated next-tag work (when upstream tags)

Exactly two file edits (target: single-commit PR):

1. src-tauri/tool-versions.toml — bump maximum_tested_version + recommended_version from 3.7.3 to whatever upstream lands (almost certainly 3.7.4). Append audit-notes block.
2. .claude/CLAUDE.md — extend the GAMDL cadence paragraph with one entry summarising the m3u8 rewrite + zero-surface admission, in the same prose style as the existing 3.5.2 / 3.7.2+3.7.3 entries.

No GamdlFeature gate needed. No regex changes. No classifier changes. No new CLI flags or INI keys.

Trigger

Close this issue when upstream tags the release and MeedyaDL ships the admission PR.

Related

• v3.7.2 + v3.7.3 audit: GAMDL v3.7.2 + v3.7.3 audit — surface 'Media is not streamable' classification + admit to support window #898 (closed)
• Audit doc convention: .github/audits/gamdl-v3.5.2-audit.md, .github/audits/gamdl-v3.7.2-v3.7.3-audit.md

[Salem874]

Pre-flight prep landed on branch prep/gamdl-next-audit

Commit 18cbef0c on prep/gamdl-next-audit (off latest alpha). Two files changed, +107 / -0.

What landed

• .github/audits/gamdl-post-v3.7.3-audit.md (new) — full audit doc with per-commit analysis, audit-grep table, and post-tag admission plan. Will be renamed to gamdl-v<tag>-audit.md the moment upstream tags.
• src-tauri/tool-versions.toml (modified) — added a 22-line UPSTREAM WATCH comment block alongside the existing v3.7.2 + v3.7.3 notes so the pre-flight context survives until the bump PR.

Tasks status

• Step 1 — Diagnostic audit ✅
• Step 2 — Audit doc draft ✅ — landed on prep/gamdl-next-audit
• Step 3 — Pre-stage tool-versions.toml bump ✅ — UPSTREAM WATCH comment block in place; constants still at 3.7.3 (will bump in the admission PR)
• Step 4 — Release notes line. Deliberately deferred. The next alpha pre-release will pick this up in its .github/release-notes/v1.10.0-alpha.NN.md (or higher) once the version bump lands.

Post-tag admission PR shape

When upstream cuts the tag (most likely 3.7.4), the admission PR will rebase prep/gamdl-next-audit onto the latest alpha and add a follow-up commit that:

1. Bumps maximum_tested_version + recommended_version in tool-versions.toml from 3.7.3 to the new tag, fills in the pre-staged audit-notes block, and removes the UPSTREAM WATCH placeholder.
2. Extends the GAMDL cadence paragraph in .claude/CLAUDE.md.
3. Renames the audit doc to gamdl-v<tag>-audit.md.

Expected total diff for the admission commit: ≤ 40 lines + a file rename. No code change. No tests to update.

Test status

• cargo test --lib services::gamdl_capabilities:: — 31/31 pass (no regression from the audit-notes-only edit)
• No frontend tests / clippy / linters touched (audit-doc-only commit)

What's NOT in this prep

• No PR opened against alpha yet — the bump constants stay at 3.7.3 so the branch is intentionally a no-op build until upstream tags. Pre-staging the prose + audit grep + cadence note gets the bulk of the work out of the critical path; the actual admission is a near-mechanical follow-up.
• No version bump in package.json / Cargo.toml / tauri.conf.json — those are released-tag bumps and have nothing to do with the GAMDL pin.

[Salem874]

Trigger condition met — upstream tagged 3.7.4, MeedyaDL admission shipped

Per the body's own close-trigger: "Close this issue when upstream tags the release and MeedyaDL ships the admission PR."

• Upstream tagged 3.7.4 on 2026-06-12 (commit e0d4d5d).
• tool-versions.toml ceiling bump 3.5.2 → 3.7.4 shipped in PR fix: bundled audit hardening + #935 syllable lyrics + #937 release pipeline + repo hygiene (closes #935, #937, #938-#946) #947 (merged 2026-06-18 as 134e3e8).
• CLAUDE.md admission paragraph for v3.7.4 already lives in the GAMDL section (covers all 5 functional commits with zero-code-change admission rationale).
• Detailed audit doc tracked separately in audit: admit GAMDL v3.7.4 (zero-code-change, reliability patch) #925 — landing as part of the follow-up housekeeping wave.

Closing per the explicit close-trigger.