feat(frontend): evento Compra aprovada no manifesto de eventos (CRM-316)

[nickoliveira23]

Summary

• Espelho do catálogo de eventos do evo-flow ganha purchase.approved na categoria nova purchase ("Compra aprovada" / "Purchase approved"), com o mesmo schema do backend.
• Categoria aparece no seletor de evento do gatilho de jornada (ícone de carrinho) e no editor de condição de segmento ("Eventos de Compra"), com a chave categories.purchase nos 6 locales.
• catalog.spec.ts entra na lane Vitest (lista fechada).

Security

• Só manifesto, rótulos e i18n. Sem chamada nova, sem dado sensível.

Test plan

• npx vitest run src/lib/events-manifest/catalog.spec.ts src/i18n/locales/i18n-parity.spec.ts
• npx tsc --noEmit
• Camada conta: Jornadas → nova jornada → gatilho por evento mostra "Eventos de Compra → Compra aprovada"; Segmentos → condição por evento idem.

Nota

• O manifesto do front já não trazia pipeline.stage_changed (23 eventos contra 24 do backend). Drift pré-existente, fora do escopo.
• A tela do gatilho por evento hoje pede os campos required do catálogo como inputs obrigatórios (ids de compra/card). Defeito anterior a esta PR, tratado em card próprio.

Changed Files

• src/lib/events-manifest/event-names.ts
• src/lib/events-manifest/types.ts
• src/lib/events-manifest/catalog.ts
• src/lib/events-manifest/catalog.spec.ts
• src/components/journey/shared/EventSelector/EventSelector.tsx
• src/components/segments/SegmentConditionEditor.tsx
• src/i18n/locales/{pt,pt-BR,en,es,fr,it}/events.json
• .github/workflows/test.yml

Related PRs

• evo-flow (deploy primeiro): feat(flow): compra aprovada vira evento purchase.approved no catálogo (CRM-316) evo-flow-community#124
• CRM: feat(crm): webhook de compra emite purchase.approved para o evo-flow (CRM-316) evo-ai-crm-community#345
• frontend (vendor/crm): feat(frontend): evento Compra aprovada no manifesto de eventos (CRM-316) #369

Linked Issue

• CRM-316

🤖 Generated with Claude Code

https://claude.ai/code/session_01JxYjUwr2vV69kYddiXJHRo

Summary by Sourcery

Add support for approved purchase events across the frontend event manifest, journey triggers, and segment conditions.

New Features:

• Add the purchase.approved event to the frontend event manifest under a new Purchase category, including its localized labels and schema.
• Expose Purchase events in journey event triggers and segment event conditions with localized category labels.

Enhancements:

• Update manifest validation to account for the expanded backend event set while explicitly excluding the pre-existing pipeline stage event from the frontend mirror.

CI:

• Include the event manifest catalog test in the Vitest CI lane.

Tests:

• Extend catalog coverage to validate the new Purchase category and purchase.approved event.

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="src/components/segments/SegmentConditionEditor.tsx" line_range="59" />
<code_context>
   conversation: 'Eventos de Conversa',
   message: 'Eventos de Mensagem',
   campaign: 'Eventos de Campanha',
+  purchase: 'Eventos de Compra',
   custom: 'Personalizado',
 };
</code_context>
<issue_to_address>
**issue:** The segment event picker renders the new purchase category with the hardcoded Portuguese string `Eventos de Compra`, so English, Spanish, French, and Italian users see a Portuguese category heading even though `categories.purchase` was added to all locale files.

**Triggers:** When a non-Portuguese user opens the Performed or LastPerformed event selector.

**Suggested fix:** Use the events i18n namespace and render `t('categories.purchase')` (and the existing category labels) instead of hardcoded Portuguese strings.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: src/components/segments/SegmentConditionEditor.tsx:59

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[sourcery-ai]

issue: The segment event picker renders the new purchase category with the hardcoded Portuguese string Eventos de Compra, so English, Spanish, French, and Italian users see a Portuguese category heading even though categories.purchase was added to all locale files.

Triggers: When a non-Portuguese user opens the Performed or LastPerformed event selector.

Suggested fix: Use the events i18n namespace and render t('categories.purchase') (and the existing category labels) instead of hardcoded Portuguese strings.