Moltaro 0.0.32-beta

Release date: 2026-08-29

This release introduces the administrable File Protection module foundation, unifies Entity UI surface management around dependency-aware diagnostics, and prevents terminal batch-upload failures from retaining unusable storage reservations.

Highlights

• File Protection now has a versioned module lifecycle, readiness model, security roles and assignments, administrator workspace, and supported read-only .NET automation status contract. This foundation does not yet create repositories, schedules, recovery points, or protected file copies.
• Entity Definition administration presents table, card, and form surfaces in one searchable registry. Cross-entity and reusable dependencies are resolved from one server snapshot, while missing targets are shown as actionable, non-interactive warnings.
• File Protection and Work Schedule role mappings use guided association workflows that explain access level, scope, and effective permissions before an administrator applies a change.
• Terminal failures in parallel attachment uploads abort their physical attempts and release reserved capacity; retryable failures retain their resumable upload state.

Detailed changes

File Protection foundation

• The optional File Protection module can be enabled, disabled, inspected, and repaired through its administration API and workspace administration page. Readiness is computed from the installed manifest, module settings, preset mappings, and current role associations rather than a manually maintained status flag.
• The delivered security manifest separates administrator, operator, recovery operator, recovery approver, and auditor responsibilities. The guided UI assigns workspace roles to those internal roles and shows the resulting permission intersection in administrator language.
• The new Moltaro.Package.NET.FileProtection SDK surface exposes lifecycle, capability, configuration-state, and safe blocker diagnostics to supported API-hosted Action, Command, and HTTP endpoint functions. It does not expose repository secrets, paths, files, runs, or restore operations.
• This release is the FP-01 foundation only. No customer file becomes protected merely by enabling the module; repository provisioning, sources, schedules, backup execution, recovery points, and restore remain later delivery stages.

Entity UI surface administration

• Runtime and reusable Entity UI surfaces are consolidated into one searchable dependency registry with consistent table, card, and form rows.
• The registry resolves host/default relationships, cross-entity selectors, reusable surfaces, and case-normalized keys from one authoritative backend dependency graph. Missing or incompatible targets remain visible without offering an unsafe navigation action.
• Field-driven table, card, and form generation remains available from a compact Create action. Existing deep links continue to open the appropriate surface editor or host configuration drawer.

Module security administration

• Work Schedule and File Protection mappings now use a shared guided flow for choosing a workspace role, module role, supported scope, and permission review before save.
• Mapping tables use the common grid interaction model, place destructive row actions at the end, hide configuration navigation while a module is disabled, and avoid showing transient settings content during initial loading.
• All new module and surface administration copy is available in English, Ukrainian, German, Polish, and Spanish.

Runtime reliability

• Non-retryable failures after a batch upload session has been created now abort that physical attempt before returning the item result and release its storage reservation. Interrupted cleanup retains a stable recovery claim so administration can finish it without terminating unrelated sibling uploads.
• Retryable upload failures remain resumable, preserving the existing idempotency and retry contract.
• Record-matching full scans execute authorization and result reads within the captured Unified Security transaction boundary, preventing a scan from publishing or returning results against a stale actor or policy snapshot.
• Runtime VM host-policy scripts are normalized before remote execution so source checkout line endings cannot break Linux log-retention convergence.

Database and upgrade impact

This release adds Workspace schema state for the File Protection module foundation and its workspace-role associations. No existing customer records, files, security assignments, or backup artifacts are rewritten. PortalDb has no schema change.

Each Managed App has ordinary full-runtime replacement downtime while its recovery point is captured, the Workspace migration is applied, and API, WebApp, Worker, and broker readiness are verified. Rollback must use the verified pre-release recovery point with the previous runtime; operators must not remove the new schema objects manually.

Deployment and operator actions

• Publish 0.0.32-beta using full ReplaceRuntime for every production Managed App. Do not prepare or apply a delta update.
• Preserve the attached Runtime VM staging volume, automatic Managed App backups, Object Storage bindings, application secrets, and Workspace databases. The latest automatic backup attempt for every running application must be Available before production mutation.
• After replacement, verify exact target images, API/WebApp/Worker/RabbitMQ readiness, Runtime VM agent 0.1.43, empty active operation queues, and bounded release/Docker retention.
• Verify that File Protection administration loads without enabling protection implicitly, Entity UI surface dependencies resolve in the unified registry, and existing Work Schedule security mappings remain readable.
• No new credential, provider account, protection repository, or customer configuration is required for this foundation release.

Compatibility and breaking changes

No known breaking API or persisted-data change is introduced. The Moltaro.Package.NET.FileProtection assembly and its read-only automation status interface are additive. Existing applications that do not enable File Protection retain their current behavior.

Batch-upload callers may now observe that a non-retryable item failure has already released its upload reservation instead of leaving a resumable attempt. Retryable failures retain the previous resumable behavior. Entity UI deep links remain supported, although administration now opens them through the unified surface registry.