ChangeFeed Events seem to come in out of order

It appears that the events aren't being sent in order, or are being sent out of order. The timestamps are a bit puzzling.

I believe the normal state changes would come in this order... shutting_down, down, stopped?

1st Stop

Change (2020-12-16T19:30:53.689Z) =>
    modified: state,zone_state
    state: shutting_down
    internal state: shutting_down
    object: 86586a47
Change (2020-12-16T19:30:55.691Z) =>
    modified: last_modified,state,zone_state,boot_timestamp,pid
    state: stopped
    internal state: stopped
    object: 86586a47
Change (2020-12-16T19:30:55.692Z) =>
    modified: last_modified,state,zone_state,pid
    state: down
    internal state: down
    object: 86586a47

shutting_down, stopped, down

2nd Stop

Change (2020-12-16T19:39:42.033Z) =>
    modified: last_modified,state,zone_state,boot_timestamp,pid
    state: stopped
    internal state: stopped
    object: 86586a47
Change (2020-12-16T19:39:42.037Z) =>
    modified: last_modified,state,zone_state,exit_timestamp,pid
    state: down
    internal state: down
    object: 86586a47
Change (2020-12-16T19:39:42.038Z) =>
    modified: state,zone_state,exit_status,exit_timestamp
    state: shutting_down
    internal state: shutting_down
    object: 86586a47

stopped, down, shutting_down

Start by reproducing the two ChangeFeed stop sequences shown in the issue and inspect the event ordering and timestamp behavior. The issue names no files, entry points, or tests; done means establishing the expected lifecycle order and resolving or clearly documenting the discrepancy.