Bump Compose deps and align the Android side with the Compose BOM

[solcott]

Stack 1/4 — base main. Three commits.

1. Move Compose Multiplatform to 1.12.0-rc01, drop three unused aliases

androidx-compose-ui-tooling, androidx-compose-ui-tooling-preview and androidx-compose-foundation
are removed because nothing declared them — the Compose Multiplatform equivalents replaced all three
during the KMP migration.

2. Bump the rest

metro             1.4.1         -> 1.4.2
circuit           0.36.0        -> 0.36.1
composeUi         1.12.0-rc01   -> 1.12.0     (AndroidX Compose is stable now)
material3         1.5.0-alpha25 -> 1.5.0-alpha26
appcompat         1.7.1         -> 1.8.0
dependency-sorter 0.20.0        -> 0.21.0

Metro is the one worth checking rather than assuming — it is a compiler plugin, so it is coupled
to the Kotlin version, and this branch is on Kotlin 2.4.10 (the Kotlin bump lives in #8, because SKIE
supports 2.4.10 at the latest). 1.4.2 works there.

This commit also corrected a claim the first one got wrong: it had asserted "no version skew on
Android", which was measured on :ui alone and did not generalise.

3. Align Android with the Compose BOM

Rather than document the skew, remove it. Only ui and runtime were declared anywhere, so only
they followed the composeUi pin; foundation and animation were declared nowhere and drifted to
1.12.0-beta01 on :app behind CMP and material3. Nothing warns about that.

androidx.compose:compose-bom:2026.08.00 is the BOM whose core artifacts are 1.12.0. Applied to
Android configurations only — :app, plus an androidMain.dependencies block in :ui and
:presenter, the only KMP modules that pull Compose. Never commonMain: androidx.compose.runtime
is genuinely multiplatform and reaches jvm/native/web through CMP's alias, so a common-scoped BOM
would drag those onto the AndroidX line too.

Verified on both configurations rather than one:

	ui	foundation	animation	runtime
:app	1.12.0	1.12.0	1.12.0	1.12.0
:ui	1.12.0	1.12.0	1.12.0	1.12.0

material3 stays outside the BOM deliberately. The BOM manages it at 1.4.0, older than the alpha
line this project tracks. That is harmless only because a direct dependency with an explicit version
beats a lower BOM constraint — :app resolves 1.5.0-alpha26 and :ui resolves 1.5.0-alpha22 through
CMP's material3. Both resolve up from 1.4.0, never back. Worth re-checking after a BOM bump: a BOM
that ever pins material3 above the alpha would silently win.

A BOM had been rejected once before, per the catalog comment this replaces, on the grounds that it
would stop material3 being pinned independently. That turned out to be avoidable rather than true.

One trap now recorded in AGENTS.md: platform(...) does not exist on a KMP source-set dependency
handler, so androidMain.dependencies { } needs project.dependencies.platform(...). A bare
platform(...) fails to configure.

Verification

ktfmtCheck, test, assembleDebug on this branch alone, plus both dependency reports above, plus
a check that :desktop still resolves Compose Multiplatform 1.12.0-rc01 — the Android alignment did
not leak to other targets.

🤖 Generated with Claude Code