Platform Updates

Repositories: Partners and partners-api. Discord roles and Telegram member tags for Dealers Den now belong to individual table packages, like attendee benefits belong to registration tiers. Edit a package to choose its entitlements; application contact requirements remain event-wide. Existing dealer entitlement configuration is carried into existing packages during migration, while new packages start without bot entitlements.

Validation: Partners typecheck and production build, desktop/mobile package-editor preview, API typecheck and package entitlement regression tests. Entitlement selection and revocation follow each attendee slot’s active dealer registration and selected package. Real provider delivery is not exercised by the synthetic preview.

Repository: Partners. Dealers Den application questions and shared Rego/prefill questions now appear at the bottom of their configuration pages. Form builder panels, existing questions and sections start collapsed. Expand only the part you need; collapsing an opened editor preserves its draft and uploads. Dealers and registration configuration on/off settings, including question requirements, use switches.

Validation: Partners typecheck, production build and responsive authoring preview checks. Form schemas, saved answers and configuration persistence keep their existing contracts.

Repository: Rego. Dealers and attendee registration now share the same payment-method cards. Dealers choose a method, then see the assigned organiser account on the payment screen. Methods without a receiving account are omitted, and an account’s published limit prevents continuing with an amount it cannot accept. Changing the method clears the previous receipt and reference. Dealers can also use Problem with this account? to report an issue and recover to the next account or another payment method, using the same reporting flow as attendee registration.

Validation: Typecheck, production build and responsive component previews cover method selection, assigned-account display, unavailable methods and account limits. No payment or registration was submitted during these checks.

Repository: Rego. Dealers registration now follows the attendee form layout, with readable progress steps, a visible table selection summary, larger package prices and clearly listed included attendee places. Payment steps appear only when payment is needed. Choose a package, then use Continue to attendees to hold capacity and review your team.

Validation: Typecheck, production build and desktop/mobile component previews. Package reservations, attendee validation and payment submission retain their existing flow. No registration or payment was submitted during preview checks.

Approved application details now show Complete Dealers Den rego when no table rego has been started. The action opens the existing verified registration flow. Applications under review and applications with an existing table rego do not show this prompt. A failed table-rego lookup now reports an error instead of incorrectly treating it as absent.

Next-step validation: Rego and API typechecks, the Rego production build, approval/registration-state fixtures and responsive button checks pass. The reusable preview covers approved, under-review and already-started states. No table registration was submitted during these checks.

Repositories: Partners API, Rego. Status: Released.

What’s Changed: Dealers Den information includes the verified event ID that Rego uses to match application requirements to the selected event. Previously, enabled setups could show a “requirements changed” error because that ID was missing from the response.

Impact: Existing event configuration and saved applications are preserved. Attendees can retry their event’s Dealers Den application page after the release.

Validation: API typecheck, actual-handler identity/privacy/error fixtures and application-form tests pass. The Git-linked Worker build succeeded; live SFW27 event and Dealers Den information now return matching event identities with Dealers Den enabled. No application was submitted during verification.

Repositories: Rego, Partners API. Status: Released.

What’s Changed: Event Shop uses readable single-column product cards on narrow phones, consistent artwork frames, concise pickup/delivery labels, and icon-only add-to-cart controls. Items that need answers or a variant have a working Choose options button. Search, sorting and scrolling category buttons are easier to scan, with selected categories clearly marked.

Impact: Attendees can browse products with less clutter from empty carts and sign-in prompts. The empty cart explains how to start; checkout appears once items are present. Payment, account and saved-cart rules remain in place.

Inactive, unavailable and sold-out products stay visible as disabled grayscale cards. Live stock and purchase windows determine whether a product or variant can be selected. Available preorder products have an orange Pre-order pill directly below the name and above the description.

Shop detail modals give Pickup or Delivery, Availability, and Stock their own labelled sections. Opening and closing dates, remaining quantities and purchase limits are easier to read. Variant selectors and legacy select questions appear as dropdowns with the configured choices.

The product name and price lead the detail modal, with a larger per-item price and a compact category label. Secondary labels and information panels use quieter styling so the purchase details are easier to scan.

The Rego page footer reserves space for the floating Report a problem button, including the device safe area, so the footer remains readable after scrolling to the bottom.

Validation: Typechecks, the Rego production build and API availability fixtures pass. Browser checks cover 320px, 390px and desktop layouts, disabled cards and variant options, orange preorder pills, search and sorting. Git-linked hosting builds succeeded; the live public Shop API returns current stock availability. No production checkout was performed.

Upgrade Notes: No organiser configuration changes are required. The public catalog now includes an availability status for each listing and variant; cart additions recheck capacity, while checkout retains transactional stock enforcement.

Repository: Partners. Status: Released.

What’s Changed: Dealers Den application questions and the shared Rego/prefill question builder now have a Reset to default button. Confirming restores the 15 standard Dealers Den application questions or the eight standard Rego/prefill cards, replacing edited questions and custom sections in the draft. Rego’s fursona question is optional except when the attendee is fursuiting.

Impact: Resetting changes only the question draft. Use the existing save control to apply the defaults to applicants; cancelling the reset keeps your edits. Other event and Dealers Den configuration remains unchanged. Canvas previews include the same control.

Validation: Real builder browser checks pass at 1440px, 390px and 320px widths for both flows, including reset cancellation, restored labels and required rules, replacement of custom sections and questions, explicit saving, and reload persistence. Typecheck, production build and documentation checks pass. The Git-linked hosting check succeeded, and hosted builder assets include both reset callbacks and the Reset to default control.

Repositories: Partners, Partners API, Rego. Status: Released; hosted attendee checkout unverified.

What’s Changed: Rego Config now has one shared question builder for registration and prefill. Tier, badge name, fursuiting, fursona, add-ons, wearable sizes, catalog questions and Conditions of Entry appear as editable default cards. Partners can change labels and required rules, remove cards, restore defaults or add custom questions. The former fixed-question inventory and competing fursona/fursuiting toggles have been removed.

Impact: Both flows use the saved form, and retained prefill answers continue into registration. Removed questions no longer collect answers or block progression. Existing custom questions remain; removing every question saves an intentionally empty form. A removed tier chooser uses an eligible default tier, and a removed badge-name question uses the attendee profile name. Event pricing, capacity, identity and fursona ownership, catalog fulfillment and payment checks remain enforced. Conditions document management stays separate.

Upgrade Notes: Review Rego and prefill questions in the event’s Rego Config, adjust the cards and save changes. Check the draft attendee preview before publishing. Local builder browser checks pass at desktop, 390px and 320px widths, including edits, save/reload, removal, restoration, conditional fursona requirements and empty forms. Eighteen attendee browser scenarios pass across registration and prefill, including saved-answer continuation, native and catalog required rules, and discarded removed fields. Partners and Rego typechecks and production builds, API typecheck and Worker dry build, API Hono fixtures and Dealers Den regressions, and documentation checks pass. The Git-linked API, Partners and Rego deployment checks succeeded. Hosted Partners and Rego assets include the shared form handling, and the public API returns the default/authored schema. Group and paid-gift handling were reviewed in source; hosted attendee checkout remains unverified.

Repositories: Partners, Partners API, Rego. Status: Released; hosted attendee submission unverified.

What’s Changed

Dealers Den configuration now starts its application form builder with the 15 standard table, portfolio, social, product, percentage, and notes questions. The builder explicitly applies only to application questions; dealer registration questions are configured separately in Rego Config. Organisers can edit, reorder, add, or remove questions and save the resulting applicant form. Existing extra questions are retained, and removing every question keeps the form empty after saving.

Impact

Applicants answer the saved questions; removed questions no longer block submission. The partner preview follows the current draft. Representative contact, assistant invitations, fees, linked account requirements, and Conditions of Entry continue through their existing settings. Other products is an optional editable question; organisers can set its required rule and conditional paths in the builder.

Upgrade Notes

Review Application questions in Dealers Den configuration, adjust the form, and save configuration. Local checks cover desktop and mobile builder editing, save/reload, removals, empty forms, applicant submission and prefill, and API validation. Partners and Rego typechecks and production builds, API type-check, and documentation checks pass. Canonical Rego browser checks cover new applications, edits, removals, empty forms, and loading retries. The Git-linked API, Partners, and Rego deployment checks succeeded. The hosted builder serves the application-only wording, the public API returns the default schema, and the hosted Rego application asset contains the saved-form handling. A real attendee submission remains unverified.

Repositories: Partners, Partners API. Status: Released.

What’s Changed: A requirement response cannot be accepted while any attached evidence is quarantined or rejected. If an accepted response’s file is later given either disposition, the response and requirement return to revision requested. This is an administrator disposition check, not an automatic malware scan.

Impact: Reviewers can request replacement evidence before accepting the response. Assigned people can submit a new revision. Work items can still be marked complete without a platform scan.

Upgrade Notes: Scan downloaded files on your own device before opening them. Planning administrators should quarantine or reject a file when they identify a problem and record the reason.

Validation: Partners typecheck, build, and Files dialog fixture passed. Partners API type-check and build check passed. The migration was published; its three database guards are present, and a live count found zero accepted submissions linked to quarantined or rejected evidence. Cloudflare Pages deployed the merged Partners commit, and the merged API Worker was deployed. An authenticated production review journey was not exercised.