Feat/439 notification center emails trigger

[RamRamez]

• https://github.com/Giveth/giveth-v6-core/issues/439

Summary by CodeRabbit

• New Features

  • Added optional support for routing notification events through Ortto’s v6 activities and journeys.
  • Notifications continue using legacy activity handling when v6 routing is not enabled.
  • Added v6-specific routing for project verification events, including distinct verification statuses and rejection details.
  • Events without a dedicated v6 journey continue using their existing activity behavior.

• Tests

  • Expanded coverage for v5/v6 routing, event mappings, and verification attributes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: f778c44f-cc22-4b96-baf2-2fab2183eb89

📥 Commits

Reviewing files that changed from the base of the PR and between d782984 and c831c40.

📒 Files selected for processing (5)

• src/services/notificationService.test.ts
• src/services/notificationService.ts
• src/types/notifications.ts
• src/types/requestResponses.ts
• src/validators/schemaValidators.ts

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

The notification API now accepts an optional Ortto v6 routing flag. A resolver selects v6 or legacy activity slugs. Verification events use v6-specific status attributes. Tests cover activity mappings, fallbacks, trigger ids, and coverage exceptions.

Changes

Ortto v6 activity routing

Layer / File(s)	Summary
Activity and request contracts src/types/notifications.ts, src/types/requestResponses.ts, src/validators/schemaValidators.ts	Adds the partial v6 activity map, slug resolver, optional request flag, and Joi validation field.
Notification routing integration src/services/notificationService.ts	Passes the v6 flag to activityCreator, resolves v6 or legacy slugs, and emits the v6 unverified status when enabled.
Routing and coverage validation src/services/notificationService.test.ts	Tests v6 mappings, legacy fallbacks, verification attributes, provisioned trigger ids, and documented coverage exceptions.

Estimated code review effort: 4 (Complex) | ~45 minutes

Suggested reviewers: ae2079

Merge Risk: ⚪ Minimal · up to c831c

This change adds opt-in Ortto v6 notification routing while preserving existing legacy behavior for callers that do not enable it. The current implementation and coverage support merging with normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the main change: triggering notification-center emails for the v6 event handling work.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 5…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/439-notification-center-emails-trigger

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit hops through routes of green,
V6 activity paths are seen.
Old trails remain when flags are bare,
Status branches bloom with care.
Tests guard each journey bright.}

_{Comment @coderabbitai help to get the list of available commands.}