Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Event merch appears before fee checks finish
Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Event merchandise appears as soon as the public event record loads. Fee and Event Shop availability checks finish in place. Fees are marked as pending while they are being checked, and the Shop action appears only after availability is confirmed. Product images outside the immediate view load as they are needed.
Impact
Attendees can browse merchandise sooner on slower connections without waiting for the separate settings requests. The displayed Shop action and fee guidance still depend on current API results.
Validation
Rego typecheck and production build passed. A local mobile browser fixture held both settings responses and confirmed that products appeared first, the Shop action stayed gated, and fees updated without navigation. Hosted timing remains to verify.
Pawsport changes stay on screen
Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Claiming a Pawsport or marking one lost now updates the credential and history from the saved API response without replacing the page with a loading skeleton. A background check refreshes the full record. If that check fails, the saved result remains visible with a separate retry control.
Impact
Attendees can see a successful claim or lost status immediately and continue reading their Pawsport history while details refresh. A successful lost action cannot be repeated from a stale active-credential form.
Validation
Rego typecheck and production build passed. A local mobile browser fixture delayed the follow-up read after a lost action and confirmed the saved status, history, URL, and absence of a route loading skeleton. Authenticated hosted behavior remains to verify.
More dashboard tools open while status loads
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
SMS campaigns, attendee feedback form settings, activity submission review, and organization bot integrations now show their main controls or status sections while their first data reads finish. Loaded submission rows stay visible during background checks.
Impact
Operators can begin SMS drafts and submission searches sooner. Sending, review decisions, publication, and integration changes still wait for current data. After an uncertain feedback or submission save, or an integration change whose follow-up read fails, the dashboard checks saved state automatically. It keeps repeat changes locked while checking and does not repeat the original write.
Validation
Local browser fixtures covered delayed first reads, quiet polling, and automatic saved-state checks without a Refresh click. Partners typecheck and production build passed locally. Authenticated hosted timing and sitewide save checks remain open.
Direct Rego event links start loading current details sooner
Repository: Rego. Status: Released through the linked GitHub branch; hosted route timing remains to verify.
What’s Changed
Direct links to an event now start the current event-detail request while the page code downloads. The result is used only for the same event, campaign, and attendee session. Failed early reads use the normal request path, and account changes discard an old response.
Impact
Visitors should reach current event details and available actions sooner when opening a direct link. Published event overviews still appear while a delayed current response is checked; registration decisions remain with the API.
Validation
In three matched local slow-mobile runs with a delayed synthetic event API, median current-content time fell from 4.80 to 4.00 seconds. Browser checks covered anonymous and signed-in entry, campaign links, failed early reads, account replacement, and the existing delayed-preview behavior. Rego typecheck, synthetic production build, and route-contract checks passed. These local timings do not establish hosted performance across all events or routes.
More event workspaces open before their queues arrive
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Dealers Den applications and registrations, the registration waitlist, approved activity submissions, and LAN snapshot history now display their headings, search, filters, or navigation while event data loads. Loaded records stay visible during background checks.
Impact
Operators can orient themselves and prepare searches sooner. Decisions and offers still wait for current event data. Saved dealer decisions, registration changes, and waitlist settings or offers trigger automatic checks of the server result; the dashboard does not repeat the original write. Transient background-read failures leave loaded lists visible.
Validation
Local browser fixtures covered delayed reads, background failures, event changes, and automatic saved-state checks. Partners typecheck and production build passed locally. Authenticated hosted timing and sitewide save checks remain open.
Rego notification saves keep the inbox settled
Repository: Rego. Status: Released through the linked GitHub branch; authenticated production behavior remains to verify.
What’s Changed
After an attendee marks every notification read, the unread inbox keeps its saved empty state visible while the site checks the latest server result. Switching to a filter with no currently visible matches shows a quiet check message rather than rebuilding loading cards.
Impact
Attendees can see that their read action was saved without a page refresh or a return to loading placeholders. Current notification state still reconciles with the API.
Validation
Local mobile and desktop browser checks held the follow-up read, confirmed that the empty inbox stayed visible, and observed no document reload. Rego typecheck and a localhost-only synthetic production build passed. Authenticated hosted behavior remains unverified.
Event operations open sooner and saved orders recheck automatically
Repositories: Partners and Partners API. Status: Released through linked GitHub branches; authenticated production timing remains to verify.
What’s Changed
Check-in search and queue navigation, the point-of-sale counter, and shop order controls appear while their current event data loads. Shop dashboard headings and order metrics appear as the metrics arrive. The shared dashboard access endpoint starts independent membership and authentication checks together.
Impact
Event operators can prepare check-in, sales, and order review sooner. Actions that depend on current registrations, stock, permissions, or orders remain unavailable until that data arrives. After an uncertain order save, the dashboard automatically rechecks the saved state and keeps repeat writes locked until it is confirmed.
Validation
Local browser fixtures covered held reads, event changes, and automatic order rechecks. Partners typecheck and production build, API access fixtures, type-check, and Worker dry build passed. Authenticated production timings and sitewide save checks remain open.
Public Rego home opens with fewer downloads
Repository: Rego. Status: Released through the linked GitHub branch; hosted timing remains to verify.
What’s Changed
The public event home now loads attendee navigation code only after sign-in. Event discovery and sign-in remain available immediately to visitors.
Impact
Visitors download fewer files before seeing events. Signed-in attendees still get their Transactions, Applications, Notifications, and other navigation links.
Validation
A controlled local slow-mobile fixture showed the event card at a median of 2.53 seconds, down from 3.01 seconds, with 31 initial assets instead of 39. Mobile and desktop browser checks confirmed that anonymous visitors skip the attendee navigation download and signed-in visitors receive the links. These local measurements do not establish hosted timing.
Account, notification, and publishing pages show useful content sooner
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Account security displays identity and authentication sections as their checks finish. Notifications displays event alerts and payment reports while plan reminders load. Social Publishing shows scoped controls and connection actions while its queue loads. Social Page verification keeps current requests visible during refresh.
Impact
Partner teams can read and use available sections without waiting for every request. Uncertain display-name, payment-report read, and Social Page verification changes trigger automatic saved-state checks. Failed reads do not repeat the original write.
Validation
Local browser checks covered delayed reads, failed refreshes, automatic saved-state checks, and partner or event scope changes. Typecheck and production build passed locally. Authenticated production route and save timings remain to verify.
Activity and volunteer forms open while account choices load
Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Event activity and volunteer application forms now show their roles and questions as soon as the event form arrives. Saved fursona choices load alongside the form. If a question needs a fursona, its picker shows the pending check and the form waits for those choices before continuing.
Impact
Attendees can read roles and fill other answers without waiting for the saved fursona list. Draft answers remain in place while the picker updates.
Validation
Rego typecheck, production build, and route-contract checks passed. Desktop and mobile browser fixtures held the fursona response while confirming the forms and text inputs remained available, then checked upload, draft, submission, and account-switch behavior. Authenticated production timing remains to verify.