dtm-labs/dtm ? reverse-engineered prompt

Build me a distributed transaction manager in Go that helps microservices stay in sync when one step fails. I want it to support the main transaction styles people use in real systems, like saga, TCC, XA, workflow, outbox, and a two phase message approach. It should be able to run as a standalone service, with a simple admin view or basic management endpoints, and it should work with common databases and storage backends like MySQL, Redis, MongoDB, and Postgres.

Please make it easy to use from other languages too, at least with a clean API pattern that could fit Go and a few other popular SDKs. Include a quick start example for a simple money transfer between two services, plus a rollback example so I can see compensation working when a step fails. If you need to check current docs or best practices online, do that. Keep it practical, with clear config, good defaults, and a setup that can scale and stay available in production.