sent-templateslisted

# Sent Templates Operate existing template records with `templates.list`, `templates.get`, `templates.get_by_name`, and `templates.delete`. ## Establish connection and scope Use client-managed OAuth 2.1/PKCE and never request or expose credentials. Surface the active organization and Sender Profile before deletion; use `sent-account-readiness` if the connection context does not expose both. Reauthorize in the client to change scope. Avoid repeating template body text or sample data unnecessarily. Prefer template identifiers, names, languages, channels, categories, and statuses in summaries. ## Find and inspect templates - Use `templates.list` for filtered discovery and pagination. - Use `templates.get` for an exact template identifier. - Use `templates.get_by_name` when the user supplies a name. If a name can match more than one language, channel, or scope, present the candidates and resolve one exact record before continuing. These tools inspect existing records. For authoring or classification, hand off to `waba-template-author`; for a tenant-facing creation experience, hand off to `template-builder-ui`. ## Delete a template 1. Resolve the request to one exact template. 2. Fetch that target first with `templates.get` or `templates.get_by_name`. Never delete from a guessed identifier, broad filter, or stale list result. 3. Show a delete preview with the selected organization, Sender Profile, exact template identifier, name, language, channel, category, and status. S