Class ModifyInteractiveFormAction

Modify an existing interactive-form override.

Behavior is driven by the VersionBumpKind input and the source Override's status (Override is the canonical "is this live" signal — Component.Status can drift independently):

Defaults preserve historical behavior: omit VersionBumpKind and Pending sources stay in-place, Active sources bump minor, Inactive sources bump patch (the conservative branch-from-historical case).

Security clamp. Modify always writes a User-scope Pending Override, regardless of the original override's scope. Even if the caller is modifying a Role-scope or Global override (which they have permission to read because they pass the ownership check), the new Pending sibling is always User-scoped to the calling user. Scope promotion (User → Role → Global) is a separate, deliberate human action with its own permission gate in Component Studio / Form Builder. The agent cannot widen scope through Modify any more than through Create.

Ownership check. The caller must own (or have role membership for, or be admin over) the existing override they're modifying. See checkOverrideOwnership in _shared.ts. Returns FORBIDDEN if rejected.

Inputs:

• OverrideID (required, string) — the override to modify
• Spec (required, ComponentSpec | string) — the new form spec
• Notes (optional, string) — appended to the override's Notes column
• VersionBumpKind (optional, 'in-place' | 'patch' | 'minor' | 'major') — see table above

Outputs:

• ComponentID — the Component row that now holds the spec (new for snapshots, same for in-place)
• OverrideID — the Override row that points at it
• Mode — 'in-place' or 'new-version'
• Version — the Component's resulting Version string