🐛 Fix potential nil error in organisations stats view

This commit addresses a potential issue where nil values for contribution requested and paid could cause errors in the view. The changes ensure that calculations and displays only occur when both values are present.

🔥 Remove contribution offset feature and simplify payment form

This commit removes the contribution offset feature and simplifies the payment form in the organisation view. The changes were made to streamline the contribution process and remove unnecessary complexity.

🎨 Refactor event contribution logic and update display text

This commit simplifies the logic for determining contributable events and updates the display text to more accurately reflect the organization's activity. The changes aim to improve code readability and user understanding.

🐛 Fix fallback contribution calculation in EventAccounting module

The commit changes the way the fallback contribution is calculated in the EventAccounting module. Instead of using an instance method, it now uses a class method Event.contribution_gbp_fallback. This ensures consistent fallback values across all instances and improves maintainability.

♻️ Refactor update_paid_up method for better readability and efficiency

This commit simplifies the update_paid_up method by: 1. Separating logic for contribution-exempt organizations 2. Removing unnecessary begin-rescue block 3. Using update_attributes instead of multiple update_attribute calls 4. Eliminating redundant paid_up attribute updates

✨ Add Lepton to DEFAULT_PROVIDERS in OpenRouter

🐛 Hide payment form when balance is zero or negative

This commit adds a conditional check to only display the payment form when the balance is greater than zero. This prevents users from attempting to make payments when there's no outstanding balance, improving the user experience and reducing potential errors.

✨ Add fallback mechanism for contribution calculation in GBP

This commit introduces a new method contribution_gbp_fallback and enhances the contribution_gbp method to improve robustness and maintainability. The changes provide a safer fallback option when currency conversion fails or when dealing with unknown currencies.

🔧 Update contribution calculation and display logic

This commit makes several changes to the contribution system:

1. Remove per-event fixed fee and cap logic
2. Change contribution calculation from 5% to 1% of ticket sales
3. Simplify contribution display in views
4. Remove unused fields and methods related to old contribution system

These changes aim to simplify the contribution system and make it more flexible for different types of events and organizations.

✨ Add Ruby Reed as a new advisor and update advisor section layout

🐛 Fix hidden_field_tag syntax in ticketholder email form

This commit corrects the syntax for the hidden_field_tag in the ticketholder email form. The 'value' parameter was missing, which could lead to incorrect data submission. This change ensures proper form functionality and data handling.

✨ Add email update feature for ticket holders

This commit introduces a new feature that allows updating the email address for ticket holders. It includes the following changes:

1. Refactor routes for updating ticket holder information
2. Add email update notification functionality
3. Create new email template for ticket email updates
4. Update views to support the new email update feature
5. Implement send_email_update_notification method

These changes improve the ticket management system by allowing easier updates to ticket holder information and notifying event facilitators about email changes.

♻️ Refactor ticket notifications into a separate concern

This commit refactors the ticket notification logic into a separate concern to improve code organization and maintainability. It also adds a new feature to send notifications for ticket resales.

✨ Add functionality to edit ticket name and email

This commit introduces new features to allow event administrators to edit the name and email associated with a ticket. The changes include:

1. New routes for editing tickets (/tickets/:id/edit)
2. Controller actions to handle GET and POST requests for ticket editing
3. A new view (events/ticket.erb) for the ticket editing form
4. Updated tickets table to include a link for changing name or email

These additions improve ticket management capabilities for event admins.

✨ Add enable_resales checkbox to organisation fields

This commit introduces a new checkbox field 'enable_resales' to the organisation fields, allowing organisations to toggle resale functionality.

🚧 Implement experimental ticket resale feature

This commit introduces an experimental feature allowing ticket resales for certain events. The changes include:

1. Moving the 'enable_resales' checkbox in the event build form
2. Adding a description for the 'enable_resales' field in EventFields
3. Adding an 'enable_resales' field to the Organisation model

These changes lay the groundwork for a ticket resale system, which will allow ticketholders to resell their tickets through the event platform when a ticket type is sold out.

🔤 Update "Check-in" to "Check-in scanner" in events navigation menu

✨ Add co-host filtering for event statistics

This commit introduces the ability to filter events by co-host in the event statistics view. It enhances the user experience by allowing more specific event queries and analysis.

✨ Add AI tagging feature for events using OpenRouter API

This commit introduces an AI-powered tagging system for events. The new feature generates tags automatically based on the event's name and description, enhancing event categorization and searchability.

♻️ Refactor AI-generated feedback summaries

This commit refactors the implementation of AI-generated feedback summaries for activities and accounts. It removes the Anthropic gem dependency and switches to OpenRouter for AI interactions. The changes improve code organization and add admin controls for refreshing summaries.