marmotAudit runs docs/scripts/marmot-kmp-imports.sh --check from `check`, beside the M3,
brand and wallet audits. Verified both ways: silent on a clean tree, and on a tree with
one import put back it names the file and the line and fails with a pointer to the note.
That is C2 made enforceable -- a cherry-pick from a Bennu still on quartz 1.15.2 brings
the old spelling back, and "re-run the rule" is advice until a build failure makes it a
step.
The other three items of this phase are named in the note rather than done, each for a
reason:
- The app's own copies: nothing to delete. CommitOrdering is still live in NostrDao's
reindex sweep and MarmotInboundManager's epoch tracker, and marmot-kmp has no
CommitOrdering at all -- the convergence engine replaced the idea, not the class. Under
D4 the legacy pipeline keeps its behaviour, so the comparator retires with the profile.
- The sender ratchet record wants a new table, so schema 36 -> 37 and an AutoMigration,
and the interface says the write MUST be durable before it returns or a lost position
reuses an AEAD key and nonce pair. A per-message write path with a correctness hazard
does not belong in the tail of a migration whose discipline was D5. It is the obvious
next task, and it is the same shape as the receive-side write Phase 5 pinned: one piece
of work that decides how often this app persists a group, in both directions.
- Durable ingest dedup is taken by MarmotManager, not by MarmotInboundProcessor, so it
needs the client D1 deferred. Phase 3 is where that stopped being hypothetical.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>