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.

How JSON_Cursor_Manager lets the mobile app fetch only changed sections. Per-section timestamps, the ?cursor= request parameter, when reset_cursor() is called, and the bypass_caching flag for cloning admins.

The shape of the JSON payload returned by local_app_get_phone_data: top-level keys, button arrays, content sections, form data, notification list, navigation, and the conventions sibling plugins must follow when injecting their…