Release Notes Through 2026-05-31

• Platform product code rate sheet mapping
• Update Loan Scenarios UI
• Platform ratesheet detail view updates
• Fix search events in pipeline
• Admin customer switch
• Fix fees table formatting
• Harden pricing
• Switch to Action Based Auth 
• Updated the ListUsers API endpoint to use inline filtering on the users can be viewed (if the role/permissions document defined scoped permissions)
• Added integration and unit tests to validate ReportDestination behavior, including multiple destination support, delimiter handling, and filtering logic
• Replaced legacy request context properties
• Removed legacy action string constants
• Method level action permissions are only evaluated to see if you have the action permission

Maestro

• Remove weeks from mapped results
• Journey List Counts
• Fixed incorrect numbers for inState display of journey
• Remove LATEST.COUNT
• Delete and Rename Journey
• New Entry Limiting Mapping
• Filter out draft journeys for journey list view page
• pause/resume promote/start functionality
• Moved `RUN_JOURNEY` argument earlier in MaestroCli command to align with the required argument order
• Added public MLS match endpoint
• Added UpdateJourneyRequest model  to support journey updates with validation via annotations
• Add ESTIMATED_EQUITY and ESTIMATED_EQUITY_THOUSANDS tags to OfferCollectionExtractor
• Refactored action representations in `Actions` to use enum-based metadata. Updated references across APIs, tests, and authorization
• Introduced enums `ResourceType` and `Section` with full resource and section definitions
• Refactored opt-out handling
• Fixed the LoanApplicationResourceExtractor to pull from the loanOfficerEmail
• Journey execution lifecycle — published-only, single-active, per-execution pause/resume/stop, re-publish guard
• Walk-history termination reason output
• EmailTemplateRenderer: derive plain-text from html
• Maestro defect batch — helper-aware email tag discovery + action-exception disqualification + Draft/Published execution leak
• Journey lifecycle observability
• Event-driven journey primer simplification
• Issue reusing terminal candidates
• Terminal re-entry candidates were bypassing waitCondition, causing the emails to fire immediately instead of honoring the configured waitCondition