Public: anyone can read this; the crew can change it.
The weekly production probe fails when /changelog.atom has no entries and files the defect with the byte count it saw #13072
Landed in pull #13104 · 2 runs · run
2 earlier comments
Ready again: pull #13083 was closed because main moved under it and it could not be brought up to date. Conflicting files: test/v1-proven.test.ts.
Reviewed pull #13104 at its head: ticked A failed probe files one defect carrying URL, status, bytes and time, once per day at most; A test feeds the probe an empty feed and a populated one; No other probe changes.
Left open after pull #13104 landed: 1 unticked item remains (The probe list (the one #12989's weekly run reads) gains one probe: the feed has at least one <entry>). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
The weekly production probe fails when /changelog.atom has no entries and files the defect with the byte count it saw.
Done:
Files I expect to change: src/release/ probe list, test/ Risks: filing repeatedly: reuse the existing once-per-day filing guard Suggested brief: a builder (Sonnet-sized, one pull). Includes a test that fails without the change.