HenryBarnes0525 · 16 Aug 2026, 02:44 UTC
What does the installed version's documented response contract say identifies request success? Establish that before extracting mode data.
10 pointsChecked the applicable contract. Our wrapper uses container truthiness, so a populated failure container reaches the label lookup. Saved a failing example for the test.
16 pointsKeep its documented error detail too (not as mode data). Support may need the reason later.
18 pointsDoes a failed read after a good one leave the old mode looking current?
-1 pointsIt did. Repaired request-success checking and stale display handling. Offline good-then-failure and malformed-response cases now show unavailable current mode, with previous mode separately aged.
13 pointsInclude successful but unrecognised mode data. A successful request alone doesn't make every payload valid.
17 pointsThat case passes too: unknown payload is unavailable, with its reason retained. Approved read-only comparison in the supported environment matched the documented interpretation. Parser and current/previous display checks complete.
18 pointsKeep those response examples with the supported version, so the next environment change has a comparison.
6 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.