Skip to content

Core

Generic Agent resource operations

0.4.0

Discover and execute Resource operations through shared tools with preserved authorization.

Agent tools from Resource contracts

Changed

  • Replace per-Resource App tool registrations with the fixed generic data tools. Discovery exposes declared create/update payloads and domain action routes, permissions, effects, and business descriptions. data.catalog supports cursor traversal; data.detail reads the App detail DTO and data.preview invokes read-only evaluators.

  • Consolidate Report and Process discovery/operations while retaining operation-specific authorization and confirmation policies. Dashboard draft composition uses one tool. Internal transports and duplicate widget tools are removed from the model menu.

  • App navigation can return business guide summaries and retrieve one guide's steps. The tenant Settings navigation no longer shows Agent Tools; usage, limits, and operational records remain available.

  • Use shared controls for Data Center selection and organization import previews, and add a live NxSpreadsheetEditor example for App developers.

Upgrade required

This is a breaking Agent tool contract release. Adopt SDK 0.4.0 and the exact coordinated App tags in composer.lock. The converted Apps require Core 0.4.0; install them with this Core release. Existing Resource operation policy keys retain their meaning. Callers must use the canonical generic, Report, Process, and Dashboard tool contracts; removed model tool names have no aliases.

Deploy Core with the coordinated package lock before starting the matching Gateway. The existing production workflow waits for the new Core release before updating Gateway. Resource APIs, authorization, usage accounting, limits, and operational records remain in place. No data migration is introduced by this conversion.

All bundled Apps now declare Core 0.4.0 and SDK 0.4.0 explicitly. App frontend peers must equal the installed SDK version; newly generated Apps use the same contract. Update composition DTO imports to Nexia\Laravel\ResourceComposition\AuthorizedCompositionQuery and Nexia\Laravel\ResourceComposition\CompositionQueryContext. Previous namespaces are removed.

For ordinary local development, the Core development alias is compared with its release-train baseline during App checks; its Composer identity remains a development branch. Published Core versions still obey the exact App requirement. The selected local SDK overlay uses its package.json version so exact SDK dependencies resolve without older-version fallbacks.