[Beta] beta-110226 Server-Driven Action Builder Metadata + Pipeline Rule Engine Summary

[johnwatso]

Summary
Introduces a server-driven Action Builder metadata schema for the WEBUI, replacing hard-coded assumptions while maintaining legacy fallbacks.

Key Changes

• Refactored rules system into a block-based pipeline:
  • Triggers
  • Filters
  • AI processing
  • Modifiers
  • Actions
• Added validation and compatibility checks across pipeline stages.
• Expanded supported triggers, conditions, and actions.
• Introduced AI blocks and additional moderation/utility actions.

Execution Engine

• Updated Discord execution flow to run through a shared pipeline context.
• Modifier routing now happens through the pipeline.
• AI outputs are handled within the pipeline context.
• Added safeguards to prevent duplicate AI responses.

UI / UX Improvements

• Major improvements to the SwiftUI rule editor:
  • Guided onboarding
  • Empty states
  • Loading states
  • Searchable pickers
  • Variable insertion tools

Documentation

• Updated project documentation.
• Updated release notes to reflect new architecture and capabilities.

Known Issues

1. Bot-authored messages now enter the rule engine.

   • Rules can self-trigger unless a filter such as “is from user” is added.
   • Alternatively a guard can be reinstated in the engine.

2. Member join rules currently only execute sendMessage actions.

   • Modifiers, AI blocks, and other actions are skipped.
   • Behavior differs from other trigger types.

3. WEBUI defaults the Send Message destinationMode to replyToTrigger.

   • This hides server/channel fields for non-message triggers.
   • Can result in no output unless users manually change the destination.