Moltaro 0.0.52-beta

Release date: 2026-09-09

File Protection gains configurable source and agent signals with explicit recipients and working-time thresholds. Work Inbox retains completed signal episodes, while Task Queues gain editable limits and warning settings for their configuration.

Highlights

• Configure independent File Protection conditions, severity, recipients and counted-time calendars.
• Monitor file modification metadata separately from backup transfers; inspect and accept a stale-file episode without claiming that the file became fresh.
• Browse Active, Completed and All signals in Work Inbox, including exact read-only historical episodes.
• Configure Queue execution/postponement limits, warning thresholds and dispatcher exception settings.

Detailed changes

File Protection policies and diagnostics

Source policies cover failed protection, lack of progress, missed scheduled protection, unavailable recovery copies and individual files that have not changed. Agent availability is configured on the Agent. Conditions remain independent; escalation changes the existing episode. Recipients are explicitly selected from workspace roles and responsibility groups for each rule and severity, and must retain the required access. Administrators are not subscribed implicitly.

Duration rules count actual time inside configured weekday/time windows in the workspace time zone. File observations use stable modification time and size, not repeated downloads or full-file hashing. Missing, unreadable, unstable and unobserved files remain distinct diagnostic states. An unchanged heartbeat or backup does not make an old file fresh.

Authorized operators can accept a File not updated episode for all its recipients until the next confirmed update of that file. Actor, time and an optional comment are recorded. This is separate from personal Inbox archive or snooze and does not certify backup contents or business-data correctness.

Sources, Agents and their detail/preview surfaces show signal summaries, configuration, filtered history and actionable diagnostics. File-name lookups respect protected-content permissions. The changed interface supports English, Ukrainian, Polish, German and Spanish.

Queued protection reports why it is waiting for its Agent, Source, repository or authorization. Temporary authorization configuration problems use the bounded retry window, and exhausted attempts retain the relevant failure cause. Protection repository validation also uses stable database timestamp precision.

Durable Work Inbox history

Active remains the default view; Completed and All include separate historical episodes with stable deep links and read-only previews. History is visible only to its recorded audience while the user retains current access. Recipients addressed earlier in an episode remain part of its historical audience even after severity routing changes. Historical delivery never grants resource access.

Resolution and recurrence update the Inbox and active count across open tabs. Personal archive/snooze does not resolve the underlying problem. Unknown old creation dates or resolution actors are not invented, and a replaced condition is not presented as confirmed recovery.

Task Queue configuration

Queue details and previews expose maximum concurrent execution, maximum postponed tasks, WIP/paused/blocked warning thresholds and dispatcher exception settings. Authorized configurators can edit these settings with row-version and idempotent-operation protection; dispatcher membership alone does not grant configuration access.

A missing hard maximum means unlimited; a hard maximum of zero means no increase. Warning zero means disabled, and warnings use strictly greater-than thresholds. Defaults preserve unlimited maxima, disabled warnings and disabled exceptions. This release delivers configuration and deterministic policy contracts, not live task counters, persisted runtime enforcement, warning delivery, Worker Profiles or automatic assignment.

Installation and monitoring fixes

Installation-package operations resolve the configured installation content and data-protection key roots. Metrics requests avoid unrelated request-workspace initialization. These fixes do not change workspace identity or introduce request-time database selection.

Database and upgrade impact

Workspace databases change during the full runtime replacement. Allow a short service interruption for each installation and retain the verified pre-upgrade database and associated storage/key recovery material. PortalDb has no new schema migration in this release.

Existing File Protection notifications and active legacy signals are archived as replaced, preserving recorded audit facts. New policies are disabled and recipient lists are empty after upgrade; configure both explicitly to enable the new monitoring. Existing backup contents, retention and recovery access are not reformatted or deleted. Existing module enablement is preserved.

Do not roll back by starting the previous runtime against the upgraded schema. Recovery restores the verified pre-upgrade database together with its matching runtime and necessary storage/key state. In particular, reversing schema alone does not undo legacy signal archival or reconstruct discarded audience facts.

Deployment and operator actions

• Release mode: ReplaceRuntime. Publish Portal/documentation, the versioned Runtime VM agent bundle and the complete runtime; replace every in-scope Managed App sequentially. No delta update package is published.
• Use the supported two-phase preparation and frozen-runner promotion. Check every application against the target package before downtime, then create recovery points and activate prepared artifacts.
• Preserve existing module enablement, scheduled work, application ownership, placement and Object Storage bindings. Drain active customer work naturally before its replacement and restore the captured schedule configuration after health acceptance; do not cancel jobs or replay business work for this release.
• Install the matching File Protection Agent package on customer Windows/Linux machines before resuming their protection work. Updating Managed App runtimes does not install or update that external client automatically.
• Configure new signal recipients and Source/Agent policies when ready to use them. Do not enable modules or create policies merely to validate deployment.

Compatibility and breaking changes

• External File Protection Agents require protocol 3.0 (Agent CLI 3.0.0). Older protocols are rejected with fileProtection.agent.updateRequired. File Protection Agent is distinct from the Runtime VM agent bundle 0.1.46.
• Signal collection reads use GET /api/workspace/attention-signals with state 0 (Active), 1 (Resolved) or 2 (All), replacing the former /active collection route. Exact history reads use GET /api/workspace/attention-signals/history/{historyId}. Update integrations that called the removed route; historical entries are read-only.
• Tasks contract is 1.10.0. Queue installation/export format 4 requires the complete limits block, including explicit nullable maxima. Earlier Queue document formats are rejected; regenerate documents with the current tools.
• File Protection no longer emits its former implicit notification stream. Configure the new explicit signal policies and recipients instead.