Add sports-score-alert ability: live scores, schedules, and results via ESPN

[hassan1731996]

Summary

• Live sports scores, upcoming schedules, and recent results via ESPN's public scoreboard API
• Supports MLB, NBA, NFL, NHL, and MLS — no API key required
• Background daemon alerts the user when a tracked team's game starts or ends
• Full-name keyword matching to avoid team name collisions (e.g. "Red Sox" vs "Reds")
• 3-day lookahead for schedules, 3-day lookback for results

Trigger phrases

"sports scores", "how did [team] do", "when does [team] play", "track my teams", and more

Test plan

• "track my teams" → setup flow, team names saved
• "how did the Yankees do" → last result returned
• "when do the Red Sox play" → next scheduled game within 3 days
• "what's the score" → live score if game in progress
• Background daemon fires when tracked team game starts/ends
• validate_ability.py passes (exit 0)

[github-actions]

🔀 Branch Merge Check

PR direction: feature/sports-final → dev

✅ Passed — feature/sports-final → dev is a valid merge direction

[github-actions]

✅ Community PR Path Check — Passed

All changed files are inside the community/ folder. Looks good!

[github-actions]

✅ Ability Validation Passed

📋 Validating: community/sports-score-alert
  ✅ All checks passed!

[github-actions]

🔍 Lint Results

✅ __init__.py — Empty as expected

Files linted: community/sports-score-alert/background.py community/sports-score-alert/main.py

✅ Flake8 — Passed

✅ All checks passed!

[uzair401]

Thanks @hassan1731996 — this is your second PR with the same storage bug as air-quality-pollen-alert, so worth calling out clearly: please follow these patterns going forward, since they'll come up in every future ability.

• Storage saves must be create_key-first, checking the actual success field in the response. try: update_key(...) except: create_key(...) looks reasonable but is broken — update_key doesn't raise and just no-ops on a missing key, so the very first save silently never persists.
• Exit-word matching needs to check the whole utterance, not do a substring/word check across EXIT_WORDS. In a sports context, "stop" and "done" show up constantly in ordinary sentences ("what a stop by the goalie," "is it done yet") — a plain match exits the ability mid-conversation. It also meant "stop following the Yankees" always exited instead of reaching your own UNFOLLOW handling.
• Daemon call() must set background_daemon_mode before constructing CapabilityWorker, and daemons should pass self, not self.worker.

Fixed all of these plus the identical background.py copy. Everything else here (the ESPN integration, the team-collision keyword matching, the in-memory-data workaround for the create_key visibility lag) is genuinely well thought out — these three patterns are just worth locking in for next time.