Moltaro 0.0.35-beta

Release date: 2026-09-04

This release adds governed object collaboration to Entity records and Board items, keeping messages, mentions, quotes, and linked files with the work they describe. It also makes record consolidation safer when association records overlap and strengthens release-artifact cleanup.

Highlights

• Entity records and Board items now provide one collaboration surface for messages and files, with a permanent desktop panel, responsive detail section, and compact drawer mode.
• A single idempotent Send can publish text, mentions, one flat quote, and multiple prepared files atomically, so partially published collaboration is not exposed to readers.
• Bounded cursor history, direct message anchors, realtime new-content notification, authorized search, and Work Inbox mentions keep long-running conversations navigable without loading an unbounded feed.
• Record merge now remaps or coalesces overlapping association records through the normal governed Entity lifecycle instead of producing duplicate edges or bypassing eligibility and business-invariant checks.

Detailed changes

Object collaboration

• Entity and Board detail surfaces combine messages and attachments while retaining the owning object’s authorization boundary. Preview drawers expose the same experience through a shared Data / Collaboration switch.
• Users can prepare files, compose text, mention colleagues, quote one earlier message, and publish the complete draft with one Send action. Failed or cancelled drafts do not expose deferred files, and uncertain responses can be retried with the same operation key.
• Quotes are flat server-captured snapshots rather than a nested reply tree. Direct links can return to the quoted message, and access revocation or deletion hides content that the current reader may no longer view.
• Messages link to their permitted files and file details link back to related messages without copying file bodies. Attachment details, download routing, focus restoration, narrow layouts, keyboard interaction, and inaccessible context redaction are aligned across desktop and mobile surfaces.
• Collaboration history uses independent bounded windows for messages and files. Refresh and realtime invalidation preserve already loaded pages, signal newer content, and avoid replacing the active projection with stale results.
• Mentions create Work Inbox attention signals that deep-link to the exact authorized Entity or Board message. Realtime traffic carries opaque invalidations; clients re-read the current object through the governed API.

Integration and extension contracts

• The public workspace and Boards APIs add bounded history, counts, direct anchors, composite Send, prepared-file status, cancellation, linked-file relationships, and flat quote projection. History returns 50 entries by default and accepts at most 100 per request.
• Moltaro Package SDK and runtime module packages move to the coordinated 2.0 contract. Comment APIs now expose quoted-message identity and snapshot data plus explicit comment-file relationships instead of hierarchical replies and stored reply counts.
• Existing comments, file descriptors, layouts, notifications, and supported comments/attachments entry links remain available after the upgrade.

Record consolidation and delivery reliability

• Record merge detects self-referential and two-ended association tables, locks the affected rows, remaps the surviving edge, archives duplicates, and reports conflicts without silently discarding association payload.
• Association remaps use the same authorization, Reference Eligibility, Business Invariant, audit, idempotency, and lifecycle paths as ordinary Entity mutations.
• Object-storage release retention treats empty listings and legacy manifests with absent artifact collections as empty, avoiding a false post-acceptance failure while preserving all referenced objects.

Database and upgrade impact

Workspace databases gain atomic collaboration publication state, links between messages and files, flat quote snapshots, and publication provenance for linked files. Existing parent-comment relationships are preserved as quote references; the upgrade does not invent historical quote snapshots or delete existing messages, files, layouts, or notifications. PortalDb has no schema change.

Each Managed App requires normal full-runtime replacement downtime while its recovery point is captured, Workspace migrations are applied, and API, WebApp, Worker, PostgreSQL, RabbitMQ, and Restore Gateway readiness are verified. Rollback after users publish new collaboration data is not lossless through a schema downgrade: restore the verified pre-release Workspace backup together with the previous runtime. Do not manually recreate the former reply hierarchy or edit migration history.

Deployment and operator actions

• Publish this version with full ReplaceRuntime for all production Managed Apps. Do not prepare or apply a delta update.
• Require a recent Available automatic backup for every Managed App before promotion and preserve the pre-release Workspace and PortalDb recovery points until acceptance is complete.
• No new service, port, secret, external dependency, or request-time workspace selector is introduced. Existing file-body Object Storage remains the data path for collaboration attachments.
• Rebuild customer and trusted package source against the coordinated 2.0 Package SDK before deploying code that reads or writes comments.
• After replacement, verify exact target images and component readiness, then confirm an authorized Entity and Board collaboration surface can load its bounded history and that existing comments and files remain visible.

Compatibility and breaking changes

The comment and Package SDK contract intentionally removes hierarchical reply members (ParentCommentId, ParentComment, Replies, and ReplyCount). Use QuotedCommentId, the quoted-message projection and snapshot fields, and explicit comment-file relationships. No compatibility shim is shipped; package source using the removed members must be updated and rebuilt against version 2.0 before it is deployed.

The collaboration API uses bounded cursor windows instead of an unbounded full feed. Clients must follow Before, After, or direct-anchor navigation and must not rely on every historical message being returned in one response. Existing supported comments and attachments deep links remain accepted. There is no intentional authentication, Entity-security, Board-process, or ordinary file-download compatibility change.