Integrate with machine-translation lifecycle safely

POM Translate does not expose a public filter for replacing the provider response or bypassing its queue, quota, locking, placeholder validation, and persistence.

The supported observation points are the normal pom_translate_string_changed and pom_translate_translation_changed actions. Machine-generated saves carry their stored workflow status through the translation-changed action.

For software catalogs, pom_translate_software_mt_source_locale( string $source_locale, string $domain, string $target_locale, array $context ) can correct the detected source locale before POM Translate requests a machine translation. Return a valid WordPress locale. Treat the context array as opaque so the integration does not depend on transport details.

Do not call remote services from either action. Queue integration-owned asynchronous work with idempotency and recursion protection if observation is required.

The callable translate_raw_strings() method belongs to the current coordinator implementation, not a general promise that arbitrary visitor text can be sent remotely. Public integrations should use the documented POM AI workflow rather than constructing provider requests.