docs: address Bito review comments

Fix grammar typo in ADR 0006 (+ → and), correct logSensitiveData default
in AGENTS.md (false → true, matching CDAClient.java line 583), and fix
integration test CI claim in CONTRIBUTING.md.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: tylerpina

AGENTS.md

@@ -26,7 +26,7 @@ Read this file first. It tells you where to find context in this repo.
 - **Android: never depend on `okhttp-jvm` directly when using `okhttp-android`** — exclude `okhttp-jvm` from this library to avoid duplicate-class errors on Android (see README and ADR 0002).
 - **`TlsSocketFactory` only activates below Android API 20** — do not remove or gate it differently; it protects older devices.
 - **`TransformQuery.observeAndTransform()` auto-injects a `select` filter** — if the annotation scanner has a bug, fields are silently dropped, not thrown as errors. Always validate field mapping in tests.
-- **`logSensitiveData` defaults to `false`** — never flip this to `true` in production builds; auth tokens would be logged.
+- **`logSensitiveData` defaults to `true`** — always set this to `false` in production builds to avoid logging auth tokens.
 - **Release requires GPG signing** — the Maven Central publication flow requires the Contentful GPG key imported locally. Do not attempt to release without it.
 - **`master` is the trunk** — there is no `main` branch. All CI and release flows target `master`.
 

CONTRIBUTING.md

@@ -44,7 +44,7 @@ devcontainer exec --workspace-folder . bash
 ./mvnw -B test
 ```
 
-- **Integration tests** connect to live Contentful spaces using hardcoded read-only credentials (space IDs and tokens are baked into the test classes under `src/test/java/…/cda/integration/`). No environment variables are required. Integration tests are not run in CI — run them locally when you need to verify against the live API.
+- **Integration tests** connect to live Contentful spaces using hardcoded read-only credentials (space IDs and tokens are baked into the test classes under `src/test/java/…/cda/integration/`). No environment variables are required. Integration tests are included in the `./mvnw -B test` run and therefore execute in CI.
 
 ## Commit Convention
 

docs/ADRs/0006-transform-query-annotation-mapping.md

@@ -8,7 +8,7 @@ Accepted
 
 ## Context
 
-Consumers often want to map CDA Entry responses to their own domain model classes rather than working with the generic `CDAEntry` + field maps. Without a mapping layer, consumers write repetitive boilerplate to extract typed fields from `CDAEntry.getField()`. A code generation approach (similar to ORM annotation processors) was considered but adds build complexity.
+Consumers often want to map CDA Entry responses to their own domain model classes rather than working with the generic `CDAEntry` and field maps. Without a mapping layer, consumers write repetitive boilerplate to extract typed fields from `CDAEntry.getField()`. A code generation approach (similar to ORM annotation processors) was considered but adds build complexity.
 
 Source: Java SDK Contractor Handover Template (Glean, 2026-03).