Skip to content

Core

Runtime catalog boundaries and shell loading performance

0.5.1

Improve App runtime activation boundaries, shell loading behavior, and background refresh performance.

Changed

  • Idle App runtime warming now loads only installed App registration entries. App language catalogs remain deferred until the App is used, reducing background network and parsing work without changing route or widget activation.
  • Prevented repeated notification and task refreshes during App loading, and paused hidden dashboard data requests until the tab is shown again.

Fixed

  • Agent routing now instructs the model to answer in chat by default. Reading data does not imply creating a dashboard or opening a screen.
  • App components in Agent output load their active-language catalogs before rendering, including when the component code is already registered.
  • Dashboard composition requires an explicit delegated Legal Entity when its data source needs one. Missing context returns a request for input; an authorized target is bound to the widget query without bypassing backend permissions.
  • Command Palette search and its Favorites requests wait until the palette opens; Favorites typing is debounced and obsolete list requests are canceled.
  • Data migration run lists pause while their Work Tab is hidden, poll every 3 seconds while processing, and use a 30-second visible discovery interval so newly started runs and terminal completion remain discoverable.
  • Approval and process authoring surfaces activate the language catalogs named by explicit App descriptors before showing App-owned labels.
  • Approval and process widgets activate their explicit owning App runtime and fail closed when that App is unavailable, while preserving Core authorization checks and in-progress form drafts.
  • Cross-App Inspector widgets resolve their owner from navigation resource metadata before activation. Installed owners load their catalog and runtime on demand; uninstalled owners are blocked, activation failures expose Retry, and locale reloads preserve Inspector drafts.

Upgrade notes

Apply the Core and Agent Gateway changes together. Existing saved dashboards without a target are not migrated, and this change does not add a target selector to existing chats.

The Core runtime changes above do not require SDK changes. This release also adopts People 0.4.4 and Procurement 0.3.0-beta.3 for corrected approval permission enforcement and labels for certificate issuance and purchase requests. Run php artisan nexia-access:sync-manifest --all-tenants after updating so every tenant receives the permission definitions. Definition sync does not grant new authority to custom roles: check existing people.certificate.request grants, and explicitly add procurement.purchase_request.submit only to custom roles intended to submit purchase requests.