I think you misunderstood the state of authentication. This integration has already implemented the POST process to get its own token. Allowing the user to generate a token for several minutes after proving proximity is not currently scheduled for removal at some future date, as it is an intended use case. I'm not 100% certain, but I believe that the "at some point in the future we will make the panel re-lock itself" I alluded to months and months ago was deployed in the firmware revision that introduced the proximityProven boolean.
I think you misunderstood the state of authentication. This integration has already implemented the POST process to get its own token. Allowing the user to generate a token for several minutes after proving proximity is not currently scheduled for removal at some future date, as it is an intended use case. I'm not 100% certain, but I believe that the "at some point in the future we will make the panel re-lock itself" I alluded to months and months ago was deployed in the firmware revision that introduced the proximityProven boolean.