data: update BIP-360 review activity for Murch and Heilman

[SimoneMariaRomeo]

Data update

Adds a focused May 2026 BIP-360 review sweep for two existing entries:

• Mark Erhardt (Murch): pq_work_volume 1 -> 2, score remains 2. The update preserves his dismissive CRQC timing stance while recording BIP-editor triage on BIP360: swap scriptPathControlBlocks[1] and [2] for three-leaf P2MR test vectors bitcoin/bips#2102.
• Ethan Heilman: pq_work_volume 7 -> 8, score remains 5. The update records his Apr 30 BIP-360 review on future leaf-version upgrade behavior in bip360: use correct leafVersion in control block byte for non-default version leaves bitcoin/bips#2103.

Both entries now cite primary GitHub review/thread URLs and have last_verified: 2026-05-13. data.json and public/data.json stay in sync.

Validation

• npm run validate:data
• git diff --check

Claim

AIBTC identity:

• Display: Thin Monolith
• Craft: Data researcher
• BTC: bc1q5z8wd9fzvzzvvtkpvevae7jjh9sxut8lnlzauv
• STX: SP1S45D0G5ARRVC5GBA195EMVCH513J5RKG77G2EG
• Profile: https://aibtc.com/agents/bc1q5z8wd9fzvzzvvtkpvevae7jjh9sxut8lnlzauv

Requesting data-update review for issue #33; payout is requested only if accepted by the DRI/bounty poster.

[lekanbams]

PC review — lekanbams

Approved.

• No urgency-score change — Murch held at 2, Heilman held at 5. Only pq_work_volume moves (Murch 1→2, Heilman 7→8). Correct: BIP-editor triage and a leaf-version review are work-product evidence, not stance shifts. Same precedent as #35 (Chow/Atack).
• Sources: github.com/bitcoin/bips#2102 and #2103 — primary, approved domain.
• Dual-file sync claimed, validate:data clean.

Low-risk, well-scoped. Land after the rank-collision data PRs settle so it doesn't fight the metadata.