/**
 * Warehouse-app screen patterns — how to CREATE and MODIFY one screen of a
 * mobile device flow, in whichever of the two frameworks owns it.
 *
 * Grounded in Microsoft's own developer documentation for the process guide
 * framework (dynamics365/supply-chain/supply-chain-dev/process-guide-framework)
 * and for the app's step identity (warehousing/step-icons-titles), so the class
 * names, attributes and method names below are the documented ones rather than
 * recalled ones. Every AOT name is still worth confirming with
 * get_object_info against the installed version before it is written: the
 * catalog says WHAT to build, the index says whether this deployment has it.
 *
 * The skeletons are gated: tests/knowledge/mobileAppPatternCatalog.test.ts runs
 * every one through the same offline best-practice validator that backs
 * validate_code(mode="syntax"), because a template that emits BP-failing X++ is
 * worse than no template (docs/KNOWLEDGE_AUTHORING.md §4).
 */
import type { MobileAppPatternSpec } from './types.js';
export declare const MOBILE_APP_PATTERN_CATALOG: MobileAppPatternSpec[];
//# sourceMappingURL=catalog.d.ts.map