Moltaro 0.0.13-beta

Release date: 2026-08-09

This release strengthens governed Board workflows and historical reconciliation, makes grid and picker working state durable, improves Entity drawers and assignment visibility, exposes safer managed-upload contracts, and bounds Net Operation Project source processing with explicit limits and retryable errors.

Highlights

• Board transitions can require a configured number of linked items on another Board before an item may move, with the rule enforced consistently by the administration API, Runtime API, Package SDK, and WebApp.
• Trusted Net Operation Project automation can reconcile data and tags on terminal historically imported Board items without reopening them or weakening ordinary terminal-item mutation rules.
• Data Explorer, shared grids, and Reference pickers retain per-user filters, ordered sorting, quick filters, and hierarchy state across navigation and reload, while recovering safely from obsolete stored state.
• Entity details and preview drawers restore automatic Assignments surfaces, use a consistent responsive toolbar, and present adaptive section labels and caption groups more predictably.
• Attachment clients can query the effective upload policy before creating a session, and agent-facing documentation now exposes resumable FileSystem upload endpoints and version-specific release context.
• Net Operation Project diagnostics and manual edits have bounded concurrency, processing deadlines, exact source-size limits, and structured retryable errors instead of allowing unbounded Roslyn work or project-lock waits.

Detailed changes

Boards and historical automation

• A transition may define link prerequisites by link type, direction, target Board, target definition, minimum count, and optional maximum count. Invalid ranges and duplicate scopes are rejected, and runtime create/move paths evaluate the same package-owned rule before committing a status change.
• The Board administration dialogs, localized validation, API models, Package SDK schema, runtime package services, and public documentation expose the same prerequisite contract.
• ReconcileHistoricalItemDataAsync updates only Subject, Description, and Board-owned Part fields for terminal items with historical import identity. Each item uses optimistic concurrency, exact replay is write-free, and the operation preserves status, target, rank, lifecycle history, and completion.
• ReconcileHistoricalItemTagsAsync adds tags or replaces an explicitly managed tag set on terminal historical items. It preserves manual and unrelated tags, commits each owner independently, returns structured per-item outcomes, and never changes the Board item row version or lifecycle.
• Tag authorization now distinguishes Entity and Board tag settings, terminal historical-operation requirements, permission denial, and unknown owners through safe correlated error responses and stable SDK error codes.

Data Explorer, grids, pickers, and drawers

• Entity List filters and ordered sorting persist per actor and grid context. Shared administrative grids use the same local-state contract, while Reference pickers maintain an independent state scope and recover when saved columns, filters, or hierarchy nodes are no longer valid.
• Reference pickers reuse the shared Quick Filter Bar and preserve table/tree sorting semantics. Parent trees now honor configured default table sorting.
• Entity details and preview drawers automatically include Assignments when a configured layout omits that host-owned surface. Drawer toolbars, responsive action collapse, selected section labels, caption groups, and drag-and-drop section ordering now use the shared presentation contract.

Files, attachments, and integration contracts

• Attachment and Package SDK clients can preflight the effective storage type, maximum body size, checksum requirement, and MIME policy before opening a managed upload session.
• Pre-session failures keep stable error codes. Non-seekable streams, idempotent completion retries, checksum read-back, and managed S3 Entity File uploads use the same effective upload policy.
• The public integration OpenAPI profile now includes resumable FileSystem upload-session endpoints. Downloaded agent guides point agents to the release notes for the installed documentation version before workspace work begins.

Net Operation Project authoring safety

• Source revisions remain limited to 500 files, 512 KiB per UTF-8 source file, 5 MiB total source, and 500 changes per manual edit. Diagnostics default to a 30-second deadline with two concurrent Roslyn analyses per host; manual edits default to a 15-second deadline.
• Diagnostics and manual-edit responses now include the effective limits. Diagnostics timeout returns HTTP 503 with netOperationProject.language.analysis.timeout; manual-edit or project-lock timeout returns HTTP 503 with netOperationProject.source.manualEdit.timeout. Clients may retry these outcomes and should branch on codes rather than message text.
• A manual edit that exceeds its bounded deadline rolls back without creating a revision. Content-hash conflicts remain distinct HTTP 409 outcomes.

Release and agent documentation

• Deployctl child processes no longer inherit the interactive operator terminal input. The console closes child stdin unless it explicitly supplies a guarded payload, preventing Windows OpenSSH from retaining a completed production probe and stalling the release pipeline.
• Public release notes now use a compact version index plus a separate detailed page for every release. Agent documents require an installed-version check before work starts or resumes.
• The production release console validates the note against every Git commit since the deployed documentation source and rejects uncovered product changes before building or mutating production.

Database and upgrade impact

Each Managed App Workspace database changes during its replacement maintenance window to store optional Board transition link prerequisites. Existing transitions receive no implicit prerequisites, so movement remains unchanged until an administrator configures a rule. There is no PortalDb or file-body data change. After the new schema is used, rollback requires the normal exact-version database backup/restore procedure; backups are retained.

Deployment and operator actions

• Publish 0.0.13-beta as a full managed runtime replacement. Do not create or publish a Managed App update package for this release.
• Deploy Portal, public documentation, API, WebApp, Worker, Package SDK, workspace migration, runtime image, and runtime catalog from the same clean source revision.
• Replace the runtime of all three active Managed Apps and verify Web, API, Worker, RabbitMQ, PostgreSQL migration state, and current runtime metadata for each installation.
• Existing managed S3 bindings, signer capability, file-body storage, backup scheduler, and backup retention policy do not change. Do not delete backups or prior runtime artifacts automatically; report them for explicit manual retention review after acceptance.
• API and Worker receive the new Net Operation Project source-processing defaults from packaged configuration. No production secret or host-specific configuration key is added.

Compatibility and breaking changes

• Existing Board definitions and transitions remain compatible because link prerequisites are opt-in and an empty collection has the previous behavior.
• Net Operation Project clients must tolerate HTTP 503 for bounded diagnostics and manual-edit timeouts and should honor returned Retryable and limit metadata. Requests beyond the documented file, byte, or change limits are rejected explicitly.
• New attachment preflight, Board historical-reconciliation, transition-rule, and release-note manifest fields are additive. Consumers that regenerate clients from OpenAPI or recompile supported Package SDK integrations receive the new contracts; existing clients that ignore unknown response fields remain compatible.
• Existing saved grid state is installation-local UI state. Stale or incompatible entries are discarded or normalized without workspace data migration.
• No known removal of a supported Runtime API route is included in this release.