Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
The first event link prepares its page code
Repository: Rego. Status: Released through the linked GitHub branch; hosted navigation timing remains to measure.
What’s Changed
After the current home event list arrives, Rego starts downloading the shared event page code for the first visible event card. Event details themselves are still fetched when the attendee opens the event.
Impact
The first event link can open with less code to download at click time. Home discovery keeps priority over this later download.
Upgrade Notes
No action is needed.
Validation
Rego typecheck, a localhost-configured build, and mobile and desktop browser fixtures passed with a held event-list response. The fixtures confirmed that the event code waits for the list and that no event detail API request is prefetched. The linked Rego Cloudflare Pages check succeeded. Hosted navigation timing remains to measure.
Fursona edits remain available during a save
Repository: Rego. Status: Released through the linked GitHub branch; hosted authenticated saves remain to verify.
What’s Changed
The My Fursonas editor now keeps typing made while a save is in progress. If the earlier version saves first, the editor stays open, shows which changes were recorded, and lets the attendee save the newer edits. Creating a Fursona also carries its new record into that follow-up save without reopening the page.
Impact
Attendees can continue editing a Fursona during a slow save without losing their newer changes or refreshing the page.
Upgrade Notes
No action is needed.
Validation
Rego typecheck and a held-response local browser fixture passed at mobile and desktop widths. The fixture confirmed that a second save updates the newly created Fursona, with one document navigation, no browser errors, and no horizontal overflow. The linked Rego Cloudflare Pages check succeeded. An authenticated hosted save journey remains to verify.
Planning and affiliate pages stay visible while loading
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Planning Settings, Planning Notifications, and EMS Affiliate Tracking now show their page structure and navigation while initial data loads. Existing records and open drafts remain visible during later refreshes. Uncertain Planning Settings and affiliate saves check the affected saved values automatically before another submission is allowed.
Impact
Planning and event staff can navigate these pages sooner and keep their place during refreshes or saves. A save with an uncertain response stays locked while the page checks the recorded result.
Upgrade Notes
No action is needed.
Validation
Focused local browser checks, Partners typecheck, and production build passed. The linked Partners branch was pushed. Authenticated hosted timing and complete sitewide save certification remain open.
Signed-in event entry reuses its early read
Repository: Rego. Status: Released through the linked GitHub branch; hosted signed-in timing remains to verify.
What’s Changed
Event detail now reuses the document-start event read after a stored account finishes loading. The page skips a duplicate read for the same event and account, while anonymous entry still starts immediately. Responses from a previous route or account cannot replace the current event.
Impact
Direct event links can show useful details with fewer requests. A slow account refresh keeps the published event overview visible while the signed-in view resolves.
Upgrade Notes
No action is needed.
Validation
Rego typecheck and a local browser fixture passed for anonymous, campaign, and signed-in direct entries with one event request each. The fixture also covered failed-read fallback, account switching, and a held refresh with the overview visible. The linked Cloudflare Pages check succeeded. Hosted signed-in timing and action flows remain to verify.
Rego reads event Conditions once per document
Repository: Rego. Status: Released through the linked GitHub branch; hosted attendee journeys remain to verify.
What’s Changed
Rego event detail now requests the compact Conditions format and restores the familiar six Conditions lists in its client data layer. Its document-start read uses the same compact URL, so registration, gifting, and transaction views continue to receive the expected lists without carrying repeated document text over the network.
Impact
Public event entry transfers a smaller event response while preserving the Conditions attendees must review.
Upgrade Notes
No action is needed.
Validation
Rego typecheck, a localhost-configured production build, and a browser fixture comparing compact and expanded Conditions passed. The linked Cloudflare Pages check succeeded. The live Worker returned the compact response with six-list parity. A hosted public event check returned 200 with one compact detail request, no page errors, and no page overflow at 390 px. Hosted signed-in registration and gift journeys, and end-to-end latency, remain to verify.
Dashboard saves check their status automatically
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Checkout renewals, shop order claims, check-in and inclusion claims, workflow settings, payment-account report decisions, and Report Edit now check uncertain saves automatically. Their forms stay open and prevent another submission while the affected record is checked. Forecasting and Planning Departments show useful controls while initial data loads, and Department teams appear before workload totals finish.
Impact
Partner and event staff can keep working in the current page instead of refreshing it to confirm a save. An uncertain inventory return remains locked for administrator review when its exact correction cannot be identified.
Upgrade Notes
No action is needed. If an inventory return reports an uncertain outcome, ask an event administrator to review the correction before trying again.
Validation
Focused browser checks for the affected workspaces, Partners typecheck, and the production build passed locally. The Partners branch was pushed. Authenticated hosted route timing and complete save-flow certification remain open.
Event Conditions use a smaller optional API response
Repository: Partners API. Status: Released through the linked GitHub branch; hosted latency remains to measure.
What’s Changed
The public event detail API can now return one Conditions document catalog plus assignment IDs when a client requests the compact format. Its default response and registration snapshots keep their existing shape for other clients. The same documents and ordering still apply to registration, waitlist, upgrades, refunds, volunteering, and global Conditions.
Impact
Event detail clients that opt in can transfer fewer repeated Conditions documents. The smaller response can help event pages become ready sooner without changing which Conditions attendees must review.
Upgrade Notes
No action is needed.
Validation
API typecheck and a strict local six-action parity fixture passed, including ordering, duplicate IDs, and missing IDs. The linked Workers Builds check succeeded. A hosted read-only comparison for one event confirmed all six Conditions lists match; its event-detail JSON fell from 306,903 to 53,760 bytes, with one compressed sample falling from 83,450 to 15,935 bytes. These sizes are a sample, not a production latency measurement.
Friends opens with concurrent account reads
Repository: Rego. Status: Released through the linked GitHub branch; hosted signed-in timing remains to verify.
What’s Changed
The Friends page starts its friendship summary and Social settings reads together. Enabled accounts no longer wait for settings to finish before requesting the summary. The disabled-Friends view remains tied to the current settings, and later refreshes keep loaded content visible.
Impact
Friends can open sooner for attendees who have the feature enabled, without changing friendship actions or the disabled-account message.
Upgrade Notes
No action is needed.
Validation
Rego typecheck, a held-settings local browser fixture at phone and desktop widths, and existing Friends mutation and retry fixtures passed. The linked Cloudflare Pages check succeeded. Hosted signed-in Friends timing and actions remain to verify.
Asset pages download only the active workspace
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Asset pages now load the panel needed for the current destination, and navigation intent preloads that panel without starting its data requests. The shared Asset workspace script fell from about 346 KB to 9.7 KB in the local production build. Event Shop Orders Dashboard shows its order and claim links while metrics load, and keeps loaded metrics during refresh. After an uncertain LAN snapshot import, the page automatically checks history without submitting the file again.
Impact
Partners reaching Asset overview avoid downloading unrelated operations controls. Event operators can navigate Shop orders sooner. A LAN import with no identifiable receipt stays locked against a duplicate submission.
Validation
Local Asset overview browser checks confirmed the operations panel was not fetched and navigation prefetch made no API reads. Shop dashboard and LAN import browser checks, dashboard navigation check, Partners typecheck, and production build passed. Authenticated hosted timing remains open.
Account Security keeps saved authenticator status current
Repository: Rego. Status: Released through the linked GitHub branch; hosted authenticated checks remain open.
What’s Changed
Account Security keeps the current authenticator list visible while a background status check runs. After an authenticator is added or removed, an older response can no longer replace the newer saved status. A response arriving after leaving the page is also ignored.
Impact
Attendees no longer see a removed authenticator briefly reappear during a later status check. Security settings remain in place while the page refreshes its data.
Upgrade Notes
No action is needed.
Validation
Rego typecheck and a local held-response browser fixture at 390 px and 1440 px passed. The fixture covered a removed authenticator, delayed status responses, and navigation away from the page. The linked Cloudflare Pages check succeeded. Hosted authenticated add and remove journeys remain to verify.