Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Forecasting and notification setup open sooner; asset saves recover
Repository: Partners. Status: Partners 37cd5c11 linked Pages build passed.
What’s Changed
EMS Forecasting starts its first authorized read while its workspace route loads, alongside the chart modules needed to show the result. EMS Notification Config starts its event, Telegram, and Discord reads together during route loading. After confirmed Asset Audit Open or Transit dispatch and handoff saves, the dashboard automatically rechecks the current scoped list through a temporary failure or out-of-date result without repeating the write. Existing rows stay visible while it checks; denied access clears protected data.
Impact
Event operators should reach these workspaces sooner. Asset operators can continue reading their current lists after a save without a manual saved-state check or full-page refresh. No action is required.
Upgrade Notes
Held-route and saved-state browser fixtures, existing Forecasting, Notification Config, and Asset Audit regressions, Partners typecheck and production build, Docs check, staged diff checks, and the linked Pages build passed. In separate signed-in visits, Forecasting’s access-to-first-read gap was 325 ms before and 5 ms after release, while Notification Config’s was 315 ms before and 4–5 ms after. The post-release forecast read itself took 1.694 seconds. These request-order samples do not establish controlled whole-page load gains. Hosted interrupted-save behavior remains unverified.
Inventory opens sooner and notification readiness updates itself
Repository: Partners. Status: Partners 81b72141 linked Pages build passed.
What’s Changed
EMS Inventory Analytics and Tracking start their first authorized reads while their workspace routes load. Tracking also starts movement history alongside its main read. After a confirmed Telegram or Discord link or unlink, Planning checks personal notification readiness automatically through a temporary failure or an out-of-date result. The SMS draft stays in place while it checks; denied access clears protected data.
Impact
Event operators should reach inventory data sooner. Planning members can continue editing reminder settings while delivery readiness updates without a manual check or page refresh. No action is required.
Upgrade Notes
Held-route inventory and saved-readiness browser fixtures, Partners typecheck and production build, Docs check, staged diff checks, and the linked Pages build passed. In separate signed-in Test Event visits, the access-to-first-read gap for Inventory Analytics was 827 ms before and 3 ms after release; Tracking’s inventory and movement reads were 334–335 ms before and 4–5 ms after. These request-order samples do not establish controlled whole-page load gains. Hosted interrupted-save behavior remains unverified.
Rego returns to merchandise and account security faster
Repository: Rego. Status: 4e3e2e0 pushed to main; linked Pages build and hosted assets confirmed.
What’s Changed
Returning to event merchandise keeps recently viewed item names and descriptions visible while current availability is checked. Returning to Account Security shows the last same-account factor summary while a fresh status check runs. Security actions, current merchandise prices and Shop actions wait for verified responses.
Impact
Attendees can recognize their previous merchandise or security status sooner on an in-app return. No action is required.
Upgrade Notes
A local three-minute Merch return showed item names in 119 ms in one mobile fixture. Mobile and desktop security return, transient failure, retry and authenticator-removal fixtures passed, as did Merch transient and volunteering return checks. Rego typecheck, production build and linked Pages check passed; the hosted Merch and Account Security pages serve the new route assets. Browser behavior checks are local synthetic or intercepted cases; hosted signed-in timing and saves remain unverified.
Rego application history needs fewer API reads
Repository: Partners API. Status: d4538a1 pushed to main; linked Workers build passed.
What’s Changed
Application history now obtains event, department and position labels in its attendee-scoped read, avoiding a later group of label lookups.
Impact
Attendees may see their volunteer application history sooner. No action is required.
Upgrade Notes
API typecheck, focused response and ownership tests, a local read-only database relationship check, and the linked Workers build passed. Hosted signed-in latency and the separate public event-overview delay remain unverified.
Analytics opens sooner and saved lists recover in place
Repository: Partners. Status: Partners 859e895f linked Pages build passed.
What’s Changed
EMS Rego Analytics and Finance Analytics start their first authorized reads while their workspace routes load; denied access does not start those reads. After confirmed Planning Department saves, the dashboard automatically retries a temporary list refresh failure. Asset Operations Hub tasks, master records, custody, and quality actions, plus Asset Register intake and checkout, also recheck their current lists after confirmed saves. Existing rows stay visible during a temporary or stale read, and the write is not repeated. An access denial clears protected data.
Impact
Event and finance operators should reach analytics sooner. Planning and asset operators can keep reading their work after a save without a full-page refresh or manual saved-state check. No action is required.
Upgrade Notes
Admitted and denied analytics routes, temporary and stale saved-list reads, one-write counts, and partner switching passed focused browser fixtures. Partners typecheck and production build, Docs check, staged diff checks, and the linked Pages build passed. In separate signed-in visits, the access-to-first-read gap for Rego Analytics was 318 ms before and 6 ms after release; Finance Analytics was 314 ms before and 4 ms after. These request-order samples do not establish controlled whole-page load gains. Hosted interrupted-save behavior remains unverified.
Planning workspaces open sooner and configuration saves recover
Repository: Partners. Status: Partners cadd0eb7 linked Pages build passed.
What’s Changed
Planning Departments, Files, Gates, and Settings reuse the current authorized project read. Departments begins its member and workload reads while the workspace route loads. After a confirmed Event Configuration save, the workspace stays visible and automatically retries a stale or failed scoped read without repeating the write. Controls that could repeat the change stay locked until the current result is confirmed, and denied access clears protected data.
Impact
Planning operators should wait less when opening these workspaces and can keep working after a save while the current configuration is checked. No manual saved-state recheck or page refresh is needed. No action is required.
Upgrade Notes
Leader admission and Event Configuration recovery browser fixtures, existing leadership and settings regressions, Partners typecheck and production build, Docs check, staged diff checks, and the linked Pages build passed. In separate signed-in visits, Departments started workload and member reads 4 ms after its one project read ended; Files, Gates, and Settings each made one project read. These request-order observations do not establish controlled whole-page load gains. Hosted interrupted-save behavior remains unverified.
Rego shows more useful content during first checks
Repository: Rego. Status: f42c682 pushed to main; linked Pages build and hosted assets confirmed.
What’s Changed
The activity proposal page starts loading its question editor with the page and loads the Conditions of Entry editor when needed. A published event overview can show public pass type names while current event details load. Current event data still decides prices, availability and registration actions. The local route audit now defines 43 specific checks, including sign-in, profile setup, account security and event feedback.
Impact
Attendees may see pass type names sooner and encounter less delay when opening an activity form. No action is required.
Upgrade Notes
The four new route checks resolved 48/48 useful-content samples in a local mobile and desktop browser run. They used invented account, MFA and form responses. Activity return and draft-refresh browser fixtures passed. A separate published-pass preview fixture passed four mobile/desktop held-read, retry and removal cases with one document and no writes or page errors. Rego typecheck, production build with a reachable live API, and the social-metadata generator test passed. The linked Pages check passed, and the hosted event page serves the new route and discovery assets. Local checks do not prove hosted sign-in, faster live event reads or completed saves.
Rego notification and application reads start sooner
Repository: Partners API. Status: 1b85de0 pushed to main; a later Workers deployment was observed without a commit identifier.
What’s Changed
The attendee notifications page starts its default message and acknowledgement reads together. The full human-resources view reuses the account identity already established for the request.
Impact
Attendees may wait less for notifications and application history when those reads are slow. No action is required.
Upgrade Notes
API typecheck and focused notification and application-history tests passed. Hosted signed-in timing and exact deployment-to-commit attribution remain unverified; this change does not establish a faster event overview or completed save flow.
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.