Hot pixels: persistent self-maintaining blacklist

[Cybis320]

For cameras with in-camera hot/stuck pixel filtering disabled. Detections recurring at the same pixel across the night — spread over ≥3 quarters of it, with no net drift — are blacklisted in hotpixels.json, removed from CALSTARS, and excluded from the ff_min_stars meteor gate live during capture. The file is re-read on every FF, so priming or manual edits apply mid-capture; entries unseen for 14 days age out.

• RMS/HotPixels.py: detection, persistence, matching; CLI (python -m RMS.HotPixels to list, -p <night_dir> to prime from CALSTARS, -r X Y to remove)
• Pipeline hooks in DetectStarsAndMeteors (live gate + nightly update), ExtractStars.extractStarsAndSave, ExtractStarsFrameInterface — all CALSTARS writers curate
• Config options in [StarExtraction] (hot_pixels_*), on by default
• 12 tests; gates validated on real US005A nights (a slow near-pole star with 383 recurrent hits is correctly rejected; the quarters+drift gates, not counts, discriminate)

Note: flux-empirical-lm already contains the SkyFit2 amber-marker UI (030cfba) which imports RMS.HotPixels — this PR supplies the module, so it should merge first. Supersedes branch hot-pixel-blacklist.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QoBAW8t3qgi9nixYhnLwc1