Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Faster signed-in checks and waitlist prompts
Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Rego now checks attendee profile readiness and site-access MFA policy at the same time. The read-only MFA status request no longer queues unrelated page reads behind a cookie-changing auth action. A session nearing expiry still refreshes before protected reads, and a pending waitlist offer still waits for both current checks.
Impact
Signed-in pages can continue loading while the security policy is checked. Attendees with a waitlist offer should see its time-sensitive prompt sooner. Profile setup, required authenticator approval, and account switching remain enforced.
Validation
Rego typecheck, production build, and route-contract checks passed. Mobile and desktop browser fixtures verified overlapping reads, offer gating, one refresh for an expiring session, and incomplete-profile redirect. Session-boundary and account-switch/MFA fixtures passed. Authenticated production timing remains to verify.
Transaction and application histories show records sooner
Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
The attendee transaction and application pages now show records as each existing source responds, while the remaining sources continue loading. They keep visible records in place during Retry, preserve results from a source that fails, and show partial-load errors without losing available records.
Impact
Attendees can read their first available regos, orders, gifts, Dealers Den, vollie, or activity records sooner. Switching signed-in accounts resets the history to the new account before its records load.
Validation
Rego typecheck, production build, and route-contract checks passed. Mobile and desktop browser fixtures held slower sources, confirmed fast records appeared first, then checked partial failure, in-place Retry, and retained records. Authenticated production timing remains to verify.
Event settings stay open during refresh
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Event Management HR settings, Conditions of Entry, event notification settings, Google Wallet settings, and saved registration prefills now keep their current editors or lists visible while the latest data loads. Drafts and filters stay in place, and a failed refresh offers an inline retry. Saves continue without a full page reload.
Impact
Event operators can keep reading and editing while these views update. Actions that need the current saved state pause during a pending read, and a later response cannot overwrite a newer save.
Validation
Focused browser fixtures exercised delayed reads, failed reads, retry, draft preservation, and event/source changes. Partners typecheck and production build passed. Authenticated production timing remains to verify.
Faster attendee rego form loading
Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
After an attendee signs in, the event rego form now requests saved choices, fursonas, and any gift or waitlist continuation as soon as the event is known, alongside the profile check. Profile completion and current event eligibility still control when the form opens.
Impact
Attendees with complete profiles should reach their rego choices sooner, especially when the profile service responds slowly. A profile that needs setup still goes to the setup flow before registration.
Validation
Rego typecheck, production build, and route-contract checks passed. Mobile and desktop browser fixtures held the profile response while confirming the saved-choice and fursona requests had already started, then rendered the rego form after profile release. Authenticated production timing remains to verify.
More Partner Dashboard work stays visible while updating
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Event Management activity forms, feedback responses, and gift payment reviews now keep their current work visible while records refresh. Finance Audit keeps receipts and the selected detail visible during refresh. Activity edits made during a delayed save remain available for the next save. Gift payment decisions pause until the refreshed queue confirms the latest state.
Impact
Event teams and finance reviewers can continue reading and editing while routine updates run. A failed filter or audit refresh shows an inline message and keeps the last loaded results; switching partner or event scope hides records from the previous scope.
Validation
Focused browser fixtures exercised delayed and failed reads, newer edits during a save, gift decision locking, and partner scope changes. EMS checks covered desktop and narrow mobile widths. Partners typecheck and build passed. Cloudflare Pages lists commit fba60b4 as active production, and the custom domain serves its updated Finance Audit and Feedback bundles. Authenticated production timing remains to verify.
Faster Event Shop opening
Repository: Rego. Status: Released through the linked GitHub branch; production timing remains to verify.
What’s Changed
Published event shops now request their catalog while current event details load, removing a serial wait before the shop appears. If the event’s identity has changed since publication, the shop fetches the current catalog before showing items.
Impact
Attendees should reach event merchandise sooner. Live event details and the current shop response continue to control what appears and whether checkout is available.
Validation
Rego typecheck, production build, and route-contract checks passed. Mobile and desktop browser fixtures held the event response to verify that the shop request started concurrently, and verified that a stale published event ID never delayed the current catalog. Authenticated production timing remains to verify.
Faster Dealers Den forms and in-place assistant replies
Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Dealers Den applications and table rego now request independent account details while event details load. Event-specific eligibility still waits for the current event ID and API response. When an assistant accepts or declines a table invitation, the confirmed status updates on the same page without restarting the event load.
Impact
Applicants and table representatives should reach their Dealers Den forms sooner. Invited assistants keep their place after replying. Current application eligibility, event offerings, and final rego remain API-controlled.
Validation
Rego typecheck, build, and route-contract checks passed. Desktop and mobile browser fixtures held the event response to confirm independent reads started first, then verified the form or assistant view after event-specific data arrived. The assistant fixture confirmed one accepted reply without a document reload or second event read. Authenticated production timing remains to verify.
Faster Partner Dashboard design canvas
Repository: Partners. Status: Released through the linked GitHub branch; authenticated workspace timing remains to verify.
What’s Changed
The Partners design canvas now loads preview sections as they approach the screen. Its entry route bundle is much smaller, and the Manage Plans and plan Notification Settings route previews are available again.
Impact
Partners staff and reviewers can open the canvas sooner and continue through its route and component galleries without a page reload. Operational data and save behavior in protected workspaces are unchanged by this canvas update.
Validation
Partners typecheck, production build, canvas parity inventory, and local browser rendering passed. The canvas entry chunk fell from about 1,148 KB to about 26 KB before compression. Cloudflare Pages lists Partners commit 763426c as the active production deployment, and the custom domain serves the matching canvas asset. Authenticated workspace and production timing remain to verify.
Faster attendee profile saves in Rego
Repository: Rego. Status: Released through the linked GitHub branch; authenticated production save timing remains to verify.
What’s Changed
When an attendee changes their profile username, Rego checks the phone number and username availability at the same time before saving. The current API still validates and owns both writes.
Impact
Attendees spend less time waiting on sequential checks when saving profile preferences. The saved page stays in place and shows confirmation without a document reload.
Validation
Rego typecheck and production build passed. A local browser fixture held both validation responses to confirm that the requests overlap, then completed one profile update and one username update without replacing the page. Production account timing remains to verify.
Rego event overviews appear sooner
Repositories: Rego and Partners API. Status: Rego production deployment and hosted behavior verified; authenticated timing remains to verify.
What’s Changed
Published event pages now show their event overview to signed-in visitors as well as guests while current registration details load. Registration actions and availability still wait for the live API. Hidden events do not use the public overview. The API reads independent inclusion, social-benefit, and catalog-revision details together so they add less waiting to event details.
Impact
Visitors can see an event’s cover, name, schedule, venue, and description sooner. Current prices, capacity, eligibility, campaign access, and checkout remain server-controlled.
Validation
Rego typecheck, build, and route-contract checks passed. Desktop and mobile browser fixtures showed the overview before a held live response for guests and signed-in visitors, without a stale registration action; a hidden-event fixture showed no public overview. API typecheck, dry build, public inclusion and offering-revision checks passed. A local public event response matched the hosted response apart from media-proxy origins. In one-vantage samples, the event detail API median Worker time fell from about 1.69 to 0.83 seconds across ten requests before and after the initial release, and the hosted mobile guest heading appeared in 0.5–1.0 seconds across three fresh visits. Authenticated hosted timing and broader percentiles remain to verify.