Use Case

As a... CSFLE/QE user
I want... to easily understand which filename I need to specify where
So that... I am less confused by the presence of libmongocrypt, mongocryptd, crypt_shared and other files with similar names.

User Experience

• Users stop trying specify a libmongocrypt file or other one in place of the crypt_shared library.

Dependencies

• Not really a dependency, but a ticket with similar goals: MONGOCRYPT-738

Risks/Unknowns

• There's an obvious risk that users could rename their files, which is definitely supported, but highly unlikely to happen in a typical environment. Working around this restriction is easy.

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward