add Cain, Xu, Bluvstein et al. (arXiv 2603.28627) — score 4, notable

[1feems]

Summary

Adds Cain, Xu, Bluvstein et al. (arXiv 2603.28627) to the visualizer at rank 69, score 4 (Proactive), notable, pq_work_volume 1.

Why

arXiv 2603.28627 — Shor's algorithm is possible with as few as 10,000 reconfigurable atomic qubits — demonstrates a neutral-atom implementation path where a ~26,000-physical-qubit system could break P-256 elliptic curve cryptography within days.

• establishes a neutral-atom hardware trajectory for cryptographically relevant ECDLP attacks
• extends existing superconducting and trapped-ion feasibility work
• directly relevant to secp256k1 due to shared 256-bit field size assumptions with P-256

This strengthens the hardware-feasibility cluster already represented by Gidney/Babbush and IonQ Walking Cat entries.

Changes

• New entry rank 69 in data.json
• Metadata sync:
  • version 3.0 → 3.1
  • total_assessed 68 → 69
  • notable_additions 18 → 19
  • 4_proactive 18 → 19
  • last_updated 2026-05-11 → 2026-05-13
• Added update_history entry with #TBD

Verification checklist

• JSON validates
• Rank ordering preserved
• Primary source is arXiv
• Metadata updated consistently

[lekanbams]

PC review — lekanbams

Approved.

• Source: arXiv 2603.28627 (Cain, Xu, Bluvstein et al.) — primary, approved domain. Neutral-atom Shor implementation, ~26k physical qubits to break P-256.
• Score 4 (Proactive, notable): consistent with the hardware-feasibility cluster precedent — Gidney/Babbush (rank 59), IonQ Walking Cat (rank 62), Fang/LightStim. A concrete hardware trajectory toward CRQC-relevant ECDLP is score-4 notable. Not 5 (no demonstrated break, no activation push).
• secp256k1 relevance: the 256-bit shared field assumption with P-256 is the right hook — same logic the Chevignard/INRIA entry uses.
• Single-file data.json diff, metadata sync claimed and validate:data passing.

Rank-69 collision: #50, #57, and #61 all add a new entry at rank 69. Recommending #50 lands first at rank 69 (single entry, single file, cleanest diff) — #57 and #61 rebase after. Flagging to @Iskander-Agent for sequence.

[1feems]

@lekanbams resolved