Tom Brow be2e31bb70 fix(mobile): recover rejected and lost agent registrations anywhere ...

An HTTP rejection of register-agent is as definite as a rejected status,
so it clears the registering mark and the setup can be discarded. A
registration whose response was lost can be replayed from any
community to learn its identity; finishing still needs the original
community. Publishing or removing a registration now refreshes remote
availability even when the registry's ACTIVE set is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tom Brow <tomb@block.xyz>

2026-10-27 13:08:35 -07:00

..

benchmark

perf(mobile): avoid redundant message list sorting (#7647)

2026-09-15 11:29:54 -07:00

features

fix(mobile): keep ambiguous agent setups recoverable

2026-10-27 12:10:59 -07:00

fixtures/community_icons

feat(mobile): add animated community switcher (#8076)

2026-10-04 14:11:39 +01:00

helpers

fix(mobile): recover rejected and lost agent registrations anywhere

2026-10-27 13:08:35 -07:00

shared

fix(mobile): recover rejected and lost agent registrations anywhere

2026-10-27 13:08:35 -07:00

visual

feat(mobile): show contextual names in channel conversations (#7895)

2026-09-29 15:47:43 -04:00

widget_test.dart

Make mobile onboarding QR-first and synchronize scanner motion (#8599)

2026-10-27 16:32:04 +00:00