Stay inside the supported machine-translation boundary

Supported extension points include:

• registering stable standalone strings;
• registering approved metadata and structured content;
• filtering the documented machine-translation controls;
• exporting and importing translation JSON;
• reacting to documented translation lifecycle hooks.

POM Translate does not provide a public extension point for:

• replacing the POM AI client with another provider;
• changing the private service transport or authentication;
• storing provider credentials in plugin settings;
• bypassing queue locks, quotas, placeholder checks, or statuses;
• writing translations directly to plugin tables.

Use pom_translate_machine_translation_settings only to adjust the documented machine-translation settings array. It is not a provider adapter. Use pom_translate_machine_translation_daily_limit to constrain the calculated site limit when an integration needs a stricter policy.

When a requirement falls outside this boundary, use the public import/export format or keep the external workflow independent. This preserves compatibility while still allowing reviewed translations to enter POM Translate.

See Machine-translation hooks for exact public hook arguments.