Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
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.
Asset overview and more saves respond sooner
Repository: Partners. Status: Source pushed and linked Pages build passed.
What’s Changed
Asset Overview now loads its page code while dashboard access is checked and starts its owned, loaned, and summary reads as soon as the current partner is authorized. Renewed asset checkouts show the confirmed return date before a quiet saved-state check completes. Saved registration prefills show confirmed revocations immediately; uncertain outcomes are checked automatically without repeating the revoke. LAN snapshot history keeps its page visible while retrying a failed first read.
Impact
Partner and event operators can read these workspaces sooner and keep working after a confirmed save without a page refresh. If a prefill revoke result remains uncertain, the action stays locked while visible-tab checks continue. No action is required.
Validation
Focused browser fixtures covered denied and wrong-partner Asset reads, immediate saved results during held or stale background reads, automatic uncertain-save checks, and the LAN history retry. Partners typecheck, production build, and linked Pages build passed. A signed-in Test Partners Asset visit before the change started its first asset reads 1,284 ms after access completed. A first post-release visit had a 246 ms gap; a repeat with cached code had a 3 ms gap. These separate visits show improved request ordering but do not establish a controlled cold-load result. Wider route, role, and save certification remains open.
Rego sign-in and Vollie status respond more smoothly
Repository: Rego. Status: Source pushed and linked Pages build passed; hosted signed-in behavior remains to verify.
What’s Changed
The sign-in page now checks browser passkey support after it becomes interactive, preventing a mismatch that could make the page redraw during opening. A returning attendee’s Vollie application status remains visible while Rego checks the current record in the background. New saves and account changes still use current, account-scoped data.
Impact
Attendees should see a steadier sign-in page and can read their Vollie status immediately when returning to it. No action is required.
Validation
Rego typecheck, production build, and the 62-route contract check passed. Local mobile and desktop browser checks held the Vollie status read, confirmed the visible application stayed in place, rejected an older result after a simulated update, and hid it after an account switch. Signed-out sign-in and signed-in redirect checks completed without hydration errors. A local timing report covers six routes with route-specific readiness checks and identifies limits of the broader route survey; hosted signed-in speed remains to verify.
More dashboard saves stay on screen
Repository: Partners. Status: Source pushed and linked Pages build passed.
What’s Changed
Social Publishing begins its partner-authorized overview read as soon as dashboard access is confirmed, while the workspace code loads. Planning Department edits and Event Management refund decisions now appear from confirmed save responses before their background checks finish. Asset Maintenance pause and reassignment update the visible work order before an automatic exact-record check. A Planning Risk create response can confirm the save even when the database normalizes optional fields.
Impact
Partner operators can keep working in these registers without a page refresh after a confirmed save. If a save response is missing or uncertain, the dashboard checks saved state automatically and does not repeat the write. No action is required.
Validation
Focused browser fixtures covered Social Publishing admission and duplicate-read prevention, visible Planning/Refund/Asset save results during held background reads, and automatic checks after interrupted writes. Partners typecheck, production build, and linked Pages build passed. A signed-in Test Partners Social Publishing visit before this change showed its first overview request starting 628 ms after access completed. One initial post-release visit had a 437 ms gap; on a repeat visit with cached assets, the request started 3 ms after access. These separate samples show request ordering but do not prove a controlled cold-load speedup. Wider route/role/save certification remains open.
Rego profile setup opens with saved account details
Repository: Rego. Status: Source pushed and linked Pages build passed; hosted signed-in timing remains to verify.
What’s Changed
Opening profile setup from the account profile now shows the current attendee’s details immediately. A fresh read updates the form in the background while preserving any edits made during that read. Switching accounts clears the saved view so details cannot cross accounts.
Impact
Attendees returning to profile setup see the form without waiting through another loading screen. They can keep typing while the page checks current details. No action is required.
Validation
Rego typecheck, the 62-route contract check, and a sanitized production build passed. A local mobile browser check held the fresh profile read, confirmed the form remained visible and typed edits survived, then switched accounts and confirmed an older response could not replace the new account’s details. Navigation stayed within one document. Hosted signed-in timing remains to verify.
Survey and operational edits keep moving
Repositories: Partners and Partners API. Status: Linked Worker and Partners Pages builds passed.
What’s Changed
Survey overview now starts its three scoped reads as soon as dashboard access is confirmed, while the workspace code loads. Opening a survey starts its analytics, responses, and rewards reads alongside the detail request. The API also reads three independent survey analytics collections together. Planning Risks shows confirmed edits immediately and closes confirmed creation before its register refresh; interrupted creation checks saved records automatically without submitting a second create. Point of Sale keeps the counter visible while it automatically rechecks an interrupted sale, without showing a foreground loading state for temporary read failures. Asset Maintenance shows a confirmed new work order in its register immediately; interrupted creation checks the saved record automatically without sending another create.
Impact
Partner operators should see Survey information sooner and continue working in Planning, Point of Sale, and Asset Maintenance without a page refresh after these actions. If a create or sale result cannot be attributed safely, its repeat action stays locked for review. No action is required.
Validation
Focused browser fixtures covered Survey request ordering and admission, Survey editor first paint, Planning confirmed and interrupted changes, a held and failed POS read without replaying a sale, and Asset Maintenance confirmed and interrupted creation. The Survey API fixture verified scoped admission, bounded reads, output, and error handling. API and Partners typechecks, production builds, and linked Cloudflare builds passed. A signed-in Test Partners Survey overview visit before this Partners change showed access ending at 1,087 ms and its first Survey requests starting at about 1,717 ms from navigation start. On one repeat post-release visit, access ended at 571 ms and all three Survey requests started at 574 ms. These separate samples show request ordering, not a controlled speedup. An initial post-release cold asset request took much longer; broader hosted timing and role/save coverage remain open.
Faster group edits and event shop entry in Rego
Repository: Rego. Status: Source pushed and linked Pages build passed; hosted signed-in timing remains to verify.
What’s Changed
In group registration, selecting another attendee now uses the confirmed save result for the current attendee and opens the next form without rereading the whole group. Direct event shop entry reuses its first event and catalog requests as the anonymous session check finishes; a returning signed-in visitor waits for the correct account before reading their cart.
Impact
Group organizers spend less time waiting between attendee forms, with the current draft kept on screen during the save. Visitors to the event shop avoid duplicate loading work. No action is required.
Validation
Rego typecheck, sanitized production build, group registration parity check, and mobile/desktop shop browser checks passed. A held group save kept the draft mounted, then selected the next member after one PATCH without a group GET. A held event read completed shop entry with one event GET, one shop GET, and one document. A pre-release hosted shop trace showed two of each GET; three post-release anonymous visits to the canonical shop route showed one of each and one document. That event’s shop is currently disabled, so these traces verify request count rather than checkout speed. Signed-in timing remains to verify.
Planning, shop, finance, and reports open sooner
Repositories: Partners and Partners API. Status: Linked builds passed; hosted request ordering verified for Planning.
What’s Changed
Event Planning warms its small read module during direct entry, begins first-screen reads as soon as access is verified, and shares nearby managed-plan navigation reads. Its API now reads independent timeline collections together and overlaps My Work membership lookups. Shop Orders shows an authorized queue summary before full details and confirmed save receipts in the current page, then checks uncertain saved state automatically. The Shop dashboard also rechecks totals after verified order or claim saves, when the tab regains focus, and periodically while visible. The EMS Staff Roster keeps its assignment grid visible without a foreground spinner during automatic saved-state checks. Finance Settings reuses its authorized access read and shows the canonical saved payment-account result without refreshing the page. Finance record decisions also show a verified result immediately; interrupted responses trigger bounded automatic checks, keeping the affected record locked if the result remains unreadable. Reports Overview now overlaps its own report and watchlist reads with sharing checks, avoids a duplicate grant read, and filters shared watchlist entries by each enabled sharing type, and pages complete report collections beyond the API row cap.
Impact
Partner and event operators can reach useful Planning and Reports information sooner and continue working after confirmed Shop and Finance saves. Uncertain Shop, roster, and Finance record saves recheck automatically without repeating the write or replacing the loaded view. An unresolved Finance record asks for audit review before another action. No action is required.
Validation
Focused local browser and API fixtures covered first-read ordering, one managed-plan navigation read across desktop and mobile, in-page save receipts, automatic reconciliation, Shop dashboard and roster held-read visibility, Finance record receipts and interrupted-response outcomes, scoped report sharing including disabled sharing types, complete 1,205-row synthetic report collections, Planning overlap and authorization, and proxy-safe Finance account responses. API and Partners typechecks and builds passed, as did their linked Worker and Pages checks. Signed-in Planning samples started My Work and timeline reads 24 ms, 16 ms, and 8 ms after access on separate earlier reloads. A later signed-in reload after the Planning API release ended access at 574 ms, timeline at 1,075 ms, and My Work at 1,176 ms from navigation start. Cold asset delivery varied, so these checks confirm request order rather than controlled total-load speed. Broader role-by-role save checks remain open.
Rego registration opens with fewer waits
Repositories: Rego and Partners API. Status: Linked Pages and Workers builds passed; broader signed-in timing remains to verify.
What’s Changed
Opening an event registration link now reuses its first event read when the account check finishes, avoiding a duplicate request during anonymous entry. If the event, gift, Dealers Den, or feedback form code temporarily fails to download, visitors can retry inside the page while their event details and entered work stay visible. The API starts the slower event-detail reads earlier while keeping the same response.
Impact
Visitors may reach registration sooner and can recover from a temporary form download failure without refreshing the whole page. Feedback responses retain their entered text during repeated download retries. No action is required.
Validation
Rego typecheck, production build, route-contract check, and local browser fixtures for registration, event details, gifts, Dealers Den, and feedback passed. The feedback check rejected three code downloads, then recovered on a fourth URL on desktop and mobile with the answer and document preserved. One hosted anonymous registration trace showed one event read, down from two in the earlier trace. Partners API typecheck, event-detail parity fixtures, and a synthetic latency check passed; its linked Workers build succeeded. The synthetic check measured a 528 ms to 391 ms median event-detail response for its controlled workload. Eight subsequent hosted public reads succeeded, with a 456 ms median Worker time versus 546 ms across five earlier reads; these small samples are directional rather than a controlled comparison. Signed-in journeys need further measurement.