@eullersilva-plankchecks…scim/stack-1-db-types → main124 files · +13909 −802updated 11h agoPart 1/7 of the SCIM integration stack — foundation layer with no behavior change.
packages/types: SCIM schemas (incl. activity events), org-settings SCIM settings, error codes| # | Branch | Layer |
|---|---|---|
| 1 | scim/stack-1-db-types | Prisma models + migrations, shared types |
| 2 | scim/stack-2-fusionauth | FusionAuth SCIM provisioning + rate limiting |
| 3 | scim/stack-3-engine | SCIM engine: ingestion, projection, reconcile, repair |
| 4 | scim/stack-4-ingress | Webhook routes, token endpoint, crons, proxy paths |
| 5 | scim/stack-5-settings-ui | Admin tRPC surface + SSO & SCIM settings UI |
| 6 | scim/stack-6-onboarding | Getting-started wizard (SCIM-aware) |
| 7 | scim/stack-7-misc-docs | Workflows page + SCIM customer docs |
How to merge — single merge to main (top-down cascade):
scim/stack-6-onboarding, #597 into scim/stack-5-settings-ui, #596 into scim/stack-4-ingress, #595 into scim/stack-3-engine, #594 into scim/stack-2-fusionauth, #593 into scim/stack-1-db-types. Each head is a descendant of its base, so these merges are conflict-free and none of them touch main.main as a merge commit (preserves the per-layer commits for bisect/blame). This is the only merge that lands on main.If a layer needs changes during review, push the fix to that layer's branch; the fix is then propagated up the stack so later branches include it.
Every layer typechecks, lints, and passes its tests independently. The stack tip is content-identical to integration/scim (+ current main), except three one-off backfill scripts in apps/admin/scripts-tmp/ that were intentionally left out of main.
@codex review
Codex Review: Didn't find any major issues. Keep it up!
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
@codex review
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| composio-enterprise-internal |  Error | Jun 12, 2026 9:43pm |
@eullersilva-plank must be a member of the Composio team on Vercel to deploy. - Click here to add @eullersilva-plank to the team. - If you initiated this build, request access.
Learn more about collaboration on Vercel and other options here.