test(triggers): guard the provider granularity the path route depends on

[waleedlatif1]

Summary

• The public trigger route classifies delivery eligibility by provider, not by trigger id, so a provider owning both a polling and an HTTP trigger would have its HTTP deliveries rejected
• Sim already models dual-delivery services as two providers (slack / slack_app), but nothing asserted it — every existing POLLING_PROVIDERS sync assertion still passes for a mixed provider
• Adds that assertion, with a message pointing at the fix (split the HTTP triggers onto their own provider)

Type of Change

• Bug fix

Testing

Verified the new assertion fails on a deliberately mixed provider and that the three existing assertions stay green through it — i.e. the suite genuinely did not cover this. Full webhook/trigger suites pass (675 tests), plus type-check, lint, check:api-validation:strict, check:boundaries, check:trigger-block-cycle.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 8, 2026 8:38pm

[cursor]

PR Summary

Low Risk
Test-only change with no runtime behavior; it prevents misconfigured trigger registry entries that would break HTTP webhook delivery.

Overview
Adds a registry invariant test so a provider cannot mix polling triggers with path-delivered HTTP triggers under the same provider name.

The public trigger route treats acceptsPathWebhookDelivery at provider scope: if a provider is in POLLING_PROVIDERS, path deliveries for that whole provider are rejected (404). Existing POLLING_PROVIDERS sync tests did not catch a hypothetical mixed provider; this new case fails when both polling and non-polling triggers share a provider. Internal providers and handlers with ingressMode === 'provider' are skipped, since they do not use the generic path route.

The failure message directs authors to split providers (e.g. slack vs slack_app).

^{Reviewed by Cursor Bugbot for commit f939e97. Configure here.}

[greptile-apps]

Greptile Summary

The PR adds a registry invariant ensuring providers do not combine polling triggers with triggers delivered through the public path route, while exempting providers rejected wholesale by that route.

• Groups registered triggers by provider and delivery type.
• Exempts internal and provider-ingress delivery providers.
• Reports mixed providers with their polling and path trigger IDs.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
apps/sim/triggers/constants.test.ts	Adds a focused provider-level delivery invariant and correctly completes the prior-thread fix by matching the route’s internal-provider and provider-ingress exclusions.

_{Reviews (2): Last reviewed commit: "test(triggers): exempt provider-gated tr..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit f939e97. Configure here.}