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 version deletion and currentVersionId/pendingVersionId updates inside a DB transaction; mistakes here could leave policies without a valid current version. Scope is small and duplicated in two helper implementations (API and onboarding).

Overview
Fixes policy regeneration to avoid foreign-key constraint/cascade side effects when removing old policy versions.

In both the API and onboarding updatePolicyInDatabase helpers, the transaction now explicitly nulls currentVersionId and pendingVersionId on the policy record before deleteMany removes existing policyVersion rows, then creates a fresh version and reassigns currentVersionId.

^{Written by Cursor Bugbot for commit 71f0637. 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	Apr 2, 2026 8:03pm
comp-framework-editor	Ready	Preview, Comment	Apr 2, 2026 8:03pm
portal	Ready	Preview, Comment	Apr 2, 2026 8:03pm