Skip to content

Document reconnect flow; retire recovery-code from the user guide - #11

Merged
KodeStar merged 1 commit into
mainfrom
docs/reconnect-and-recovery-removal
Jul 11, 2026
Merged

Document reconnect flow; retire recovery-code from the user guide#11
KodeStar merged 1 commit into
mainfrom
docs/reconnect-and-recovery-removal

Conversation

@KodeStar

Copy link
Copy Markdown
Owner

Pairs with audiosilo-frontend#56.

User Guide

  • Removed all self-service recovery-code instructions (account, connecting, troubleshooting, admin invites, api-keys, demo, mobile-apps) - the feature is being retired from the client, so we no longer advertise it.
  • Added the new Reconnect behaviour: a one-tap "Reconnect to <server>" shortcut on the connect screen after signing out, and a "Reconnect" banner when a session is rejected.
  • Reframed "Set a password" as the reliable, durable way back in on any device (especially for pairing-only users), and rewrote the sign-out warning to match the app's actual password nudge.

Developer Docs

  • Server API reference keeps POST/DELETE /auth/recovery, the admin revoke, and has_recovery (the server still does this for older clients) but marks them legacy / slated for removal.
  • Frontend pages updated: /settings password-only nudge, /connect Reconnect shortcuts + ReconnectBanner, src/lib inventory (recoveryknown-servers + auth-failure), and the testing page's helper/test lists.

Gate

npm run build green (no broken links/anchors/images). No page/sidebar entry needed deleting (no page was recovery-only); no screenshot manifest image orphaned (recovery only ever appeared inside the settings shot - its capture hint was updated).

The player now surfaces a one-tap "Reconnect to <server>" flow (a banner
on a rejected session, and pre-filled shortcuts on the connect screen) and
nudges users to set a password as their durable way back in. Document both
in the User Guide, and remove the self-service recovery-code instructions -
the feature is being retired from the client, so we no longer advertise it.

The server still accepts recovery codes for older shipped clients, so the
developer API reference keeps POST/DELETE /auth/recovery and has_recovery
but marks them legacy / slated for removal. Frontend developer pages are
updated to the password nudge + reconnect flow.
@KodeStar
KodeStar merged commit 1c1820c into main Jul 11, 2026
1 check passed
@KodeStar
KodeStar deleted the docs/reconnect-and-recovery-removal branch July 11, 2026 20:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant