Support completing first-run setup after session restoration
This commit is contained in:
@@ -20,6 +20,11 @@ failures do not invalidate a successfully verified session.
|
||||
Restored sessions retain the server's mandatory credential-replacement state.
|
||||
An omitted replacement flag is treated conservatively as requiring setup rather
|
||||
than silently allowing the dashboard to consider setup complete.
|
||||
Dashboard loading and realtime connection wait until credential setup is complete;
|
||||
the server independently enforces the same operational-access restriction.
|
||||
The setup form includes a current-password field because restored keyring
|
||||
sessions intentionally do not restore the user's password. This lets setup
|
||||
continue after a client restart without storing the password on disk.
|
||||
|
||||
Run `node --test src/session-recovery.test.js` for response classification and
|
||||
retry-schedule coverage. This is not a substitute for native AppImage acceptance.
|
||||
|
||||
Reference in New Issue
Block a user