Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Rego gift and transaction action pages open sooner
Repository: Rego. Status: Source pushed; linked Pages build passed.
What’s Changed
The gift page begins reading current event details while its form code loads. A previously opened upgrade, refund or transfer page shows the attendee’s last event and rego reference while current ownership and policy are checked. Action choices and submissions open only after the current response arrives.
Impact
Attendees spend less time waiting on the first gift visit and can recognize the rego immediately when returning to an action page. Current event, account and policy checks still govern what can be submitted. No action is required.
Validation
Local mobile and desktop browser fixtures held the gift form download and confirmed one event read started before it finished, while the receiver form waited for current data. Held-read upgrade, refund and transfer fixtures showed the last view in 31–61 ms after same-document return, hid it on an account switch and blocked writes under a newly closed policy. Rego typecheck, route contract, sanitized build and focused fixtures passed. Hosted signed-in timing remains unverified.
More Partners workspaces start their first reads sooner
Repositories: Partners, Admin, and partners-api. Status: Source pushed; linked Partners and Admin builds passed.
What’s Changed
Finance Automation, Finance Integrations, and Asset Settings now begin their first authorized reads while their pages open. The initial Asset Settings read matches the selected search and page. Finance Automation checks finance capability before loading notification options. Dashboard access also avoids an extra factor inventory read for a session that has already satisfied strong authentication; account security still fetches current factor details, and sessions needing verification retain the live check.
Impact
Partner operators should reach these workspaces sooner on direct visits. Saved forms remain on screen, and uncertain Finance Automation saves continue checking automatically. No action is required.
Validation
Signed-in Test Partners samples previously left 331 ms after access before Finance Integrations reads, 1,269 ms before Finance Automation reads, and 920 ms before Asset Settings reads. Separate post-release visits started their first reads 3–8 ms after access. A verified-session access response completed in 285 ms of Worker time without a factor-listing stage; an earlier multi-second access outlier remains unexplained. These samples establish request order, not a controlled whole-page speedup. Local authorization, refresh, scope, MFA, and automatic save-recheck fixtures passed, as did Partners/Admin typechecks and builds and API access fixtures. Wider route and save verification remains open.
Rego checkout details and Dealers Den load sooner
Repositories: Rego and partners-api. Status: Source pushed; linked builds passed.
What’s Changed
Event Shop fills the purchaser name and region when the attendee profile arrives, while the country list finishes separately. Dealers Den table registration begins an older application-detail read during event loading when the application is not already included. The API’s isolated overview fixture now records repeated Worker timings to guide further speed work.
Impact
Attendees may see checkout details sooner and spend less time waiting for a Dealers Den table form. Current catalog, price, stock, event, application and checkout checks still govern actions. No action is required.
Validation
Rego typecheck, sanitized build, route contract and focused mobile/desktop browser fixtures passed. A held-country fixture showed the purchaser name before the country response and preserved typed edits. A held-event fixture showed the Dealers Den application read starting 433–450 ms before event release. The API fixture used invented isolated data, matched the overview response across 11 campaign/access variants and removed its temporary database objects. Both linked builds passed. Hosted signed-in timing remains unverified.
More Partners detail pages start loading sooner
Repository: Partners. Status: Source pushed; linked Pages build passed.
What’s Changed
Finance Settings, Pawsport Bindings, and linked Survey details now start their first authorized data reads as soon as dashboard access is confirmed, while the page finishes opening. Their first render uses those results; Refresh still retrieves current data. Existing Survey and Pawsport save flows retain the form and automatically recheck uncertain saved state.
Impact
Partner operators should see these pages finish loading sooner on direct visits. No action is required.
Validation
A signed-in Test Partners Finance Settings sample showed a 482 ms delay between access completion and its four initial reads before this change. After a smaller settings read module was released, a signed-in reload started those four reads 5–6 ms after access; Pawsport Bindings started its history read 4 ms after access in a separate visit. These samples verify request ordering, not a controlled whole-page speedup. Focused browser fixtures confirmed no reads before access, no duplicate first reads, fresh manual refresh, scope isolation, and denied Survey gates. Partners typecheck, production build, and linked Pages build passed. Wider route and save verification remains open.
Rego group saves and activity returns feel faster
Repository: Rego. Status: Source pushed; linked Pages build passed.
What’s Changed
Group registration advances after the server confirms a member’s tier or add-on choices, without waiting for a second full group read on each Continue. A previously opened Activity proposal shows its last form as a read-only preview when an attendee returns, while the current form and eligibility are checked.
Impact
Attendees can keep moving through group registration and see the Activity form sooner on return. Current roster and eligibility checks still govern submission; the Activity preview does not restore unsaved answers. No action is required.
Validation
Rego typecheck, route contract, sanitized build and focused local browser fixtures passed. A held Activity read displayed the preview in 23–30 ms across mobile and desktop with account isolation and one document. The group fixture confirmed no extra read after a saved tier choice and retained the form after a failed save. The linked Pages build passed. Hosted signed-in timing remains unverified.
More Rego account pages stay on screen
Repositories: Rego and partners-api. Status: Linked builds passed; hosted signed-in checks remain open.
What’s Changed
Profile preferences now keeps the review form and saved values visible after a successful save. Returning to a Vollie application shows the roles already seen while current eligibility loads. Returning to a rego confirmation shows the recent receipt while current payment status is checked and clearly marks the status as last known until that check completes. A local API fixture now measures the event overview database read to guide the next speed investigation.
Impact
Attendees can continue reviewing saved profile details and previously opened applications or confirmations without waiting for a blank loading view. Role selection and submission still require current eligibility. No action is required.
Validation
Rego typecheck, route contract, sanitized build and focused mobile/desktop browser fixtures passed. The profile fixture confirmed one document and no duplicate write on an unchanged save. Held-read local fixtures showed Vollie roles in 35–44 ms and a recent confirmation in 35–36 ms, with account isolation. The API overview fixture passed local event and campaign parity checks. Both linked builds passed. Hosted signed-in timing and provider outcomes remain unverified.
More Partners pages begin loading on entry
Repository: Partners. Status: Source pushed and linked Pages build passed.
What’s Changed
Account Settings, Finance Audit, Planning Notifications, and the EMS registration roster now start their first authorized reads earlier on direct entry and reuse those results when each page opens. Refresh still requests current data. When a save result is uncertain, the saved state is checked automatically.
Impact
Partner teams and event operators should see these pages become useful sooner and can keep working without a whole-page refresh after a save. No action is required.
Validation
Partners typecheck, production build, and focused local checks passed. In separate signed-in post-release visits, Account Settings started its first reads 4 ms after access completed, Finance Audit 101 ms after, Planning Notifications 3 ms after, and an EMS registration roster 3–4 ms after. Planning Notifications’ readiness request started 2 ms after its plan returned. These request-order samples do not establish a controlled total-load gain. Wider route and save certification remains open.
Rego merch and saved forms respond sooner
Repositories: Rego and partners-api. Status: Linked builds passed; hosted signed-in timing remains to verify.
What’s Changed
The Merch page requests the current visible products and prices through a smaller event API response, without waiting for registration, payment-account and social-benefit details. A saved registration prefill now confirms within the same form so attendees can review or adjust their choices without a page refresh. A recently opened Dealers Den application stays visible when revisited while its current details are checked; editing and withdrawal become available after that check.
Impact
Attendees should reach Merch products sooner and spend less time waiting when they save a prefill or return to a Dealers Den application. Event eligibility, product visibility and prices, and account actions still use live API decisions. No action is required.
Validation
Rego typecheck, route contracts, a sanitized local build and focused mobile/desktop browser checks passed. The prefill fixture confirmed one document through save and review; the Dealers Den fixture showed the earlier view in 29–34 ms during a held current-data read and kept actions gated. The API projection passed visibility and age-gate checks and matched full event product data against an isolated local database. Both linked builds passed. A small hosted mobile read-only check showed a live Merch product in 453–564 ms across three visits, with one main app document and no page errors. Hosted signed-in journeys remain to verify; local fixtures do not prove payment or provider outcomes.
More Partners workspaces start loading sooner
Repository: Partners. Status: Source pushed and linked Pages build passed.
What’s Changed
General Notifications, Organization Settings, and Linked Operations now start their first partner-authorized reads as soon as dashboard admission succeeds. Each workspace uses the matching result when it opens, so its data can appear sooner without an extra first read. Refresh still requests current data, and saved-state checks run automatically after uncertain writes.
Impact
Partner teams and operators should spend less time waiting when opening these workspaces directly. They can continue working after a save without refreshing the whole page. No action is required.
Validation
Partners typecheck and production build passed. Focused local checks covered one-time first reads, partner scope isolation, and automatic saved-state checks without another write. A signed-in hosted visit started General Notifications reads 82 ms after access completed, Organization Settings 3 ms after, and Linked Operations 352 ms after. These separate request-order samples do not establish controlled cold-load gains. Wider route and save certification remains open. Docs check and build passed.
Rego pages and return visits shed extra waits
Repository: Rego. Status: Source pushed and linked Pages builds passed; hosted signed-in timing remains to verify.
What’s Changed
Rego’s generated page documents now let the app’s startup scripts run in their intended order when Cloudflare optimizes page scripts. Sign-in method choices respond even if tapped before the app finishes starting. Signed-in event registration starts downloading its form while current event and account information loads. Successful Friends changes update the visible list and its same-account return view immediately. Transaction detail also keeps confirmed changes visible on a return visit while checking the current record.
Impact
Attendees should spend less time waiting to choose sign-in, open a registration form, or revisit recently changed Friends and transaction pages. Current event eligibility, price, and account access still come from live checks. No action is required.
Validation
Rego typecheck, route contracts, and sanitized local builds passed. Local browser checks covered a delayed event read during form-code download, mobile/desktop Friends mutations, a saved Event Shop payment detail return, and sign-in taps before app startup. The broader local password, email-code, signup, recovery, and virtual-passkey fixture passed. Both linked Pages builds passed; hosted public documents had no deferred startup scripts, and early password-choice probes reached the form without page errors. Hosted signed-in speed remains to verify. Local fixtures do not prove provider or payment behavior.