[hubbuugittuuu]

Problem

As Soroban contracts evolve across releases (new errors, token custody changes, partial release semantics), the NestJS backend configures contracts through environment IDs (STELLAR_ESCROW_CONTRACT_ID). Previously, there was no centralized tracking of which backend versions are compatible with which deployed WASM hashes or how in-flight escrows created on older bytecode should be settled.

Solution

1. Added contracts/COMPATIBILITY.md documenting:
   • Compatibility matrix covering payment_escrow and revenue_distribution contracts across Soroban SDK versions, entrypoints, and compatible backend release ranges.
   • Entrypoint signature mapping and on-chain EscrowStatus enum mapping (0 -> UNINITIALIZED through 3 -> REFUNDED).
   • In-flight escrow coexistence policy (ensuring existing escrows settle via original contract addresses).
   • Checklist for contract PR authors.
2. Updated .github/PULL_REQUEST_TEMPLATE.md to require PR authors to update or confirm compatibility in contracts/COMPATIBILITY.md.
3. Updated contracts/README.md to link directly to contracts/COMPATIBILITY.md.

Closes #2028

[vercel]

@hubbuugittuuu is attempting to deploy a commit to the naijabuz's projects Team on Vercel.

A member of the Team first needs to authorize it.