When an agreement is created in the AUTHORING state, updating form fields via the API endpoint PUT /agreements/{agreementId}/formFields should not automatically transition the agreement to IN_PROCESS.

Currently, calling this endpoint causes the agreement to be sent immediately. This makes it impossible for integrations to programmatically place required signature fields and still allow users to review the agreement as a draft before sending.

This behavior differs from the Adobe Sign web UI, where users can place form fields, save the agreement, and continue reviewing or editing without triggering a send. The UI appears to perform a form-field update operation while preserving the AUTHORING state. Additionally, programmatically setting form fields without automatically sending was previously possible in earlier versions of the API.

A typical integration workflow would look like:
1. Create an agreement via API with state = AUTHORING
2. Programmatically add required signature fields (including page number and x/y coordinates) using PUT /agreements/{agreementId}/formFields
3. Present the user with an AUTHORING view of the agreement for review
4. Allow the user to explicitly send the agreement when ready (via UI or PUT /agreements/{agreementId}/state)

This feature would allow Adobe Sign integrations to support a consistent and user-friendly authoring experience:
- Enables dynamic placement of required signature fields
- Preserves user control over when an agreement is sent
- Aligns public API behavior with the Adobe Sign UI
- Avoids forcing integrators to rely on static templates or manual field placement