Invoking it
The profile is selected with --profile high-trust on the conformance validator, whose default is --profile default:
packages/ver-validator/ is the reference implementation of this profile; the flag is the profile's selector, and the identifier at the head of this document is its full versioned form. The profile member of a report stays the base profile's identifier — high-trust is a severity policy over vera-profile/1.1-draft, not a separate rule set — and the promotion is visible where it belongs, in the severity of the finding.
Selecting high-trust against a 1.0.0 or 1.0.1 record changes nothing. VER1606 is a 1.1-draft rule and never fires for a 1.0.x schema_version, so the run's output is what the default profile produces, byte for byte. The flag is accepted rather than rejected there because a deployment sets its policy once and validates a mixed corpus with it, and a usage error on the older records would be a policy flag behaving like a schema flag.