Werkbaum `#dash.matrix.sdk`: **Trixnity runs on the dashboard's JVM, with vodozemac rather than libolm.**
A spike in `dashboard/spikes/matrix-sdk`, a Gradle build of its own — nothing reaches the dashboard's classpath or bundle. It signs in nowhere and sends nothing:
- Olm: two accounts, pre-key message and answer decrypted.
- Megolm: three room messages through a group session decrypted.
- The client's vodozemac crypto driver module loads.
- With a server name as argument: `.well-known` discovery and `/versions` of its homeserver.
Run from `dashboard/`: `../gradlew -p spikes/matrix-sdk run --args="matrix.org"` (also `classpathSize`, `moduleDeps`).
Findings, recorded in the Werkbaum description:
- Trixnity 5.9.2 compiles with the dashboard's Kotlin 2.2.21 on Temurin 21 and pulls kotlin-stdlib 2.3.21.
- vodozemac via JNI; the native library (Linux x86-64/aarch64) is unpacked into the temp directory, which must allow execution; needs glibc 2.34 — mih09 has 2.36.
- Discovery and versions work against matrix.org and the user's homeserver (not named in the repository).
- For the bundle: 49 jars, 24 MB more; jlink additionally needs `java.logging`, `java.management`, `java.instrument`, `jdk.unsupported`.
- Next: the client's store, `trixnity-client-repository-exposed` on the sqlite-jdbc the dashboard already has.
Dashboard tests still green; the Werkbaum parser reports no warnings.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: mhoennig <michael@hoennig.de>
Reviewed-on: #5
miandmhoennig
3a14978aae