LIKELY REAL ROOT CAUSE of "pages don't load, systems dumbed down, asking for a token" found and fixed -- a bug I introduced myself earlier in this session, not the new login.php screen (which was a real but secondary finding). Several of my own earlier sed commands today used the WRONG replacement pattern: matched only the hex portion of the old token (d60283b1...) but substituted the FULL new token string (including its own "yttcom-admin-" prefix) in its place. Net effect: "yttcom-admin-" + "d60283b1..." became "yttcom-admin-" + "yttcom-admin-3a50115a..." -- a corrupted, double-prefixed token that matches nothing in tokens.json's active[] array. Affected 5 files: backend/sys-com/cmd-popup.js, backend/sys-com/commands.html, backend/tools/ml-editor.html, backend/sys-com/dashboard.html, backend/sys-com/panel.html. My own post-fix verification at the time was flawed -- I checked for substring presence of the new token's hex portion, which was still technically true even with the corrupted double-prefix wrapped around it, so my checks reported false-positive success. This went undetected until now. Found while investigating dashboard.html for the session-login rollout (unrelated task) -- happened to grep the file and saw the literal doubled "yttcom-admin-yttcom-admin-..." string. Immediately checked all 5 files known to have been touched by the same buggy sed pattern, confirmed all 5 corrupted, fixed all 5 (exact string replace of the corrupted value back to the correct new token), re-verified with an exact-match check this time (not just substring), confirmed clean. This is very likely the actual cause of the "systems dumbed down / pages don't load / asking for a token" symptoms USR369 reported -- these are exactly the pages (dashboard, panel, cmd-popup CM button on every page, commands reference, ml-editor) that would show broken/failing behavior with an invalid token baked in, and it happened right around when USR369 started noticing problems.