Docs for getting Kotlin/maven component seem incomplete

I followed the docs in the Readme to add to my build.gradle.kts script, and I get:

Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
      > Could not find any matches for rustls:rustls-platform-verifier:latest.release as no versions of rustls:rustls-platform-verifier are available.
        Searched in the following locations:
          - https://dl.google.com/dl/android/maven2/rustls/rustls-platform-verifier/maven-metadata.xml
          - https://repo.maven.apache.org/maven2/rustls/rustls-platform-verifier/maven-metadata.xml
          - file:/Users/rob/Workspace/external/rustls-platform-verifier/android-release-support/maven/rustls/rustls-platform-verifier/maven-metadata.xml
          - file:/Users/rob/Workspace/external/rustls-platform-verifier/android-release-support/maven/rustls/rustls-platform-verifier/
          - file:/Users/rob/Workspace/external/rustls-platform-verifier/android-release-support/maven/rustls/rustls-platform-verifier/.gitkeep/rustls-platform-verifier-.gitkeep.pom
          - file:/Users/rob/Workspace/external/rustls-platform-verifier/android-release-support/maven/rustls/rustls-platform-verifier/.gitkeep/rustls-platform-verifier-.gitkeep.jar
        Required by:
            project ':app'

That android-release-support/ seems to be empty. The kotlin files are in android/. Am I supposed to compile something and copy it to android-release-support/?

Maybe this is because I have a local cloned repo. (I had to because I need to use JNI 0.22, which you have on a branch).

Can I just copy the .kt files to my Android App project? That might be easier than dealing with Gradle.

Start with the Kotlin/Gradle instructions in the README and compare them with the contents of android/ and android-release-support/. Reproduce the dependency-resolution failure if possible, then document the correct local-build or dependency setup and whether copying the .kt files is supported. Done means a newcomer can follow the README without the missing-artifact error.