Figma Dev Mode and Code Connect: keeping mapped components truthful as the code library evolves

We are adopting Figma's Dev Mode so developers can inspect designs, and we plan to publish Code Connect mappings from our component repository so Dev Mode shows real usage snippets instead of generic generated CSS. Both features are documented and supported, but the boundary between them is what concerns us.

Our understanding is that the mapping is one-directional and manual: Figma does not validate that a mapped code component's props still match the design component's variants after a refactor. That means a renamed prop or a restructured variant in the code library could leave Dev Mode showing stale snippets with no warning on either side. We also assume Code Connect availability depends on plan tier and supported frameworks, which we still need to confirm against current Figma documentation.

Before we commit, we need to resolve ownership and freshness: design system maintainers versus application teams could each plausibly own the mapping files, and republishing cadence is entirely up to us.

Is there any supported mechanism—event, API signal, or CI-friendly check—for detecting when a Code Connect mapping has drifted from the actual code component's props? How do teams typically structure ownership of mapping files in a monorepo with multiple consuming apps? And does republishing a mapping require any action on the Figma file side, or is it purely a repository-side operation?