Awkward handling of contact addition to non active client

We had a recent discovery with a custom app that, as part of its workflow, creates a client contact if not already defined (by email) in the client.

This app failed to take into account the "status" state of the client and would attempt this regardless.

We found the home API is perfectly fine with creating a "person" with first name, last name, email against a "Potential" client. However, when an attempt is made to edit this new contact with mailing address through the client API will issue a access error.

This seems to be an disconnected decision. I would have expected to not being able to add the person in the first place. As this is, the app would create the contact but then failed trying to complete the process making a mess of the contact state.

How would I post a change request to the home API to change this behavior?