Clarification on `aud` claim of Request object

Specification provides the following description

When the Verifier is sending a Request Object as defined in [RFC9101], the aud claim value depends on whether the recipient of the request can be identified by the Verifier or not:

• the aud claim MUST be equal to the iss (issuer) claim value, when Dynamic Discovery is performed.
• the aud claim MUST be "https://self-issued.me/v2", when Static Discovery metadata is used.
  Note: "https://self-issued.me/v2" is a symbolic string and can be used as an aud claim value even when this specification is used standalone, without SIOPv2.

Can you please clarify what this Dynamic vs Static discovery means when

• we have a OpenID4VP authorization request (not combined with SIOP) and
• wallet is a mobile application

To my understanding, in the above case a Verifier has the chance to "dynamically" discover the wallet only if

• Verifier uses request_uri_method equal to post and
• Wallet performs such a post, passing wallet_metadata

Start with the linked OpenID4VP specification section on the Request Object aud claim, then review its definitions of Dynamic Discovery, Static Discovery, request_uri_method, and wallet_metadata. Compare those definitions with the OpenID4VP authorization-request flow for a mobile wallet. Done means the issue receives a clear, specification-backed explanation of which discovery case applies.