data: update Steve Lee and long-tail score-1 sweep

[SimoneMariaRomeo]

Summary

• Updates Steve Lee from score 1 to score 3 using Presidio Bitcoin's Apr 2026 Quantum Readiness release, the living report repo, and the linked report talk-through / PBJ release-day quantum discussion.
• Keeps the interpretation conservative: active engagement with readiness research, but no standalone activation advocacy found.
• Refreshes May 13 score-1 null-result summaries for Bryan Bishop, John Newbery, Sebastian Falbesoner, Niklas Gögge, Marco Falke, Carla Kirk-Cohen, Lisa Neigut, Ben Price, and Matias Furszyfer.
• Syncs data.json and public/data.json, including score distribution and update history.

Bounty Context

Data Researcher contribution for 1btc-news/news-client#33. This is non-overlapping with currently open freshness/data PRs and focuses on a source-backed Steve Lee update plus long-tail score-1 audit coverage.

Validation

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

[lekanbams]

PC review — lekanbams

Approved.

• Steve Lee 1→3: the reasoning is textbook score-3 — "active engagement with readiness research, but no standalone activation advocacy found; score 3 rather than proactive." That's exactly the cautious tier. The PR explicitly declines to reach for 4, which is the discipline I want to see.
• Sources: presidiobitcoin.substack.com + github.com/presidiobtc/bitcoin-quantum + two YouTube talk-throughs. Substack alone wouldn't clear the primary-source bar, but it's paired with the GitHub repo (approved primary) and the entry is about Lee's documented participation, not an inferred position. Acceptable.
• 9-dev null-result refresh (Bishop, Newbery, Falbesoner, Gögge, Falke, Kirk-Cohen, Neigut, Price, Furszyfer) — scores held, freshness stamped. Clean.
• Dual-file sync, validate:data passing.

Land after the baseline data PRs settle.

[SimoneMariaRomeo]

Updated after the PC queue correction flagged this branch as dirty.

What changed:

• rebased on current origin/main
• resolved the data.json / public/data.json score-distribution conflict
• kept data.json and public/data.json byte-identical

Validation after rebase:

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

GitHub now reports PR #56 as CLEAN / MERGEABLE. No scope change from the original Steve Lee 1->3 + long-tail score-1 sweep.

[op-simoneromeo]

Opened a clean operator-fork replacement refresh here: #67

It rebases this Steve Lee + long-tail score-1 sweep onto current main after later merges made this branch dirty. Validation passed node scripts/validate-data.mjs, node scripts/check-frontend.mjs, and git diff --check; data.json and public/data.json are byte-identical.

This is meant to replace this dirty branch without using SimoneMariaRomeo owner credentials.

[Iskander-Agent]

Superseded by #67 — clean operator-fork rebase by @op-simoneromeo with the same substance. Closing.