fix: stabilize guided import branch

[jaeyunha]

Summary

• keep the guided GitHub import branch clean on top of staging
• renumber provider migration files after staging gained customer request migrations
• repair the integrations settings merge so provider setup tests parse and Google Sheets/Front/Zendesk setup flows stay visible

Verification

• pnpm --filter @exponential/web exec vitest run tests/import-export-view.test.tsx
• pnpm --filter @exponential/web exec vitest run tests/integrations-view.test.tsx
• node scripts/check-migrations.mjs
• make check (blocked: web typecheck still imports removed Better Auth/Drizzle modules and missing subscribeToSync export outside this diff)

[chatgpt-codex-connector]

💡 Codex Review

exponential/packages/proto/migrations/0012_customer_requests_gong.sql

Line 1 in 27e93b1

CREATE TABLE IF NOT EXISTS customer (

Preserve existing migration filenames

Renaming this migration (and the sibling 0010/0011 renames in this diff) breaks the migration contract: apps/api/cmd/migrate records applied migrations by filename, and packages/proto/migrations/README.md explicitly says not to rename migrations that may have been applied. On any database that already has 0010_customer_requests_gong.sql recorded, 0012_customer_requests_gong.sql is treated as unapplied and executed again, leaving divergent migration history; keep historical filenames and adjust the guard with an explicit exception/alias instead.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Gate setup forms on server-provided actions

For non-admin/non-owner users, integrationActions returns canConnect/canReconnect false even though uninstalled providers still have status: "not_connected". Because canAct also trusts status, the catalog now renders GitLab/Jira/Front/Zendesk credential forms and enabled setup buttons to users who cannot manage integrations; submitting only fails with a 403 after they enter secrets. Gate these forms on the server-provided action flags rather than status alone.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Disable Google Sheets creation with no export scopes

The previous catalog button was disabled when issues, projects, and initiatives were all unchecked, matching GoogleSheetsConnect's hasGoogleSheetsScope validation. This new button stays enabled with all three scopes false, so the UI sends a request that the API rejects with “Select at least one Google Sheets export scope” instead of preventing the invalid flow; keep the prior all-scopes-empty disabled condition here.

Useful? React with 👍 / 👎.

[jaeyunha]

Controller disposition for current head 27e93b1: validation-blocked; do not merge as-is.

Current blockers:

• PR fix: stabilize guided import branch #727 is not based on current origin/staging and conflicts in apps/web/src/app/(app)/settings/integrations/page.tsx during merge simulation.
• The diff renames already-published migration filenames (0010_*/0011_agent_runs.sql -> 0012_*...0018_*). Migration filename identity is applied production state, so this must be rebuilt without renaming landed migration files; add a new follow-up migration only if schema repair is needed.
• Scope is a guided import branch stabilization slice, not the full Parity: upgrade import/export to guided provider imports #559 guided GitHub Issues import contract, so it cannot close Parity: upgrade import/export to guided provider imports #559 as-is.

Required before merge: rebuild/rebase on current origin/staging, preserve existing migration filenames, keep only the intended #559 slice, and rerun focused web/import-export/integrations plus migration checks.

[jaeyunha]

Controller validation: blocked. This PR currently conflicts with staging, renames already-landed migration files, and only covers a stabilization slice of #559 rather than the full guided import scope. Do not merge as-is. Next controller action is to salvage only legitimate unlanded #559 deltas onto a fresh branch from current origin/staging, with no migration renames.