Moltaro 0.0.5-beta

Release date: 2026-07-29

Moltaro 0.0.5-beta expands governed data modeling and runtime navigation, replaces the legacy Lucene search subsystem with PostgreSQL-native entity search, and improves day-to-day administration.

Highlights

Configurable PostgreSQL entity search

• Entity search now runs directly against PostgreSQL and no longer depends on a separate Lucene index, rebuild queue, or persistent full-text volume.
• Configurators choose explicit direct or related search targets instead of enabling search for an entire Entity Definition.
• Search results reflect committed data immediately and continue to respect record, field, comment, and attachment access rules.
• Exact #number and #{record-id} shortcuts provide unambiguous direct lookup alongside ordinary literal substring search.

Parent Tree View

• A Table Surface can present records as a server-paged hierarchy through an indexed direct self-reference field.
• The configured Tree surface may be the entity default or an explicitly selected custom surface. Data Explorer, direct tables, full Reference Lookup pickers, Details related data, and Details/Drawer related-table blocks share the same lazy hierarchy contract.
• Roots and each parent’s children are paged independently. Embedded related tables append additional roots with a root-level Load more action without loading the complete hierarchy into the browser.
• Filtering keeps the relevant ancestor context visible, while access checks, paging, ordering, cycle protection, and stale-configuration diagnostics stay authoritative on the server.
• Parent Tree View requires a ready parent-leading BTREE index. List and LongList reference inputs cannot target a Tree surface; use the full Lookup picker. Value-based Group By, write-time cycle prevention, drag-and-drop reparenting, and expand-all remain separate capabilities.

Typed field defaults

• Configurators can define type-safe defaults for supported Entity fields.
• Defaults apply when a field is omitted during creation; explicit null, false, 0, empty text, and empty selections remain deliberate caller values.
• New rows added to Table fields receive their configured child-field defaults without changing existing records or backfilling stored data.

Governed Business Invariants

• Administrators can define and activate cross-object Business Invariants that evaluate governed mutations before they are committed.
• The same authoritative decision is enforced across runtime forms, APIs, Boards, relationships, comments, attachments, tags, and trusted C# extension paths.
• Denials return structured diagnostics and remain visible to operators instead of failing as an unexplained generic request error.

Administration and platform refinements

• User creation can set an initial password for a local Workspace user while preserving deliberate passwordless and Service-user provisioning.
• User, role, group, permission, and assignment surfaces use more consistent interaction and error-state behavior.
• Boards can recover stable historical import identities needed by repeatable package and migration flows.
• Public documentation adds current guidance for entity search, hierarchies, typed defaults, calculated fields, API automation, and agent workflows.

Runtime fixes

• Entity and Board reads now correctly hydrate published Net Operation Project descriptors whose function kinds are stored as the documented string enum values. Existing string and numeric descriptors remain readable.

Database and upgrade impact

The Workspace database changes during the full replacement to support field defaults, PostgreSQL-backed entity search, and Parent Tree View configuration. Legacy full-text configuration and queue state are removed, but old opt-in flags are not converted into broad search behavior; configurators explicitly select the paths that should be searchable.

Operations

• API, Worker, and WebApp are shipped together in the 0.0.5-beta runtime.
• Existing managed applications require a full runtime replacement and Workspace migration; this release is not published as a delta update.
• After a successful replacement, the obsolete data/fulltext bind mount and its local index directory can be removed. Backups contain no search-index payload and restores require no index rebuild.