Class ActivateInteractiveFormVersionAction

Promote a Pending override to Active. Flips:

• target Override: Status='Active'
• target Override's Component: Status='Active'
• prior Active sibling Override: Status='Inactive'
• prior Active sibling Component: Status='Inactive'

"Sibling" = another of the caller's User-scope overrides on the same EntityID that is currently Status='Active'. The target is the row identified by the input OverrideID.

Only the caller's own User-scope overrides can be activated. A Role or Global override, or another user's, returns FORBIDDEN for every caller (see CheckPersonalWrite in _shared.ts): shared forms are managed from Form Builder or the form's Manage drawer. The target's Component and Override flip to Active in one entity transaction. Each prior Active sibling is set aside after that transaction: its Override first, then its Component. Every prior is tried. If a save fails, the action returns PERSIST_FAILED that names each prior row not updated, and the target stays Active. A prior whose Override could not be set aside is still Active, so a retry sets it aside. A prior whose Override is set aside but whose Component status could not be updated is not found by a retry, and its Component keeps its old status.

Idempotency. If the target Override is already Active, the caller's other Active overrides on the entity are set aside and the action returns SUCCESS with a no-op message that carries DemotedCount. So a retry after PERSIST_FAILED sets aside a prior whose Override could not be set aside; a prior whose Component status could not be updated is not found again. If the target is Inactive, that's a misuse — we surface NOT_PENDING so the agent / UI can ask the user what they really want.

Inputs:

• OverrideID (required, string) — the Pending override to activate

Outputs:

• ComponentID — the Component now Active
• OverrideID — echoed for convenience
• PreviousActiveOverrideID — the first override that was demoted (or null)