Moltaro 0.0.19-beta

Release date: 2026-08-14

This release adds actor-safe Reference defaults, contextual Entity UI routing, durable Net Operation Project publication diagnostics, extension-aware file policies, and more predictable responsive Card layouts for workspace users, administrators, operators, and package developers.

Highlights

• Scalar Reference fields can use a workspace-local default record while preserving authorization, eligibility, integrity, and explicit user choices.
• Entity Definitions can expose multiple keyed list, details, and drawer hosts, and menus or Reference navigation can target the intended surface directly.
• Failed Net Operation Project publications retain a safe, correlated diagnosis and remediation guidance instead of leaving operators with an opaque failure.
• Workspace file policy now validates a filename extension and declared MIME type as one configured pair and exposes the authoritative rules to trusted package code.
• Entity Cards size fields uniformly from the available container and declared column span, without renderer-specific full-row surprises.

Detailed changes

Reference defaults

• Administrators and package authors can assign one Scalar Reference default by record identity. Create forms show the actor-shaped number and display name through the existing Reference picker experience.
• The default is applied only to a new root or child record when the caller did not supply a value. An explicit replacement or explicit null wins, and existing records are neither edited nor backfilled.
• Definition updates, imports, previews, and final saves verify that the target belongs to the configured Entity Definition and remains active, visible, eligible, and valid for the current actor. An unavailable target is shown as unavailable rather than leaking protected record information.

Contextual Entity UI navigation and Card layout

• An Entity Definition can own multiple keyed Entity List Page, Details Page, and Drawer hosts while retaining its system hosts. Role-aware selectors choose the appropriate surface for the current actor and context.
• Runtime menu items can target a keyed list host. Reference navigation can open a configured Details Page or Drawer and select a keyed target; module Resource Catalog routing continues to take precedence for module-owned destinations.
• Entity Definition YAML version 7 carries keyed hosts, selector lists, Reference open targets, and portable back targets. Board back targets use the Board key so they can be restored after the Board resource is applied.
• Responsive Entity Cards now derive their grid from the container width and honor only the configured one-to-three-column span. Text, Markdown, collection, and other renderers no longer force an unexpected full-width row.

Net Operation Project publication operations

• Each publication build now has durable correlation plus a sanitized failure reason, category, retryability flag, target, remediation, and bounded SQLSTATE when applicable. Raw SQL, stack traces, credentials, and provider secrets are not published through these diagnostics.
• Publication failure evidence, audit state, and the durable failure counter are committed together. Ambiguous commit outcomes fail closed, and capacity, transient database, serialization, and permanent failures receive distinct operator guidance.
• Administrators can inspect the same safe evidence from Function Operations, while authors can drill from Studio into the correlated failed build.

File type policy and Package SDK

• Owners and administrators can configure ordered file rules containing allowed extensions and their declared MIME types. Moltaro selects the longest matching extension and accepts an upload only when that extension and MIME type occur in the same rule.
• The rule set is non-empty, bounded, normalized, and protected by optimistic concurrency. It applies consistently to API, WebApp, trusted Package SDK, and direct-database attachment upload paths.
• GetUploadCapabilitiesAsync().FileTypeRules is now the authoritative package contract. AllowedMimeTypes remains a deprecated conservative projection for older clients and must not be used to decide whether a filename is accepted.
• File policy governs declared format pairs; it is not malware inspection. Administrators remain responsible for the formats they intentionally allow.

Database and upgrade impact

The Workspace schema changes add contextual Entity UI routing metadata, nullable Net Operation Project publication diagnostics and durable counters, plus versioned file type rules. Portal has no schema change. No customer record, attachment body, or business value is bulk-rewritten. Existing UI hosts remain usable, existing Reference fields are not backfilled, and existing file settings are normalized into the current rule contract during initialization.

Deployctl creates a database recovery point and managed object-storage backup for each Managed App before its Workspace upgrade. Expect ordinary sequential full-replacement downtime for each app; Portal, documentation, StorageSigner, the base runtime, and the Runtime VM agent are published in the same release workflow.

Rollback must use the complete matching pre-release recovery points. Do not downgrade only containers or manually remove schema history: restore the Workspace database, managed object storage, runtime, and configuration together. An older runtime that cannot preserve the active file policy may reject formats conservatively; it must not broaden upload acceptance.

Deployment and operator actions

• Publish 0.0.19-beta with production ReplaceRuntime for all three Managed Apps. Do not prepare or apply a delta update package.
• Publish Portal, StorageSigner, regenerated public documentation, the base runtime package, and Runtime VM agent 0.1.40, then replace each Managed App sequentially from its generated recovery points.
• Avoid Entity UI host configuration, Net Operation Project publication, and file policy changes while the affected app is being replaced. Resume them after API and Worker health checks pass and both report the new version.
• No new environment variable, credential, storage bucket, signer policy, DNS record, Portal setting, or agent configuration is required.
• After each replacement, verify migration/model parity, API/WebApp/Worker and RabbitMQ health, exact runtime version, package/project build state, managed file access, publication diagnostics, and absence of migration, unsupported contract, authorization, or repeated-restart errors.

Compatibility and breaking changes

The trusted .NET package gateway remains contract version 10, Net Operation Project remains 7, and Workspace UI host remains 1; existing compatible artifacts do not require a mandatory rebuild solely for this release. Runtime HTTP additions are backward-compatible for clients that ignore new properties. No Runtime VM agent protocol change is included; the agent remains 0.1.40.

Upload integrations must send a filename whose allowed extension matches its declared MIME type and should migrate capability checks from the deprecated AllowedMimeTypes projection to FileTypeRules. A previously MIME-only upload can now be rejected when no configured rule contains the matching extension and MIME pair. Packages that want to consume the new rule model must rebuild against the delivered SDK.

New Entity UI routing exports use YAML version 7. Automation that authors v7 host definitions must use keyed hosts and selector lists; the removed legacy host FormSelectors shape is rejected rather than silently translated. Existing applied records and system hosts remain available.