MOON v5.0.4 — COMPLETE FIRST UPLOAD — build 5.0.4-patch2 November 1, 2026. Companion remains MOON Skin Lab v5.0.2. READY FOR A DIRECT DREAMWEAVER / FTP MERGE The Website-Folders ZIP now includes the required public company configuration and tenant JSON, prepared from the current public deployment files. You do not need to run Python, assemble company files or edit JSON for this first upload. 1. Extract MOON-v5.0.4-Website-Folders.zip. 2. Open its UPLOAD-TO-WEBSITE-ROOT folder. 3. Upload that folder's CONTENTS into the existing massie.online website root. Merge/overwrite the supplied files; do not delete remote files or use a synchronization option that removes files absent from this package. 4. Open /temp-index.html and hard-refresh with Ctrl+Shift+R. 5. Check the new links and use Acceptance-Matrix.txt before changing the main launch page. The package does not contain a replacement root index.html. CONTENTS TO UPLOAD temp-index.html Temporary portal using the new addresses legal.html Old root link forwards to MassieOnline/legal.html privacy.html Old root link forwards to MassieOnline/privacy.html moon-service.html Old root link forwards to the migrated service page MassieOnline/ Complete compatibility Beta app, service/policy pages, docs and 9 skins / 3 process styles / 3 keypad styles MOONbase/BETA/ New Beta deployment with its public company JSON MOONbase/MWGCCM/ New stable MWG/CCM deployment with its own JSON MOONbase/MILLTECH/ New MillTech deployment with its own JSON MOONbase/DEMO/index.html Clearly marked unconfigured demo landing page MassieOnline/index.html remains a working Beta login during this first rollout. Its application assets are retained because they also support the current root portal. Removing old application files comes AFTER you test the new addresses. Do not delete /MOON/MWGCCM/ or /MOON/MILLTECH/ during this upload. COMPANY CONFIGURATION IS INCLUDED THIS TIME BETA and MWGCCM keep the SAME project-moon-1e6d3 database and backend. MillTech keeps moon-milltech. Company identity, calendar, provisioning and Firebase values are retained from each current public config. New company configs change applicationPath and add the staging portal/navigation paths. company/config.json remains authoritative; company/tenant.json is its matching reference snapshot. New application logins return to temp-index.html for testing. Do not enable provisioning or reconnect Drive merely because the URL moved. FUTURE UPDATES Later routine application updates should omit each deployment's company/ folder, its unique config/tenant files, docs and custom company assets. Preserve approved customer catalogs. This full package is specifically for the first folder setup. Do not repeatedly overwrite customer configuration from this initial snapshot. STYLE LIBRARIES MassieOnline/libraries.html provides links to every style and library index: 9 skins: Classic, Copper Shop, Steel Blue, 90's Neon, Solo Cup Jazz Print, Postal Service, VHS Rewind, MillTech Ag and Dinosaur Truck. 3 process styles: Industrial Console, Digital Signal, Spreadsheet Fill. 3 PIN keypads: Industrial Console, Digital HMI, MOON Classic. New deployments retain released local copies of their approved catalogs. Beta has all 9 skins; MWG/CCM retains its 7 common skins; MillTech retains its 8. Updating the central master library does not silently change stable customers. PIN keypads are now actual manifest JSON presets read by Employee Station and its settings selector, with the original three presets as a fallback. Opening a library JSON file does not write settings. The Skin Lab companion is unchanged. LEGAL / PRIVACY / CUSTOMER SERVICE The existing policy text and service UI now live inside MassieOnline/. The root forwarding files preserve older links. Service email-link sign-in returns to the migrated page and accepts older root service links for compatibility. The temporary portal and migrated service console inspect MOONbase deployments. The unchanged current root index continues using the older company addresses. BACKUP AND RESTORE Owner -> Settings -> immediately below Diagnostics and Advanced Settings. This is the requested interface example. Schedule review, history and export, import or recovery plans do not run database operations or create schedules. No new backup functions or Firestore permissions are installed by this build. BACKEND / DATA If each company backend is already on v5.0.3, no Cloud Shell commands are needed. Backend source, Firestore rules and dependency locks are unchanged from v5.0.3. The new and old website copies share each company's REAL data: ordinary edits in one also appear in the other. No database migration accompanies this move. No live upload has been performed by ChatGPT. Validation uses synthetic Firebase/Drive/weather responses; complete your live sign-in, Drive and TV checks. After testing, review screenshots and remove unused historical files separately.