Runtime and adoption

Core uses the published PHP and React SDK 0.7.1 artifacts in both execution modes. Existing Composer App versions and references, including People 0.5.8, remain unchanged.
Set NEXIA_APP_RUNTIME=composer for embedded released Apps, or sandbox for isolated App execution. Sandbox enables native runtime and developer hosting together; retire DEVELOPER_SANDBOX_HOST and DEVELOPER_NATIVE_RUNTIME_ENABLED.
Install the matching committed Composer profile in a fresh release directory. Sandbox uses composer.sandbox.json and its lock, rejects embedded business Apps, and obtains App catalogs from isolated runtimes. Rebuild configuration caches and restart workers after changing mode.
Standard Runtime declarations, catalog digests, request-bound host capabilities, replayable write receipts, and explicit recovery protect isolated App operations. Unsupported contracts fail closed. Adopt matching Sandbox Manager and operator runtime versions before using new isolated capabilities.
Apply Central and tenant migrations, including App migration integrity, initialization history, and runtime host-write records. Preserve existing App data and migration history; no database reset is required. Inspect unresolved partial writes instead of treating them as rolled back.

Developer and Agent workflows

App submissions use connected GitHub repositories and immutable tags, isolated preparation/review, and explicit publication and installation steps. Sandbox lifecycle and developer identity are isolated from production.
Agent tools support runtime-authorized App actions and widgets, current-form save reconciliation, write outcome inspection, and private artifact assessment. Deploy compatible Core/frontend first, then Gateway and AWS Edge; these are separate rollouts.
Resource generation follows the SDK contract/queries/ListSurface/RecordSurface layout. Existing split forms require explicit migration before regeneration, and custom Inspectors are preserved. Existing schema APIs remain compatible.

Export approval case lists and details as Excel while retaining existing access checks.
Improve saved-dashboard reuse, report discovery, Agent operation policy, and draft-state handling.
Preserve catalog digests through PostgreSQL storage and remove duplicate server translation keys that prevented screen loading.

Remove the legacy main-push Laravel Cloud deployment workflow. Main promotion does not invoke that deployment hook or create a Core tag automatically; release tagging and AWS deployment are explicit operator steps.
Production and Developer retain separate runtime modes, credentials, storage, and ECS services. Keep the previous release and task definitions for rollback, and evaluate migration compatibility before reverting code.