Dual writes or runtime version detection for rollback-safe schema changes?
Constraint A Ballerina 2.x service needs a rollback-safe response to a breaking record-schema change, including data produced by both the previous and new schema versions. The goal is a defined restoration guarantee, not automatic conversion of persisted records: record versioning addresses compatibility with older payloads, while transactional rollback depe
ballerina