Moltaro 0.0.29-beta

Release date: 2026-08-27

This release makes high-volume Board governance predictable, restores core User integrations inside package runtimes, and streamlines Worker association and Entity Security administration in the WebApp.

Highlights

• Board-governed Entity mutations discover locks by configured Board and Entity Definition instead of scanning every affected Board Item, keeping large mutation batches bounded while preserving the same fail-closed governance.
• Package and Net Operation Project invocations can use the supported core User presentation and lifecycle services across functions, data sources, invariants, concurrency strategies, schedules, and resource consumers.
• User administrators can create a Worker from the association dialog, start with editable User-name values, and immediately link the created Worker.
• Work Schedule catalog reconciliation preserves colliding customer Entity Definitions and allocates a separate stable technical name for the system-owned Operational Location, Site, or Worker definition.
• Entity Security previews use the shared resizable drawer experience, and security, Entity Explorer, upload, monitoring, and Blueprint wording is corrected across the supported locales.

Detailed changes

Board governance

• Entity pre-commit governance collapses a mutation batch to distinct Entity Definitions, resolves configured Boards, and acquires at most one shared barrier per Board. Exact governing Board Items are resolved only after the barrier, so activation and configuration races remain protected without lock discovery growing with every Entity instance in a large batch.
• The final runtime retains stable multi-Board lock ordering and the existing security-aware constraint evaluation. This is a performance and scalability correction; it does not weaken Board Statements, status invariants, or mutation authorization.

Package runtime User integrations

• Core User presentation and lifecycle services are attached to each collectible package invocation state instead of being unavailable outside the host runtime. Supported package code can now resolve and manage Users in ordinary function execution, queued and scheduled work, data sources, Business Invariants, concurrency strategies, and resource-event consumers.
• The bridge remains host-owned and invocation-scoped. Package code does not receive host service-provider access or a new authorization bypass.

Workers and Work Schedule catalogs

• Link and Change Worker dialogs offer quick creation through the normal Entity Instance form. FirstName and LastName are prefilled from the User but stay editable; a successful create selects and links the Worker through the existing association operation.
• Canceling creation leaves the association unchanged. If linking fails after creation, the created Worker remains selected so the administrator can correct the problem and retry without creating a duplicate.
• System Entity Definition provisioning now treats SystemKey as identity and the descriptor name as a preferred creation name. A customer definition that already owns Worker, Site, or OperationalLocation is preserved; the system definition receives a free Moltaro... name and later reconciliation continues by stable SystemKey.

Entity Security and localized administration

• Access Policy and Assignment Rule previews use the shared resizable work drawer, synchronized overview/raw sections, fresh singleton reloads, and responsive empty states. Administrators can inspect the governed summary and exact statements without losing the current policy context.
• Entity Security, Entity Explorer, managed-upload, operational-metrics, Blueprint, User, and Work Schedule text is aligned across English, Ukrainian, German, Polish, and Spanish.

Database and upgrade impact

No Workspace or Portal schema migration and no bulk data rewrite are introduced by this release. Each Managed App has ordinary full-replacement downtime while its API, WebApp, Worker, package runtime, and system version are replaced and verified. Existing customer definitions, Board configuration, security policy, and Worker associations remain in place.

Use the normal verified pre-replacement recovery point for rollback. Because this release does not add a schema or data migration, no migration-specific rollback action is required.

Deployment and operator actions

• Publish 0.0.29-beta as a full ReplaceRuntime deployment for all three production Managed Apps. Do not create or apply an update package.
• Preserve the configured external Runtime VM staging volume, Managed App backups, Object Storage bindings, application secrets, and existing Workspace databases.
• Verify the exact target image, Web/API/Worker/RabbitMQ readiness, package runtime compatibility, Board-governed mutation readiness, Work Schedule catalog state, and User-to-Worker administration after replacement.
• No new infrastructure setting, credential, manual data conversion, or customer security migration is required.

Compatibility and breaking changes

No supported API, Package SDK type, persisted schema, or security contract is removed. Integrations that identify system Entity Definitions must continue to use SystemKey; a preferred technical Name is not a stable system identity when a customer definition already owns that name.

The package runtime User-service change is additive. Existing package code that does not use those services is unaffected.