Problem:
Commit object activities with rollback error handling can roundtrip from commit $X on error rollback; to commit $X; because the writer omits rollback as a default and the parser does not restore it when the BSON field is absent.
Expected:
Rollback error handling should survive describe/exec/describe for commit activities.
Impact:
The textual roundtrip loses an explicit behavior setting and creates unnecessary drift for commit actions.
Proposed fix:
Make parser and writer handling symmetric: parse absent commit error handling as rollback, and always write the field with rollback as the default value.
Problem:
Commit object activities with rollback error handling can roundtrip from
commit $X on error rollback;tocommit $X;because the writer omits rollback as a default and the parser does not restore it when the BSON field is absent.Expected:
Rollback error handling should survive describe/exec/describe for commit activities.
Impact:
The textual roundtrip loses an explicit behavior setting and creates unnecessary drift for commit actions.
Proposed fix:
Make parser and writer handling symmetric: parse absent commit error handling as rollback, and always write the field with rollback as the default value.