MYCDIC v1.9.37.4 - deployment order

1) Backup website and database.
2) Upload the v1.9.37.4 patch over v1.9.37.3. Preserve server-only private configuration.
3) In phpMyAdmin SELECT THE REAL MYCDIC RUNTIME DATABASE, then import only MYCDIC_v1.9.37.4_RUNTIME_REPAIR_MIGRATION.sql. It has no hardcoded USE statement.
4) Replace Applicant Operations Apps Script with HF5, redeploy the same Web App deployment, run installMYCDICV160284HF5() once, then diagnoseMYCDICV160284HF5().
5) Replace General Notifications Apps Script with V2.4, preserve MYCDIC_NOTIFICATION_SHARED_SECRET, run setupMYCDICNotificationSystem() and authorizeMYCDICNotificationServices(), then redeploy the same Web App deployment.
6) To show system@mycdic.org as the visible From address, add it to the deployment Google account as an authorized Gmail Send-As alias (or deploy under that account). Code alone cannot grant this Workspace permission.
7) Membership Settings: keep PayPal sandbox until an end-to-end test succeeds. Enter real Moroccan/Spanish institutional bank details and enable only accounts you intend to publish to accepted candidates.
8) Test admin login + MFA once. Reopening the private admin entry in the same authenticated browser should return to the dashboard during the 12h absolute / 4h idle session window.
9) Test Interview Operations / Staff & Roles / Practical Tasks / Selection Settings. Recoverable runtime problems should show a diagnostic instead of a blank HTTP 500.
10) Test one application: Google Sheets primary row -> compact SQL recovery -> Practical lifecycle.
11) Test one official reply from Submissions and verify the notification queue/email.
12) Test PayPal sandbox and bank-proof flows before production use.
