Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Dashboard activity opens with fewer reads
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
The dashboard overview now loads separately from other workspaces and is fetched when navigation points to it. Its event metrics, report panels, and safety signals share one activity read. Gift Review shows the event heading while its queue loads. Transfer Review keeps loaded requests usable through quiet refreshes. Upgrade Review continues automatic saved-state checks when a decision is uncertain and keeps repeat decisions locked until the expected result appears.
Impact
Other workspaces download less dashboard code, and the overview starts fewer requests. Event operators can identify a gift review earlier and keep their place in transfer queues during background checks.
Upgrade Notes
No action is needed. An uncertain upgrade decision remains locked while its saved status is checked automatically.
Validation
The built local browser check observed one dashboard rows request, no overview chunk on the Guide route, and reuse of the prefetched chunk. Desktop/mobile dashboard and focused gift, transfer, and upgrade browser checks passed. Partners typecheck and production build passed locally. Authenticated hosted timing and complete sitewide save certification remain open.
Rego profile and transaction pages make fewer requests
Repositories: Rego, Partners API, Partners database. Status: Released through linked GitHub branches; the database change is published. Authenticated hosted behavior remains to verify.
What’s Changed
Ordinary profile and display-name saves now use the profile response directly when the username is unchanged. The display-name editor keeps newer typing visible if an earlier save finishes first and prevents duplicate submissions.
Transaction category pages load their selected history first. Changing the filter requests missing categories, and returning to a loaded category checks for fresh records without hiding those already visible. The unified transaction page still starts all five history reads together.
Event Shop cart checks now ask the database for bounded usage totals for the listings and stock sources in the cart. Checkout still verifies current stock and purchase limits when an order is submitted.
Impact
Attendees can save a display name with fewer requests and continue editing without a page refresh. Category transaction pages avoid downloading unrelated histories before showing the selected records. Cart validation transfers less historical order data for busy events.
Upgrade Notes
No attendee action is needed.
Validation
Local mobile and desktop browser checks confirmed two profile saves used one profile request each, kept newer edits, and did not reload the page. Transaction checks confirmed a category entry requested one history feed, filter changes fetched missing feeds, loaded records remained visible during a fresh check, and the unified page requested all five feeds. Rego typecheck and a local production build passed. Isolated database checks covered more than 1,200 synthetic orders, and a sanitized local API check covered more than 1,100; the new database migration is recorded remotely. Rego commits 2ef4e33 and 0a08547, Partners API commit 08037f5, and Partners database commit 477a175 passed their linked release steps. Hosted public route responses were successful, but signed-in saves, transaction history, and cart checks have not been certified with a live attendee session.
Rego saves keep newer edits and event pages load sooner
Repositories: Rego, Partners API, Partners database. Status: Released through linked GitHub branches and the database migration; authenticated hosted timing remains to verify.
What’s Changed
Rego profile setup now keeps changes typed while an earlier save is still finishing. It only advances to the profile after the current draft has been saved. The Notifications page also avoids a redundant unread-count request when it first loads; changes that affect unread status still refresh the shared count.
Dealers Den starts the event information read alongside its opportunity read when the event identity is already known. If the opportunity names a different event, the page loads that canonical event information before showing it.
Event detail capacity now counts distinct active people in the database instead of downloading every prefill record to the API. This also removes the first-page limit that could undercount a large event.
Impact
People can keep editing profile details during a slow save without losing newer input or leaving the form early. The Notifications page makes one fewer initial request. Dealers Den can display event details sooner on eligible routes. Event detail responses transfer less data for events with many prefills and report the correct active-person count.
Upgrade Notes
No attendee action is needed.
Validation
The local profile-save browser fixture held the first response, confirmed newer phone input stayed visible, and observed only the initial document request; saving used in-app navigation without a page refresh. Rego typecheck and production build passed. A local production-preview check found one unread-count request on the Notifications page. Four production-preview mobile Dealers Den cases passed, including matching event identity and changed-identity fallback, with no page errors or overflow. The isolated database fixture counted 1,206 active people across more than 1,000 records; the former first-page method counted 998. The database migration was published and appears in remote migration history. Rego commits a839e68, 0ea54a7, and 83f0e77, Partners API commit ac1bb74, and Partners database commit 495c544 carry this release. The linked Rego Pages and API Workers Builds checks succeeded, and a hosted public event detail returned JSON with a numeric active-person count. Hosted signed-in saves and event timing remain to verify.
Event creation opens sooner and saved changes check themselves
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
The new event form opens from the authorized partner session without waiting for the event directory. Report editing keeps an open draft in place while session access refreshes. Activity forms, Conditions of Entry, organization bot disconnects, and Social Page verification decisions continue checking saved state automatically when a save response or first read is uncertain. Repeat actions stay locked until the expected saved change appears.
Impact
Event operators reach the create form sooner and can keep working in report drafts during routine checks. Delayed reads no longer require a manual saved-state recheck for these settings.
Upgrade Notes
No action is needed. If a saved change is still being checked, keep the page open until its status resolves.
Validation
Focused local browser checks covered held event-directory reads, report draft preservation, delayed saved-state reads, and duplicate-write prevention. Partners typecheck and production build passed locally. Authenticated hosted route timing and complete sitewide save certification remain open.
Appeals and report details stay in place during checks
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Partner network-ban appeals now show the current section while their first read runs, then keep the loaded appeal and open draft visible during refresh. An uncertain submission checks saved appeal status automatically without sending the appeal again. Report Detail keeps local enforcement controls in place during a refresh, disabling actions until current data returns. EMS Settlements quietly refreshes balances and history while the page is visible and no editor is open.
Impact
Report and finance operators can keep their place during routine checks. An uncertain appeal no longer needs a manual saved-state check; repeat submissions stay locked until the saved change is confirmed.
Upgrade Notes
No action is needed. If an appeal remains uncertain, review its saved record before starting another action.
Validation
Local appeal, report-detail, and settlement browser checks passed, including delayed reads, saved-state retries, and draft preservation. Partners typecheck and production build passed locally. Authenticated hosted timing and complete sitewide save certification remain open.
Event discovery carries less catalog data
Repositories: Partners API and Rego. Status: Released through their linked GitHub branches; hosted timing remains to measure.
What’s Changed
The event list API now offers a compact discovery view for Rego home cards. Rego uses that view for the home list and Shop order event context. The existing full event list remains available to callers that need its complete catalog; event details and final purchase checks continue to use their current authoritative routes.
Impact
Home and Shop order context transfer less event catalog data, which can make these pages ready sooner on slower connections. Event card status, price range, and urgency labels remain the same.
Upgrade Notes
No action is needed.
Validation
In a synthetic 17-event fixture, the list response changed from 134,027 to 20,875 JSON bytes, with exact card status, price, and urgency parity. The default full-list response remained unchanged. Partners API commit a8ad4db passed its linked Workers Builds check, and Rego commit fd7b9805 passed its linked Cloudflare Pages check. A hosted public check found one successful compact-list request from Rego home and no browser errors; the live full and compact API responses measured 14,172 and 3,025 JSON bytes. There were no upcoming event cards in that check, so hosted card navigation timing remains to measure.
More dashboard records appear while supporting data loads
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Planning Requirements and Schedule show their records while plan details and editing permissions finish loading. Survey Questions opens before analytics, responses, and rewards. Asset Operations requests labels alongside records, and the Checkout list stays visible during refresh. Survey saves refresh the changed survey without restarting every supporting read. Uncertain My Work changes check the saved record automatically before another action is enabled.
Impact
Planning, survey, and asset operators can read and navigate sooner. An open list or draft stays on screen through routine refresh, and uncertain writes do not need a manual Refresh click.
Upgrade Notes
No action is needed. If an action remains uncertain, review the saved record before starting a new one.
Validation
Local browser checks covered held supporting reads, in-place refresh, and saved-state recovery. Partners typecheck and production build passed. Authenticated hosted timing and complete sitewide save certification remain open.
Planning pages open sooner and keep forms during saves
Repositories: Partners and Partners API. Status: Released through their linked GitHub branches; authenticated production timing remains to verify.
What’s Changed
Planning Files, Gates, Meetings, Risks, and the portfolio Timeline now show scoped controls while their first reads finish. Loaded lists and calendars stay visible during refresh. Risk rows can appear before slower plan controls. Uncertain edits, meeting replies, gate actions, uploads, and handoff creation start automatic read-only saved-state checks while keeping the open form and preventing repeat submissions.
The API now provides an actor-scoped handoff receipt read. Its supporting database function was applied before the API and dashboard changes, so an uncertain handoff creation can be checked by its exact receipt without creating another package.
Impact
Planning staff can navigate and prepare work sooner, and stay on the same page when a read or save is slow. An action without an attributable receipt remains locked for review rather than risking a duplicate.
Upgrade Notes
No action is needed. If an action remains uncertain, review its saved record before starting a new action.
Validation
Focused browser and API policy checks, Partners and API typechecks, and production build checks passed locally. The live database confirms the receipt function exists and is executable only by the Worker service role. The hosted API publishes the receipt route. Authenticated route timing and complete sitewide save certification remain open.
Event details use fewer variation data reads
Repository: Partners API. Status: Released through the linked GitHub branch; hosted event timing remains to measure.
What’s Changed
The public event detail API now retrieves configured variation groups, choices, and designs together instead of making two dependent data reads after the group list. Events without variation groups retain their existing response.
Impact
Event detail pages with product or tier variations can finish their server data work sooner. Attendee choices and variation information are unchanged.
Upgrade Notes
No action is needed.
Validation
API typecheck, focused fixture, and an isolated synthetic Worker check passed for fixed and randomized variation groups. No-group responses matched byte for byte. In the local warm synthetic workload, mean event detail time changed from 30.4 ms to 28.0 ms. The linked Workers Builds check succeeded; hosted latency remains to measure.
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.