LOCAL TEST: ACCOUNT SESSION COLLECTION

Add current / refresh now captures the signed-in account's .ROBLOSECURITY session cookie into chrome.storage.session. This is a temporary in-memory store, not chrome.storage.local or sync. The manifest requests the cookies permission for the existing Roblox hosts.

Enable Multi-Roblox calls enableMultiRoblox() in multi-controls.js, then collectAccountCookies() in account-sessions.js. The collectedAccountCookies array stays in that background module. Only counts and missing IDs return to the popup. Nothing is displayed, logged, sent, launched or switched by this function.

Previously added profiles have no saved session cookie. Sign in and add each again after updating. Reloading/disabling the extension or restarting the browser clears these temporary cookies; the profile list stays. Roblox logout or session revocation can invalidate a captured cookie before its expiration time. Collection does not validate or revive it.

Removing an account deletes its captured session and clears the collected array. The collected array also clears when the service worker stops; the temporary snapshot store lasts until the browser/extension session ends.

Only the Roblox authentication cookie is captured, not analytics cookies or cookies from other websites. Its value grants access to the account: do not publish it or put it in logs.
