[comp] Production Deploy

[github-actions]

This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.

---

Summary by cubic

Fixes policy content writes that were saving empty blocks and ensures drafts stay in sync so publishing doesn’t revert edits. Adds transaction row locks and a single lock order to prevent deadlocks and race conditions. Addresses Linear CS-722.

• Bug Fixes
  • Preserve TipTap nodes by reading raw obj.content in UpdateVersionContentDto to prevent [[],[],...] serialization.
  • On draft policy updates, write non-empty edits to both content and draftContent to avoid phantom “unpublished changes” and publish reverts.
  • In updateVersionContent, lock the policy row, reject edits to published/pending versions, and mirror edits into Policy.draftContent (and Policy.content when editing the live draft).
  • Use a consistent lock/order in publishes and approvals: update Policy before PolicyVersion to avoid Postgres deadlocks.
  • Added focused regression tests for serialization, draft syncing, publish-without-version behavior, and lock ordering.

^{Written for commit c3ffd85. Summary will update on new commits.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
comp-framework-editor (staging)	Ready	Preview, Comment	Jul 29, 2026 1:28pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
app (staging)	Skipped		Jul 29, 2026 1:28pm
portal (staging)	Skipped		Jul 29, 2026 1:28pm

[cubic-dev-ai]

1 issue found across 4 files

Confidence score: 3/5

• In apps/api/src/policies/policies.service.ts, updating a draft with content: [] appears to keep stale draftContent while persisting empty content, so the no-versionId publish path can publish old text instead of the intended cleared policy—treat explicit empty arrays as a real draft update (clear draftContent) and add a regression test for this publish flow.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/api/src/policies/policies.service.ts">

<violation number="1" location="apps/api/src/policies/policies.service.ts:420">
P2: Clearing a draft policy's content with an explicit empty array leaves `draftContent` on the previous text. The same update then persists `content: []`, while the no-`versionId` publish path prefers non-empty `draftContent` over `content`, so publishing after a clear can restore the old policy body instead of preserving the requested empty document. Since `content` is array-validated but not non-empty-validated, this branch should either preserve the explicit empty array in `draftContent` or reject it before writing; it should not silently leave the two policy fields inconsistent.

(Based on your team's feedback about preserving explicitly saved empty arrays.) [FEEDBACK_USED]</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Clearing a draft policy's content with an explicit empty array leaves draftContent on the previous text. The same update then persists content: [], while the no-versionId publish path prefers non-empty draftContent over content, so publishing after a clear can restore the old policy body instead of preserving the requested empty document. Since content is array-validated but not non-empty-validated, this branch should either preserve the explicit empty array in draftContent or reject it before writing; it should not silently leave the two policy fields inconsistent.

(Based on your team's feedback about preserving explicitly saved empty arrays.)

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/api/src/policies/policies.service.ts, line 420:

<comment>Clearing a draft policy's content with an explicit empty array leaves `draftContent` on the previous text. The same update then persists `content: []`, while the no-`versionId` publish path prefers non-empty `draftContent` over `content`, so publishing after a clear can restore the old policy body instead of preserving the requested empty document. Since `content` is array-validated but not non-empty-validated, this branch should either preserve the explicit empty array in `draftContent` or reject it before writing; it should not silently leave the two policy fields inconsistent.

(Based on your team's feedback about preserving explicitly saved empty arrays.) </comment>

<file context>
@@ -410,6 +410,16 @@ export class PoliciesService {
+        // (POST :id/versions/publish with no versionId, which snapshots
+        // draftContent) revert the content that was just written. An empty
+        // array carries no text, so it must never wipe the stored draft.
+        if (contentValue.length > 0) {
+          updatePayload.draftContent = contentValue;
+        }
</file context>

Suggested change

	if (contentValue.length > 0) {
	updatePayload.draftContent = contentValue;
	}
	updatePayload.draftContent = contentValue;