## The symptom

After upgrading `getbrevo/brevo-php` from 2.0.6 to 2.0.7, every `updateContact()`
call fails with a 400 Bad Request. The request goes to something like:

```
PUT https://api.brevo.com/v3/contacts/{url-encoded-UpdateContact-JSON}
```

The whole UpdateContact object is serialized into the endpoint path instead of
the contact identifier.

## Why

The parameter order of `updateContact()` changed in 2.0.7 (tagged as a patch
release). Calls written for 2.0.6 put the UpdateContact object where the
identifier belongs, and the SDK passes it into `ObjectSerializer::toPathValue()`
instead of the email/identifier.

## The fix

Swap the two arguments so the contact identifier goes into the identifier slot
and the UpdateContact object goes into the body slot, matching the 2.0.7
signature. Check `docs/Api/ContactsApi.md` in the SDK for the exact order.
Several users confirmed swapping the arguments resolves the 400s.

## Going forward

If you pinned to 2.0.6 you are unaffected. But audit every Brevo SDK update:
the SDK is generated code and parameter order has changed before, including in
patch releases. A quick diff of the `ContactsApi` signatures after each upgrade
is cheap insurance.