The AJAX entry point for the mobile API. Frozen public contract: action name local_app_get_phone_data plus the modern alias mam_get_phone_data. Both delegate to MAM_Phone_Data_Pipeline::run().

How mam-main is organized: 22 subsystems, 4-phase phone-data pipeline, notification dispatcher, settings cascade, and the cross-cutting infrastructure (MAM_Current_Request, MAM_Account_Code_Manager, MAM_Migration_Tasks, repositories) that every feature relies on.

How button definitions are persisted: serialized arrays in the local-app-button-array* options. Why the option key is frozen, the per-role variants, and the implications for renames or schema changes.

mam_codex_manager — the settings inspection / discovery API. Lets admin tooling enumerate all registered settings, categories, and content-class field schemas without parsing PHP source.

Reusable UI section builders that content classes assemble into per-screen output. 15 filters covering add-to-cart, featured-image, social-media, chat config, order details, and more. Loaded from includes/content-class-elements/general-elements.php.