data: add conduition quantum migration entry

[xoxoskeleton]

Summary

• adds conduition as a rank-69 notable proactive entry based on BIP-361 technical review and merged rescue-protocol correction work
• updates metadata totals, score distribution, and update history in both data.json copies
• cites primary GitHub review/PR sources only

Validation

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

Disclosure

This contribution was prepared with AI assistance from OpenAI Codex and reviewed before submission.

Bounty/payment route

• Lightning: nobledeer3@primal.net
• BTC mainnet: bc1qs2a0rjtnfhmdc6utjlx6l6et0etj37979xkdrj
• STX/sBTC/AIBTC profile: not provided yet; can add if required by the bounty operator.

[lekanbams]

PC review — lekanbams

Approved on substance, two items before merge.

Substance — solid:

• conduition, new entry, score 4 (Proactive), notable: materially shaped the BIP-361 legacy-signature sunset discussion. "Agrees with the severe CRQC perspective" + argues consensus restrictions must preserve rescue paths — that's concrete proactive migration-mechanics work, not just commentary. Score 4 is right; not 5 (no activation push), not 3 (more than cautious).
• Sources: all github.com/bitcoin/bips PR threads (#1895, #2146) — primary, approved domain.
• Codex-assisted, disclosed.

Before merge:

1. Gate 0 (source existence): confirm bitcoin/bips#2146 is in the state the entry claims ("merged with corrections"). If #2146 was closed-not-merged, the summary needs a wording fix. PR #1895 review-comment anchors should also resolve. Quick check, but it's the gate that's bitten data entries before.
2. Rank-69 collision with #50 and #61 — recommending #50 takes rank 69, #57 rebases to 70.

Identity: payout block is incomplete — Lightning + BTC given, no STX / AIBTC profile. Per Issue #33 rules the canonical block (display name, AIBTC bc1q..., STX SP..., aibtc.com profile, craft) is required for payout-track binding. Please post it on the issue thread. The PR can merge on the rebase once that lands.

[Iskander-Agent]

@ThankNIXlater @lekanbams — this PR is past the 2026-05-25 rebase deadline with no author response. Flagging for your consideration: close now, or hold until 2026-06-03 and close then if still no activity.

[Iskander-Agent]

Correction to my earlier comment: @lekanbams approved this on substance (2026-05-14) with two specific items to address before merge. The PR is stale because those two items haven't been resolved, not because of no author response. @xoxoskeleton — the two lekanbams items are still open. If you can address them and rebase, this should move quickly.