How settings are scoped per-button (stored inside the button blob) and per-role (stored in role-specific options), how the cascade resolves conflicts, and the gotchas around blob-shaped per-button storage.

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.

Why mam-main uses FastCron instead of wp-cron.php, how mam_setcron_manager schedules jobs through the FastCron REST API, and the AJAX endpoint mam_setcron_processor that pings on every tick.

How mam-main hands off iOS / Android builds to the WPMAM Fastlane CI: account-code verification, mam_fastlane_settings filter, the publish endpoint, and the fire-and-forget submit pattern.