chore: npm run serveStagingAccount impl

Author: abose

package.json

@@ -74,6 +74,7 @@
         "_majorVersionBump": "gulp majorVersionBump",
         "serve": "node serve-proxy.js . -p 8000 -c-1",
         "serveLocalAccount": "node serve-proxy.js . -p 8000 -c-1 --localAccount",
+        "serveStagingAccount": "node serve-proxy.js . -p 8000 -c-1 --stagingAccount",
         "_serveWithWebCacheHelp": "echo !!!Make sure to npm run release:dev/stageing/prod before testing the cache!!!",
         "serveWithWebCache": "npm run _releaseWebCache && npm run _serveWithWebCacheHelp && http-server ./dist -p 8000 -c-1",
         "serveExternal": "node serve-proxy.js . -p 8000 -a 0.0.0.0 --log-ip -c-1",

src/services/readme-login-browser-no_dist.md

@@ -100,6 +100,7 @@ For testing with a local account server instance:
 
 1. **Configure Proxy Server:**
    - use `npm run serveLocalAccount` to serve phoenix repo server, instead of using npm run serve command.
+   - use `npm run serveStagingAccount` to use the staging endpoint. To get access to staging server, contact team.
 
 2. **Setup Local Account Server:**
    - Start your local account development stack on `localhost:5000`
@@ -109,10 +110,12 @@ Now just visit login server at `http://localhost:5000` and login. It should work
 at https://localhost:8000/src when you run phoenix code dev server via `npm run serve`. This works without any
 manual cookie copy needed as the dev server sets cookies localhost wide. But if that didnt work, please see
 manual cookie copy instructions below.
+
+For staging server at https://account-stage.phcode.dev , you may need to copy cookie manually like below:
 
 1. **Login and Copy Session:**
-   - Navigate to `http://localhost:5000` in browser
-   - Login with test credentials
+   - Navigate to `http://localhost:5000` in browser. (if staging, use https://account-stage.phcode.dev)
+   - Login with your credentials
    - Copy `session` cookie value from DevTools
 
 2. **Set Cookie in Phoenix App:**

src/services/readme-login-desktop-no_dist.md

@@ -243,22 +243,19 @@ For testing desktop authentication with a local account server:
 
 1. **Configure Proxy Server:**
     - use `npm run serveLocalAccount` to serve phoenix repo server, instead of using npm run serve command.
+    - use `npm run serveStagingAccount` to use the staging endpoint. To get access to staging server, contact team.
 
-2. **Rebuild Application:**
-   ```bash
-   npm run build
-   ```
-
-3. **Start Your Local Account Server:**
-   - Ensure your local account server is running on the configured port (e.g., localhost:5000)
-   - Verify all authentication endpoints are properly configured
+2. **Setup Local Account Server:**
+    - Start your local account development stack on `localhost:5000`
+    - Ensure all login endpoints are properly configured
 
-4. **Test Desktop Authentication:**
-   - Desktop app will now use your local server for all authentication calls
-   - Verification codes and API key resolution will go through your local server
+3. **Test Desktop Authentication:**
+   - Desktop app will now use your local/staging server for all authentication calls
+   - Verification codes and API key resolution will go through your local/staging server
    - Auto-verification will attempt to connect to your local account service
 
-**Note:** Unlike browser testing which requires proxy server configuration, desktop apps simply use the `account_url` directly from config.json.
+**Note:** Like browser testing which requires proxy server configuration, desktop apps also use the proxy server
+for communication with backend.
 
 ## Troubleshooting