MPC v6.82.190 cPanel-safe staging deployment

TARGET
  Folder: /home/marljsei/staging.marlothparkcentral.com
  URL:    https://staging.marlothparkcentral.com
  Node:   20.20.2

IMPORTANT
  This release does not package or overwrite cPanel's .htaccess Passenger block.
  CloudLinux must own PassengerAppRoot, PassengerNodejs and the node_modules symlink.
  Do not delete the existing .htaccess or node_modules symlink when replacing files.

1. In cPanel File Manager, open:
     /home/marljsei/staging.marlothparkcentral.com

   Delete the previous application files, but KEEP:
     .htaccess
     node_modules  (CloudLinux-managed symlink)
     tmp/           (optional)

   Do not delete:
     /home/marljsei/mpc-runtime-staging

2. Upload the release ZIP to /home/marljsei and extract it there.
   The archive contains the top-level folder:
     staging.marlothparkcentral.com

3. In cPanel > Setup Node.js App, confirm:
     Node.js version: 20.20.2
     Application mode: Production
     Application root: staging.marlothparkcentral.com
     Application URL: staging.marlothparkcentral.com
     Startup file: server.js

   Required environment values:
     APP_ENV=staging
     SITE_URL=https://staging.marlothparkcentral.com
     NEXT_PUBLIC_SITE_URL=https://staging.marlothparkcentral.com
     MPC_RUNTIME_ROOT=/home/marljsei/mpc-runtime-staging
     MPC_ADMIN_PASSWORD=<strong staging-only password>

4. In cPanel Terminal run exactly:
     source /home/marljsei/nodevenv/staging.marlothparkcentral.com/20/bin/activate
     cd /home/marljsei/staging.marlothparkcentral.com
     bash scripts/deploy-cpanel-staging.sh

5. Verify:
     cd /home/marljsei/staging.marlothparkcentral.com
     bash scripts/verify-live-staging.sh https://staging.marlothparkcentral.com 6.82.190

CPANEL RED "ERROR" RECOVERY
  The red cPanel toast is generated by CloudLinux before the application code starts.
  If SAVE still returns only "Error":

  A. Do not run npm start, next start or another daemon from "Run JS Script".
  B. Use DESTROY to remove only the Node.js application registration. Do not delete
     the application folder or /home/marljsei/mpc-runtime-staging.
  C. Wait 60 seconds, then recreate the app with the settings in step 3.
  D. Run step 4 from Terminal.

  If DESTROY also fails, the hosting administrator must clear the stale CloudLinux
  application lock/process. That is a hosting-control-plane fault, not an application
  package fault.

EXPECTED RESULT
  /healthz returns 200 and environment=staging
  /readyz returns 200 after startup
  /api/build-info reports buildVersion=6.82.190
  all staging responses include noindex/nofollow
  robots.txt contains Disallow: /
  public routes, assets and downloads return their intended 200/redirect responses