CS-208: [Bug] - Statement of Applicability only allows you to change answers from Yes to No and not the other way around

[github-actions]

This is an automated pull request to merge chas/statement-of-applicability into dev.
It was created by the [Auto Pull Request] action.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
app	Ready	Preview, Comment	Apr 3, 2026 7:25pm
comp-framework-editor	Ready	Preview, Comment	Apr 3, 2026 7:25pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
portal	Skipped		Apr 3, 2026 7:25pm

[cursor]

PR Summary

Medium Risk
Changes SOA answer editing and optimistic table state by carrying both isApplicable and justification through the update path, which could affect how saved vs autofilled values display until SWR revalidation.

Overview
Fixes SOA applicability editing so answers can be changed both from Yes→No and No→Yes, and ensures saves immediately reflect in the table without relying on a full document reload.

This introduces a typed SOAFieldSavePayload and extends row answer state with savedIsApplicable, updating SOAFrameworkTable/SOATable/row components to use the payload and prefer the manually-saved applicability over autofill results. UI polish replaces the YES/NO badge with a consistent swatch+label display (ApplicableSwatchRow) in both read-only cells and the select menu.

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

[linear]

CS-208 [Bug] - Statement of Applicability only allows you to change answers from Yes to No and not the other way around

[chasprowebdev]

Recording:

applicability.mov

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