For now sort by rowid

- Due to how stront values are currently duplicated when reinforced is
  detected.
- Should really fix the root cause, and this can cause problems in a
  RDBMS that does not use sequential autoinc primary keys.
More rigidly define/follow API usage codes.

- Make 0 really define the state for completed sucessfully.
- Update the methods to reflect this fact so we don't get towers that
  never updated due to bugs be marked as not tracked by API.
I guess evelink doesn't deal with XML parse errors

- We will handle them here for now :cripes:.