The Installation snippet in rollbar-okhttp/README.md only lists `com.rollbar:rollbar-okhttp` and `com.squareup.okhttp3:okhttp`, but the recorder example below calls `rollbar.recordNetworkEventFor(...)` and `rollbar.log(...)` — methods defined on `com.rollbar.notifier.RollbarBase` in the rollbar-java module. `rollbar-okhttp/build.gradle.kts` only declares `api(project(":rollbar-api"))`, and rollbar-api contains no `Rollbar` notifier class, so a user who copy-pastes the install snippet alongside t

rollbar-okhttp/build.gradle.kts:8 declares `testImplementation("org.mockito:mockito-core:5.23.0")`, but the root subprojects block already adds `org.mockito:mockito-core:5.18.0` to every non-example non-Android subproject (build.gradle.kts:55). Both versions land on the test classpath; Gradle resolves to the highest (5.23.0), so tests pass — but rollbar-okhttp silently diverges from every other module's pinned version, and a future root mockito bump won't apply uniformly here. Drop the local lin

**Logging consistency:** `RollbarOkHttpInterceptor` uses `java.util.logging.Logger`, but every other production module in the SDK (rollbar-java, rollbar-web, rollbar-jakarta-web, rollbar-struts2, rollbar-reactive-streams, rollbar-android, etc.) uses SLF4J via `org.slf4j.LoggerFactory`, and rollbar-java declares `slf4j-api` as an `api` dependency. Switching to `org.slf4j.Logger` / `LoggerFactory.getLogger(RollbarOkHttpInterceptor.class)` would keep this module consistent with the rest of the SDK