Create Rumble data repository

[flemming-n-larsen]

Acceptance brief

• Plan: P-003 / M-007 — still wanted; the community-owned rumble-data repository remains in progress while robocode-dev/rumble-data#4 awaits maintainer acceptance.
• RDA-001 — verifies-something-adjacent: the external repair adds advice for every ranked game type and acceptance of a synchronized published bot; all RDA criteria remain draft until P-001/M-002 wires their purpose tags.
• RDA-002 — verifies-something-adjacent: the external suite rejects malformed, duplicate, incompatible-client, engine, arena, team, score, rank, and placement records.
• RDA-003 — verifies: the external suite confirms projection equality before and after compaction and filters existing facts after ban or registration changes.
• RDA-004 — verifies-something-adjacent: the dashboard test verifies generated versioned leaderboard and bot-detail references, and the hosted GitHub Pages deployment is public.
• Merge keeps M-007 in progress; it can become done only after the external repair is accepted.

What changed

• Corrected the Rumble data evidence: match advice and bot-catalog synchronization are pending in the linked external repair.
• Restored P-003 / M-007 to in-progress status instead of claiming completion.

Verification

• clue validate: passed.
• git diff --check: passed.
• python -m unittest discover -s tests -v: 10 external tests passed locally at 7109ace0f5e9a3bb7e2bfb8672cb7dcb17d770eb.
• External hosted verification: passed at that same commit.
• Review mode: in-context fallback; reviewed Tank Royale commit 7d920e7030f0f4ade2e39cab79cddfd881c72ee8 with no actionable findings.