I can suppose this was provisional on your part (to be somewhat unspecified, but still unambiguous) to keep it bw compat, until you’ve settled on the right API.
The guide you link to is the one main update we’ve since that thread. Were you looking for more information about the values coming back from hub.sync.status specifically, or was your question more broad?
In general, we recommend writing host firmware that checks for specific codes you expect or have encountered, while also handling unknown errors gracefully—since new versions of Notecard firmware may introduce additional codes over time.
I see, I was hoping to have a wrapper around each of the response’ status and handle them properly in firmware in advance.
As I’m still relatively new to the ecosystem, one of the good ways in which I can get a solid grasp on the subject is if I can successfully write a good adaptation layer around it, to aid the design of our firmware for the future.