Versioning and Compatibility
The repository VERSION file is authoritative. Stable releases use semantic versioning, and prereleases use standard suffixes.
Within the 1.x series, documented configuration keys, installer options, migration-ledger behavior, public routes and API payloads, and supported extension points remain backward compatible. Compatible minor releases may add optional capabilities. Security and correctness fixes that preserve compatibility are patch releases.
An intentional breaking change requires a major release. Deprecations are recorded in the changelog and normally remain for at least one minor release when security permits.
RAD Admin templates, undocumented classes, implementation-specific database details, and developer execution tools are internal surfaces. Applications must not treat them as compatibility boundaries.
Database upgrades use forward migrations. Applied migration files are immutable and checksum-verified. Back up before upgrading; downgrade support exists only where a migration explicitly provides a supported rollback.