Moltaro 0.0.55-beta

Release date: 2026-09-09

File verification now starts from committed upload notifications and processes ready work continuously. Tasks adds Worker Profile and Queue selection configuration, while File Protection improves signal history, diagnostics and the clarity of protection and download operations.

Highlights

• Uploaded files can enter verification promptly without waiting for the next periodic check, including files transferred by workspace C# integrations.
• Tasks administrators can manage Worker Profiles, capacity settings, Queue selection policies and published typed C# selector bindings.
• File Protection provides searchable signal and audit history, clearer waiting and download states, and detail dialogs that preserve the parent view.

Detailed changes

File verification and publication

Managed upload completion and explicit publication retry notify the Worker after the database transaction commits. The Worker continues through eligible batches without an idle delay between them. Ordinary file inspection uses the same notification-driven processing behavior.

Persisted upload state and existing leases remain authoritative. Periodic recovery discovers missed notifications and eligible retries; its default interval is now 15 seconds. Explicit installation overrides are preserved. Deferred content still waits for its explicit Send/publication action, and verification remains required before ordinary content becomes available.

Tasks configuration

Worker Profiles provide a mandatory Default and optional specialized profiles. A new specialized profile copies the current Default capacity settings once; later changes to Default do not overwrite that copy. Administrators can edit capacity and warning settings, transfer eligible Workers between profiles in an atomic batch, and return Workers to Default. A specialized profile must be empty before deletion, and Default cannot be deleted.

The Configuration Management role provides common configuration permissions for Task Definitions, Queues and Worker Profiles. Existing workspace mappings for Queue Management migrate to the new role. Runtime roles and Worker membership do not grant configuration authority.

Queue settings expose Any, First, Last and Auto-assignment selection modes, with First as the default. Auto-assignment configuration requires an enabled, published compatible C# Queue selector. A selector can serve several Queues; retired or unavailable bindings remain visible with diagnostics. Invocation settings cover task entry, state change, manual invocation and CRON, including an explicit time zone or inheritance from the workspace.

Developer Studio and package authoring support the typed Queue selector contract. The configuration API and Tasks automation contract expose selection, profile capacity and membership operations with authorization, version checks and idempotent command receipts. This release delivers configuration and selector authoring/publication only: actual Task acquisition, assignment, selector execution, runtime capacity enforcement and selector CRON dispatch are not enabled by these settings.

File Protection operations and history

Source and Agent views show recent signal and audit history, with separate full-height search for older entries. Search supports contextual filtering and server pagination; diagnostic dialogs retain the original query and parent view. Policy/severity filters match the actual signal condition, and historical audit diagnostics use facts captured for that event.

Version, signal and audit details open above the current Source view and return focus to their original action. Nested Escape handling closes only the top dialog. Background refresh preserves equivalent grid rows and action focus. Policy calendars, recipient selection, validation, narrow layouts and copy feedback are also improved.

Manual protection operations reject an offline assigned Agent with an explicit error. Waiting operations expose their current wait reason, and historical run details are read by their exact Source/run identity. Reassigning a Source to its existing Agent leaves the assignment unchanged. Ordinary cancellation accepts an optional comment while retaining authorization and audit records.

Recovery-point views distinguish unavailable, expired and soon-expiring download access. Download admission continues to enforce the retention safety margin and current access permissions.

Database and upgrade impact

Workspace databases change to store Worker Profiles, profile membership and Queue selection configuration. Existing Tasks configuration receives a Default profile and initial Queue selection settings. Known Queue Management role mappings migrate to Configuration Management. PortalDb has no new migration.

Deploy using full runtime replacement, with a service interruption for each application while the target runtime and database changes activate. Keep the pre-release database recovery point and required keys and file-body references. After migration, returning only to older containers is not a supported rollback; restore the matching pre-release database/runtime recovery state.

Referenced backups depend on their retained Object Storage file generations. Release recovery points do not establish an independent disaster-recovery copy or change the installation’s existing backup retention policy.

Deployment and operator actions

• Release mode: ReplaceRuntime. Prepare the exact candidate, validate the complete application fleet, inspect the ready preparation, then promote with its frozen runner. This release does not publish a delta update package.
• Publish Portal, public documentation, agent documentation, both OpenAPI documents and versioned release pages with the same frozen source. Publish and verify Runtime VM agent 0.1.46; no agent protocol change requires a version increment. No customer File Protection Agent reinstall is required.
• Require healthy latest automatic backups and all-application upgrade compatibility before activation. Promotion creates the supported PortalDb and per-application recovery points.
• Let the release workflow own service stop/start. There is no general manual schedule-disable or empty-queue prerequisite. Running trusted C# work may be interrupted; this release does not add automatic replay of uncertain effects.
• After replacement, verify application and Worker readiness, completed migrations, Tasks configuration readiness where the module is configured, and existing File Protection Source/history navigation. Observe a fresh normal integration upload reaching verified/published state through the notification-driven Worker; do not infer a throughput guarantee from generic health endpoints.
• Keep existing customer polling overrides when configured. With the normal defaults, missed notifications use 15-second recovery polling; no manual production configuration patch is required.

Compatibility and breaking changes

• Tasks automation is contract 1.12.0. Integrations must use the current configuration permission keys and Configuration Management role rather than the removed Queue Management contract. Existing supported workspace role associations migrate automatically; external references need updating.
• Queue installation/export now requires format 5, including Selection and Invocation. Older formats and incomplete documents are rejected. Update package-generation inputs; Auto-assignment imports require a compatible selector that has already been published.
• Queue selectors use their dedicated typed contract. Ordinary Run, Action, enqueue and Schedule entry points reject them; publishing a selector does not start runtime execution.
• File Protection API clients should handle the explicit offline-Agent and download-retention errors and the additional history/wait metadata. Ordinary cancellation no longer requires a comment. Agent protocol and protected storage formats are unchanged.
• File Protection audit responses replace raw ConfigurationJson with typed diagnostic, policy and recipient snapshots. Audit queries use event filters rather than current-episode State or FileId. Episode history is ordered by last update; date filtering defaults to Updated. Clients that need the former raised-time window must explicitly select DateField=Raised. Update generated clients against the release’s API reference.