TIL: Nov 2

TIL: When implementing bi-directional synchronization between two database entities (like Studios and Podcast Sets), wrapping updates in a single transaction and using granular cache tags (e.g., 'podcast') is essential to prevent race conditions and stale data across admin routes. Always ensure that "details-only" updates omit status fields to avoid inadvertently overwriting availability states toggled by concurrent processes.