chore(soccer-scoreboard): move fine-tuning config fields behind Advanced Settings (x-advanced)

[ChuckBuilds]

Pull Request

Summary

Applies the "easy stuff up front, power stuff behind one click" treatment (LEDMatrix core PR #417's x-advanced mechanism) to soccer-scoreboard's config_schema.json: 331 of 470 flat fields are now flagged "x-advanced": true, so the core web UI collapses them into one "Advanced Settings" section at the bottom of the config page. Purely additive schema-data change — no field removed or renamed, no default or required changed, no manager.py change.

Type of change

• Bug fix in an existing plugin
• New plugin (also fill out the SUBMISSION.md checklist below)
• New feature for an existing plugin
• Documentation only
• Repo-wide change (registry script, hook, top-level docs)
• UX-only config schema reorganization (no behavior change)

Plugin(s) affected

soccer-scoreboard

Related issues

N/A — part of the plugin-store-wide config UX uplift following LEDMatrix core PR #417.

Test plan

• Loaded the plugin in LEDMatrix on real hardware
• Loaded the plugin in LEDMatrix emulator mode (EMULATOR=true python3 run.py)
• Rendered the plugin in the dev preview server (scripts/dev_server.py)
• Verified the web UI configuration form against the schema
• N/A — repo-wide / docs-only change

Details: schema still parses as strict JSON; verified programmatically that recursively stripping every x-advanced key from the new schema yields an object deep-equal to the one on main (so validation behavior is byte-for-byte identical — only rendering changes); update_registry.py --dry-run reported changes for this plugin only. Rendering was not eyeballed against a live core web UI in this environment — the x-advanced flags use exactly the mechanism core already ships, and a wrong flag degrades gracefully (field renders in the collapsed section instead of up top).

Required for plugin changes

• Bumped version in plugins/<id>/manifest.json (2.3.0 → 2.3.1, with a versions[] changelog entry)
• class_name in manifest.json matches the actual class in manager.py exactly (unchanged)
• entry_point matches the real file (unchanged)
• Updated the plugin's README.md if config keys changed (no keys changed — N/A)
• config_schema.json is the source of truth for the web UI form — no new options added, only x-advanced render hints
• Pre-commit hook ran successfully (update_registry.py run directly; plugins.json synced to 2.3.1)

Checklist

• My commits follow the message convention in CONTRIBUTING.md
• I read CONTRIBUTING.md and CODE_OF_CONDUCT.md
• I've not committed any secrets

Notes for reviewer

What was flagged advanced, and why (one line each):

• Top-level update_interval_seconds, live_update_interval, recent_update_interval, upcoming_update_interval, live_game_duration, game_display_duration — poll-interval / dwell-time tuning with sane defaults.
• background_service.* (enabled, max_workers, request_timeout, max_retries, priority) — worker/timeout/retry tuning the README never asks users to touch.
• Per-league (all 10 league blocks, uniformly): exclude_teams — niche spoiler-protection filter; display_modes.{live,recent,upcoming}_display_mode — switch/scroll enum defaulting to "switch"; scroll_settings.* (6 fields) — scroll speed/delay/gap/card-width fine-tuning; live_priority, live_game_duration, non_favorite_live_game_duration, recent_game_duration, upcoming_game_duration, celebration_duration, celebrate_opponent_goals, live_update_interval, update_interval_seconds — rotation/duration/poll fine-tuning; filtering.favorite_live_boost — rotation-weighting knob; dynamic_duration.* (9 fields) and mode_durations.* (3 fields) — advanced duration-override system, disabled by default.

Kept basic (never flagged): enabled toggles, favorite_teams / custom_leagues (the core setup interaction), league enable toggles, show_favorite_teams_only / show_all_live filtering, show_records / show_ranking / show_odds, display_duration, and recent/upcoming game-count limits.

All 10 predefined league blocks share an identical 45-field structure, so flags were applied uniformly (32 advanced per league). x-advanced was only applied to scalar/array/enum fields, never object properties. jsonschema package wasn't available locally, so manifest-vs-schema/manifest_schema.json validation is left to CI.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LFNedFLmEcSHqSHG9Lwa62

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@ChuckBuilds, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4ee53b7b-e4f5-4aa7-afbf-5496f26976f4

📥 Commits

Reviewing files that changed from the base of the PR and between 3ba5905 and 331f1bd.

📒 Files selected for processing (3)

• plugins.json
• plugins/soccer-scoreboard/config_schema.json
• plugins/soccer-scoreboard/manifest.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/chuck-builds-plugin-config-65322r-soccer-scoreboard

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[ChuckBuilds]

Closing in favor of the consolidated PR #208 (per maintainer request, all x-advanced schema uplifts in one PR — this plugin's change is included there as its own commit).

---

Generated by Claude Code