fix(onboarding): add initialize-organization trigger task and recover…

[Marfuen]

…y guard

If createOrganizationMinimal partially fails (org created but initializeOrganization doesn't run), the org ends up with no framework instances, controls, policies, or tasks. completeOnboarding now detects this and runs initializeOrganization as recovery before triggering the onboard job. A standalone Trigger.dev task allows manual re-runs from the dashboard for orgs already in this broken state.

Also saves raw framework IDs to context for reliable recovery lookups and upserts the onboarding record in case that was also missing.

What does this PR do?

• Fixes #XXXX (GitHub issue number)
• Fixes COMP-XXXX (Linear issue number - should be visible at the bottom of the GitHub issue description)

Visual Demo (For contributors especially)

A visual demonstration is strongly recommended, for both the original and new change (video / image - any one).

Video Demo (if applicable):

• Show screen recordings of the issue or feature.
• Demonstrate how to reproduce the issue, the behavior before and after the change.

Image Demo (if applicable):

• Add side-by-side screenshots of the original and updated change.
• Highlight any significant change(s).

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

• Are there environment variables that should be set?
• What are the minimal test data to have?
• What is expected (happy path) to have (input and output)?
• Any other important info that could help to test that PR

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my changes generate no new warnings

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
app	Ready	Preview, Comment	Apr 10, 2026 8:26pm
comp-framework-editor	Ready	Preview, Comment	Apr 10, 2026 8:26pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
portal	Skipped		Apr 10, 2026 8:26pm

[cursor]

PR Summary

Medium Risk
Touches onboarding completion flow and framework initialization, adding recovery paths that write core framework/control/policy/task data; failures or mis-resolved framework IDs could leave orgs partially initialized or trigger extra work.

Overview
Ensures orgs that reached completeOnboarding in a partially-created state are automatically recovered by initializing missing framework instances before triggering the main onboarding job, and by upserting a missing onboarding record.

Adds a reusable resolveFrameworkIds helper (prefers stored raw frameworkIds, falls back to name-based lookup) and updates minimal org creation to persist both framework display names and raw ID JSON in onboarding context.

Introduces a standalone Trigger.dev initialize-organization task (queue + retries) to manually or programmatically re-run organization framework initialization, skipping work if initialization already happened.

^{Reviewed by Cursor Bugbot for commit 73df3dd. Bugbot is set up for automated code reviews on this repo. Configure here.}

[claudfuen]

🎉 This PR is included in version 3.21.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀