fix(ci): preserve landing dependencies and favor integration latency

Author: waleedlatif1

.github/CI.md

@@ -9,7 +9,7 @@ A PR compares its merge base with the checked-out merge commit. Pushes and norma
 | Independent SDK | That workspace's tests and type-check; no app build, services, or browsers |
 | App unit test | App test shards and test type check |
 | Integration test | Both provision paths; no HTTP/browser job merely for the test edit |
-| Workspace UI | Database integration, mobile and live Electron, plus app tests/build |
+| Workspace UI | Database integration, mobile, SEO and live Electron, plus app tests/build |
 | Landing content | SEO, app tests/build; no database integration or Electron |
 | Shared runtime or transitive dependency | All dependent boundaries |
 | One E2E harness | Its acceptance group and the shared production build |
@@ -18,11 +18,15 @@ The server boundary deliberately includes all API routes and backend domains. Sh
 
 Integration also depends on workspace UI because the desktop executor integration suite runs the production workspace stream dispatcher against PostgreSQL and Redis. Its explicit harness inputs include the database and realtime Vitest configs and integration setup files, which runtime tasks exclude.
 
+SEO depends on workspace UI and server code: landing pages reuse workspace pricing and preview components, provider models/pricing, and the block registry. These directory boundaries are not isolated application dependency graphs.
+
 `affectedTasks` already uses task inputs. Do not enable `futureFlags.affectedUsingTaskInputs` just for this planner: that flag also changes pruning, which can pull CI-only cross-app task dependencies into production Docker contexts.
 
 Affected type-checks follow the package graph too; repository audits and lint always run. Workspace-only unit jobs use a free GitHub runner and do not start the app test shards.
 
-Lightweight HTTP suites and database integration run on free standard GitHub runners. Memory-heavy builds and browser jobs retain appropriately sized Blacksmith runners. Electron uses 4-vCPU Blacksmith: both shards passed within 14 seconds of the 8-vCPU control; the free GitHub rest shard was slower and its lease run stalled.
+Lightweight HTTP suites run on free standard GitHub runners. Database integration uses 2-vCPU Blacksmith: a same-source comparison of all 16 jobs had a slowest shard of 6m 04s versus 6m 55s on free GitHub, with identical coverage. The existing `CI_PROVIDER` switch retains that tested GitHub fallback; provider changes also select the matching cache setup. This is one paired sample, not a long-run percentile estimate.
+
+Memory-heavy builds and browser jobs retain appropriately sized Blacksmith runners. Electron uses 4-vCPU Blacksmith: both shards passed within 14 seconds of the 8-vCPU control; the free GitHub rest shard was slower and its lease run stalled.
 
 Every HTTP and browser group consumes the same production build in an isolated job/database. Electron also uses that build and skips its development-route warm-up. Local HTTP and Electron development runs retain their dev-server behavior. Build inputs exclude test-only files so a harness edit can reuse an unchanged production build.
 

.github/workflows/checks.yml

@@ -71,12 +71,12 @@ jobs:
     # The two paths build different schemas (migrations add triggers, checks and NOT VALID
     # constraints that `db:push` does not), so each runs the whole suite. Vitest splits each
     # suite's files across eight shards by measured duration (DurationBalancedSequencer in vitest.shared.ts); a
-    # shard runs its files one at a time against its own database. Standard GitHub runners are
-    # free for this public repository and have enough memory for the app, Postgres and Redis.
+    # shard runs its files one at a time against its own database. Blacksmith keeps the critical
+    # integration path fast; standard GitHub runners retain a free, validated fallback.
     name: integration (${{ matrix.provision }}, ${{ matrix.shard }}/8)
     needs: changes
     if: needs.changes.outputs.integration == 'true'
-    runs-on: ubuntu-24.04
+    runs-on: ${{ (vars.CI_PROVIDER == '' || vars.CI_PROVIDER == 'blacksmith') && 'blacksmith-2vcpu-ubuntu-2404' || 'ubuntu-24.04' }}
     timeout-minutes: 20
     strategy:
       fail-fast: false
@@ -135,7 +135,7 @@ jobs:
       - name: Setup workspace
         uses: ./.github/actions/setup
         with:
-          provider: github
+          provider: ${{ vars.CI_PROVIDER }}
 
       - name: Provision a fresh database through the supported command
         working-directory: packages/db

apps/sim/turbo.json

@@ -131,7 +131,7 @@
       "cache": false
     },
     "ci:e2e-seo": {
-      "dependsOn": ["ci:shared"],
+      "dependsOn": ["ci:server", "ci:ui"],
       "inputs": ["app/(landing)/**", "content/**", "scripts/test-landing-seo-e2e.ts"],
       "cache": false
     },

scripts/ci-changes.test.ts

@@ -144,7 +144,7 @@ describe('CI task attribution through real Turborepo', () => {
       'apps/sim/app/workspace/[workspaceId]/home/hooks/stream/dispatch-stream-event.ts',
     ])
     expect(plan.fallback).toBeUndefined()
-    expect(groups(plan)).toEqual(['mobile'])
+    expect(groups(plan)).toEqual(['mobile', 'seo'])
     expect(plan.flags).toMatchObject({
       desktop_live: true,
       integration: true,
@@ -164,6 +164,15 @@ describe('CI task attribution through real Turborepo', () => {
       build: true,
     })
   })
+  it.each([
+    'apps/sim/app/workspace/[workspaceId]/upgrade/components/comparison-table/comparison-data.ts',
+    'apps/sim/providers/models.ts',
+    'apps/sim/blocks/registry.ts',
+  ])('runs SEO when landing pages consume changed workspace or backend code: %s', (file) => {
+    const plan = classifyFiles([file])
+    expect(plan.fallback).toBeUndefined()
+    expect(groups(plan)).toContain('seo')
+  })
   it('preserves the implicit app test dependency on docs content', () => {
     const plan = classifyFiles(['apps/docs/content/docs/integrations/netsuite.mdx'])
     expect(plan.fallback).toBeUndefined()