BRT mint: rewire to discover finalized ReleaseDrafts (key on draft UUID, drop Submission/N)

[magent-cryptograss]

Context

After the ReleaseDraft flow replaced the manual Blue Railroad Submission/N namespace, the mint pipeline never got rewired. Every Blue Railroad video uploaded since Submission/8 has had no mint page on cryptograss.live.

Current state

• Pickipedia has exactly 8 Blue Railroad Submission/N pages — 1 through 8.
• arthel's build polls those (pickipedia_submissions.js iterates 1..MAX_SUBMISSION_ID=20) and produces static mint pages at blox-office/admin/mint/bluerailroad/from-pickipedia/{N}.
• New uploads via Special:DeliverBlueRailroad create ReleaseDraft:<UUID> → finalize → bot creates Release:<CID>. No Submission page is written, so arthel doesn't see them.
• Result: from-pickipedia/9 and beyond return 404. Confirmed against live arthel as of 2026-04-30.

Proposed fix

Switch arthel from "iterate the old Submission namespace" to "discover finalized BRT ReleaseDrafts and key mint pages on the draft UUID."

• Query Pickipedia for finalized ReleaseDrafts of type: blue-railroad (likely via the existing Category:Release_Drafts plus a status filter, or a Semantic MediaWiki query, or by enumerating Release: pages whose source draft was a BRT).
• Build mint pages at blox-office/admin/mint/bluerailroad/from-draft/{draft_uuid} (or /from-cid/{cid} — see "open question" below).
• The page contents come from the same data shape they do today: ipfs_cid, exercise, blockheight, participants, etc., now sourced from ReleaseDraft YAML + the IPFS metadata.json on the pinned CID.

Open question

Key the URL on the draft UUID or on the CID?

• UUID (Justin's lean): stable across re-finalizes, maps 1:1 with the wiki ReleaseDraft, no canonicalisation gotchas.
• CID: self-verifying — the URL itself names the content being minted.

Decision: probably UUID. CID could be a secondary alias if useful.

Pickipedia follow-up (separate, small)

Once the URL pattern exists, add a "Mint this token" button on finalized ReleaseDraft:<UUID> pages of type: blue-railroad, linking to the new URL. This goes in cryptograss/pickipedia ext.pickipediaReleases.

Why this matters

• Justin currently can't mint his Nine Pound Hammer draft (3bc713f8-8686-4ec5-b8db-f87e453532d1) without manually creating Blue Railroad Submission/9 and triggering an arthel rebuild — a workaround we should make unnecessary.
• Same issue blocks every BRT release since Submission/8.

Out of scope (already filed elsewhere if needed)

• The dual-segment "mint from existing video" flow (one source video → two Releases with different trim/exercise/blockheight). That's a separate feature; this issue is just about restoring the existing-pin → mintable-page path for drafts.