r-zakarya
683655415f
Reported as "the token field saves nothing", and it was exact: LockVault called PushConfig, which pushes the STORED server settings back into the page. Every lock therefore overwrote a freshly typed token with the old one - including the three-minute auto-lock, so it happened with no gesture from the user at all, and the field looked like it forgot on its own. The user's own sequence isolated it: deleting one character gave a 401, which proves the typed value does reach the wire; then open, lock, sync gave a 200 again, the lock having restored the old token in between. PushConfig now runs at startup only. It was pointless in the other four places anyway: PM.wipe clears the list and the detail, never the configuration fields. Along the way, and part of the same confusion: the three settings fields had no labels, only placeholders that vanish once filled - and since the token was masked this morning it became indistinguishable from the sync password sitting right below it. They are labelled now, and the log reports both fingerprints so a value landing in the neighbouring field shows up immediately. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
