Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Event and transaction links respond sooner
Repositories: Rego and Partners API. Status: Linked releases succeeded; hosted signed-in timing remains to verify.
What’s Changed
On signed-in event pages, registration, gift and Dealer ownership checks now run alongside the current event read. Hovering or focusing an available transaction change starts its current action-state request and loads the destination code before navigation; a prompt click reuses that read. Profile and Settings links also prepare their destination code on intent. The activity list API now reads forms and Conditions of Entry together.
Impact
Attendees should wait less after an event opens, after selecting a transaction action, and when moving through account settings. Registration, eligibility and saves still use current API decisions. No action is needed.
Validation
Rego typecheck, 62-route contract and local production build passed. Mobile and desktop browser fixtures confirmed that three account reads overlapped a held event-detail request and that transaction hover and navigation used one upgrade-state read with one page document and no browser errors. The API typecheck and response-parity fixture passed; a controlled 60 ms per-read activity scenario completed in 121 ms instead of 183 ms. Both linked builds succeeded, and the hosted event and transaction routes and public activity response returned successfully. These checks do not establish hosted signed-in latency or real-account save performance.
Feedback opens sooner and Dealer details overlap
Repositories: Rego and Partners API. Status: Linked releases succeeded; hosted signed-in timing remains to verify.
What’s Changed
Event feedback now shows its current categories before loading the question editor and Conditions of Entry. The Continue button waits until those tools are ready. If an optional download fails, the form offers a reload and restores the attendee’s saved draft. Dealer’s Den information now starts its event conditions lookup alongside the other independent reads.
Impact
Attendees can choose feedback sooner and keep their entered response through a download retry. Dealer registration needs less serial server work when checking its current requirements. No action is needed.
Validation
Rego typecheck, route contract, production build, and mobile and desktop browser fixtures passed. The local feedback route preloaded about 74 KB less raw JavaScript; first use reached an editable field in 36–61 ms after Continue. A forced optional download failure preserved and restored a nonempty draft. The API typecheck and owner-isolation fixture passed, and a controlled overlap test completed independent 80 ms and 75 ms reads in about 81 ms. Both linked builds succeeded; the hosted feedback route omitted optional form modules from its initial preload, and a published event’s anonymous Dealer info returned the expected public response. Hosted signed-in timing and real-account saves remain to verify.
Finance and Surveys open sooner after sign-in
Repositories: Partners and partners-api. Status: Linked releases succeeded; broader dashboard checks continue.
What’s Changed
Finance and Surveys now request their first data as soon as dashboard access is confirmed, while their pages finish loading. Survey totals are counted on the server without downloading response rows, including when there are more than 1,000 surveys or responses. Planning discussion comments, reactions, and watches appear after a confirmed save without rereading the whole workspace. If a feedback-template restore response is interrupted, the form checks the server automatically, keeps newer browser edits, and prevents a repeat write while the outcome is unclear.
Impact
Partner teams should see Finance and Survey content sooner on repeat visits and stay in place after these saves. No action is needed. If an interrupted feedback restore cannot be attributed, the form shows its checked server version for review before another write.
Validation
On separate signed-in repeat visits after release, Finance reads began 18 ms and Survey reads 15 ms after access finished; earlier separate samples had 316 ms and 503 ms gaps. The Survey reads overlapped its page download. These are request-order samples, not a controlled total-load comparison; the first Finance visit still waited on cold page code. Browser fixtures covered single initial reads, scope changes, automatic recovery, draft preservation, and in-place discussion saves. Typecheck, production build, indexed survey-count tests, and the linked Pages and Worker builds passed. Wider roles and save journeys remain to verify.
Event links and transaction changes respond sooner
Repository: Rego. Status: Linked release succeeded; hosted signed-in timing remains to verify.
What’s Changed
Event cards and event sharing links now use the direct published page address, avoiding an extra redirect for newly generated links. Transactions and Communications load fewer form modules when opened directly. Finalizing an approved rego upgrade shows the confirmed result immediately without rereading the full upgrade state. If the response is interrupted, Rego checks the current upgrade once and prevents a second submission when the outcome is still uncertain.
Impact
Attendees can reach linked event pages with one fewer network step, open transaction and communication pages with less initial code, and stay on the upgrade confirmation after a save. No action is needed.
Validation
Rego typecheck, route contract, production build, and focused mobile and desktop browser fixtures passed. In the local build, Transactions preloaded about 108 KB less raw JavaScript and Communications about 28 KB less. Hosted anonymous traces found a redirect on older bare event URLs; new event links and canonical addresses use the direct form. Fixtures covered confirmed, interrupted, rejected, and unresolved upgrade saves with no page reload. The linked Pages build succeeded, and hosted event, transaction and communication routes responded. Hosted signed-in timing and real-account saves remain to verify.
Reports list requests data sooner
Repository: Partners. Status: Linked release and signed-in route check succeeded; wider dashboard journeys remain under review.
What’s Changed
The Reports directory now requests its list as soon as dashboard access is confirmed, while the page finishes loading. Direct links to the Reports list and Guide index also start the protected workspace correctly.
Impact
Partner teams and report reviewers should reach their report list sooner and no longer wait indefinitely at “Checking access” on those direct links. No action is needed.
Validation
A signed-in Reports All sample before this change showed a 323 ms gap between the access response and the directory requests. On a separate repeat visit after release, both requests began 10 ms after access finished; a cold direct Reports list visit also opened and overlapped data reads with page download. These samples confirm request order but are not a controlled total-load comparison. Local browser and request-ownership checks, a 138-path route audit, typecheck, production build, and the Partners and Docs linked Pages checks passed. Other dashboard save journeys remain to verify.
Internal event edits save without reloading details
Repository: Partners. Status: Linked release and a signed-in test save succeeded; wider save journeys remain to verify.
What’s Changed
Editing an event’s internal name now sends only that changed field and keeps the Event Details form in place after a confirmed save. Public names, status, and event dates still refresh the event scope when they change. If a response is interrupted, the form checks the saved event automatically before another write.
Impact
Event operators can make internal corrections without waiting for the dashboard to reread access and event details. No action is needed.
Validation
A reversible edit on Test Partners / Test Event stayed on the same page and was restored to its original server value after reload. After the linked release, the same edit reached Saved with one API request of about 599 ms and no access or detail reread; the original value was restored and confirmed after reload. Local browser checks covered scope-changing edits and interrupted-save recovery. Partners typecheck and production build passed. Other roles and save journeys remain to verify.
Rego profile pages open with fewer form modules
Repository: Rego. Status: Linked release succeeded; hosted signed-in timing remains to verify.
What’s Changed
Profile setup and preferences now request only the form controls they use on direct entry. Profile photo editing and saves still open in place, and saved details remain tied to the signed-in attendee.
Impact
Attendees opening profile setup or preferences download less JavaScript before using the page. No action is needed.
Validation
Rego typecheck, route contract, production build, and mobile and desktop browser fixtures passed. Each local direct profile route preloaded about 26 KB less raw JavaScript. The fixtures covered immediate photo editing, a single inline profile save, and account switching without stale data. The linked Pages build succeeded, and both hosted profile routes responded. Hosted signed-in timing and real-account saves remain to verify.
Account and registry pages request data sooner
Repository: Partners. Status: Linked release succeeded; signed-in request order was verified on three pages.
What’s Changed
Account Security, Asset Checkout, and the Pawsport Registry now start their authorized data requests while their page code loads. Each page uses that same request when it opens. A change of account or partner scope stops an outdated read from filling the new page.
Impact
Account holders, asset operators, and registry staff should see useful current information sooner after opening these pages. No action is needed.
Validation
Local browser checks covered authorization before reads, one request per page, account and partner changes, and existing save recovery. Partners typecheck and production build passed, and the linked Pages build succeeded. In separate signed-in samples, the protected data requests started 16–20 ms after access finished, versus 317–613 ms in earlier samples. Server timing and scope varied, so this verifies request order rather than a controlled total-load improvement.
Shop details and Friends privacy respond with less waiting
Repositories: Rego and Partners API. Status: Linked releases succeeded; hosted signed-in timing remains to verify.
What’s Changed
Shop product details open immediately while question fields load only for items that need them. A confirmed Friends privacy change updates its switch in place without reloading the Friends lists. If a save response is interrupted, Rego checks the saved setting before confirming it. Shop order history now loads each account-owned page with one database read instead of resolving the attendee identity in a separate read.
Impact
Shop pages request less code on direct entry, privacy changes keep the current page in place, and shop order history has less serial server work. No action is needed.
Validation
Rego typecheck, route contract, production build, and mobile and desktop browser fixtures passed. The local Shop route preloaded about 14 KB less raw JavaScript while product details kept their previous opening speed. Friends fixtures covered confirmed, interrupted, rejected, and account-switched saves without a page navigation. API typecheck, a live read-only relationship probe, and a synthetic ownership and pagination fixture passed. Both linked builds succeeded; hosted authenticated timing and real-account saves remain to verify.
Custody and account saves settle in place
Repository: Partners. Status: Linked release succeeded; hosted signed-in save timing remains to verify.
What’s Changed
Asset Checkout returns and transfers keep their dialogs open while an interrupted save is checked automatically against the authorized checkout list. A complete return response updates the visible row immediately. Partner Pawsport notes and confirmed authenticator or passkey changes also update the page without a full list reread. When a result cannot be identified safely, the action stays locked and shows the next support step.
Impact
Asset operators, partner registry staff, and account holders can keep their place after a save. They do not need to trigger a saved-state recheck or submit the action again.
Validation
Local browser fixtures covered one-write checkout recovery, note receipts and interrupted responses, account factor checks, and scope loss. Partners typecheck and production build passed, and the linked Pages build succeeded. Hosted signed-in saves remain to verify.