docs/scripts/marmot-kmp-imports.sh, with --apply, --revert and --check. The destinations
in it are not derived from the packages' names but from listing what quartz 2.15.1 still
has under `marmot/` against what marmot-kmp 2.2.1 and mls-kmp 1.3.0 declare, which is how
the split inside `mip00KeyPackages`, `mip02Welcome`, `mip03GroupMessages` and
`mip05PushNotifications` came out: the events and tags stay, the five stores and managers
beside them move. marmot-kmp imports the quartz half itself.
Applied and reverted on a clean tree it moves 187 lines and puts all 187 back -- 79 onto
marmot-kmp, 80 onto mls-kmp, 27 onto crypto-kmp, one KDoc line -- and leaves the 42
`quartz.marmot` event imports standing, which is the count the plan's table predicts.
Reversible because the fork still cherry-picks from upstream, upstream is on quartz 1.15.2
with the engine inside it, and every line this touches is one a cherry-pick will conflict
in. The resolution is to re-run the rule, not to read the diff.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>