Platform Updates

Repository: Rego.

What’s Changed: Stylesheet links appear ahead of startup scripts, and the interactive application waits for the initial document styles to finish loading before starting React. Layout measurements therefore use the page’s loaded styles.

Impact: Visitors on slower connections should no longer see an unstyled interactive page while its stylesheet is downloading. The existing public overview remains the first screen.

Upgrade Notes: No event configuration changes are needed. Production-build Chrome and Firefox checks delay the stylesheet for five seconds and confirm that first paint and layout readings wait for loaded styles. A separate failed-style request check confirms that startup recovers. Type checking and the production build also pass; browser diagnostic text is separate from these paint checks.

Repository: Rego.

What’s Changed: The event overview and homepage load current public details without waiting for account checks. Expired or malformed saved account details no longer leave the event overview waiting indefinitely. Dealers Den and activity links open public application introductions; sign-in and event verification happen when visitors select Start application. Activity form selections are preserved when returning from sign-in.

Impact: Visitors can review event information and application requirements before creating an account. Actual forms, owned application edits and submissions retain their existing API access controls.

Upgrade Notes: No event configuration changes are needed. Desktop and mobile browser fixtures check public entry, expired-account recovery and verification success, failure and cancellation. Type checking and the production build are release checks; intercepted fixtures do not prove provider-backed verification.

Repositories: Rego, Partners.

Tier inclusion lists now show each design once when several random draws share the same variant. Draw summaries count all configured draws, and each design retains its draw membership. Separate designs with the same name, guaranteed quantities, and draw-specific reveal and repeat rules remain distinct.

Rego Config also opens saved variant previews by default, so operators can see the designs under each inclusion without expanding every preview. Inactive variants remain listed with their status. A read-only SFW27 catalog comparison confirmed all 41 variants referenced by public tiers are among its 48 saved variants.

This corrects the public tier cards and keeps the shared dashboard helpers in sync, without changing organizer configuration, allocation or inventory records.

Validation: Desktop/mobile browser regressions cover shared candidate IDs, distinct same-name designs, guaranteed quantities, pool policies, tier draw changes and visible active/inactive catalog variants. Existing tier-comparison and nine catalog workflows, typechecks, 91-module parity and production builds passed. Cloudflare deployments passed, and the live SFW27 page now shows each of the four Enamel Pin designs once with two different designs included. The saved catalog comparison was read-only; no allocation or inventory data was changed.

Repositories: Partners API, Partners, Rego.

Status: Released to main; production builds and public delivery checks passed.

What’s Changed

Confirmed attendee and Dealers Den receipts can request a signed Apple Wallet pass through Partners API and WalletWallet. The API returns the pass binary as application/vnd.apple.pkpass. The dashboard workspace is named Pass Config and includes an independent Sample pass on iPhone action alongside the existing pass builder, artwork controls and Google provider settings.

Impact

Real Apple passes contain the public event title and registration reference/QR. Names, tiers, add-ons, balances and payment, refund or transfer details remain outside these passes. Current ownership and confirmation are checked at issuance; staff still verify current eligibility at admission. The dummy sample cannot grant admission. Receipt QR and official Wallet actions remain visible together, with aligned heights and equal click areas. Browser-specific Safari instructions have been removed.

Upgrade Notes

WalletWallet supplies the signing identity. These passes have no background updates, and repeated downloads may create separate cards. The sample remains available if Google settings fail to load. Local API handler tests, real middleware navigation checks, attendee/dealer desktop and mobile browser checks, typechecks, canonical preview parity and release builds validate the changes. Cloudflare deployments passed. The live sample returned HTTP 200 with an 11,184-byte pass and the exact Apple Wallet content type. Hosted Pass Config assets and official receipt artwork were verified; unauthenticated real-pass requests were denied. Native iPhone installation and authenticated live attendee downloads remain unverified.

Repository: Partners.

Activity and other shared form-builder cards now start drag reordering from their title/grip only. Their editable bodies retain native cursor placement, selection and selected-text dragging, preventing text editing from accidentally starting a card reorder. Existing move buttons and drop targets remain available.

Validation: Browser regression checks compare the actual activity field hierarchy before and after the change, including pointer placement, drag selection, selected-text dragging, source and visual editing, and title-based reordering. Type checking, canonical form parity and production build checks. Ordinary isolated cursor clicks already passed before the fix; selected-text dragging reproduced the reorder conflict.

Repositories: Partners and Rego.

Shared dashboard Markdown fields now offer a WYSIWYG button beside Write and Preview. Partners can edit rendered text directly and see formatting immediately, while saved content and previews continue through the existing sanitized Markdown backend. Formatting controls, keyboard shortcuts, search, undo and redo work across source and visual editing. Rich paste is sanitized; supported pasted images retain their insertion location while uploads finish. Mermaid diagrams share the existing renderer. Diagram definitions and complex raw HTML remain editable in Write.

Validation: 250 keyboard checks, 17 rendered Markdown round-trip and unsafe-paste checks, actual shared editor desktop/mobile browser checks covering cursor selection, formatting, history, preview parity, protected content, deferred image upload and overflow; type checking, canonical form parity and production builds. Local upload callbacks do not prove hosted file delivery.

Repository: Partners.

Dashboard Markdown text areas now use Google Docs keyboard conventions first, followed by compatible Word and OpenOffice shortcuts. Supported actions include formatting, headings, alignment, lists, indentation, paragraph movement, footnotes, find and replace, word count, and copying formatting. A shortcut reference is available in the editor. Undo and redo cover typing, formatting buttons and automatic list continuation together, with visible Undo and Redo buttons. Formatting preserves the selected text, and clicking the source cancels any pending automatic cursor placement. Browser text selection, copy and paste remain available. Ctrl or Command plus S opens the existing dashboard save confirmation when a draft is available.

Validation: Official Google Docs, Microsoft Word and Apache OpenOffice shortcut references; 250 shortcut conflict and modifier checks; actual shared editor desktop and mobile browser fixtures for mouse selection, editor commands, clipboard controls and mixed undo/redo; save-confirmation keyboard tests; type checking and the production build. Page-layout, font-size and document-file operations remain outside this Markdown editor. Ordinary pointer selection already worked in the isolated previous editor; the originally reported hosted pointer issue was not reproduced there.

Repositories: Partners and Partners API.

Registration configuration confirms saves against canonical API receipts instead of raw draft JSON. Server-added defaults and catalog ordering no longer leave the save bar stuck. Tier activation is returned correctly after saving. ZEP entitlement writes follow catalog updates to avoid overlapping writes. Partial failures retain the draft and permit retry after the saved state is checked. The save bar distinguishes saving from checking, and session refresh has a bounded timeout without discarding the session or mounted draft.

Validation: Canonical save receipt and partial-failure regressions, session refresh timeout checks, API tier readback tests, type checks, Partners build and local desktop/mobile save fixtures. These checks do not modify live event configuration or recover edits from a closed browser page.

Repositories: Partners and Partners API.

Dealer Wallet passes now show the dealer’s attendee display name as the ticket holder, with “Dealer table name” as a separate detail. The holder stays beside the package on the card. Zero-slot packages use the applicant’s canonical identity as the holder. The configuration preview and wording controls show the same separation. Table wording uses its own setting instead of reusing older attendee-name labels. Existing passes adopt these values on their next normal synchronization.

Validation: Wallet payload, holder identity and synchronization regression checks, API and Partners type checks, Partners build and desktop/mobile reference preview checks. Tests do not synchronize user devices.

Repositories: Partners and Partners API.

Attendee Google Wallet tickets no longer repeat the ticket holder under “Attendee or table”. That detail is reserved for Dealers Den registrations. The holder name stays beside the tier/package on the card face. The configuration preview uses the same distinction, including when switching between attendee and dealer samples. Previously issued attendee passes clear the old table field on their next synchronization.

Validation: Wallet payload regression checks, API and Partners type checks, Partners build and desktop/mobile reference-preview checks. Existing passes on user devices have not been synchronized by these tests.