Platform Updates

Repositories: partners.furries.ph, docs.furries.ph

Status: Ready for deployment

What’s Changed

• Custom ordering throughout the partner dashboard now uses draggable rows or cards with a consistent grip handle and drop-target feedback.
• The change covers registration tiers, add-ons, Event Shop listings and categories, custom catalog questions, activity and volunteer form items, and Conditions of Entry documents.
• Up/down arrow ordering controls have been removed from these workflows.

Impact

• Event operators can arrange dashboard content with the same interaction already used for registration inclusions.

Upgrade Notes

No database migration or operator action is required. Astro diagnostics, Event Shop certification, and the production build pass.

Repositories: rego.furries.ph, docs.furries.ph

Status: Ready for deployment

What’s Changed

• Registration no longer asks attendees to choose a Fursona twice after they say they will be fursuiting.
• The existing Fursona question remains optional for other attendees and becomes required when fursuiting is marked yes.
• The selected Fursona is carried through prefills, individual registration, group registration, and the order review.

Upgrade Notes

No database migration or operator action is required. Registration browser certification passes all six checks.

Repositories: partners.furries.ph, rego.furries.ph, docs.furries.ph

Status: Ready for deployment

What’s Changed

• Event operators can provide clearer descriptions for add-ons, registration inclusions, and Event Shop listings.
• Attendees now see those descriptions while comparing registration tiers, selecting add-ons, reviewing upgrade choices, and browsing the Event Shop.
• Catalog descriptions support the platform’s sanitized Markdown presentation where rich descriptions are already enabled.

Upgrade Notes

Existing descriptions are used automatically. No database migration or operator action is required.

Repositories: partners-api, partners.furries.ph, rego.furries.ph, docs.furries.ph

Status: Database repair deployed; API fallback ready for deployment

What’s Changed

• Signed-in regosite users now receive their attendee account as part of the authenticated identity bootstrap instead of waiting for profile submission.
• Existing Auth identities missing attendee links were repaired, and future signups are covered by a private database trigger.
• First-time users can proceed to profile setup without registration, avatar, notification, or transaction requests failing with “No attendee account found.”
• Profile photos can now be selected, cropped, uploaded, and saved during first-time setup before the remaining profile fields are submitted.

Impact

• Affected attendees can retry sign-in immediately. No account recreation or operator action is required.

Validation

• Production verification reports zero Auth users without attendee accounts, one active bootstrap trigger, and no public API execute grants on the trigger function. API certification passes 15/15; the first-setup photo browser flow, Astro diagnostics, and the 71-page regosite build also pass.

Repositories: partners.furries.ph, rego.furries.ph, docs.furries.ph

Status: Ready for deployment

What’s Changed

• Dashboard and registration-site loading screens now use a balanced four-toe paw centered inside the animated rings.
• Saving overlays use the same shared artwork as initial page loading, preventing the two states from rendering different paw shapes.
• The paw now pulses in place instead of bobbing off center.

Upgrade Notes

No database migration or operator action is required.

Repositories: partners.furries.ph, partners-api, docs.furries.ph

Status: Ready for deployment

What’s Changed

• Pawsport issuance now starts with attendee search and a visible account confirmation instead of a raw username and partner-ID form.
• Operators can verify the attendee display name, username, email, and existing active Pawsports before issuing another credential.
• Issuing partners now use the current scoped partner list, while the binding history presents clearer account, source, status, and timestamp details.
• FPH super admins can now change a Pawsport’s bound attendee from Registry by selecting a verified replacement account and recording an audit reason.
• Every Registry entry now shows holder/account identity, issuer, enrollment, issue and expiry dates, check digit, NFC state, MRZ, stamps, binding history, and note history in one responsive record.
• Authorized dashboard staff can add and edit staff-only internal notes; account reassignment remains restricted to FPH super admins in both the dashboard and API.
• FPH super admins can edit expiry, NFC UID, and claimable-holder metadata directly from Registry; machine-readable fields regenerate after a save.
• FPH super admins can permanently delete an exact Pawsport record after a destructive confirmation. Related bindings, notes, stamps, and enrollment history are removed by existing database cascades.
• The Pawsports overview now links directly to account issuance and registry management.

Impact

• Partner staff get a clearer handoff flow and are less likely to bind a new Pawsport to the wrong attendee account or issuer scope.

Upgrade Notes

• No database migration or operator action is required. Pawsport source certification, API type-checking, and dashboard diagnostics pass.

Repositories: partners.furries.ph, rego.furries.ph, docs.furries.ph

Status: Ready for deployment

What’s Changed

• Rego Config now loads the actual regosite registration interface using the current form values, including unsaved changes, instead of maintaining a separate dashboard simulation.
• Operators can step through the same tier, inclusion, add-on, attendee-details, payment, Conditions of Entry, and review components attendees use, at desktop or mobile width.
• The dashboard and regosite exchange the draft through a short-lived, origin-checked preview session. Submission, upload, reservation, group, inventory, and payment mutations remain disabled.
• Firefox embedding now works for both trailing-slash and non-trailing-slash preview URLs; the dedicated route is resolved before the generic event registration rewrite while all normal regosite pages keep frame protection.

Impact

• Event teams can review the attendee journey while configuring registration without creating test registrations or changing capacity, inventory, or payment records.

Upgrade Notes

• No database migration or operator action is required. Deploy both the dashboard and regosite builds so their matching production or branch-preview environments can communicate.

Repositories: partners.furries.ph, docs.furries.ph

Status: Ready for deployment

• Shop Config now follows Rego Config’s dashboard layout and interaction language: paired settings/catalog cards on desktop, stacked cards on narrow screens, compact bordered rows, consistent add/edit/reorder/delete actions, and standard card-style editor modals.
• Shop Config editor dialogs now use Rego Config’s direct title-and-form card structure, responsive widths, and Cancel/primary action footer. Category creation and editing share the same dialog instead of switching modal patterns.
• The global Save Shop Config bar now binds directly to Shop Config on both direct page loads and in-dashboard navigation, persists the full shop-settings draft, clears the dirty state after success, and keeps API failures visible instead of reporting a false success.
• Listing summaries now include the same compact image treatment used by registration products while preserving drag ordering and arrow-button fallback controls.
• No database migration or operator action is required. Event Shop certification, the production build, documentation diagnostics, and rendered desktop interaction checks pass.

Repositories: partners.furries.ph, docs.furries.ph

Status: Ready for deployment

• Event Management navigation now retains the selected event ID during normal navigation, copied-link use, and open-in-new-tab actions.
• The saved-prefill route is now part of the canonical dashboard SPA manifest, so its controller mounts on direct loads and in-dashboard navigation.
• The screen now waits for its data loader correctly and shows saved records, an empty state, or a recoverable timeout/error instead of remaining on Loading indefinitely.
• Operators can refresh and retry if the partner API does not answer within 15 seconds; no prefill data or permissions changed.

Repository: docs.furries.ph

Status: Ready for deployment

• Updated Astro to 7.2.0 and its Markdown integration to 7.2.2 as a compatible maintenance update.
• A complete static verification run produced 189 pages plus the generated sitemap. Repeated local Windows stress builds can still encounter an upstream intermittent prerender chunk-resolution failure; diagnostics remain clean and deployment builds should retain their normal Linux/Cloudflare environment.
• Documentation diagnostics report zero errors, warnings, or hints.