fix(espn): fetch a window's edge months whole, cap chunk requests per process

A soccer board with eight leagues logged ~90 NameResolutionErrors for
site.api.espn.com within a minute of every start on ledpi, plus
"update() timed out". ESPN rejects date ranges, so every league's
fortnight-either-side window became 29 day requests, several managers
fetched it at once, and each window got its own six chunk threads:
~450 requests per start with ~45 in flight, each request past a
session's pool a new connection and a new DNS lookup.

- fetch_espn_date_chunks() asks for a partial edge month whole once the
  window covers ESPN_MONTH_COVER_MIN_DAYS (7) of its days, and trims the
  answer to the window by each event's US Eastern start date, the day
  ESPN's dates=YYYYMMDD means (417/417 live soccer events matched). A
  29-day window over two months is 2 requests, not 29. A live poll's
  1-2 days stay day requests. A capped trimmed month re-asks only the
  window's days; an undatable event is kept. New espn_request_chunks().
- Chunk requests share one process-wide cap of ESPN_CHUNK_WORKERS in
  flight instead of six per window.
- A new process starts as if a range had just been rejected, so it no
  longer spends a doomed 400 per window at every start.

Live ESPN, soccer-scoreboard 2.39.2, alternating runs: ~450 -> 46
requests per start, peak ~45 -> 13 in flight, ~75 -> 30 DNS lookups.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.codacy.yml

@@ -0,0 +1,6 @@
+---
+exclude_paths:
+  - "plugin-repos/**"
+  - "plugins/**"
+  - "assets/**"
+  - "test/**"

.gitattributes

@@ -1,2 +1,15 @@
 # Auto detect text files and perform LF normalization
 * text=auto
+
+# Files the Pi executes must stay LF even in a Windows checkout with
+# core.autocrlf=true: a CRLF shebang line fails with "bad interpreter",
+# and systemd rejects CRLF unit files.
+*.sh text eol=lf
+*.service text eol=lf
+
+# Generated by scripts/build_css.py; collapsed in diffs, not hand-edited.
+web_interface/static/v3/tailwind.css linguist-generated=true
+web_interface/static/v3/plugin-frame.css linguist-generated=true
+
+# Installed as an executable (its shebang runs it) by install_service.sh.
+scripts/install/ledmatrix_refresh_units.py text eol=lf

.github/FUNDING.yml

@@ -0,0 +1,4 @@
+github: ChuckBuilds
+buy_me_a_coffee: chuckbuilds
+ko_fi: chuckbuilds
+

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,84 @@
+---
+name: Bug report
+about: Report a problem with LEDMatrix
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+<!--
+Before filing: please check existing issues to see if this is already
+reported. For security issues, see SECURITY.md and report privately.
+-->
+
+## Describe the bug
+
+<!-- A clear and concise description of what the bug is. -->
+
+## Steps to reproduce
+
+1.
+2.
+3.
+
+## Expected behavior
+
+<!-- What you expected to happen. -->
+
+## Actual behavior
+
+<!-- What actually happened. Include any error messages. -->
+
+## Hardware
+
+- **Raspberry Pi model**: <!-- e.g. Pi 3B+, Pi 4 8GB, Pi Zero 2W -->
+- **OS / kernel**: <!-- output of `cat /etc/os-release` and `uname -a` -->
+- **LED matrix panels**: <!-- e.g. 2x Adafruit 64x32, 1x Waveshare 96x48 -->
+- **HAT / Bonnet**: <!-- e.g. Adafruit RGB Matrix Bonnet, Electrodragon HAT -->
+- **PWM jumper mod soldered?**: <!-- yes / no -->
+- **Display chain**: <!-- chain_length × parallel, e.g. "2x1" -->
+
+## LEDMatrix version
+
+<!-- Run `git rev-parse HEAD` in the LEDMatrix directory, or paste the
+release tag if you installed from a release. -->
+
+```
+git commit:
+```
+
+## Plugin involved (if any)
+
+- **Plugin id**:
+- **Plugin version** (from `manifest.json`):
+
+## Configuration
+
+<!-- Paste the relevant section from config/config.json. Redact any
+API keys before pasting. For display issues, the `display.hardware`
+block is most relevant. For plugin issues, paste that plugin's section. -->
+
+```json
+```
+
+## Logs
+
+<!-- The first 50 lines of the relevant log are usually enough. Run:
+  sudo journalctl -u ledmatrix -n 100 --no-pager
+or for the web service:
+  sudo journalctl -u ledmatrix-web -n 100 --no-pager
+-->
+
+```
+```
+
+## Screenshots / video (optional)
+
+<!-- A photo of the actual display, or a screenshot of the web UI,
+helps a lot for visual issues. -->
+
+## Additional context
+
+<!-- Anything else that might be relevant: when did this start happening,
+what's different about your setup, what have you already tried, etc. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,62 @@
+# Pull Request
+
+## Summary
+
+<!-- 1-3 sentences describing what this PR does and why. -->
+
+## Type of change
+
+<!-- Check all that apply. -->
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Documentation
+- [ ] Refactor (no functional change)
+- [ ] Build / CI
+- [ ] Plugin work (link to the plugin)
+
+## Related issues
+
+<!-- "Fixes #123" or "Refs #123". Use "Fixes" for bug PRs so the issue
+auto-closes when this merges. -->
+
+## Test plan
+
+<!-- How did you test this? Check all that apply. Add details for any
+checked box. -->
+
+- [ ] Ran on a real Raspberry Pi with hardware
+- [ ] Ran in emulator mode (`EMULATOR=true python3 run.py`)
+- [ ] Ran the dev preview server (`scripts/dev_server.py`)
+- [ ] Ran the test suite (`pytest`)
+- [ ] Manually verified the affected code path in the web UI
+- [ ] N/A — documentation-only change
+
+## Documentation
+
+- [ ] I updated `README.md` if user-facing behavior changed
+- [ ] I updated the relevant doc in `docs/` if developer behavior changed
+- [ ] I added/updated docstrings on new public functions
+- [ ] N/A — no docs needed
+
+## Plugin compatibility
+
+<!-- For changes to BasePlugin, the plugin loader, the web UI, or the
+config schema. -->
+
+- [ ] No plugin breakage expected
+- [ ] Some plugins will need updates — listed below
+- [ ] N/A — change doesn't touch the plugin system
+
+## 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 or hardcoded API keys
+- [ ] If this adds a new config key, the form in the web UI was
+      verified (the form is generated from `config_schema.json`)
+
+## Notes for reviewer
+
+<!-- Anything reviewers should know — gotchas, things you weren't
+sure about, decisions you'd like a second opinion on. -->

.github/workflows/claude-code-review.yml

@@ -0,0 +1,40 @@
+name: Claude Code Review
+
+on:
+  pull_request:
+    types: [opened, synchronize, ready_for_review, reopened]
+
+jobs:
+  claude-review:
+    # Pull requests from forks get no repository secrets, so without this
+    # guard every outside contributor's PR showed this check red for a reason
+    # they can't fix. Skipped checks don't block merging.
+    if: github.event.pull_request.head.repo.full_name == github.repository
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code Review
+        id: claude-review
+        uses: anthropics/claude-code-action@756cc22e19660d20e8cc9496b4f242475a7f7790 # v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          # Review PRs opened by the Claude GitHub App. Without this the action
+          # aborts before reading the diff ("Workflow initiated by non-human
+          # actor"), so every such PR shows this check red. Named rather than
+          # '*': the allow-list is matched against the triggering actor, so
+          # this admits claude[bot] alone and no other app.
+          allowed_bots: 'claude'
+          plugin_marketplaces: 'https://github.com/anthropics/claude-code.git'
+          plugins: 'code-review@claude-code-plugins'
+          prompt: '/code-review:code-review ${{ github.repository }}/pull/${{ github.event.pull_request.number }}'
+

.github/workflows/claude.yml

@@ -0,0 +1,42 @@
+name: Claude Code
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  issues:
+    types: [opened, assigned]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  claude:
+    if: |
+      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
+      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+      actions: read # Required for Claude to read CI results on PRs
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code
+        id: claude
+        uses: anthropics/claude-code-action@756cc22e19660d20e8cc9496b4f242475a7f7790 # v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          # This is an optional setting that allows Claude to read CI results on PRs
+          additional_permissions: |
+            actions: read
+

.github/workflows/release-version-check.yml

@@ -0,0 +1,40 @@
+name: Release version check
+
+# A release tag, the CHANGELOG, and src.__version__ must agree. They have not
+# always: v3.1.0 was tagged while src/__init__.py still said "1.0.0", which
+# silently exempted every device installed from that release from plugin
+# compatibility warnings. See docs/SPORTS_UNIFICATION.md (phase B4).
+on:
+  push:
+    tags: ["v*"]
+  release:
+    types: [published]
+  # Pre-flight: run this against the tag you are about to create.
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: "Tag to check (e.g. v3.2.0)"
+        required: true
+        type: string
+
+permissions:
+  contents: read
+
+jobs:
+  version-matches-tag:
+    name: Tag matches src.__version__
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          persist-credentials: false
+
+      - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
+        with:
+          python-version: "3.13"
+
+      # No dependencies: the script reads src/__init__.py and CHANGELOG.md only.
+      - name: Assert the tag, CHANGELOG and src.__version__ agree
+        run: python scripts/check_release_version.py "${TAG}"
+        env:
+          TAG: ${{ inputs.tag || github.ref_name }}

.github/workflows/test.yml

@@ -0,0 +1,208 @@
+name: Tests
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+  # Manual runs against any branch — useful when a PR's automatic run
+  # needs a re-run or didn't get created.
+  workflow_dispatch:
+
+# The jobs only check out the repo and run the tests.
+permissions:
+  contents: read
+
+jobs:
+  plugin-safety:
+    name: Plugin safety harness + unit tests (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    # The two Pythons the installer supports: Raspberry Pi OS Bookworm ships
+    # 3.11 and Trixie 3.13.
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.13"]
+    env:
+      # The bundled fixture plugin gives the harness at least one real plugin
+      # to render, and REQUIRE_PLUGINS turns "discovered zero plugins" into a
+      # hard failure instead of a silent all-skip green run.
+      LEDMATRIX_PLUGINS_DIR: test/fixtures/plugins
+      LEDMATRIX_REQUIRE_PLUGINS: "1"
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          persist-credentials: false
+
+      - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r requirements.txt -r web_interface/requirements.txt -r requirements-test.txt
+          pip install RGBMatrixEmulator
+
+      - name: Run plugin safety harness
+        run: |
+          pytest --no-cov test/plugins/
+
+  unit-tests:
+    name: Core unit tests (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    # Bookworm's Python (3.11) and Trixie's (3.13); see plugin-safety.
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.13"]
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          persist-credentials: false
+
+      - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r requirements.txt -r web_interface/requirements.txt -r requirements-test.txt
+          pip install RGBMatrixEmulator
+
+      # Run the ENTIRE test tree (except test/plugins, which the
+      # plugin-safety job owns). New test files are enrolled automatically;
+      # excluding anything requires a visible, commented --ignore here.
+      # Coverage is measured and enforced only in this step — pytest.ini
+      # deliberately carries no coverage flags so local runs stay fast.
+      - name: Run core unit suites
+        run: |
+          pytest -m "not hardware" test/ \
+            --ignore=test/plugins \
+            --cov=src --cov=web_interface \
+            --cov-report=term \
+            --cov-fail-under=52
+
+  js-tests:
+    name: Web UI JS tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          persist-credentials: false
+
+      - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
+        with:
+          python-version: "3.13"
+          cache: pip
+
+      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
+        with:
+          node-version: "22"
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r requirements.txt -r web_interface/requirements.txt
+          npm install --no-audit --no-fund --prefix test/js
+
+      # The DOM suites test the real server-rendered pages and API, so they
+      # need the web interface running. REQUIRE_DOM turns "couldn't reach it"
+      # into a failure instead of a silent skip.
+      - name: Start the web interface
+        run: |
+          EMULATOR=true python -c "from web_interface.app import app; app.run(host='127.0.0.1', port=5000, threaded=True)" > web.log 2>&1 &
+          for i in $(seq 60); do curl -sf -o /dev/null http://127.0.0.1:5000/ && exit 0; sleep 1; done
+          cat web.log
+          exit 1
+
+      - name: Run JS suites
+        env:
+          BASE: http://127.0.0.1:5000
+          REQUIRE_DOM: "1"
+        run: node test/js/run_all.js
+
+  css-build:
+    name: Tailwind CSS is up to date
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          persist-credentials: false
+
+      - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
+        with:
+          python-version: "3.13"
+
+      # Downloads the pinned standalone Tailwind CLI (SHA-256 checked; no
+      # Node), rebuilds static/v3/tailwind.css and plugin-frame.css from the
+      # templates and JS, and fails if the committed files differ. Fix a
+      # failure by running `python3 scripts/build_css.py` and committing.
+      - name: Check the committed CSS matches a fresh build
+        run: python scripts/build_css.py --check
+
+  type-check:
+    name: Type check (mypy ratchet)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          persist-credentials: false
+
+      - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
+        with:
+          python-version: "3.13"
+          cache: pip
+
+      # The runtime requirements are installed so mypy sees the real types of
+      # PIL, requests, psutil and friends -- missing, they'd be Any and the
+      # result would differ from a developer's machine. mypy and the stubs are
+      # pinned so a new release can't turn this red without a code change.
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r requirements.txt -r web_interface/requirements.txt
+          pip install mypy==1.20.2 types-requests==2.33.0.20260906 types-pytz==2026.4.0.20260926
+
+      # mypy on exactly the modules in mypy-clean.txt; fails on any error in
+      # them, or if a listed file is missing. See CONTRIBUTING.md.
+      - name: Run mypy on the ratchet list
+        run: python scripts/check_types.py
+
+  sports-drift-report:
+    name: Sports drift report (report only)
+    runs-on: ubuntu-latest
+    # A progress measure for docs/SPORTS_UNIFICATION.md, never a gate: the
+    # monorepo's own check_sports_drift.py is the gate. The step summary shows
+    # how many bodies each scoreboard method family still has.
+    continue-on-error: true
+    steps:
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          persist-credentials: false
+
+      - name: Check out ledmatrix-plugins (main)
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+        with:
+          repository: ChuckBuilds/ledmatrix-plugins
+          path: ledmatrix-plugins
+          persist-credentials: false
+
+      - uses: actions/setup-python@0b93645e9fea7318ecaed2b359559ac225c90a2b # v5.3.0
+        with:
+          python-version: "3.13"
+
+      # Stdlib only; exits 0 whatever it finds.
+      - name: Report method-family drift across the nine scoreboards
+        run: |
+          python scripts/sports_drift_report.py --plugins ledmatrix-plugins \
+            --markdown --json sports-drift.json >> "$GITHUB_STEP_SUMMARY"
+          python scripts/sports_drift_report.py --plugins ledmatrix-plugins
+
+      - name: Upload the full report
+        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        with:
+          name: sports-drift-report
+          path: sports-drift.json

.gitignore

@@ -3,8 +3,13 @@ __pycache__/
 *.py[cod]
 *$py.class
 
-# Secrets
-config/config_secrets.json
+# Secrets and per-device state. Everything the software writes into config/
+# is local to one device -- config.json, config_secrets.json, wifi_config.json,
+# ytm_auth.json (a login session), saved_repositories.json, font_overrides.json,
+# and the temp files atomic writes leave behind when interrupted -- so only
+# the templates are tracked. Listing files one by one missed several.
+config/*
+!config/*.template.json
 credentials.json
 token.pickle
 
@@ -13,6 +18,7 @@ token.pickle
 .venv
 env/
 venv/
+venv*/
 ENV/
 
 # IDE
@@ -20,6 +26,64 @@ ENV/
 .idea/
 *.swp
 *.swo 
+emulator_config.json
 
-# Cache directory
-cache/
+# Testing
+.pytest_cache/
+.coverage
+htmlcov/
+.mypy_cache/
+
+# Cache directory (root level only, not src/cache which is source code)
+/cache/
+
+# Development plugins directory: symlinks into a ledmatrix-plugins checkout
+# See docs/PLUGIN_DEVELOPMENT_GUIDE.md and docs/MULTI_ROOT_WORKSPACE_SETUP.md
+plugins/*
+!plugins/.gitkeep
+# Local settings for scripts/dev/dev_plugin_setup.sh (template: dev_plugins.json.example)
+/dev_plugins.json
+
+# Binary files and backups
+bin/pixlet/
+config/backups/
+
+# Starlark apps runtime storage (installed .star files and cached renders)
+/starlark-apps/
+
+# JS test deps (test/js)
+node_modules/
+package-lock.json
+
+# Team logos fetched at runtime.
+#
+# src/logo_downloader.py and LogoHelper write into assets/sports/<league>_logos/
+# whenever a plugin meets a team whose logo is not on disk. Those directories are
+# also tracked -- 209 NCAA logos and 153 soccer ones ship with the repo -- so
+# every rig accumulated untracked files it was never meant to commit and
+# `git status` was permanently dirty. That noise is not harmless: it trains
+# everyone to ignore the one signal that says a checkout is not what you think
+# it is, which is how a stale tree sat unnoticed on a rig until a restart
+# surfaced four dead sports plugins.
+#
+# Ignoring a directory does not untrack what is already in it, so the logos that
+# ship keep shipping. Only new downloads are hidden.
+#
+# Adding a logo on purpose is rare and deliberate -- the last time was #415, four
+# named NCAA logos a plugin needed, and there has been no other in a year. Do it
+# with an explicit override:
+#     git add -f assets/sports/ncaa_logos/DUKE.png
+assets/sports/*_logos/
+assets/stocks/ticker_icons/
+assets/stocks/crypto_icons/
+
+# Plugin operation state written at runtime.
+#
+# web_interface/app.py writes data/plugin_state.json and data/operation_history.json
+# (older releases also data/plugin_operations.json) as the web interface runs, into
+# a directory that ships tracked (data/.gitkeep). Unignored, every rig that ever
+# opened the web UI -- and every test run that constructs the app -- would leave
+# untracked files behind and a permanently dirty `git status`. Same reasoning as
+# the logo rule above: a checkout that is always dirty is a checkout nobody reads.
+data/*
+!data/.gitkeep

.gitmodules

@@ -0,0 +1,4 @@
+[submodule "rpi-rgb-led-matrix-master"]
+	path = rpi-rgb-led-matrix-master
+	url = https://github.com/hzeller/rpi-rgb-led-matrix.git
+	branch = master

.pre-commit-config.yaml

@@ -0,0 +1,72 @@
+# Pre-commit hooks for LEDMatrix
+# Install: pip install pre-commit && pre-commit install
+# Run manually: pre-commit run --all-files
+
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.5.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-json
+      - id: check-added-large-files
+        args: ['--maxkb=1000']
+      - id: check-merge-conflict
+
+  - repo: https://github.com/PyCQA/flake8
+    rev: 7.0.0
+    hooks:
+      - id: flake8
+        args: ['--select=E9,F63,F7,F82,B', '--ignore=E501']
+        additional_dependencies: [flake8-bugbear]
+
+  - repo: local
+    hooks:
+      - id: no-bare-except
+        name: Check for bare except clauses
+        entry: bash -c 'if grep -rn "except:\s*pass" src/; then echo "Found bare except:pass - please handle exceptions properly"; exit 1; fi'
+        language: system
+        types: [python]
+        pass_filenames: false
+
+      - id: no-hardcoded-paths
+        name: Check for hardcoded user paths
+        entry: bash -c 'if grep -rn "/home/chuck/" src/; then echo "Found hardcoded user paths - please use relative paths or config"; exit 1; fi'
+        language: system
+        types: [python]
+        pass_filenames: false
+
+  # The mypy ratchet -- the same check as CI's "Type check (mypy ratchet)"
+  # job: mypy on exactly the modules listed in mypy-clean.txt. Run it with
+  #   pre-commit run mypy --hook-stage manual
+  # A local hook rather than mirrors-mypy so mypy sees the packages installed
+  # from requirements.txt, as CI does; an isolated hook env without them types
+  # PIL, requests and friends as Any and reports different errors. Needs
+  # mypy==1.20.2 (the version CI pins) in the environment you commit from.
+  - repo: local
+    hooks:
+      - id: mypy
+        name: mypy (ratchet, mypy-clean.txt)
+        entry: python scripts/check_types.py
+        language: system
+        pass_filenames: false
+        always_run: true
+        stages: [manual]
+
+  - repo: https://github.com/PyCQA/bandit
+    rev: 1.8.3
+    hooks:
+      - id: bandit
+        args:
+          - '-r'
+          - '-ll'
+          - '-c'
+          - 'bandit.yaml'
+          - '-x'
+          - './tests,./test,./venv,./.venv,./scripts/prove_security.py,./rpi-rgb-led-matrix-master'
+
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.24.3
+    hooks:
+      - id: gitleaks

CACHE_STRATEGY.md

@@ -1,173 +0,0 @@
-# LEDMatrix Cache Strategy Analysis
-
-## Current Implementation
-
-Your LEDMatrix system uses a sophisticated multi-tier caching strategy that balances data freshness with API efficiency.
-
-### Cache Duration Categories
-
-#### 1. **Ultra Time-Sensitive Data (15-60 seconds)**
-- **Live Sports Scores**: Now respects sport-specific `live_update_interval` configuration
-  - Soccer live data: Uses `soccer_scoreboard.live_update_interval` (default: 60 seconds)
-  - NFL live data: Uses `nfl_scoreboard.live_update_interval` (default: 60 seconds)
-  - NHL live data: Uses `nhl_scoreboard.live_update_interval` (default: 60 seconds)
-  - NBA live data: Uses `nba_scoreboard.live_update_interval` (default: 60 seconds)
-  - MLB live data: Uses `mlb.live_update_interval` (default: 60 seconds)
-  - NCAA sports: Use respective `live_update_interval` configurations (default: 60 seconds)
-- **Current Weather**: 5 minutes (300 seconds)
-
-#### 2. **Market Data (5-10 minutes)**
-- **Stocks**: 10 minutes (600 seconds) - market hours aware
-- **Crypto**: 5 minutes (300 seconds) - 24/7 trading
-- **Stock News**: 1 hour (3600 seconds)
-
-#### 3. **Sports Data (5 minutes to 24 hours)**
-- **Recent Games**: 5 minutes (300 seconds)
-- **Upcoming Games**: 1 hour (3600 seconds)
-- **Season Schedules**: 24 hours (86400 seconds)
-- **Team Information**: 1 week (604800 seconds)
-
-#### 4. **Static Data (1 week to 30 days)**
-- **Team Logos**: 30 days (2592000 seconds)
-- **Configuration Data**: 1 week (604800 seconds)
-
-### Smart Cache Invalidation
-
-Beyond time limits, the system uses content-based invalidation:
-
-```python
-def has_data_changed(self, data_type: str, new_data: Dict[str, Any]) -> bool:
-    """Check if data has changed from cached version."""
-```
-
-- **Weather**: Compares temperature and conditions
-- **Stocks**: Compares prices (only during market hours)
-- **Sports**: Compares scores, game status, inning details
-- **News**: Compares headlines and article IDs
-
-### Market-Aware Caching
-
-For stocks, the system extends cache duration during off-hours:
-
-```python
-def _is_market_open(self) -> bool:
-    """Check if the US stock market is currently open."""
-    # Only invalidates cache during market hours
-```
-
-## Enhanced Cache Strategy
-
-### Sport-Specific Live Update Intervals
-
-The cache manager now automatically respects the `live_update_interval` configuration for each sport:
-
-```python
-def get_sport_live_interval(self, sport_key: str) -> int:
-    """Get the live_update_interval for a specific sport from config."""
-    config = self.config_manager.get_config()
-    sport_config = config.get(f"{sport_key}_scoreboard", {})
-    return sport_config.get("live_update_interval", 30)
-```
-
-### Automatic Sport Detection
-
-The cache manager automatically detects the sport from cache keys:
-
-```python
-def get_sport_key_from_cache_key(self, key: str) -> Optional[str]:
-    """Extract sport key from cache key to determine appropriate live_update_interval."""
-    # Maps cache key patterns to sport keys
-    sport_patterns = {
-        'nfl': ['nfl', 'football'],
-        'nba': ['nba', 'basketball'],
-        'mlb': ['mlb', 'baseball'],
-        'nhl': ['nhl', 'hockey'],
-        'soccer': ['soccer', 'football'],
-        # ... etc
-    }
-```
-
-### Configuration Examples
-
-**Current Configuration (config/config.json):**
-```json
-{
-    "nfl_scoreboard": {
-        "live_update_interval": 30,
-        "enabled": true
-    },
-    "soccer_scoreboard": {
-        "live_update_interval": 30,
-        "enabled": false
-    },
-    "mlb": {
-        "live_update_interval": 30,
-        "enabled": true
-    }
-}
-```
-
-**Cache Behavior:**
-- NFL live data: 30-second cache (from config)
-- Soccer live data: 30-second cache (from config)
-- MLB live data: 30-second cache (from config)
-
-### Fallback Strategy
-
-If configuration is unavailable, the system uses sport-specific defaults:
-
-```python
-default_intervals = {
-    'soccer': 60,      # Soccer default
-    'nfl': 60,         # NFL default
-    'nhl': 60,         # NHL default
-    'nba': 60,         # NBA default
-    'mlb': 60,         # MLB default
-    'milb': 60,        # Minor league default
-    'ncaa_fb': 60,    # College football default
-    'ncaa_baseball': 60,  # College baseball default
-    'ncaam_basketball': 60,  # College basketball default
-}
-```
-
-## Usage Examples
-
-### Automatic Sport Detection
-```python
-# Cache manager automatically detects NFL and uses nfl_scoreboard.live_update_interval
-cached_data = cache_manager.get_with_auto_strategy("nfl_live_20241201")
-
-# Cache manager automatically detects soccer and uses soccer_scoreboard.live_update_interval
-cached_data = cache_manager.get_with_auto_strategy("soccer_live_20241201")
-```
-
-### Manual Sport Specification
-```python
-# Explicitly specify sport for custom cache keys
-cached_data = cache_manager.get_cached_data_with_strategy("custom_live_key", "sports_live")
-```
-
-## Benefits
-
-1. **Configuration-Driven**: Cache respects your sport-specific settings
-2. **Automatic Detection**: No manual cache duration management needed
-3. **Sport-Optimized**: Each sport uses its appropriate update interval
-4. **Backward Compatible**: Existing code continues to work
-5. **Flexible**: Easy to adjust intervals per sport in config
-
-## Migration
-
-The enhanced cache manager is backward compatible. Existing code will automatically benefit from sport-specific intervals without any changes needed.
-
-To customize intervals for specific sports, simply update the `live_update_interval` in your `config/config.json`:
-
-```json
-{
-    "nfl_scoreboard": {
-        "live_update_interval": 15  // More aggressive for NFL
-    },
-    "mlb": {
-        "live_update_interval": 45  // Slower pace for MLB
-    }
-}
-``` 

CLAUDE.md

@@ -0,0 +1,60 @@
+# LEDMatrix
+
+## Project Structure
+- `src/plugin_system/` — Plugin loader, manager, store manager, base plugin class
+- `web_interface/` — Flask web UI (blueprints, templates, static JS)
+- `config/config.json` — User plugin configuration (persists across plugin reinstalls)
+- `plugin-repos/` — **Default** plugin install directory used by the
+  Plugin Store, set by `plugin_system.plugins_directory` in
+  `config.json` (default per `config/config.template.json`).
+  Not gitignored.
+- `plugins/` — Legacy/dev plugin location. Gitignored (`plugins/*`).
+  Used by `scripts/dev/dev_plugin_setup.sh` for symlinks. The plugin
+  loader does NOT fall back to it — `PluginManager.discover_plugins()`
+  (`src/plugin_system/plugin_manager.py`) scans only the configured
+  directory. Fallbacks exist in two narrower places: store operations
+  (`PluginStoreManager._find_plugin_path()` in `store_manager.py`, which
+  searches `store_search_dirs()` from `plugin_dirs.py`) and schema lookup
+  (`SchemaManager.get_schema_path()` in `schema_manager.py`, which probes
+  `plugins/` *before* `plugin-repos/`).
+- `src/plugin_system/plugin_dirs.py` — the one resolver for "which directory
+  holds plugin X" (manifest `id` first, then `<id>` / `ledmatrix-<id>`)
+
+## Plugin System
+- Plugins inherit from `BasePlugin` in `src/plugin_system/base_plugin.py`
+- Required abstract methods: `update()`, `display(force_clear=False)`
+- Each plugin needs: `manifest.json`, `config_schema.json`, and the entry point (`manager.py` by default); `requirements.txt` if it has dependencies. Required manifest fields: `docs/PLUGIN_API_REFERENCE.md#manifest-required-fields`
+- Plugin instantiation args: `plugin_id, config, display_manager, cache_manager, plugin_manager`
+- Config schemas use JSON Schema Draft-7
+- Display dimensions: always read dynamically from `self.display_manager.width/height` — not `display_manager.matrix.width/height`, because `matrix` is `None` when hardware init fails (the properties fall back to the canvas size)
+- Secrets: namespaced by plugin id in `config/config_secrets.json`, declared
+  via `"x-secret": true` in the plugin's config schema, and deep-merged into
+  the plugin's config dict at load time — plugins read them with plain
+  `config.get(...)`, never a separate accessor
+
+## Dev Workflow
+- Link a plugin for development: `./scripts/dev/dev_plugin_setup.sh link-github <name>` clones the `ledmatrix-plugins` monorepo into `~/.ledmatrix-dev-plugins/` and links its `plugins/<name>` under the manifest id (add a repo URL for a plugin with its own repo; or `link <name> <path>`); symlinks land in `plugins/` — set `plugin_system.plugins_directory` to `plugins` so discovery picks them up. Fork/location overrides: `dev_plugins.json` (from `dev_plugins.json.example`)
+- Browser preview without the display loop: `python3 scripts/dev_server.py` → http://localhost:5001
+- Full display in emulator mode: `python3 run.py -e` (or `EMULATOR=true python3 run.py`)
+- Validate one plugin headlessly: `python3 scripts/check_plugin.py --plugin <id>`
+- Soak a rig for frame timing (on the Pi, service running): `python3 scripts/frame_soak.py --preview` — late-frame rate across every scroller; see `docs/SCROLL_PERFORMANCE.md`
+
+## Plugin Store Architecture
+- Official plugins live in the `ledmatrix-plugins` monorepo (not individual repos)
+- Plugin repo naming convention: `ledmatrix-<plugin-id>` (e.g., `ledmatrix-football-scoreboard`)
+- `plugins.json` registry at `https://raw.githubusercontent.com/ChuckBuilds/ledmatrix-plugins/main/plugins.json`
+- Store manager (`PluginStoreManager` in `src/plugin_system/store_manager.py`) handles install/update/uninstall
+- Monorepo plugins are installed without a `.git` directory: GitHub Trees API + raw downloads, falling back to ZIP extraction
+- Update detection for monorepo plugins uses version comparison (manifest version vs registry latest_version)
+- Optional registry entry fields (`store_registry.py`): `ledmatrix_min_version` refuses an incompatible install/update before the download (the post-download manifest gate stays as the fallback); `aliases` are the entry's other ids (manifest id `ledmatrix-weather` for `weather`), used with the `plugin_path` name by update/uninstall/reinstall to find the install — only this registry proof counts, never a bare `ledmatrix-<id>` folder (owner decision, #686; such a folder is only logged); `commit` is informational. An older plugins.json has none of them
+- Plugin configs stored in `config/config.json`, NOT in plugin directories — safe across reinstalls
+- Third-party plugins can use their own repo URL with empty `plugin_path`
+
+## Common Pitfalls
+- paho-mqtt 2.x requires a `CallbackAPIVersion` argument: `VERSION1` for code written against v1 callback signatures (the MQTT bridge uses `VERSION2`)
+- BasePlugin uses `get_logger()` from `src.logging_config`, not standard `logging.getLogger()`
+- `DisplayManager` has no `draw_image()` — paste onto the PIL image directly:
+  `self.display_manager.image.paste(img, (x, y))` then `update_display()`
+  (use a mask for transparency: `image.paste(rgba, (x, y), rgba)`)
+- When modifying a plugin in the monorepo, you MUST bump `version` in its `manifest.json` and run `python update_registry.py` — otherwise users won't receive the update
+- `src/pi5_matrix_support.py` hardcodes what the pinned `rpi-rgb-led-matrix-master` can drive on a Raspberry Pi 5 (`Rp1PioConfigSupported()` in `lib/rp1/rp1_pio_backend.cc`). Re-check it whenever the submodule is bumped: a stale rule blocks Pi 5 settings the new library supports, and a missing one lets the display service crash-loop. `src/matrix_support.py` holds the same kind of rules for every board (rows, chain length, mapping names, parallel per mapping) and needs the same re-check

CODE_OF_CONDUCT.md

@@ -0,0 +1,137 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+This includes the LEDMatrix Discord server, GitHub repositories owned by
+ChuckBuilds, and any other forums hosted by or affiliated with the project.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement on the
+[LEDMatrix Discord](https://discord.gg/RdrC37rEag) (DM a moderator or
+ChuckBuilds directly) or by opening a private GitHub Security Advisory if
+the issue involves account safety. All complaints will be reviewed and
+investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,129 @@
+# Contributing to LEDMatrix
+
+Thanks for considering a contribution! LEDMatrix is built with help from
+the community and we welcome bug reports, plugins, documentation
+improvements, and code changes.
+
+## Quick links
+
+- **Bugs / feature requests**: open an issue using one of the templates
+  in [`.github/ISSUE_TEMPLATE/`](.github/ISSUE_TEMPLATE/).
+- **Real-time discussion**: the
+  [LEDMatrix Discord](https://discord.gg/RdrC37rEag).
+- **Plugin development**:
+  [`docs/PLUGIN_DEVELOPMENT_GUIDE.md`](docs/PLUGIN_DEVELOPMENT_GUIDE.md)
+  and the [`ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins)
+  repository.
+- **Security issues**: see [`SECURITY.md`](SECURITY.md). Please don't
+  open public issues for vulnerabilities.
+
+## Setting up a development environment
+
+1. Clone with submodules:
+   ```bash
+   git clone --recurse-submodules https://github.com/ChuckBuilds/LEDMatrix.git
+   cd LEDMatrix
+   ```
+2. For development without hardware, run the dev preview server:
+   ```bash
+   python3 scripts/dev_server.py
+   # then open http://localhost:5001
+   ```
+   See [`docs/DEV_PREVIEW.md`](docs/DEV_PREVIEW.md) for details.
+3. To run the full display in emulator mode:
+   ```bash
+   EMULATOR=true python3 run.py
+   ```
+4. To target real hardware on a Raspberry Pi, follow the install
+   instructions in the root [`README.md`](README.md).
+
+## Running the tests
+
+```bash
+pip install -r requirements.txt -r requirements-test.txt
+pytest
+```
+
+See [`docs/HOW_TO_RUN_TESTS.md`](docs/HOW_TO_RUN_TESTS.md) for details
+on test markers, the per-plugin tests, and the web-interface
+integration tests.
+
+## Submitting changes
+
+1. **Open an issue first** for non-trivial changes. This avoids
+   wasted work on PRs that don't fit the project direction.
+2. **Create a topic branch** off `main`:
+   `feat/<short-description>`, `fix/<short-description>`,
+   `docs/<short-description>`.
+3. **Keep PRs focused.** One conceptual change per PR. If you find
+   adjacent bugs while working, fix them in a separate PR.
+4. **Follow the existing code style.** The pre-commit hooks run
+   `flake8` (E9, F63, F7, F82 plus bugbear `B` checks), `bandit`,
+   and `gitleaks` — install the CLI with
+   `python -m pip install pre-commit`, then run
+   `pre-commit install` so they run on every commit. Type checking
+   is a ratchet while the existing mypy errors in `src/` are paid
+   down: `mypy-clean.txt` lists the modules that type-check clean, and
+   CI runs `python scripts/check_types.py` (also the manual hook
+   `pre-commit run mypy --hook-stage manual`) to keep every listed
+   module clean. When you make another module clean, add it to the
+   list (sorted); don't take one off to get CI green. Keep type fixes
+   annotation-only where you can -- widen a hint rather than delete a
+   defensive runtime check mypy calls unreachable. HTML/JS in
+   `web_interface/` follows the patterns already in `templates/v3/`
+   and `static/v3/`. If you change a template or a static JS file,
+   run `python3 scripts/build_css.py` and commit the regenerated
+   `static/v3/tailwind.css` with it -- CI fails when the committed CSS
+   is out of date. It needs no Node; see
+   [`web_interface/README.md`](web_interface/README.md#styling-tailwind-css).
+5. **Update documentation** alongside code changes. If you add a
+   config key, document it in the relevant `*.md` file (or, for
+   plugins, in `config_schema.json` so the form is auto-generated).
+6. **Run the tests** locally before opening the PR.
+7. **Use the PR template** — `.github/PULL_REQUEST_TEMPLATE.md` will
+   prompt you for what we need.
+
+## Commit message convention
+
+Conventional Commits is encouraged but not strictly enforced:
+
+- `feat: add NHL playoff bracket display`
+- `fix(plugin-loader): handle missing class_name in manifest`
+- `docs: correct web UI port in TROUBLESHOOTING.md`
+- `refactor(cache): consolidate strategy lookup`
+
+Keep the subject under 72 characters; put the why in the body.
+
+## Contributing a plugin
+
+LEDMatrix plugins live in their own repository:
+[`ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins).
+Plugin contributions go through that repo's
+[`SUBMISSION.md`](https://github.com/ChuckBuilds/ledmatrix-plugins/blob/main/SUBMISSION.md)
+process. The
+[`hello-world` plugin](https://github.com/ChuckBuilds/ledmatrix-plugins/tree/main/plugins/hello-world)
+is the canonical starter template.
+
+## Reviewing pull requests
+
+Maintainer review is by [@ChuckBuilds](https://github.com/ChuckBuilds).
+Community review is welcome on any open PR — leave constructive
+comments, test on your hardware if applicable, and call out anything
+unclear.
+
+## Code of conduct
+
+This project follows the [Contributor Covenant](CODE_OF_CONDUCT.md). By
+participating you agree to abide by its terms.
+
+## License
+
+LEDMatrix is licensed under the [GNU General Public License v3.0 or
+later](LICENSE). By submitting a contribution you agree to license it
+under the same terms (the standard "inbound = outbound" rule that
+GitHub applies by default).
+
+LEDMatrix builds on
+[`rpi-rgb-led-matrix`](https://github.com/hzeller/rpi-rgb-led-matrix),
+which is GPL-2.0-or-later. The "or later" clause makes it compatible
+with GPL-3.0 distribution.

LEDMatrix.code-workspace

@@ -0,0 +1,19 @@
+{
+	"folders": [
+		{
+			"path": ".",
+			"name": "LEDMatrix (Main)"
+		},
+		{
+			"path": "../ledmatrix-plugins",
+			"name": "Plugins (Monorepo)"
+		}
+	],
+	"settings": {
+		"files.exclude": {
+			"**/.git": true,
+			"**/__pycache__": true,
+			"**/*.pyc": true
+		}
+	}
+}

LICENSE

@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

Matrix Stand STL/LICENSE.txt

@@ -1 +0,0 @@
-This thing was created by Thingiverse user randomwire, and is licensed under cc.

Matrix Stand STL/README.txt

@@ -1 +0,0 @@
-P4 Matrix Stand by randomwire on Thingiverse: https://www.thingiverse.com/thing:5169867

PRODUCT.md

@@ -0,0 +1,74 @@
+# Product
+
+<!-- impeccable:product-schema 1 -->
+
+## Platform
+
+web
+
+## Users
+
+Designed novice-first, with power tools kept within reach.
+
+- **Primary: hobbyist builders.** People who assembled an LED matrix panel on a Raspberry Pi, often by following the install video, and are frequently new to Linux and the Pi. They set the display up once (panel size, timezone, WiFi), install and enable a few plugins, then come back occasionally to tweak what the panel shows. They usually reach the control panel from a phone or laptop on their home network, sometimes as an installed home-screen app.
+- **Secondary: tinkerers and plugin developers.** Comfortable with SSH, `config.json`, and GitHub. They lean on the Config Editor, Logs, Cache, Operation History, Tools, GitHub-repo installs, and per-plugin config while building or debugging. Their tools must stay reachable without sitting in the novice's path.
+
+## Product Purpose
+
+LEDMatrix turns a Raspberry Pi and an RGB LED matrix panel into an information-rich display (clock, weather, calendar, sports scores, stocks, music, and more) through a plugin platform. The web control panel ("LED Matrix Control") is where the display gets configured, extended, and kept healthy.
+
+Success means a builder gets from a freshly flashed Pi to a working, personalized display without needing a terminal, and can keep it running (updates, recovery, troubleshooting) the same way.
+
+## Positioning
+
+Four strengths define LEDMatrix, and future work must protect all of them:
+
+1. **Plugin ecosystem.** The core ships only `starlark-apps` and `web-ui-info`; everything else comes from the built-in Plugin Store (the official `ledmatrix-plugins` monorepo), third-party GitHub repos, or Starlark (Tidbyt-style) apps. Each installed plugin gets its own configuration tab, generated from its schema.
+2. **Runs on tiny Pis.** The UI is served by the same device that drives the matrix, on boards as small as the Pi Zero 2 W (512 MB), Pi 3/3B+, and the 1 GB Pi 4.
+3. **Recovers without SSH.** WiFi access-point fallback with a captive setup page, backup & restore, in-UI updates, live logs, diagnostics, service control, and plugin health let users fix problems from the browser.
+4. **Open and community-led.** GPL-3.0, a Discord community, and contributions welcome. The maintainer (ChuckBuilds) builds in public and openly relies on AI development tools.
+
+## Operating Context
+
+- **Access.** Served on the local network at `http://<pi-ip>:5000` by the `ledmatrix-web` service. It is installable as a PWA (`web_interface/static/v3/manifest.json`, short name "LEDMatrix").
+- **First run.** When the Pi has no network it creates its own WiFi access point, so the captive setup page (`templates/v3/captive_setup.html`) may be the very first screen a user sees, on a phone, with no internet connection.
+- **Navigation.**
+  - System tabs: Overview, General, WiFi, Schedule, Display, Rotation, Config Editor, Backup & Restore, Fonts, Logs, Cache, Operation History, Tools.
+  - A second row holds Plugin Manager (with the Plugin Store), Starlark Apps, and one tab per installed plugin.
+- **Live data.** The Overview shows system stats (CPU, memory, temperature, power/throttling) and a live display preview, streamed over SSE.
+- **Getting Started checklist.** The Overview's first-run checklist runs: set panel size → set timezone → install a plugin → enable it → configure it.
+- **Development.** `python3 scripts/dev_server.py` gives a browser preview without the display loop; `python3 run.py -e` runs the full display in emulator mode.
+
+## Capabilities and Constraints
+
+- **Hard constraint: plugin UI compatibility.** Third-party plugins rely on JSON Schema (Draft-7) generated config forms, the widget registry (`static/v3/js/widgets/`), `x-secret` fields, and plugin web-UI actions. UI changes must keep these working.
+- **Config storage.** Plugin configuration lives in `config/config.json` and secrets in `config/config_secrets.json`, never in plugin directories, so configs survive reinstalls.
+- **Stack.** An existing Flask + HTMX + Alpine.js app with Jinja templates (`web_interface/templates/v3/`) and static JS/CSS (`web_interface/static/v3/`), with self-hosted vendor assets.
+- **Terminology.** Plugin, Plugin Store, Starlark app, rotation, display duration, Vegas Scroll Mode, on-demand, AP mode.
+- **Open decisions** (offered during init, not adopted as constraints):
+  - Whether the UI must work fully offline, with no CDN fallbacks at runtime.
+  - Whether a Node/CSS build step is acceptable for contributors.
+  - Whether a formal accessibility standard (e.g. WCAG 2.2 AA) is a requirement.
+
+## Brand Commitments
+
+- **Names.** The product is "LEDMatrix" and the web UI is titled "LED Matrix Control". The maintainer brand is ChuckBuilds.
+- **Voice.** Friendly, honest, and learning-in-public, as in the README.
+- **App icons.** They live in `web_interface/static/v3/icons/`.
+
+No other visual identity has been made binding.
+
+## Evidence on Hand
+
+- **Photos.** Real photographs of running displays are linked in `README.md` (clock, weather, calendar, NHL/MLB/NFL/NCAA, stocks, music).
+- **Video.** YouTube install and walkthrough videos from ChuckBuilds.
+- **Docs.** Extensive documentation in `docs/`, e.g. `WEB_INTERFACE_GUIDE.md`, `GETTING_STARTED.md`, `WIFI_NETWORK_SETUP.md`, `LOW_MEMORY_BOARDS.md`, `PLUGIN_STORE_GUIDE.md`.
+- **Absences.** There are no testimonials, user counts, or benchmark figures. Do not fabricate them.
+
+## Product Principles
+
+1. **Novice path first, power one click away.** Default views serve the first-time builder, while advanced tools stay discoverable for tinkerers.
+2. **Never strand the user at a terminal.** Every setup, recovery, and troubleshooting task has a browser path, including from the AP-mode captive page.
+3. **Respect the Pi.** Every feature is paid for in memory and CPU on a Pi Zero 2 W that is also driving the display.
+4. **The ecosystem is the product.** Plugins, including third-party ones, must feel first-class and keep working across core UI changes.
+5. **Honest and welcoming.** Plain language, truthful status, and no overstated claims, in keeping with an open, community-built project.

SECURITY.md

@@ -0,0 +1,109 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+If you've found a security issue in LEDMatrix, **please don't open a
+public GitHub issue**. Disclose it privately so we can fix it before it's
+exploited.
+
+### How to report
+
+Use one of these channels, in order of preference:
+
+1. **GitHub Security Advisories** (preferred). On the LEDMatrix repo,
+   go to **Security → Advisories → Report a vulnerability**. This
+   creates a private discussion thread visible only to you and the
+   maintainer.
+   - Direct link: <https://github.com/ChuckBuilds/LEDMatrix/security/advisories/new>
+2. **Discord DM**. Send a direct message to a moderator on the
+   [LEDMatrix Discord](https://discord.gg/RdrC37rEag). Don't post in
+   public channels.
+
+Please include:
+
+- A description of the issue
+- The version / commit hash you're testing against
+- Steps to reproduce, ideally a minimal proof of concept
+- The impact you can demonstrate
+- Any suggested mitigation
+
+### What to expect
+
+- An acknowledgement within a few days (this is a hobby project, not
+  a 24/7 ops team).
+- A discussion of the issue's severity and a plan for the fix.
+- Credit in the release notes when the fix ships, unless you'd
+  prefer to remain anonymous.
+- For high-severity issues affecting active deployments, we'll
+  coordinate disclosure timing with you.
+
+## Scope
+
+In scope for this policy:
+
+- The LEDMatrix display controller, web interface, and plugin loader
+  in this repository
+- The official plugins in
+  [`ledmatrix-plugins`](https://github.com/ChuckBuilds/ledmatrix-plugins)
+- Installation scripts and systemd unit files
+
+Out of scope (please report upstream):
+
+- Vulnerabilities in `rpi-rgb-led-matrix` itself —
+  report to <https://github.com/hzeller/rpi-rgb-led-matrix>
+- Vulnerabilities in Python packages we depend on — report to the
+  upstream package maintainer
+- Issues in third-party plugins not in `ledmatrix-plugins` — report
+  to that plugin's repository
+
+## Known security model
+
+LEDMatrix is designed for trusted local networks. Several limitations
+are intentional rather than vulnerabilities:
+
+- **Web UI authentication is optional and off by default.** Out of the
+  box the web interface assumes the network it's running on is trusted.
+  Setting a password under **General > Security** makes every page and
+  API route require a login or an API token (`Authorization: Bearer`),
+  with wrong passwords rate-limited per address
+  (`web_interface/auth.py`). Deliberately left open even then: requests
+  from the Pi itself (loopback without proxy headers; a reverse proxy on
+  the Pi must add `X-Forwarded-For`, or every request it relays counts as
+  local), the Wi-Fi setup flow while the Pi is in access-point mode,
+  static files, and a status-only `/api/v3/health`. The password is a
+  werkzeug hash and tokens are stored as SHA-256, in
+  `config/config_secrets.json`, which no API returns. There is no TLS:
+  over plain HTTP the password and tokens cross the LAN in the clear, so
+  still don't expose port 5000 to the internet; put a TLS reverse proxy
+  or a VPN in front for remote access. Anyone with shell access to the Pi
+  can turn login off (`scripts/reset_web_password.py`), which is the
+  documented recovery path.
+  "Trusted network" does not mean "trusted websites", though: any page
+  a LAN user opens could make their browser POST to the Pi. So the
+  interface refuses a `POST`/`PUT`/`PATCH`/`DELETE` whose `Origin` (or
+  `Referer`) header names another site (`web_interface/origin_guard.py`),
+  and `/api/v3/system/action` only accepts JSON or HTMX requests. Tools
+  that send neither header (curl, Home Assistant, the MQTT bridge) are
+  unaffected. Not covered: DNS rebinding, and anyone who can reach the
+  port directly.
+- **Plugins run unsandboxed.** Installed plugins execute in the same
+  Python process as the display loop with full file-system and
+  network access. Review plugin code (especially third-party plugins
+  from arbitrary GitHub URLs) before installing. The Plugin Store
+  marks community plugins as **Custom** to highlight this.
+- **The display service runs as root** for hardware GPIO access. This
+  is required by `rpi-rgb-led-matrix`.
+- **`config_secrets.json` is plaintext.** API keys and tokens are
+  stored unencrypted on the Pi. Lock down filesystem permissions on
+  the config directory if this matters for your deployment.
+
+These are documented as known limitations rather than bugs. If you
+have ideas for improving them while keeping the project usable on a
+Pi, open a discussion — we're interested.
+
+## Supported versions
+
+LEDMatrix is rolling-release on `main`. Security fixes land on `main`
+and become available the next time users run **Update Code** from the
+web UI's Overview tab (which does a `git pull`). There are no LTS
+branches.

assets/README.md

@@ -0,0 +1,22 @@
+# assets/
+
+Static assets bundled with LEDMatrix. **Do not delete these directories** —
+several look unused from core code alone but are resolved at runtime by
+installed store plugins.
+
+| Directory | Used by |
+|---|---|
+| `fonts/` | Core (`FontManager`, `DisplayManager`) and most plugins |
+| `sports/` | Core logo tooling (`src/logo_downloader.py`) and the sports scoreboard plugins; team logos are downloaded here on demand |
+| `stocks/` | `ledmatrix-stocks` plugin (`crypto_icons/`, `ticker_icons/`) |
+| `weather/` | `ledmatrix-weather` plugin (weather icons) |
+| `news_logos/` | `news` plugin |
+| `broadcast_logos/` | `news` and `odds-ticker` plugins |
+| `static_images/` | Legacy examples referenced in the `static-image` plugin's docs; the plugin itself stores uploads under `assets/plugins/<plugin-id>/uploads/` |
+| `plugins/` | Per-plugin uploaded files (`assets/plugins/<plugin-id>/uploads/`), served by the web interface |
+
+Plugins resolve these paths relative to the LEDMatrix install directory, so
+the directories are part of the de-facto plugin API even where no file in
+this repo references them. New plugins should bundle their own assets or
+use the per-plugin upload directory instead of adding top-level
+directories here.

assets/fonts/README.md

@@ -9,20 +9,20 @@ from the utils/ directory.
 
 Tom-Thumb.bdf is included in this directory under [MIT license](http://vt100.tarunz.org/LICENSE). Tom-thumb.bdf was created by [@robey](http://twitter.com/robey) and originally published at https://robey.lag.net/2010/01/23/tiny-monospace-font.html
 
-The texguire-27.bdf font was created using the [otf2bdf] tool from the TeX Gyre font.
-```
+The texgyre-27.bdf font was created using the [otf2bdf] tool from the TeX Gyre font.
+```bash
 otf2bdf -v -o texgyre-27.bdf -r 72 -p 27 texgyreadventor-regular.otf
 ```
 
 ## Create your own
 
-Fonts are in a human readable and editbable `*.bdf` format, but unless you
+Fonts are in a human-readable and editable `*.bdf` format, but unless you
 like reading and writing pixels in hex, generating them is probably easier :)
 
 You can use any font-editor to generate a BDF font or use the conversion
 tool [otf2bdf] to create one from some other font format.
 
-Here is an example how you could create a 30pixel high BDF font from some
+Here is an example how you could create a 30-pixel high BDF font from some
 TrueType font:
 
 ```bash
@@ -31,9 +31,9 @@ otf2bdf -v -o myfont.bdf -r 72 -p 30 /path/to/font-Bold.ttf
 
 ## Getting otf2bdf
 
-Installing the tool should be fairly straight-foward
+Installing the tool should be fairly straightforward.
 
-```
+```bash
 sudo apt-get install otf2bdf
 ```
 
@@ -43,7 +43,7 @@ If you like to compile otf2bdf, you might notice that the configure script
 uses some old way of getting the freetype configuration. There does not seem
 to be much activity on the mature code, so let's patch that first:
 
-```
+```bash
 sudo apt-get install -y libfreetype6-dev pkg-config autoconf
 git clone https://github.com/jirutka/otf2bdf.git   # check it out
 cd otf2bdf

assets/sports/all_team_abbreviations.txt

@@ -1,404 +1,53 @@
 NCAAF
-  AAMU => Alabama A&M Bulldogs
-  ACU => Abilene Christian Wildcats
-  ADA => Adams State Grizzlies
-  ADR => Adrian Bulldogs
-  AFA => Air Force Falcons
-  AIC => American International Yellow Jackets
-  AKR => Akron Zips
-  ALA => Alabama Crimson Tide
-  ALB => Albright Lions
-  ALBS => Albany State (GA) Golden Rams
-  ALCN => Alcorn State Braves
-  ALD => Alderson Broaddus Battlers
-  ALF => Alfred Saxons
-  ALL => Allegheny Gators
-  ALST => Alabama State Hornets
-  AMH => Amherst College Mammoths
-  AND => Anderson (IN) Ravens
-  ANG => Angelo State Rams
+  AMH => Amherst Mammoths
   ANN => Anna Maria College Amcats
-  APP => Appalachian State Mountaineers
-  APSU => Austin Peay Governors
   ARIZ => Arizona Wildcats
-  ARK => Arkansas-Monticello Boll Weevils
-  ARMY => Army Black Knights
-  ARST => Arkansas State Red Wolves
-  ASH => Ashland Eagles
-  ASP => Assumption Greyhounds
+  ARK => Arkansas Razorbacks
   ASU => Arizona State Sun Devils
   AUB => Auburn Tigers
-  AUG => St. Augustine's Falcons
-  AUR => Aurora Spartans
-  AUS => Austin College 'Roos
-  AVE => Averett Cougars
-  AVI => Avila College Eagles
-  AZU => Azusa Pacific Cougars
-  BAK => Baker University Wildcats
-  BAL => Baldwin Wallace Yellow Jackets
-  BALL => Ball State Cardinals
-  BAT => Bates College Bobcats
-  BAY => Baylor Bears
-  BC => Boston College Eagles
-  BEC => Becker College Hawks
-  BEL => Beloit College Buccaneers
-  BEN => Benedictine University (IL) Eagles
-  BENT => Bentley Falcons
-  BET => Bethel (TN) Wildcats
-  BGSU => Bowling Green Falcons
-  BHS => Black Hills State Yellow Jackets
-  BIR => Birmingham-Southern Panthers
-  BKN => Bacone College Warriors
-  BLA => Blackburn Beavers
-  BLOM => Bloomsburg Huskies
-  BLU => Bluffton Beavers
-  BOW => Bowdoin Polar Bears
-  BRI => British Columbia Thunderbirds
-  BRWN => Brown Bears
-  BST => Bemidji State Beavers
-  BSU => Bowie State Bulldogs
-  BUCK => Bucknell Bison
-  BUE => Buena Vista Beavers
-  BUF => Buffalo State Bengals
-  BUFF => Buffalo Bulls
-  BUT => Butler Bulldogs
-  BYU => BYU Cougars
-  CAL => California Lutheran Kingsmen
-  CAM => Campbell Fighting Camels
-  CAP => Capital University Crusaders
-  CAR => Carthage College Red Men
-  CARK => Central Arkansas Bears
-  CAS => Castleton Spartans
-  CAT => Catholic University Cardinals
-  CCSU => Central Connecticut Blue Devils
-  CCU => Coastal Carolina Chanticleers
-  CEN => Centre College Colonels
-  CHA => Chapman University Panthers
-  CHI => Chicago Maroons
-  CHSO => Charleston Southern Buccaneers
-  CIN => Cincinnati Bearcats
-  CLA => Clarion Golden Eagles
-  CLEM => Clemson Tigers
-  CLMB => Columbia Lions
-  CLT => Charlotte 49ers
-  CMU => Central Michigan Chippewas
-  COE => Coe College Kohawks
-  COL => Colorado School of Mines Orediggers
-  COLC => Colorado College Tigers
-  COLG => Colgate Raiders
+  BOIS => Boise State Broncos
+  BRST => Bridgewater State Bears
+  BUENA => Buena Vista Beavers
+  CAL => California Golden Bears
+  CAR => Carroll University (WI) Pioneers
+  CLA => Claremont-Mudd-Scripps College Stags
+  COLBY => Colby College White Mules
   COLO => Colorado Buffaloes
-  CON => Concordia-Minnesota Cobbers
-  COR => Cornell College (IA) Rams
+  CONN => UConn Huskies
   CP => Cal Poly Mustangs
-  CRO => Crown Storm
   CSU => Colorado State Rams
-  CUL => Culver-Stockton Wildcats
-  CUM => Cumberland College Indians
   CUR => Curry College Colonels
-  DAK => Dakota Wesleyan Tigers
-  DART => Dartmouth Big Green
-  DAV => Davidson Wildcats
-  DAY => Dayton Flyers
-  DEF => Defiance Yellow Jackets
-  DEL => Delta State Statesmen
-  DEN => Denison Big Red
-  DEP => DePauw Tigers
-  DIC => Dickinson State Blue Hawks
-  DRKE => Drake Bulldogs
-  DSU => Delaware State Hornets
+  DEL => Delaware Blue Hens
   DUB => Dubuque Spartans
-  DUKE => Duke Blue Devils
-  DUQ => Duquesne Dukes
-  EAS => Eastern New Mexico Greyhounds
-  ECU => East Carolina Pirates
-  EDI => Edinboro Fighting Scots
-  EIU => Eastern Illinois Panthers
-  EKU => Eastern Kentucky Colonels
-  ELI => Elizabeth City State Vikings
-  ELM => Elmhurst Blue Jays
-  ELON => Elon Phoenix
-  EMO => Emory & Henry Wasps
-  EMP => Emporia State Hornets
-  EMU => Eastern Michigan Eagles
-  END => Endicott College Gulls
-  EOR => Eastern Oregon Mountaineers
-  ETSU => East Tennessee State Buccaneers
-  EUR => Eureka College Red Devils
-  EWU => Eastern Washington Eagles
-  FAU => Florida Atlantic Owls
-  FAY => Fayetteville State Broncos
-  FDU => FDU-Florham Devils
-  FER => Ferrum Panthers
-  FIN => Findlay Oilers
-  FIT => Fitchburg State Falcons
-  FIU => Florida International Panthers
+  ELM => Elmhurst Bluejays
+  FAMU => Florida A&M Rattlers
   FLA => Florida Gators
-  FOR => Fort Valley State Wildcats
-  FRA => Franklin Grizzlies
-  FRES => Fresno State Bulldogs
-  FRO => Frostburg State Bobcats
-  FRST => Ferris State Bulldogs
   FSU => Florida State Seminoles
-  FTLW => Fort Lewis Skyhawks
-  FUR => Furman Paladins
-  GAL => Gallaudet Bison
-  GAN => Gannon Golden Knights
-  GASO => Georgia Southern Eagles
-  GAST => Georgia State Panthers
-  GEN => Geneva College Golden Tornadoes
-  GEO => George Fox University Bruins
-  GET => Gettysburg Bullets
-  GLE => Glenville State Pioneers
-  GMU => George Mason Patriots
-  GRA => Grand Valley State Lakers
-  GRE => Greenville Panthers
   GRI => Grinnell Pioneers
-  GRO => Grove City College Wolverines
   GT => Georgia Tech Yellow Jackets
-  GUI => Guilford Quakers
-  GWEB => Gardner-Webb Bulldogs
-  HAM => Hampden-Sydney Tigers
-  HAMP => Hampton Pirates
-  HAN => Hanover Panthers
-  HAR => Hartwick Hawks
-  HARV => Harvard Crimson
-  HAS => Haskell Indian Nations Jayhawks
+  GTWN => Georgetown Hoyas
   HAW => Hawai'i Rainbow Warriors
-  HBU => Houston Baptist Huskies
-  HC => Holy Cross Crusaders
-  HEI => Heidelberg Student Princes
-  HEN => Hendrix College Warriors
-  HIL => Hillsdale Chargers
-  HIR => Hiram College Terriers
-  HOB => Hobart Statesmen
-  HOU => Houston Cougars
   HOW => Howard Bison
-  HUS => Husson Eagles
   IDHO => Idaho Vandals
-  IDST => Idaho State Bengals
-  ILL => Illinois Fighting Illini
-  ILST => Illinois State Redbirds
-  ILW => Illinois Wesleyan Titans
-  IND => Indianapolis
-  INST => Indiana State Sycamores
-  IOW => Iowa Wesleyan Tigers
-  IOWA => Iowa Hawkeyes
   ISU => Iowa State Cyclones
-  ITH => Ithaca Bombers
-  IU => Indiana Hoosiers
-  JKST => Jackson State Tigers
-  JMU => James Madison Dukes
-  JOH => Johnson C Smith Golden Bulls
-  JUN => Juniata Eagles
-  JVST => Jacksonville State Gamecocks
-  KAL => Kalamazoo Hornets
-  KAN => Kansas Wesleyan University Coyotes
-  KEN => Kenyon Lords
-  KENN => Kennesaw State Owls
-  KENT => Kent State Golden Flashes
-  KIN => King's College (PA) Monarchs
-  KNO => Knox College Prairie Fire
-  KSU => Kansas State Wildcats
-  KU => Kansas Jayhawks
-  KUT => Kutztown Golden Bears
-  KYST => Kentucky State Thorobreds
-  KYW => Kentucky Wesleyan Panthers
-  LA => La Verne Leopards
-  LAC => Lane Dragons
-  LAF => Lafayette Leopards
-  LAG => LaGrange College Panthers
-  LAK => Lake Forest Foresters
-  LAM => Lambuth Eagles
-  LAN => Langston Lions
-  LAW => Lawrence Vikings
-  LEB => Lebanon Valley Flying Dutchmen
-  LEH => Lehigh Mountain Hawks
-  LEN => Lenoir-Rhyne Bears
-  LEW => Lewis & Clark Pioneers
-  LIB => Liberty Flames
-  LIM => Limestone Saints
-  LIN => Linfield Wildcats
-  LOC => Lock Haven Bald Eagles
-  LOR => Loras College Duhawks
-  LOU => Louisville Cardinals
-  LSU => LSU Tigers
-  LT => Louisiana Tech Bulldogs
+  JXST => Jacksonville State Gamecocks
   LUT => Luther Norse
-  LYC => Lycoming Warriors
-  M-OH => Miami (OH) RedHawks
-  MAC => Macalester Scots
-  MAI => Maine Maritime Mariners
-  MAN => Mansfield Mountaineers
-  MAR => Maryville College Fighting Scots
-  MAS => Mass Maritime Buccaneers
-  MASS => UMass Minutemen
-  MAY => Mayville State Comets
-  MCM => McMurry War Hawks
-  MCN => McNeese Cowboys
-  MD => Maryland Terrapins
-  MEM => Memphis Tigers
-  MEN => Menlo College Oaks
-  MER => Merchant Marine Mariners
-  MERC => Mercyhurst Lakers
-  MES => Colorado Mesa Mavericks
-  MET => Methodist Monarchs
-  MH => Mars Hill Mountain Lions
-  MIAMI => Miami Hurricanes
-  MICH => Michigan Wolverines
-  MID => Midwestern State Mustangs
-  MIL => Millsaps Majors
-  MIN => Minot State Beavers
-  MINN => Minnesota Golden Gophers
-  MIS => Missouri Western Griffons
-  MISS => Ole Miss Rebels
-  MIZ => Missouri Tigers
-  MNST => Minnesota State Mavericks
-  MONM => Monmouth Hawks
-  MONT => Montana Grizzlies
-  MOR => Morningside Chiefs
-  MORE => Morehead State Eagles
-  MORG => Morgan State Bears
-  MOU => Mount Union Raiders
-  MRSH => Marshall Thundering Herd
-  MRST => Marist Red Foxes
-  MSST => Mississippi State Bulldogs
-  MSU => Michigan State Spartans
-  MTST => Montana State Bobcats
-  MTSU => Middle Tennessee Blue Raiders
-  MTU => Michigan Tech Huskies
-  MUH => Muhlenberg Mules
-  MUR => Murray State Racers
-  MUS => Muskingum Fighting Muskies
-  MVSU => Mississippi Valley State Delta Devils
-  NAU => Northern Arizona Lumberjacks
-  NAVY => Navy Midshipmen
-  NBY => Newberry Wolves
-  NCAT => North Carolina A&T Aggies
-  NCCU => North Carolina Central Eagles
-  NCST => NC State Wolfpack
-  ND => Notre Dame Fighting Irish
-  NDOH => Notre Dame College Falcons
-  NDSU => North Dakota State Bison
-  NEB => Nebraska-Kearney Lopers
-  NEV => Nevada Wolf Pack
-  NH => New Haven Chargers
-  NICH => Nicholls Colonels
-  NIU => Northern Illinois Huskies
-  NMH => New Mexico Highlands Cowboys
-  NMI => Northern Michigan Wildcats
-  NMSU => New Mexico State Aggies
-  NOR => Univ. of Northwestern-St. Paul Eagles
-  NORF => Norfolk State Spartans
-  NW => Northwestern Wildcats
-  OBE => Oberlin Yeomen
-  ODU => Old Dominion Monarchs
-  OHI => Ohio Northern Polar Bears
-  OHIO => Ohio Bobcats
-  OKL => Oklahoma Baptist Bison
-  OKST => Oklahoma State Cowboys
-  OLI => Olivet College Comets
-  OMA => Omaha Mavericks
-  ORST => Oregon State Beavers
-  OSU => Ohio State Buckeyes
-  OTT => Otterbein Cardinals
-  OU => Oklahoma Sooners
-  PAC => Pacific (OR) Boxers
-  PENN => Pennsylvania Quakers
-  PIKE => Pikeville Bears
-  PITT => Pittsburgh Panthers
-  PRE => Presentation College Saints
-  PRI => Principia College Panthers
-  PRIN => Princeton Tigers
-  PST => Pittsburg State Gorillas
-  PSU => Penn State Nittany Lions
+  MESA => Colorado Mesa Mavericks
+  MIL => Millikin Big Blue
+  MOR => Morehouse College Maroon Tigers
+  NOR => North Park Vikings
   RED => Redlands Bulldogs
-  RICE => Rice Owls
-  RICH => Richmond Spiders
-  RIT => Rochester Yellow Jackets
-  ROB => Robert Morris (IL) Eagles
-  ROS => Rose-Hulman Engineers
-  RUTG => Rutgers Scarlet Knights
   SAC => Sacramento State Hornets
-  SAG => Saginaw Valley Cardinals
-  SDAK => South Dakota Coyotes
   SDSU => San Diego State Aztecs
-  SET => Seton Hill Griffins
-  SIU => Southern Illinois Salukis
   SJSU => San José State Spartans
-  SLI => Slippery Rock The Rock
-  SOU => Southwestern College Moundbuilders
-  SPR => Springfield College Pride
-  ST => St. Scholastica Saints
   STAN => Stanford Cardinal
-  STE => Stevenson University Mustangs
   STET => Stetson Hatters
-  STO => Stonehill College Skyhawks
-  SUS => Susquehanna University River Hawks
-  SUU => Southern Utah Thunderbirds
-  SYR => Syracuse Orange
-  TA&M => Texas A&M Aggies
-  TAY => Taylor Trojans
-  TEM => Temple Owls
-  TEX => Texas Longhorns
-  TIF => Tiffin University Dragons
-  TLSA => Tulsa Golden Hurricane
-  TRI => Trinity University (TX) Tigers
-  TUF => Tufts University Jumbos
-  TXST => Texas State Bobcats
   UAB => UAB Blazers
-  UAPB => Arkansas-Pine Bluff Golden Lions
-  UCD => UC Davis Aggies
-  UCF => UCF Knights
   UCLA => UCLA Bruins
-  UCONN => UConn Huskies
   UGA => Georgia Bulldogs
-  UK => Kentucky Wildcats
-  UL => Louisiana Ragin' Cajuns
-  ULM => UL Monroe Warhawks
-  UMD => Minnesota-Duluth Bulldogs
-  UMDA => UMASS Dartmouth Corsairs
-  UML => UMass Lowell River Hawks
-  UNA => North Alabama Lions
-  UNC => North Carolina Tar Heels
-  UNCO => Northern Colorado Bears
-  UND => North Dakota Fighting Hawks
-  UNH => New Hampshire Wildcats
-  UNI => University of Mary Marauders
-  UNLV => UNLV Rebels
-  UNM => New Mexico Lobos
-  UNNY => Union Dutchmen
-  UNT => North Texas Mean Green
-  UPP => Upper Iowa Peacocks
-  URI => Rhode Island Rams
   USA => South Alabama Jaguars
   USC => USC Trojans
-  USD => San Diego Toreros
   USF => South Florida Bulls
-  USU => Utah State Aggies
-  UTAH => Utah Utes
-  UTC => Chattanooga Mocs
-  UTI => Utica College Pioneers
-  UVA => Virginia Cavaliers
-  VAL => Valley City State Vikings
-  VAN => Vanderbilt Commodores
-  VILL => Villanova Wildcats
-  VIR => Virginia State Trojans
-  VT => Virginia Tech Hokies
-  WAB => Wabash College Little Giants
-  WAKE => Wake Forest Demon Deacons
-  WAS => Washington-Missouri Bears
-  WASH => Washington Huskies
-  WAY => Wayne State (MI) Warriors
-  WES => Westminster College (MO) Blue Jays
-  WHE => Wheaton College Illinois Thunder
-  WIL => Wilkes University Colonels
-  WIN => Wingate Bulldogs
-  WIS => Wisconsin-Platteville Pioneers
-  WISC => Wisconsin Badgers
-  WKU => Western Kentucky Hilltoppers
-  WOR => Worcester State College Lancers
-  WSU => Washington State Cougars
-  WVU => West Virginia Mountaineers
   YALE => Yale Bulldogs
 
 NBA
@@ -1106,6 +755,181 @@ MLB Conferences/Divisions
     OAK => Oakland Athletics
     SEA => Seattle Mariners
     TEX => Texas Rangers
+
+Soccer Leagues:
+   LEAGUE_SLUGS = {
+       "eng.1": "Premier League",
+       "esp.1": "La Liga",
+       "ger.1": "Bundesliga",
+       "ita.1": "Serie A",
+       "fra.1": "Ligue 1",
+       "uefa.champions": "Champions League",
+       "uefa.europa": "Europa League",
+       "usa.1": "MLS",
+       "por.1": "Liga Portugal",  # Add this line
+   }
+
+Soccer - Premier League (England)
+  ARS => Arsenal
+  AVL => Aston Villa
+  BHA => Brighton & Hove Albion
+  BOU => AFC Bournemouth
+  BRE => Brentford
+  BUR => Burnley
+  CHE => Chelsea
+  CRY => Crystal Palace
+  EVE => Everton
+  FUL => Fulham
+  LIV => Liverpool
+  LUT => Luton Town
+  MCI => Manchester City
+  MUN => Manchester United
+  NEW => Newcastle United
+  NFO => Nottingham Forest
+  SHU => Sheffield United
+  TOT => Tottenham Hotspur
+  WHU => West Ham United
+  WOL => Wolverhampton Wanderers
+
+Soccer - La Liga (Spain)
+  ALA => Alavés
+  ATH => Athletic Bilbao
+  ATM => Atlético Madrid
+  BAR => Barcelona
+  BET => Real Betis
+  CAG => Cagliari
+  CEL => Celta Vigo
+  ESP => Espanyol
+  GET => Getafe
+  GIR => Girona
+  LAZ => Lazio
+  LEG => Leganés
+  RAY => Rayo Vallecano
+  RMA => Real Madrid
+  SEV => Sevilla
+  VAL => Valencia
+  VLD => Valladolid
+
+Soccer - Bundesliga (Germany)
+  BOC => VfL Bochum
+  BOL => VfL Bochum
+  DOR => Borussia Dortmund
+  FCA => FC Augsburg
+  FCB => Bayern Munich
+  FCU => FC Union Berlin
+  HAC => Hannover 96
+  HDH => Hertha BSC
+  KOL => 1. FC Köln
+  LEV => Bayer Leverkusen
+  M05 => Mainz 05
+  RBL => RB Leipzig
+  SCF => SC Freiburg
+  SGE => Eintracht Frankfurt
+  STU => VfB Stuttgart
+  SVW => Werder Bremen
+  TSG => TSG Hoffenheim
+  WOB => VfL Wolfsburg
+
+Soccer - Serie A (Italy)
+  ATA => Atalanta
+  CAG => Cagliari
+  EMP => Empoli
+  FIO => Fiorentina
+  INT => Inter Milan
+  JUV => Juventus
+  LAZ => Lazio
+  MIL => AC Milan
+  MON => Monza
+  NAP => Napoli
+  ROM => Roma
+  TOR => Torino
+  UDI => Udinese
+  VER => Hellas Verona
+
+Soccer - Ligue 1 (France)
+  LIL => Lille
+  LPM => Lille
+  LYON => Lyon
+  MAR => Marseille
+  MON => Monaco
+  NAN => Nantes
+  NICE => Nice
+  OL => Olympique Lyonnais
+  OM => Olympique de Marseille
+  PAR => Paris Saint-Germain
+  PSG => Paris Saint-Germain
+  REN => Rennes
+  STR => Strasbourg
+
+Soccer - Champions League
+  AJA => Ajax
+  ASM => AS Monaco
+  ASS => AS Saint-Étienne
+  BOC => VfL Bochum
+  CEL => Celtic
+  COM => Club Brugge
+  FCA => FC Augsburg
+  FCB => Bayern Munich
+  FCU => FC Union Berlin
+  FIO => Fiorentina
+  GEN => Genoa
+  HAC => Hannover 96
+  IPS => Ipswich Town
+  KSV => Kaiserslautern
+  LEC => Lecce
+  LIL => Lille
+  LIV => Liverpool
+  M05 => Mainz 05
+  MCI => Manchester City
+  MUN => Manchester United
+  NAN => Nantes
+  OSA => Osasuna
+  RBL => RB Leipzig
+  RCL => RC Lens
+  RMA => Real Madrid
+  SCF => SC Freiburg
+  SGE => Eintracht Frankfurt
+  SR => Sporting CP
+  STP => St. Pauli
+  SVW => Werder Bremen
+  TFC => Toulouse FC
+  TOT => Tottenham Hotspur
+  TSG => TSG Hoffenheim
+  UDI => Udinese
+  VEN => Venezia
+  VFB => VfB Stuttgart
+  VIL => Villarreal
+
+Soccer - Liga Portugal (Portugal)
+  ARO => Arouca
+  BEN => SL Benfica
+  BRA => SC Braga
+  CHA => Chaves
+  EST => Estoril Praia
+  FAM => Famalicão
+  GIL => Gil Vicente
+  MOR => Moreirense
+  POR => FC Porto
+  PTM => Portimonense
+  RIO => Rio Ave
+  SR => Sporting CP
+  VGU => Vitória de Guimarães
+  VSC => Vitória de Setúbal
+
+
+
+Soccer - Other Teams
+  austin => Austin FC
+  cf_montral => CF Montréal
+  charlotte => Charlotte FC
+  dortmund => Borussia Dortmund
+  gladbach => Borussia Mönchengladbach
+  lafc => Los Angeles FC
+  leverkusen => Bayer Leverkusen
+  nycfc => New York City FC
+  paris_sg => Paris Saint-Germain
+  st_louis => St. Louis City SC
+
 MLS Conferences/Divisions
   Conferences currently unsupported