fix: accept notion data source parent webhooks

[lancy]

Summary

• Accept Notion webhook parent payloads that provide data_source_id without a type field.
• Resolve database item created events from data.parent.data_source_id when present.
• Update the Notion webhook test to cover the official 2026 page.created database item shape.

Context

While validating the notion-database-item-created workflow trigger, Notion sent page.created webhook payloads for database items using the official 2026 shape: data.parent includes id and data_source_id, but no type. The previous schema required parent.type, causing these events to be rejected before they could enqueue the workflow event.

Verification

• Attempted: pnpm --dir turbo/apps/api test src/signals/routes/__tests__/webhooks-notion.test.ts
• Result: local test command could not start because node_modules is missing in this checkout (vitest: not found). CI should run the targeted suite with installed dependencies.

[codecov]

Codecov Report

❌ Patch coverage is 80.00000% with 2 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
.../signals/services/notion-workflow-event.service.ts	80.00%	2 Missing ⚠️

📢 Thoughts on this report? Let us know!

[github-actions]

API preview: https://pr-20709-api.vm6.ai

[lancy]

LGTM

PR_AUTO_REVIEW_COMMIT: 2584dfb
PR_AUTO_REVIEW_VERDICT: LGTM

Summary

This PR accepts the Notion 2026 database item webhook parent shape where data.parent includes data_source_id without a type field. The routing logic now treats data_source_id as the data source parent, while page-parent matching skips those events so database item creates do not get misclassified as child-page events.

Findings

Critical (P0)

• None.

High Priority (P1)

• None.

Testing

• Coverage: Adequate. The existing Notion webhook integration test now covers the official database item page.created payload with id plus data_source_id and no parent type, and still exercises pending event insertion for the data source scope.
• Conventions: Compliant. The test remains an API integration test and does not add internal mocks, direct fetch mocking, fake timers, or database mocking.
• Execution: Not run locally in this review; CI is rerunning on head 2584dfb after the title fix and empty commit trigger.