Idea Summary
APEXlang exports one .apx file per page, but import is whole-application only — the documentation states single-page import requires the legacy SQL format, and App Builder cannot import an APEXlang page export at all. This asymmetry means changes are reviewed in Git at page granularity but must be deployed at application granularity.

Use Case
On a ~900-page application, a one-page hotfix requires importing all ~900 pages (full validation plus import runs 30–40+ minutes, and replaces work-in-progress everywhere else in the app). For teams, whole-app import makes concurrent development hazardous: the last import wins for the entire application, so file-based workflows need application-level locking that page-level import would make unnecessary. The SQL format already supports single-page import, proving the granularity is feasible in the engine.

Preferred Solution (Optional)
apex import -input pages/p00042-invoice.apx (and shared-component files), validating the fragment against the target app's current state for dependency/reference integrity, then replacing only the named components. App Builder's Import page should accept APEXlang page exports the same way it accepts SQL page exports today.