Platform Updates

Repositories: Partners and Rego.

Registration configuration now offers Prefill, Rego, Upgrades, Transfers and Refunds previews using the actual Rego components and the current unsaved draft. Registration changes use fictional paid registrations; partners can select the sample registration tier. Draft availability and policy windows remain visible. All actions and uploads stay local to the preview.

Attendee, dealer, activity, volunteer and feedback form previews now share one modal, viewport and device control. Switching between desktop and mobile preserves the current rehearsal; restarting or closing clears it. Canonical-source parity checks cover the registration change forms alongside existing registration and application forms.

Validation: Partners and Rego type checks and production builds; 91-module canonical form parity and inclusion projection regression checks. Browser fixtures exercise the five journeys, local request confirmations and device switching. These checks do not create registrations or verify hosted authenticated submissions.

Repository: Partners.

The attendee registration preview no longer stops when a tier retains an assignment to a disabled inclusion. Paused inclusions are omitted from the preview, while the draft retains them for reactivation. Active fixed and random variations continue to use the shared Rego form; genuinely missing or invalid active variants still require correction.

Validation: Draft projection regression checks cover disabled/re-enabled inclusions, fixed quantities, variation questions, random pools and invalid active configurations. Partners typecheck, build and canonical form parity checks passed; desktop/mobile preview fixtures confirm the form renders without writes. Hosted authenticated configuration has not been exercised.

Repositories: Rego, Partners and Partners API.

Event Conditions of Entry now group every active global document under “For all event participants”, with document buttons opening read-only modals. Registration and application policies remain available separately. Wallet tickets and the Partners preview distinguish “FPH Terms and Conditions” from “Event Conditions of Entry” and retain separate public links. Existing Wallet passes receive the new labels on their next synchronization.

Validation: Rego and Partners type checks/builds, public document assignment checks, desktop/mobile modal and deep-link fixtures, and Wallet provider payload checks. Local fixtures do not prove existing passes have synchronized on users’ devices.

Repositories: Partners and Partners API.

What changed: The Google Wallet configuration preview shows the attendee or dealer table name on the left of the tier/package row. Issued event-ticket classes use Google’s supported card template override for the same placement, with date/time retained above. Existing classes receive this layout during their next normal Wallet configuration/pass sync.

Validation: API provider/payload tests and type check; Partners type check, production build and desktop/mobile checks for attendee and dealer names, labels and alignment. Local preview tests do not issue live Google passes or sync existing provider classes.

Repository: Rego.

What changed: Incomplete final rows of attendee tiers, dealer packages, inclusions and add-ons now sit centered on the event page. Cards retain the same width as a full row, with the existing one-, two- and three-column responsive layouts.

Validation: Rego type check and production build. Local browser checks cover one through six cards in all four sections on desktop, tablet and mobile, including final-row alignment, consistent widths and horizontal overflow.

Repository: Partners.

What changed: Partners can select individual shop listings or all items in the current category, then activate, deactivate or delete the selection. Bulk deletion lists the selected items in a confirmation modal and keeps the existing in-use protection and optional force-delete setting. Failed items remain selected, while completed changes are retained. Item, category, courier and deletion modal boolean settings now use switches; selection controls remain checkboxes.

Validation: Type check, production build and 85-module Rego preview parity. Desktop/mobile checks cover select-all, activation/deactivation, partial failure, deletion confirmation and cancellation, independent edit buttons and switch behavior. These checks use the actual configuration component with a local catalog and do not modify live catalog data.

Repositories: Rego and Partners form previews.

What changed: Form option cards use a native label across their border, padding and content, so the complete option activates its checkbox or radio. Cards with separate details buttons keep those actions independent. Partners previews share the exact updated control.

Validation: Desktop/mobile form checks cover selection and deselection at all four edges, padding, text, indicator and keyboard input, plus independent details dialogs. Both applications pass type checks and production builds; 85 shared preview modules pass source parity.

Repositories: Partners, Partners API and Rego.

What changed: Dealer package tables now have separate Width (cm) and Height (cm) fields. Partners can add tables with different sizes, and the table count follows the measurement rows. Event-page package details and dealer registration choices list each table’s dimensions separately.

Compatibility: Recognizable existing centimetre measurements are converted without guessing other units or wording. Unrecognized legacy measurements remain readable until replaced. Completed dealer registrations retain their saved table measurements when a package changes.

Validation: Client/API type checks, production builds and shared preview parity; desktop/mobile package detail checks for two differently sized tables. Focused API and database checks cover valid measurements, invalid values, conversion and registration snapshots.

Repositories: Rego, Partners preview components and Partners API.

What changed: Dealer packages display configured Discord server and role benefits, Telegram group access and member tags through the same Community access component used by attendee tiers. Benefits appear on event-page package cards, package details and dealer registration choices. Public package responses now include readable benefit metadata without disclosing provider target IDs.

Validation: Desktop/mobile fixtures checked Discord and Telegram benefits on package cards and in details. Client/API type checks, production builds, public projection tests and EMS preview parity verified the change. Display checks do not create registrations or grant social access.

Repositories: Rego and Partners preview components.

What changed: Event-page dealer packages use the same View details action and shared detail modal as registration inclusions. Package pricing, type and application availability follow the same information layout, with table dimensions, chairs and inherited tier inclusions grouped under Included / guidance.

Validation: Desktop and mobile browser fixtures checked package and inclusion dialogs, furniture details, inherited inclusions, close controls and responsive overflow without live writes. Type checks, production builds and EMS component parity passed.