Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Rego event timing shows where an overview request waits
Repository: Partners API. Status: b888775b pushed to main; hosted timing headers confirmed.
What’s Changed
The public event overview response now reports event_rpc_headers for the event snapshot request through upstream response headers and event_rpc_rest for the remaining RPC client work. The response content and event access rules are unchanged.
Impact
Operators can use the new response timing to narrow down slow event overviews before changing database queries or page behavior. No action is required from attendees.
Upgrade Notes
API typecheck and an isolated local Worker overview timing check passed. Five hosted event overview responses returned 200 with event_rpc_headers at 208–418 ms and event_rpc_rest at 0–58 ms. These samples identify where the request waited; this diagnostic change alone does not shorten it, and a controlled user-visible speed comparison remains pending.
Dealers Den drafts survive a temporary event check
Repository: Rego. Status: 5fc105ee pushed to main; hosted asset confirmed.
What’s Changed
The Dealers Den application keeps a typed table name and description visible when the current-event check fails temporarily. An in-page retry checks the event again and restores the ready form with the draft intact. Continuing remains unavailable until the latest event and account requirements load; a denied request clears the draft. The route readiness audit now defines 39 route-specific probes, including opt-in transaction-page fixtures.
Impact
Applicants can keep editing their table details through a temporary service issue without refreshing the page. Event operators can use the added local probes to check whether transaction pages show useful content while their data loads. No action is required.
Upgrade Notes
Rego typecheck, production build, and mobile/desktop production-preview browser checks passed for failed read, retained draft and retry, with one document and no writes. The new transaction probes passed 48 useful-content samples across four routes at mobile and desktop widths. The hosted build serves the new Dealers Den application asset. Browser checks used synthetic local responses; the hosted authenticated retry journey, signed-in speed, real transaction completion and provider-backed saves remain unverified.
Planning saves keep their place through temporary list failures
Repository: Partners. Status: Partners a443bf5f linked Pages build passed.
What’s Changed
After a confirmed write in Planning Schedule, Requirements, or Risks and Controls, the current workspace stays visible if its list refresh fails temporarily. The dashboard automatically checks the current list again without repeating the write. Controls that could change a stale record stay locked until the list confirms the result or access is lost.
Impact
Planning operators can keep reading their work after a save and do not need to refresh the whole page or trigger a saved-state check. No action is required.
Upgrade Notes
Focused browser fixtures covered one-write counts, temporary 503 and stale list reads, 403 access loss, and plan switching. Existing Planning fixtures, Partners typecheck and production build, Docs check, staged diff checks, and the linked Pages build passed. Hosted interrupted-save behavior remains unverified; local fixtures alone do not prove hosted save behavior.
More operational lists open sooner and drafts stay in place
Repository: Partners. Status: Partners 47a77f8b linked Pages build passed.
What’s Changed
Planning Schedule and Requirements, plus EMS Settlements and Shop Orders, start their first authorized reads while their workspace routes load. After a confirmed Planning removal, a temporary list refresh failure is retried automatically in place without sending the delete again. A temporary background access or token refresh failure keeps the current draft mounted while access is rechecked; a 401 or 403 authorization denial still removes protected data.
Impact
Planning and event operators should reach these lists sooner and can continue working through a temporary read failure without refreshing the whole page. No action is required.
Upgrade Notes
Planning leader/removal, EMS held-route, and session refresh browser fixtures, Partners typecheck and production build, Docs check, staged diff checks, and the linked Pages build passed. In separate signed-in visits, Settlements started its first read 348 ms after access on a first visit and 15 ms on a warm reload; Shop Orders started at 13 ms. Schedule and Requirements started their page reads 4 ms and 3 ms after their authorized project read ended, with no duplicate project read. These request-order samples do not establish controlled whole-page load gains. Hosted interrupted-save behavior remains unverified; local fixtures do not prove hosted authorization behavior.
POS opens sooner and session renewal keeps workspaces steady
Repository: Partners. Status: Partners 3d2aa4c6 linked Pages build passed.
What’s Changed
EMS POS starts three authorized first reads while its workspace route loads. Checkout stock still uses a current read. Renewing the same signed-in user’s session no longer restarts dashboard-wide access and workspace reads. Signing out or switching accounts still clears the prior user’s data.
Impact
Event operators should reach POS data sooner on a direct visit. Partner teams should see fewer loading resets during background session renewal. Checkout stock remains current, and no action is required.
Upgrade Notes
Held-route and denied-event POS browser fixtures, full POS regression, session-race fixture, Partners typecheck and production build, Docs check, staged diff checks, and the linked Pages build passed. A signed-in pre-change POS visit started its first reads 1,827 ms after access completed. In a separate post-release Test Event visit, its three first reads started 42–44 ms after access completed. These are request-order samples, not a controlled whole-page load comparison.
Rego event and merch previews survive temporary read failures
Repository: Rego. Status: Rego 8d4d9ed linked Pages build passed.
What’s Changed
Returning to an event or its merch page keeps the last viewed public description visible if a current-data check fails temporarily. An in-page retry fetches current details. Registration actions, merch prices and Shop links remain unavailable until Rego verifies the latest event and catalog data. A denied event or catalog clears the old view. The route readiness audit now has 35 specific probes, with additional local checks for registration and Dealers Den application entry.
Impact
Attendees can keep reading event and item information during a temporary service issue instead of losing the entire page to an error. No action is required.
Upgrade Notes
Rego typecheck, production build, mobile event-return and mobile/desktop Merch return browser fixtures passed. The new registration and Dealers Den samples use synthetic local form data, and their verification and submission steps were not completed. Hosted signed-in speed and provider-backed saves remain unverified.
Rego feedback drafts stay visible during a form check
Repository: Rego. Status: Rego 5afefbf linked Pages build passed.
What’s Changed
Returning to an event feedback form in the same browser document keeps its last public form and typed answers visible while Rego checks the current form. If that check fails temporarily, an in-page retry keeps the draft available. Submission waits for a successful fresh check; a changed form requires renewed review of the answers and Conditions of Entry.
Impact
Attendees can continue editing a feedback draft without waiting for the form to remount or refreshing the whole page. Current event rules still decide whether feedback can be submitted.
Upgrade Notes
No action is required. Rego typecheck, production build, and mobile/desktop local browser checks passed with one document and no page errors. Those checks used synthetic responses and did not submit feedback or measure hosted signed-in performance.
Feedback responses open sooner and Meeting edits refresh in place
Repository: Partners. Status: Partners 94475955 linked Pages build passed.
What’s Changed
EMS Feedback Responses starts its first authorized read while the workspace route loads. After a confirmed Planning Meeting edit, a temporary parent-list refresh failure is retried automatically in place. The edit stays locked until the list catches up, without sending the change again.
Impact
Event operators should reach feedback triage sooner on a direct visit. Planning operators can stay on the current page after editing a meeting without refreshing or repeating the save. No action is required.
Upgrade Notes
Direct-entry and delayed-refresh browser fixtures, Partners typecheck and production build, Docs check, staged diff checks, and the linked Pages build passed. A signed-in pre-change Feedback Responses visit started its read 338 ms after access completed. In a separate post-release Test Event visit, the read started 3 ms after access completed. These are request-order samples, not a controlled whole-page load comparison. Hosted interrupted-save behavior remains unverified.
Rego action forms stay open while current details load
Repository: Rego. Status: Rego a9cc2bf linked Pages build passed.
What’s Changed
Returning to an upgrade, refund or transfer form keeps that account’s last view and typed draft open while Rego checks current ownership and policy. Search, upload and submission stay paused until the fresh check succeeds. A temporary read failure offers an in-page retry; denied access clears the old view. Switching between gift events in one browser document now makes one current event read per event. The route timing audit now defines 32 route-specific useful-content probes, including opt-in Gift and Shop form fixtures.
Impact
Attendees can keep working in an action form through a background check without waiting for the whole form to remount. Gift navigation avoids an extra event request. Current server rules still decide whether an action can be submitted.
Upgrade Notes
No action is required. Rego typecheck, production build, mobile/desktop browser fixtures for action return, draft preservation, account isolation and gift navigation, and the linked Pages build passed. New useful-content samples passed on 14 routes in an isolated synthetic Worker, plus 24 Gift and Shop samples with locally supplied enabled-form data. The real MFA status check returned 503, so hosted signed-in speed and real save completion remain unverified. Transfer and Dealers Den forms still need usable local fixtures.
Attendee coupons open sooner and agenda lists recover after saves
Repository: Partners. Status: Partners cc66e096 linked Pages build passed.
What’s Changed
Attendee Coupons starts its authorized event and finance program reads after dashboard admission while the workspace route loads. After a confirmed Planning Agenda Item create, a temporary list refresh failure is retried automatically in place, including when the dialog closes, without sending the create again.
Impact
Event and finance operators should reach coupon data sooner on a direct visit. Planning operators can keep working after an agenda item save while the list catches up; no manual refresh is needed. No action is required.
Upgrade Notes
Held-route and denied-event Attendee Coupons fixtures, Planning delayed-save fixtures, Partners typecheck and production build, Docs check, staged diff checks, and the linked Pages build passed. A signed-in pre-change Coupon visit started its reads 1,092 ms after access completed. In a separate post-release Test Event visit, the event and finance program reads started 10–11 ms after access completed. These are request-order samples, not a controlled whole-page load comparison. Hosted interrupted-save behavior remains unverified.