[david-allison]

Note

Assisted-by: GPT-6.1-Sol xhigh

Purpose / Description

This is a very small and hopefully easy-to-review slice of the CI performance work which I've been running in the background.

This kicks off the work in a small, reviewable PR, and paves the way for larger changes.

I explicitly avoided including any large changes, or changes which affected production code in this commit (besides the libanki update).

It's here... this PR isn't much yet... but it opens us up for significantly faster tests!

Fixes

• Part of CI/tests: investigate and resolve timeout issues [Windows primarily] #22543

Approach

• Bump the backend to 0.1.76-anki26.09.3 + depend directly on anki-backend-core.
• Move libanki to the JVM: replace Timber with SLF4J and split out DB helpers.
• Unify some JvmTest functionality with RobolectricTest
• Move a variety of tests, splitting some classes our and retaining
• Add OnDiskJvmTest for future extension

How Has This Been Tested?

This is tests - heavily tested a larger PR where we had ~55% total test time reduction

On a subset of the tests which are affected by this PR:

31.79s -> 18.61s on my M1. 1 run

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[mikehardy]

Assisted-by: Grok 4.7

Thank you — splitting :libanki JVM SQL/cursor helpers from Android cursors while keeping the paging and leak checks in tests is the right foundation.

Locally I rebased onto main without force-pushing (prep stayed at the PR tip). I ran lint (lintAll, ktlintCheck, lint-rules:test), unit tests (jacocoUnitTestReport), and release emulator tests (TEST_RELEASE_BUILD=true via run_emulator_tests.py on emulator-5556 / API35_GAPI); all passed.

Reviewed the new :libanki module with Rust-backed DB/DBCursor, shared JVM test config, SLF4J logging in libanki, and moving pure JVM tests off Robolectric while WorkManager cases stay on device tests.

some acceptable findings, no action required, just leaving for posterity: libanki logs need an SLF4J provider on device; StringToLong.strtol edge cases; DB.mod still public and unused.