openmates:add-example-chat

Converting shared chat URLs into localized TypeScript demo data involves decrypting the chat content, generating TypeScript with i18n key references for messages, and producing 21-language YAML translations. You provide the share URL, encryption key, SEO slug, and category to register the example chat.

Generating i18n YAML translations from an existing chat requires extracting the decrypted messages and mapping the content to i18n keys. The process outputs translation sources covering 21 languages while preserving translation rules, ensuring the demo chat is fully localized.

Extracting and registering an encrypted shared chat for a demo UI requires the share URL and encryption key to decrypt content. The system summarizes the title, message count, and embed count, then registers the new entry in the example chat store and copies embeds as-is.

Updating the example chat registry after adding new translations is handled automatically. The process updates the example chat registry, builds the 21-language translations, and stages or deploys the changes via the project's deployment workflow without manual file edits.

Shared chat extraction preserves embeds when creating demo data by copying embeds as-is during the deterministic TypeScript data generation phase. This ensures the registered example chat maintains the exact embed structure from the original decrypted conversation.

Shared chat localization workflows require an SEO-friendly slug to identify the demo chat during registry and discovery. Generating the slug alongside the category allows the system to properly register the TypeScript data and map the i18n keys for the new example chat entry.