lightning-kmp-app moves to d87af50, which carries Kotlin 2.4.21 down to
secp256k1-kmp, and engine-interop/new follows the app as its comment asks.
The declared Kotlin now matches the stdlib quartz already resolved, and the
resolved graphs are unchanged. secp256k1-kmp and bitcoin-kmp tests,
lightning-kmp-app's library compile and engine-interop all pass. The
Kotlin/Native workaround stays until a mac links without it.
The submodule commits are on claude/dependency-update branches, not pushed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs/tools/engine-interop runs marmot-kmp 2.3.0 over mls-kmp 1.3.1 against
quartz 1.15.2's engine -- the one a Bennu peer on that version runs -- in two
JVMs over a pipe, since one build cannot hold two versions of the quartz group.
Each side creates a room in turn; the other joins by Welcome, applies two more
commits and reads a message each way at every epoch. 20 checks, all green, so
mls 1.3.1's new epoch-0 shape costs nothing against the old engine.
The note records Phase 3, including the first draft of the epoch-0 test, which
asserted a restore-time repair mls-kmp drafted and then removed before 1.3.1.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>