They are the raw replies our adapter consumes. We replaced the all-true helper with those shapes and added valid unavailable status, read failure and malformed replies. The parser now fails visibly on malformed data instead of treating a nonempty object as success.

What does the operator actually see on a read failure? Our screen once kept the last cheerful status and tucked the error into a log. You could tell something was wrong only if you already knew to look for it.

That's our next failure. The screen changes, but the export keeps the last good status without its age. I've asked the maintainer to make both preserve the read outcome and the time of the last valid observation.

Have you tested recovery after that failed read as well? The corrected export should not remain stuck on an old failure once a genuinely new observation arrives.

Yes. Saved sequences now cover first-read failure, malformed response, valid status, later failure, recovery and reopening. Screen and export agree on current availability and the identity and time of any retained observation. The covering user could distinguish old from current without my commentary. This closes the reporting bug; comparison with the live interface is still on the station's return list.

Thanks for checking it with the covering user. That is the person who has to decide whether the screen is worth believing when you aren't beside it.