Modules, Dependencies, and Update Diagnostics

Step 1: Choose Active Modules
Open Builder settings and review the feature modules. Enable the Builder, commerce, SEO, forms, learning, operations, or other compartments the site actually uses. Disabling an unused module can reduce administration noise and asset work, but never disable a module until you know which pages, shortcodes, templates, and data depend on it.

Step 2: Review Dependency State
Confirm WordPress, PHP, database, active theme, companion theme, addon contracts, and required extensions meet the release requirements. A dependency warning should identify the affected feature and a safe next action. It should not crash the whole site or replace an administrator screen with an unrelated promotion.

Step 3: Verify Update Identity
Record the installed version and immutable build hash, then compare the updater manifest, versioned ZIP, latest alias, downloaded checksum, plugin headers, readme, asset query versions, and runtime diagnostics. All of these should identify the same release before it is promoted from beta to public.

Step 4: Run the Regression Gate
After updating, open and save Builder Studio, test templates, responsive menus, forms, media, search, SEO, commerce, cache bypasses, and fresh logs. Use I.G.O.R. to report one reproducible failure with privacy-safe evidence. Keep the prior immutable package until the new release passes the real site acceptance matrix.
