Files
giza-kmp/composeApp
Kgothatso NgakoandClaude Opus 5.5 11f2cb2bab feat: the Shares section, with one approval (rotate-shares-single-approval, Phase 6)
Removing the second approval took away the only abandon button a member
who had taken part could reach: it lived on the approval row. A running
rotation is now a card above the members -- the step it is on (dealing,
storing, the group signing the new key state), who it waits on and since
when, and Abandon, behind a confirmation, for any member taking part.
It counts as running until the new generation's key state is signed,
while that signature is open, because the old shares wait on it. A
rotation that ended without completing says why until the next one.

The taking-part row now says what it decides: who is left out and as
what, and that nothing more will be asked. REFRESH_CONFIRM and its
string are gone from the UI state.

ShareRefreshManager.progress reads the step and who is missing from
stored messages. Those are now stored once, on first arrival, in record
and publishOwn: a redelivery rewrote the row and reset the stall clock.

Tests: the row names the withheld; the withheld member sees the rotation
run and cannot abandon it; the waiting-on names at dealing and storing;
the signing step, which nobody abandons; an abandoned rotation says why.
The stall-clock test backdates the messages first, and fails with the
old store-every-time behaviour put back. jvmTest 1250/1250; m3Audit at
its budgets; brand and wallet audits.

Not seen on a device.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-20 01:12:23 +02:00
..