LEDMatrix Plugin Development Rules

# LEDMatrix Plugin Development Rules

**Source of truth for agents:** `AGENTS.md` → `CLAUDE.md`.
Human deep-dive: `docs/plugin-development/`.

Do not duplicate long API catalogs here. If a rule isn’t in `CLAUDE.md`, add it
there (session-memory / promote), not as a third copy.

## Hard rules (summary)

1. Bump `manifest.json` `version` + top `versions[]` entry on every plugin change.
2. Never hand-edit `plugins.json` — pre-commit / `update_registry.py` only.
3. Fetch in `update()`, draw in `display()`; namespace cache keys by plugin id.
4. Plugin-unique names for deferred/subpackage modules (`check_module_collisions.py`).
5. Pass the core safety harness (no crash / no overflow). Classic design sizes:
   64×32, 128×32, 128×64, 256×32 (CI may test more — see docs topic 07).
6. No secrets in git. Real values stay on the Pi/core runtime
   (`config_secrets.json`); this repo keeps templates only. OAuth files
   (`credentials.json`, `token.pickle`) are gitignored.

Install hook: `cp scripts/pre-commit .git/hooks/pre-commit`

This repo is **plugins + registry only**. Core (`BasePlugin`, harness,
web UI) lives in `ChuckBuilds/LEDMatrix` — don’t apply core-edit checklists here.