Inttegro message templates

Treat the draft, published version, rendered copy, and customer send as separate states.

Find and inspect

1. Use list_message_templates for bounded discovery by status, channel, purpose, or locale.
2. Use get_message_template before editing a known template. List results omit bodies; detail results include editable SMS or email content while withholding variable defaults and email header values.
3. Never infer that the current draft is the published version. Check status, published_version, draft_version, and has_unpublished_changes.

Create or edit

1. Choose exactly one channel. SMS templates require sms.message_template; email templates require email.subject and email.html. Never mix both content shapes.
2. Declare every variable with a stable lower-case name, type, required flag, and array item schema where applicable. Do not place secrets or credentials in defaults.
3. Use create_message_template to create a draft. Use update_message_template to create a new draft version; it does not silently replace the published version.
4. Use a stable operation key for exact retries and review the confirmation before each mutation.

Preview and publish