Quiet hours are 10 PM to 6 AM by default; on Featherframe Cloud a detector's test can take 5 minutes, or wait out quiet hours
Style pass: one name for each thing, one home for each fact, footers, and developer material on developer pages Frames list, setup code, frame (not screen), self-hosted, your Featherframe webapp; gray and color frames on owner pages; self-hosted troubleshooting moves to Install the server, URLs and the command line to How it works.
Owner pages, checked against the code: the screens and labels each kit shows, the codes' day, the confirmation link, the mat, what Daily weather sends
Two front doors: owners (set up, your frame, troubleshooting) and makers Set up your frame and Your frame are new. Troubleshooting goes by symptom, with a self-hosted section last and help@featherframe.app for owners. The buttons and the light's colors move to Your frame, a second frame to Add a frame, and Settings gets a heading per row, so every fact has one page and featherframe.app/help can link to it. Hosted is Featherframe Cloud.
Settings is one card of rows; Save per section; times as people write them (W-878)
Push URLs: a refresh button makes a new one; the rule file is a link (W-865)
BirdNET-Go: import the rule from the webapp (W-865)
Updated Detection sources (markdown)
BirdNET-Go: steps name the real UI's fields (W-865)
Callouts where they carry weight; fix Build the frame's button table
BirdNET-Go sends detections through a webhook, hosted too (W-865)
Terminology pass: BirdNET device, Featherframe webapp, illustrations not plates, port 8181; Detection sources page; resolve Install stubs (W-864)