Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Partner summaries and registry pages open sooner
Repositories: Partners, Partners API. Status: Database migration and linked application builds are released; authenticated hosted timing remains to verify.
What’s Changed
General Notifications now reads compact event and planning summaries without opening each event or plan workspace. Asset Overview shows owned records and summary as soon as they arrive while finance, transit, and checkout sections continue loading. Pawsport Registry searches and pages through authorized records; refreshes and internal note checks keep the current page visible. The sign-in security dialog also loads without pulling markdown editing code into the initial page.
Impact
Partner staff can reach useful lists sooner and keep working while secondary reads finish. Saved internal notes are checked automatically. No action is needed.
Validation
Focused authorization, browser, typecheck, and production build checks passed locally. The Pawsport migration is live, both linked application builds passed, and the unauthenticated API endpoint returns 401. Authenticated hosted timing and the broader sitewide save audit remain open.
Legal pages and attendee records open with less waiting
Repository: Rego. Status: Released through the linked GitHub branch.
What’s Changed
Legal pages receive their own static documents so first-time visitors can read the full text before app scripts run. Event feedback and rego confirmation show the published event context while current records load. Registration attachments start loading alongside the attendee-owned receipt. The notification inbox keeps the selected filter’s records visible while checking for updates.
Impact
Attendees get useful page content sooner and can switch inbox views without losing the current list. Attachment details and confirmation status remain gated on authorized API responses. No action is needed.
Validation
Local typecheck, production build, and focused mobile and desktop browser checks passed, including legal documents with JavaScript disabled, delayed attendee reads, account switching, and public utility parity. Route-wide meaningful-content and authenticated hosted timing still require verification.
Check-in loads less code and background reads stay quiet
Repository: Partners. Status: Linked application release and authenticated hosted timing are being verified.
What’s Changed
Check-in and point-of-sale pages now load the camera scanning decoder when scanning starts. Finance Settings shows each account and policy section when its own data arrives. Planning Event Configuration shows the linked catalog while change history continues loading. Refund Review updates its queue in the background without interrupting the current list or showing transient polling errors.
Impact
Staff can reach manual lookup and account controls sooner, and active review screens remain usable during routine reads. Camera scanning still starts only when selected. No action is needed.
Validation
The check-in scanner control chunk fell from 476.59 KB to 7.49 KB in the local production build; the camera decoder remains available as a separate on-demand chunk. Focused check-in, POS, finance, planning, and refund browser fixtures, typecheck, and build passed. Real camera hardware, authenticated hosted timing, and the broader sitewide save audit remain to verify.
Registration, merchandise, and profile setup appear sooner
Repository: Rego. Status: Released through the linked GitHub branch; authenticated hosted timing remains to verify.
What’s Changed
Event registration starts the signed-in attendee’s existing-rego check while current event details load and keeps the event name visible during session checks. Event merchandise checks Shop availability alongside event details, using the current event ID before showing the result. Profile setup shows saved identity details when the authorized profile response arrives, while account-security and optional connected-account checks continue.
Impact
Attendees can see useful context and begin reviewing profile fields sooner. Current API responses still decide registration access, merchandise availability, and the security policy. Profile saving remains gated on the security check. No action is needed.
Validation
Local typechecks, synthetic builds, and held-response browser fixtures passed for registration, merchandise, and profile setup. Checks covered a changed event ID, delayed session and security responses, retries, saved draft retention, and an account switch. A read-only public mobile check found the home heading in 191–253 ms across five cold browser contexts; signed-in hosted timing remains to verify. These controlled and public checks do not establish a hosted speed gain for authenticated routes.
Faster gift search, staff rosters, and in-place refresh
Repositories: Partners, Partners API. Status: The database change is live; linked application releases and authenticated hosted timing are being verified.
What’s Changed
EMS Gift Review searches and sorts across the event through bounded server pages. Staff Roster reads a smaller, authorized roster view instead of unrelated HR applications and documents. Asset Operations keeps current rows on screen while filters, pages, and views load. Finance Integrations rereads the profile list after a save without blocking the rest of the screen.
Impact
Event staff can reach gift and roster results sooner. Existing records stay visible through background refreshes, and saved integration profiles are checked automatically. No action is needed.
Validation
Focused gift, HR, asset, and finance checks passed, as did API and Partners typechecks and production builds. The gift search database migration is live and the migration dry run is up to date. Authenticated hosted route timing and the broader sitewide save audit remain open.
Account, activity, and transaction pages respond sooner
Repository: Rego. Status: Released through the linked GitHub branch; authenticated hosted timing remains to verify.
What’s Changed
Account Security shows its page and a generic Social account-link section while the account security check finishes. Activity proposals show the published event name while session and form checks run. Transaction history reuses account-scoped reads already in progress when an attendee changes its type filter.
Impact
Attendees can recognize the page and event sooner during slow checks. Transaction filter changes keep completed records visible without repeating pending reads. Linked-account details, security actions, activity form fields, eligibility, and transaction records still come from their current authorized API responses. No action is needed.
Validation
Local typecheck, synthetic build, and mobile and desktop held-response browser fixtures passed. Account Security checks covered delayed and failed security status, enforced MFA, and an account switch. Activity checks covered delayed session and form responses and unknown event slugs. Transaction checks covered filter changes during five pending reads, shop pagination, failed reads and retry, and an account switch with a late response. These controlled checks do not establish a hosted latency gain; authenticated hosted timing remains to verify.
Event options and Dealers Den edits stay responsive
Repository: Rego. Status: Released through the linked GitHub branch; authenticated hosted timing remains to verify.
What’s Changed
Published event pages begin loading their public Shop and Dealers Den options while current event details are checked. Those options appear only after the live event ID matches the published event. When an attendee goes back and edits a Dealers Den application during a pending save, the newer draft stays open after the earlier version is saved. Another save updates the same application using the server’s returned revision.
Impact
Event options can be ready when the current event page opens. Dealers Den applicants can continue editing without losing work to an in-flight save or reloading the page. Prices, availability, application ownership, and final save decisions remain with the current API. No action is needed.
Validation
Local typecheck, a synthetic build, and mobile and desktop browser fixtures passed. Event fixtures confirmed one Shop and one Dealers Den read began before a deliberately delayed event detail; a changed event ID and account switch did not show stale options. Held-save checks for new and existing applications preserved newer table and question edits, then updated the saved application with its returned revision without a document reload. These tests do not establish a hosted latency gain or a real provider transaction; authenticated hosted timing remains to verify.
Rego registration context and repeat visits load sooner
Repositories: Rego, Partners API. Status: Released through linked GitHub branches; authenticated hosted timing remains to verify.
What’s Changed
Standard and Dealers Den registration show a published event name while current event details load. Versioned Rego JavaScript and CSS now have a long browser cache lifetime, so repeat visits can reuse the same files. The event API resolves optional Discord role names in the background rather than holding up prices, capacity, and registration access when Discord is slow.
Impact
Attendees see which event they are registering for sooner, and repeat visits can avoid downloading unchanged app code. Current API responses still decide prices, packages, eligibility, and registration actions. Optional Discord benefit labels may briefly show a generic label until a later request uses the refreshed name. No action is needed.
Validation
Local typecheck and synthetic build passed. With event detail deliberately held for 800 ms, the standard registration title appeared at 430 ms versus 1,199 ms anonymously and 316 ms versus 1,101 ms signed in. A Dealer Den mobile fixture showed the title at 363 ms while live event and application reads were held. Known and unknown events, changed event IDs, campaign queries, account switches, and gated actions were checked. The build checked that all files covered by the long cache rule have versioned names. A controlled API fixture verified that a delayed Discord lookup did not hold the event response. These are controlled local observations, not hosted before-and-after results; linked deployment, browser cache headers, and authenticated hosted journeys remain to verify.
Rego navigation and Friends settings appear sooner
Repository: Rego. Status: Released through the linked GitHub branch; authenticated hosted timing remains to verify.
What’s Changed
The signed-in sidebar no longer waits for a separate navigation download. Friends privacy and connected-account settings appear when their current settings arrive, while the friends list continues loading. Adding a confirmed event pass to Google Wallet opens another tab and keeps the receipt in place; if a popup is blocked, the receipt shows a link to continue.
Impact
Attendees can navigate and adjust privacy settings sooner. Switching accounts clears the previous attendee’s sidebar permissions, including when both accounts use the same email address. Wallet handoff no longer replaces the receipt page. No action is needed.
Validation
Local typecheck, an isolated synthetic build, and browser fixtures passed. The signed-in sidebar appeared at 339 ms without a separate navigation chunk in the local fixture. With the friends summary deliberately held, mobile privacy controls appeared 74 ms after its request started; a desktop account with Friends disabled showed its enable action in 49 ms. Account-switch, Friends mutation, standard receipt, Dealers Den receipt, popup-blocked, and Wallet retry checks passed. The linked Rego Pages build passed. These figures are controlled local observations, not a hosted before-and-after speed comparison; authenticated hosted timing and real Wallet delivery remain to verify.
Dashboard home, registration roster, and meeting saves
Repositories: Partners, Partners API. Status: Released through linked GitHub branches and the two database migrations; authenticated production timing remains to verify.
What’s Changed
The dashboard home reads compact counts and recent activity instead of transferring full operational lists. Registration rosters open with a page of attendee records and load the full authorized set when staff use global search or “Show all.” Access checks start independent permission reads together.
Meeting note and minutes submissions are saved as one governed transaction. If a response is lost, the page automatically checks an actor-scoped receipt and keeps the draft visible while the outcome is resolved. Registration payment status also receives an exact saved-state read when a response is uncertain. Shop Orders keeps the current queue and detail visible after an acknowledged save while it verifies the saved state quietly.
Impact
Partner and event staff can reach dashboard information and roster controls sooner. Meeting, registration, and shop order saves keep the page in place during recovery.
Upgrade Notes
No action is needed.
Validation
Focused authorization, pagination, and save-recovery checks, local database transaction tests, type checks, and production builds passed. Both database migrations and the linked API and Partners builds are live; hosted API routes enforce authentication and the hosted Partners asset manifest matches the release build. A focused Shop Orders batch recovery check passed; its broader canvas workflow remains partially verified because the preview cannot reset a locked ambiguous decision in place. Authenticated hosted route timing and complete sitewide save certification remain to verify.