[AIT-1008] Generate LiveObjects tests based on UTS test specs

[sacOO7]

• Fixes https://ably.atlassian.net/browse/AIT-1008
• Generated UTS markdown to have better understanding of existing UTS infra.
• This is also helpful for a relevant uts-to-kotlin skill to better generate ably-java tests
• Based on the doc, we have missing sandbox test, need to update the same

---

📚 Human-readable UTS guide + website

To make the UTS setup approachable, this PR adds a comprehensive guide and a self-contained website, kept in sync:

• uts/README.md — renders on the module's GitHub page.
• uts/index.html — a standalone, offline-friendly website (inline SVG flow diagrams, scroll-spy nav, light/dark theme; no external assets).

Both walk through: what UTS is → the three test tiers → the spec docs (linked to GitHub) → the uts/ module layout → the SDK hook points → the unit & proxy infrastructure → the two example tests → deviations → how to run → appendices (flow diagrams + per-file API reference + source map).

🗂️ Test package restructure

Test sources are reorganised under a domain-rooted io.ably.lib.uts package that cleanly separates infrastructure from tests, and unit from integration:

io/ably/lib/uts/
├── infra/                        # test infrastructure (no @Test methods)
│   ├── Utils.kt                  #   shared awaits (awaitState / pollUntil …)
│   ├── unit/                     #   mock transports + ConnectionDetails builder
│   └── integration/              #   SandboxApp
│       └── proxy/                #     ProxyManager, ProxySession
├── unit/realtime/                # UNIT tests          → ConnectionRecoveryTest
└── integration/proxy/realtime/   # INTEGRATION tests   → AuthReauthTest

The unit/ ↔ infra/unit/ and integration/ ↔ infra/integration/ pairing is what the new Gradle tasks key off.

Note: the ConnectionDetails test builder no longer lives in io.ably.lib.types, so it now obtains the package-private constructor reflectively (same approach as liveobjects/.../TestUtils.kt).

⚙️ Per-tier Gradle tasks + CI wiring

Added two package-filtered test tasks in uts/build.gradle.kts, mirroring runLiveObjectsUnitTests / runLiveObjectsIntegrationTests:

Task	Runs	CI
:uts:runUtsUnitTests	io.ably.lib.uts.unit.* (mocked, fast)	check.yml (PR gate)
:uts:runUtsIntegrationTests	io.ably.lib.uts.integration.* (real sandbox + proxy)	integration-test.yml → new check-uts job

✅ Validation

• ./gradlew :uts:runUtsUnitTests → 6/6 pass · :uts:runUtsIntegrationTests → 1/1 pass.
• Full CI gate checkWithCodenarc checkstyleMain checkstyleTest runUnitTests runLiveObjectsUnitTests :uts:runUtsUnitTests → BUILD SUCCESSFUL.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 65530f9a-0a70-4efb-8ad3-26fa106d362f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/liveobjects-uts-tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}