v0.9.2

• @lowdefy/modules-mongodb-plugins: ### Patch Changes

• 384da61 Thanks @JohannMoller! - Fix: EventsTimeline inline card text invisible in dark mode — the action card set a fixed light background tint but rendered its message with no explicit color, so the text inherited the theme foreground and washed out to light-on-light in dark mode. The message now uses the status's titleColor (the same dark accent already used for the badge dot), with an undefined titleColor for unknown statuses correctly falling back to inherited color.

• 384da61 Thanks @JohannMoller! - Fix: group on_complete routines were never dispatched — makeWorkflowApis emitted the {type}-group-{id}-on-complete InternalApis and planSubmit computed completedGroups, but nothing ever fired the endpoints, so an authored group on_complete silently never ran (the docs promised the engine fires it). A new dispatchGroupOnComplete phase now fires each completed group's routine post-commit, after the tracker cascade and ahead of the post-hook.

  Fan-out covers both the submitted workflow and any parent workflow reached by tracker propagation: when a child completes and a parent group thereby transitions to done, that parent group's on_complete fires too, with context.workflow set to the parent doc. planTrackerLevel computes each cascade level's completed-group diff; the submit endpoint carries a build-resolved workflow_type → group_id → endpoint bundle (own workflow + ancestors) on params.group_on_complete, and the dispatcher resolves each completion by its workflow_type (same _module.endpointId mechanism as hooks). The payload mirrors the post-hook context so a routine can reach the committed workflow doc. Failures propagate after writes have landed, so on_complete routines must be idempotent — the same contract as post-hooks. Does not fire on cancel or close.

• 771d738 Thanks @SamTolmay! - Action-card verb-default button labels — the collapsed action link is now stamped with a label that names the action the resolved verb performs: edit → Complete, review → Review, error → Resolve, view → View. So a view-only user on an action-required action reads "View", not "Complete". Previously every card fell back to the EventsTimeline default "View".

  An author-provided title on a custom-action link: / view_link: cell (or a tracker start_link) is preserved through resolveCellLink and wins over the verb default. Documented in docs/workflows/how-to/custom-actions.md (§ The action card button label) and docs/plugins/events-timeline.md.

• e87504a Thanks @SamTolmay! - Smaller EventsTimeline avatars — the timeline avatars are shrunk to sit better against the compact rows: compact 22→16px, default 32→26px (font size scaled to match).

• @lowdefy/modules-mongodb-events: ### Patch Changes

• 384da61 Thanks @JohannMoller! - Fix: events-timeline connection ConfigError on default vars — actions_collection and contacts_collection defaulted to null, but the EventsTimeline connection schema requires strings, so get-events threw [ConfigError] property "actionsCollection" must be type "string" at request time whenever a consumer left the vars unset. The var defaults are now the real collection names (actions, user-contacts) so the connection resolves to valid strings out of the box.

• @lowdefy/modules-mongodb-workflows: ### Patch Changes

• 384da61 Thanks @JohannMoller! - Fix: group on_complete routines were never dispatched — makeWorkflowApis emitted the {type}-group-{id}-on-complete InternalApis and planSubmit computed completedGroups, but nothing ever fired the endpoints, so an authored group on_complete silently never ran (the docs promised the engine fires it). A new dispatchGroupOnComplete phase now fires each completed group's routine post-commit, after the tracker cascade and ahead of the post-hook.

  Fan-out covers both the submitted workflow and any parent workflow reached by tracker propagation: when a child completes and a parent group thereby transitions to done, that parent group's on_complete fires too, with context.workflow set to the parent doc. planTrackerLevel computes each cascade level's completed-group diff; the submit endpoint carries a build-resolved workflow_type → group_id → endpoint bundle (own workflow + ancestors) on params.group_on_complete, and the dispatcher resolves each completion by its workflow_type (same _module.endpointId mechanism as hooks). The payload mirrors the post-hook context so a routine can reach the committed workflow doc. Failures propagate after writes have landed, so on_complete routines must be idempotent — the same contract as post-hooks. Does not fire on cancel or close.

• ad5bf9f Thanks @SamTolmay! - Check-action modal header restructure — the compact modal header is split into two rows: status pill · message title · in-flow close on the top row, and the assignee / due-date chips on their own right-aligned row below (a long title no longer fights the chips for width). The modal sets closable: false — an in-flow close button replaces the native floating X, which had no title strip to live in and overlapped the header; mask-click and Esc still close.

  The workflow-closed banner moved below the header (title-then-notice reading order), and the signal button bar now hides wholesale on a closed workflow instead of showing disabled buttons.

• 378c216 Thanks @SamTolmay! - Entity-context overview eyebrow — the two workflow overview pages (workflow-overview, workflow-group-overview) now render an eyebrow that names the entity the workflow hangs off ({type}: {name}, e.g. "Company: Acme Corp") above the title, instead of the static "Workflow" label. Sourced from the workflow.entity_link on the overview responses via a shared overview-entity-eyebrow component, with a title-only fallback until the instance name resolves.