[comp] Production Deploy

[github-actions]

This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.

---

Summary by cubic

Adds device sync from integrations across the stack: new DSL interpreter, API endpoints, scheduled tasks, UI provider selector, and DB fields to safely import and manage devices with “last synced” visibility.

• New Features

  • @trycompai/integration-platform: added device_sync capability, SyncDevice schema, interpretDeclarativeDeviceSync, and support for deviceSyncDefinition (with optional devicesPath).
  • API: get/set device sync provider, list available providers by syncType=device, and run dynamic device sync with credential refresh, run logging, and connection validation.
  • Generic device sync service: imports active devices (match by member email + serial or external ID), skips agent/Fleet-owned serials, backfills serial on updates, and gates removal behind isDirectorySource (default false).
  • Scheduler/Trigger: new run-device-sync task in @trigger.dev/sdk and daily orchestration to dispatch device syncs for orgs with a configured provider; fixes maxDuration (seconds) and success reporting.
  • App: Devices tab adds a provider selector and “Sync now” button, gated by integration:update; useDeviceSync hook handles provider selection, sync, and “Last synced” revalidation.

• Migration

  • Run Prisma migrations to add Device.source, integrationConnectionId, externalDeviceId (with unique index on [integrationConnectionId, externalDeviceId]), Organization.deviceSyncProvider, and DynamicIntegration.deviceSyncDefinition.
  • Update dynamic integration manifests to declare device_sync and provide a deviceSyncDefinition (use devicesPath if not devices).
  • Set the org’s device sync provider via the new endpoint or UI and ensure an active connection; the scheduler will run nightly syncs.

^{Written for commit 1fd3cdf. Summary will update on new commits.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
app (staging)	Ready	Preview, Comment	Jun 3, 2026 9:00pm
comp-framework-editor (staging)	Ready	Preview, Comment	Jun 3, 2026 9:00pm
portal (staging)	Ready	Preview, Comment	Jun 3, 2026 9:00pm

[cubic-dev-ai]

1 issue found across 26 files

Confidence score: 4/5

• This PR is likely safe to merge, with low-to-moderate risk driven by a single medium-severity concern rather than a functional break.
• In apps/api/src/integration-platform/controllers/sync.controller.ts, setDeviceSyncProvider uses an inline body type ({ provider: string | null }) instead of a DTO class, which can weaken request validation consistency and Swagger schema quality.
• Because the issue is structural/API-contract hygiene (not a confirmed runtime regression), the merge risk stays limited.
• Pay close attention to apps/api/src/integration-platform/controllers/sync.controller.ts - ensure setDeviceSyncProvider gets a proper DTO with class-validator and Swagger decorators.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/api/src/integration-platform/controllers/sync.controller.ts">

<violation number="1" location="apps/api/src/integration-platform/controllers/sync.controller.ts:1702">
P2: `setDeviceSyncProvider` uses an inline type `{ provider: string | null }` for its body instead of a proper DTO class with Swagger and class-validator decorators</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: setDeviceSyncProvider uses an inline type { provider: string | null } for its body instead of a proper DTO class with Swagger and class-validator decorators

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/api/src/integration-platform/controllers/sync.controller.ts, line 1702:

<comment>`setDeviceSyncProvider` uses an inline type `{ provider: string | null }` for its body instead of a proper DTO class with Swagger and class-validator decorators</comment>

<file context>
@@ -1671,6 +1674,87 @@ export class SyncController {
+  @Post('device-sync-provider')
+  @ApiOperation({ summary: 'Set the device sync provider' })
+  @RequirePermission('integration', 'update')
+  async setDeviceSyncProvider(
+    @OrganizationId() organizationId: string,
+    @Body() body: { provider: string | null },
</file context>