fix(policies): preserve entityId when re-generating a policy

[tofikwest]

Summary

• Fixes bug where currentVersionId became null during policy regeneration
• Root cause: deleting policy versions triggered FK cascade (SET NULL) on the policy's currentVersionId before the new version was written
• Fix: explicitly clear currentVersionId and pendingVersionId before deleteMany within the transaction
• Applied to both API-side and app-side (bulk regeneration) copies of updatePolicyInDatabase

Test plan

• Regenerate a single policy — verify it saves correctly with a valid currentVersionId
• Regenerate all policies via onboarding flow — verify none end up with null currentVersionId
• Verify policy content displays correctly after regeneration

Resolves ENG-90

🤖 Generated with Claude Code

[linear]

ENG-90 When re-generating a policy, the entityId is null causing it to not be saved properly

[cursor]

PR Summary

Medium Risk
Touches policy versioning writes inside a DB transaction; incorrect ordering could impact currentVersionId/pendingVersionId integrity during regeneration, but the change is small and localized.

Overview
Prevents policy regeneration from leaving currentVersionId/pendingVersionId in an unexpected state by explicitly nulling both fields before policyVersion.deleteMany to avoid FK/cascade issues.

Applies the same ordering fix in both the API regeneration helper and the app onboarding/bulk regeneration helper so the new version can be created and then reliably re-linked as currentVersionId.

^{Written by Cursor Bugbot for commit b14e209. This will update automatically on new commits. Configure here.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
app	Ready	Preview, Comment	Mar 30, 2026 3:29pm
comp-framework-editor	Ready	Preview, Comment	Mar 30, 2026 3:29pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
portal	Skipped		Mar 30, 2026 3:29pm