Not sure if this should be in the ACA-Py repo or in this repo, but assuming it is did:webvh specific, so needed here.
If a did:webvh DID that is to be published is intended to support DIDComm, the DIDComm service should be added to the DIDComm during it's creation. AFAIK, this is the same as when an ATTRIB is added to an Indy ledger so that a DID Doc for the DID can include an service endpoint for the DID. This is outlined in the did:sov specification, resolver section.
I suspect that there is startup configuration parameter for the endpoint, and when encountered for a DID to be created, the ATTRIB attribute is also created when using unqualified or did:sov DIDs. The same trigger should be used to insert an appropriate DIDComm service endpoint in a did:webvh DID.