Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Maintenance completion rechecks itself; Forecasting reads overlap
Repositories: Partners, Partners API. Status: Partners 1ac43360 linked Pages and Partners API c47b7267 linked Workers builds passed.
What’s Changed
After a confirmed Maintenance work-order outcome, Partners automatically rechecks the exact authorized detail and current list. Existing rows remain visible and repeat actions stay locked during the check; an access denial clears protected data. A later evidence upload failure is reported separately without repeating completion. Forecasting now looks up the latest saved vintage while it reads current source data, then waits for that result before saving any requested domain. Requests that do not persist a result continue without a vintage lookup.
Impact
Asset operators can confirm completed work without manually rechecking or refreshing the page. Event operators may receive Forecasting results sooner. No action is required.
Upgrade Notes
Focused and existing maintenance browser fixtures, Partners typecheck and production build, a forecast deferred-read ordering fixture, API typecheck and build check, forecast certification, staged diff checks, Docs check, and both linked builds passed. One signed-in Test Event forecast reported 1,172 ms of application work, including overlapping source reads at 392 ms and vintage lookup at 550 ms. Server work and variation between visits prevent a controlled speed-gain claim. Hosted interrupted-save recovery remains unverified.
Count Sheet saves confirm automatically; Forecasting reuses event details
Repositories: Partners, Partners API. Status: Partners ab4f8576 linked Pages and Partners API 38edc612 linked Workers builds passed.
What’s Changed
After a Count Sheet batch is committed, Partners validates its receipt and automatically rechecks authorized audit counts. If the response is lost, a replayed committed receipt can still be reconciled against the original validation baseline without submitting a second batch. Forecasting now uses the event details it already read during access checks instead of looking up the same event again. Forecast controls keep their narrow access check, and scheduled forecasts retain their fallback read.
Impact
Asset operators can confirm a saved Count Sheet without refreshing the page or triggering another commit. Event operators may receive Forecasting results sooner. No action is required.
Upgrade Notes
The lost-response and existing audit browser fixtures, Partners typecheck and production build, event-reuse and access-projection fixture, API typecheck and build check, event forecasting certification, staged diff checks, Docs check, and both linked builds passed. Two separate signed-in Test Event forecasts reported 3,072 ms and 1,047 ms of application work; the first included 1,316 ms of vintage writes and 1,039 ms of source reads. This variation does not establish a speed gain. Hosted interrupted-save recovery remains unverified.
Shop and application previews load sooner; notification reads stay saved
Repository: Rego. Status: 6cb6adf0 pushed to main; linked Pages build passed.
What’s Changed
The first Shop image starts promptly while later catalog images load as they come into view. Your applications can show the account’s already loaded volunteer history while current status checks finish. After a notification is marked read, a delayed list or count response no longer makes that known item appear unread again.
Impact
Attendees can see useful Shop and application content sooner and keep their place after marking notifications read. New notifications still appear unread. No action is required.
Upgrade Notes
Rego typecheck and production build passed. Mobile and desktop browser fixtures covered a 100-item Shop, held application reads, and delayed single and bulk notification readbacks with one document. Hosted signed-in timing is not yet verified. After a bulk read, a previously unseen item may briefly reflect an outdated API response until it settles.
Audit reviews recover in place and Forecasting reads overlap
Repositories: Partners, Partners API. Status: Partners 9a8c20e7 linked Pages and Partners API 0cc0c7f9 linked Workers builds passed.
What’s Changed
After a confirmed variance review or audit posting, Partners automatically rechecks the exact result and current audit counts through temporary failures or out-of-date reads. Existing rows stay visible and actions stay locked during the check; the write is not repeated. If access is denied, protected data clears. After checking event access, Forecasting reads its control settings and event details together. A stopped forecast reuses the event details already read.
Impact
Asset operators can see confirmed audit changes without a manual check or whole-page refresh. Event operators may receive Forecasting results sooner. No action is required.
Upgrade Notes
Focused and existing audit browser fixtures, Partners typecheck and production build, a forecast deferred-read ordering fixture, API typecheck and build check, Wrangler dry run, event forecasting certification, Docs check, staged diff checks, and both linked builds passed. One signed-in Test Event forecast reported 1,203 ms of application work, with overlapping event and control reads of 89 ms and 124 ms. A separate earlier visit reported 1,357 ms; these are not controlled speed measurements. Hosted interrupted-save recovery remains unverified.
Audit counts recheck themselves and Forecasting overlaps saves
Repositories: Partners, Partners API. Status: Partners 1dda7148 linked Pages and Partners API 20d2f50c linked Workers builds passed.
What’s Changed
After an audit count is saved, Partners automatically rechecks the exact result and current counts through temporary failures or out-of-date reads. Existing rows remain visible and repeat controls stay locked until the result is confirmed; the count is not submitted again. A later evidence upload failure is reported separately. Forecasting now persists independent requested-domain vintages together and waits for every write before returning the result or marking invalidation processed.
Impact
Asset operators can see a confirmed count without refreshing the page or manually rechecking it. Event operators may receive Forecasting results sooner. No action is required.
Upgrade Notes
Focused and existing audit browser fixtures, Partners typecheck and production build, forecast deferred-write ordering and failure fixture, API typecheck and build check, Wrangler dry run, Docs check, staged diff checks, and both linked builds passed. One signed-in Test Event forecast sample reported 1,357 ms of application work and 199 ms for vintage writes; a separate prior visit reported 1,607 ms and 370 ms. These are not controlled speed measurements. Hosted interrupted-save recovery remains unverified.
Rego attendee pages stay useful during slow checks
Repository: Rego. Status: 21804a3 pushed to main; linked Pages build passed.
What’s Changed
Staffing and Vollie can show the signed-in attendee’s last completed assignment view while a fresh roster check runs. Shift tracking waits for that check. After an accepted Pawsport claim, a timed-out or rate-limited details check keeps the saved credential visible and offers a read-only retry. Event item details remain readable if the enhanced viewer repeatedly fails to download.
Impact
Attendees can keep reading their assignments, credential or event details instead of losing the view during these delays. No action is required.
Upgrade Notes
Rego typecheck and production build passed. Local mobile and desktop Staffing, Vollie and event-detail browser cases, plus a Pawsport claim and retry case, passed with one document. The Pawsport case observed one enrollment write. Hosted signed-in timing and full save-flow coverage remain unverified.
Transit returns recheck automatically and Forecasting reads overlap
Repositories: Partners, Partners API. Status: Partners 7b93b343 linked Pages and Partners API 3652cddd linked Workers builds passed.
What’s Changed
After a confirmed Transit return, Partners automatically rechecks the authorized shipment list until the returned shipment appears, including through temporary failures or out-of-date reads. Existing rows stay visible during the check, and the return is not submitted again. Forecasting now overlaps independent current-event source reads with comparable-event lookup before reading the matching historical registrations.
Impact
Asset operators can keep working without refreshing the page or manually checking a saved return. Event operators may receive Forecasting results sooner. No action is required.
Upgrade Notes
The focused Transit browser fixture, Partners typecheck and production build, forecast deferred-read ordering fixture, API typecheck and build check, Wrangler dry run, staged diff checks, Docs check, and both linked builds passed. One hosted Test Event forecast reported 1,607 ms of application work, including 366 ms for comparables and 415 ms for the overlapping source phase. A separate earlier visit reported 1,743 ms; these are not controlled speed measurements. Hosted interrupted-save recovery remains unverified.
Rego pages show their destination sooner
Repository: Rego. Status: 38114b2 pushed to main; linked Pages build passed.
What’s Changed
Protected attendee links show the destination page name while the session is checked. Signed-in visitors can choose a current event registration tier while their profile and saved details load. Fursona image viewing loads its full-size viewer when an image is opened.
Impact
Attendees get useful page context during a direct visit and can begin choosing a registration tier sooner. Account data and registration actions still wait for the required checks. No action is required.
Upgrade Notes
Rego typecheck, production build, direct-entry route checks, and mobile and desktop registration and Fursona browser fixtures passed locally. These checks used intercepted API responses; hosted signed-in readiness and completed saves remain unverified.
Transit saves recover in place and Forecasting gains timing detail
Repositories: Partners, Partners API. Status: Partners a0c7ad86 linked Pages and Partners API 22abb06d linked Workers builds passed.
What’s Changed
After a confirmed Transit receipt or exception save, asset rows remain visible while Partners automatically rechecks the exact shipment or exception through a temporary failure or out-of-date read. It does not repeat the write. If a later evidence upload fails, the dashboard reports that separately from the saved Transit change. Partners API forecast responses now report duration-only timing for access, source reads, calculation, vintage persistence, and invalidation.
Impact
Asset operators can keep working without refreshing the whole page or manually checking a saved receipt or exception. Forecast timing helps support teams diagnose delays; it does not itself speed up the forecast. No action is required.
Upgrade Notes
The focused Transit browser fixture, Partners typecheck and production build, API typecheck and build check, a focused Hono timing fixture, Docs check, staged diff checks, and both linked builds passed. One hosted forecast response reported application work at 1,743 ms, source reads at 441 ms, access at 287 ms, vintage read at 292 ms, and invalidation at 242 ms. A separate signed-in disposable Event Details edit and restore each saved in the mounted form without a full document reload. These are individual observations, not controlled speed or interrupted-save proof; hosted Transit interruption remains unverified.
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.