[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.

[cursor]

PR Summary

Medium Risk
Moderate UI/state changes in SOA answering that alter how applicability/justification are displayed and how manual saves override autofill results, which could impact what users see immediately after edits.

Overview
Updates the SOA applicability cell UX by replacing the YES/NO badge with a new swatch-based ApplicableReadOnlyDisplay and matching select items (ApplicableSwatchRow).

Changes the save/update flow so EditableSOAFields reports a structured { isApplicable, justification } payload; table state now stores savedIsApplicable (SOATableAnswerData) to let manual edits immediately override autofill/processed results on both desktop and mobile without a full reload.

^{Written by Cursor Bugbot for commit d164c77. 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 (staging)	Ready	Preview, Comment	Apr 3, 2026 8:08pm
comp-framework-editor	Ready	Preview, Comment	Apr 3, 2026 8:08pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
portal (staging)	Skipped		Apr 3, 2026 8:08pm

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Edit click no longer opens justification dialog for "No" answers

High Severity

handleEditClick no longer opens the justification dialog when isApplicable is already false. Since Radix UI's Select only fires onValueChange when the value actually changes, re-selecting "no" while it's already "no" won't trigger handleSelectChange. This means users can't access the justification dialog to edit justification text for existing "No" answers. The only workaround is switching to "Yes" first, which triggers an immediate destructive save via executeSave(true, null), wiping the previous justification.