openfollow

Use when adding, removing, or changing a field on any OpenFollow config dataclass (AppConfig, CameraConfig, GridConfig, MarkerConfig, ControllerConfig, DetectionConfig, OscConfig, OtpOutputConfig, RttrpmOutputConfig, TriggerZonesConfig, ...) or adding a new editable field to a web settings form. Triggers on "add a config field", "new setting", "config option", "settings form field", "FieldRule", "web form validation". Walks the full vertical slice: dataclass normalisation, web-form markup, FieldRule registration, tests, and docs.

Use when deploying or provisioning OpenFollow to a Raspberry Pi via Ansible, or when asked to "deploy to the pi", "provision", "run the ansible playbook", "install on raspberry". Covers the install playbook, the ad-hoc inline-inventory invocation idiom (no inventory file in repo), related .deb/image artifacts, and the docs to keep in sync.

Use before pushing, committing, or opening a PR on OpenFollow, or when asked "is this ready", "run CI", "run make ci", "pre-push check". Encodes the project's pre-push gate and the rules around it: `make ci-remote` runs the gate on the testing Pi (falling back to the Mac), the full gate must pass, format fixes go through make format (not by hand), no -k / --no-verify / red-branch pushes, the offline runtime contract, branch hygiene, and the docs gate.