Update README to reflect current state of codebase

[Copilot]

README was outdated following a significant rewrite of beam_state.py. Key inaccuracies: wrong description of what beams are monitored, stale note about the script needing work, and missing documentation for new config structure and CLI args.

Changes

• Beam monitoring: updated from generic "beam strength" to the three actual targets — TS1, TS2, and Muon beam current
• Experiment monitoring: clarified as counts-threshold-triggered "about to finish" notification, not a generic "end of run"
• Removed stale caveat: dropped the "needs work for other instruments / resilience" note — the script now reconnects automatically and monitors all three beam targets
• WebSocket: noted that beam_state.py uses a real-time WebSocket with auto-reconnect
• Config: directed users to config.ini.example as a starting point; listed all three webhook keys (news_teams_url, beam_teams_url, experiment_teams_url) with their respective scripts
• CLI args: documented -n/--notify_current (mcr_news.py) and -nc/--notify_counts (beam_state.py, default 130)

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[MaxPelly]

Can you do the same for the antigravity branch

[MaxPelly]

@copilot can you do the same for the antigravity branch as well?

[Copilot]

@copilot can you do the same for the antigravity branch as well?

I can see the antigravity branch and its codebase — it already has a fairly detailed README, but there are gaps (the [PVS], [LOGGING], [TIMEOUTS_INTERVALS], and [BEAM_BOUNDARIES] config sections aren't documented, for example).

However, I'm scoped to this PR's branch and can't push commits to antigravity directly. To get those README updates applied there, you'd need to open a new issue/task targeting that branch.