Details:

Added shared Azure Container Apps monitoring support across ServerWeb and ServerAdmin with new /developer/server and /developer/logs pages backed by reusable shared services and shared UI components.

The new developer pages expose current memory, CPU, replica, and restart data from Azure Monitor plus simple Log Analytics views for console and system logs, and are now available from the developer navigation for trusted developer IPs or SuperAdmin users.

Reduced avoidable log-ingestion cost by lowering the default application log level to Warning, removing noisy debug Console.WriteLine output, downgrading non-essential admin logging, and tightening Log Analytics retention plus monitoring environment wiring in the ACA Bicep deployment files.

Verified the full solution still builds cleanly after the monitoring, access, navigation, and infrastructure updates.

Details:

Standardized action buttons across all timeslot checkout steps so both Forrige and forward CTAs are solid green and the forward button is always anchored to the far right.

Fixed the broken payment-step back button by adding an OnBack parameter to CheckoutPaymentStep and wiring it through BookingWizard to flowHost.PreviousStepAsync.

Changed SmsOptionsStep Tilbage from text/default to filled primary.

Changed all StepperPaymentCheckout Tilbage buttons from text/default to filled primary with a back-arrow icon.

Replaced all custom div/CSS layout in the wizard action footer with a plain MudStack Row SpaceBetween so the layout works correctly inside MudStepper projected content.

Removed all scoped CSS that was fighting with the projected slot.

Details:

Updated paid checkout materialization so each purchased ticket now gets its own legacy ticket reference, legacy order, shared order, and legacy user-card-detail update while QuickPay still uses the first allocated legacy ticket reference as the canonical order id for the combined payment amount.

Preserved the full per-ticket reference list through generic and time-slot checkout preparation and completion, and refreshed integration coverage to lock in the new one-payment-many-orders contract.

Simplified legacy fee loading by removing paging from the legacy fee list client, stopping use of the non-existent /api/v1/fees/active endpoint, and deriving active payment options from the full legacy fee list while keeping checkout on the active-fee path only.

Verified the targeted checkout integration tests pass and the full solution builds cleanly after the changes.