Implement transaction draft versioning, diffing, and rollback

[Just-Bamford]

Description

Problem

Transaction drafts can be persisted, but there is no robust version history or mechanism for determining what changed between saved states.

Users working on complex transactions may accidentally overwrite a valid draft and have no way to inspect or restore a previous version.

Solution

Extend transaction draft persistence with immutable version snapshots.

Every meaningful draft update should create a version containing the transaction builder state and metadata. Provide comparison utilities capable of identifying added, removed, and modified operations.

Add rollback functionality that restores a previous version as a new current version rather than destroying history.

Acceptance Criteria

• Draft versions are stored independently.
• Each version receives a deterministic identifier or sequence number.
• revertDraft(name, version) restores a previous version.
• Reverting creates a new version instead of deleting history.
• compareDraftVersions(name, from, to) returns structured differences.
• Operation additions, removals, and modifications are detected.
• Version retention is configurable.
• Corrupted versions fail validation before restoration.
• Tests cover creation, comparison, rollback, retention, and corrupted state.
• Exported through src/transaction/index.ts and src/index.ts.

Note for Contributors

Preserve backward compatibility with the existing draft persistence API. Draft history should not silently mutate older versions.

[dot-enny]

@dot-enny has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi there, I'd like to work on this please. Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dot-enny to this issue.

[Turawa2]

@Turawa2 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I can work on this task , assign me please!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Turawa2 to this issue.

[malaysiaonelove]

@malaysiaonelove has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, I’m interested in working on this issue. I have relevant experience and have reviewed the requirements. Please assign it to me I’m confident I can deliver a high-quality solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @malaysiaonelove to this issue.

[heymide]

@heymide has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I can take this on. I've gone through the details and will provide a well-tested solution aligned with the project standards.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @heymide to this issue.

[midexol]

@midexol has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @midexol to this issue.

[dakwa001]

@dakwa001 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi! I’d like to take this issue. I’ll go through the existing implementation, identify the root cause, and work on a clean solution before submitting a PR for review.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dakwa001 to this issue.

[drips-wave]

Congratulations, @dakwa001! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @dakwa001: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊