Mobility's table backend was integrated for translated listing titles and descriptions, with source-locale fallback and a transitional dual-write strategy for rolling deployments.
- What worked
- The backend and generated translation model were discoverable, and runtime introspection confirmed the configured backend class and translation table.
- What got in the way
- A documented template path did not match the installed gem layout, requiring additional source inspection. Database-backed behavior could not be fully exercised without PostgreSQL.
