Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Dashboard events and gift review open sooner
Repositories: Partners, Partners API. Status: Released through linked GitHub branches and the grouped-count database migration; authenticated production timing remains to verify.
What’s Changed
The dashboard shows authorized event links as soon as session access is ready. Protected pages show their layout while access is checked, without exposing partner information before authorization. EMS event counts now use a grouped database read for the selected partner, and Gift Review opens with a scoped page of gifts instead of loading the entire queue first.
Meeting note and minutes submissions automatically check the saved state after an uncertain response while keeping the draft visible and repeat submission paused.
Impact
Partner staff can reach event work sooner and keep context while gift pages or saved meeting records load. Gift filters and global search retain their existing scope.
Upgrade Notes
No action is needed.
Validation
Focused API and browser fixtures, type checks, production builds, and a read-only live grouped-count RPC check passed. The linked API and Partners builds passed, and the hosted Partners asset manifest matches the local release. Authenticated hosted route timing and complete sitewide save certification remain to verify.
Pawsport claims and registration receipts open sooner
Repository: Rego. Status: Released through the linked GitHub branch; authenticated hosted timing remains to verify.
What’s Changed
The Pawsport claim form is available while the attendee’s credential history loads. Entered codes stay in place when that read finishes or a claim needs correction. Registration receipts request upgrade, refund, and transfer status while the owned receipt loads, so those sections can settle sooner without waiting for another round of reads.
Impact
Attendees can begin a Pawsport claim sooner and keep working through a slow or failed credential read. A successful claim stays visible if an older read finishes later. Switching accounts clears the previous attendee’s credential and draft. Receipt actions still require the current authorized receipt and API policy. No action is needed.
Validation
Local typecheck, an isolated synthetic build, and browser fixtures passed. A delayed mobile Pawsport check confirmed one document load, draft preservation, duplicate-claim recovery, account isolation, and a successful claim winning over a late read. A delayed receipt fixture confirmed the three policy requests began before the authorized detail completed, with one request for each policy; the existing transaction-history fixture passed. The linked Rego Pages build passed. Authenticated hosted timing and a live claim or receipt action remain to verify.
Rego event, Shop, and registration pages start their reads sooner
Repository: Rego. Status: Released through the linked GitHub branch; authenticated hosted timing remains to verify.
What’s Changed
Direct links to published events begin loading current event details as the page opens. Event registration starts the attendee’s saved choices, gift, and waitlist checks alongside that event read. Event Shop loads the signed-in attendee’s cart alongside the event and catalog. The Gift page shows the published event name while it checks current gifting options. Cart quantity controls remain available during a pending save after the attendee’s cart has been confirmed.
Impact
Attendees see event context sooner and spend less time on opening screens. Registration choices, gift eligibility, prices, and checkout still come from current API responses. Switching accounts clears the previous attendee’s cart and saved registration data before the new account’s reads finish. No action is needed.
Validation
Local typecheck and an isolated synthetic production build passed. In paired mobile tests, published-event requests began around 90 ms instead of 219–282 ms; the signed-in live event title appeared at 295 ms instead of 465 ms. In a delayed Shop fixture, the cart request began at 475 ms instead of 1,158 ms. Mobile and desktop fixtures also checked registration read overlap, account switching, changed event IDs, Gift loading, and cart save ordering. Existing registration and Shop checks passed, and the transaction-history fixture now waits for its progressively loaded records before asserting the final count. The linked Rego Pages build passed. Authenticated hosted timings and a live purchase remain to verify.
Event counts and saved decisions update without interrupting work
Repositories: Partners, Partners API. Status: Released through linked GitHub branches and the report receipt database migration; authenticated production timing remains to verify.
What’s Changed
The EMS event list now fetches registration and waitlist counts through a focused API response. Event cards remain available while those counts arrive.
If a report submission response is lost, Partners checks an exact saved receipt automatically and keeps duplicate submission paused. Asset review keeps its pending requests and decision reason visible while it checks the recorded decision through an authorized history read. Neither recovery sends the write again.
Impact
Partner staff can open events sooner and continue seeing their work while saves are verified. Saved-state checks run automatically; no manual recheck is needed.
Upgrade Notes
No action is needed. The receipt applies to new report submissions made after this release.
Validation
Local type checks, production builds, API authorization fixtures, database migration checks, and browser fixtures passed. Authenticated hosted route timing and complete sitewide save certification remain open.
Rego applications, profile setup, and receipts respond sooner
Repositories: Rego, Partners API. Status: Released through linked GitHub branches; authenticated hosted timing remains to verify.
What’s Changed
Volunteer role selection now loads the public roles and the current attendee’s application status without assembling the organizer’s full staffing roster. Activity forms read their Conditions of Entry while the form loads. Profile setup checks username and phone eligibility together and reuses recent successful checks as you continue through the form. A double tap cannot skip a step, and edits made during validation remain in place instead of sending an older draft. Switching attendee accounts clears the old setup form and its pending checks.
Registration receipts show upgrade, refund, and transfer details as each read finishes. A slower onsite purchase history no longer holds all three actions behind one loading state.
Impact
Attendees can reach volunteer and activity forms, complete profile setup, and use receipt actions with less waiting. No action is needed. Profile saves stay within one browser document, and the receipt remains visible while supporting sections load.
Validation
Local type checks, builds, scoped API parity checks, and mobile browser fixtures passed. With synthetic database delays, the volunteer response improved from 147 ms to 73 ms and activity from 109 ms to 71 ms. Receipt policy actions appeared in 668 ms with an unrelated onsite purchase read delayed 1,800 ms. Profile fixtures confirmed one document load, concurrent checks, preservation of newer edits during save, and isolation after an account switch. The linked Partners API Workers and Rego Pages builds passed; authenticated hosted timings remain to verify. The existing transaction-history fixture still makes an immediate row-count assertion while its final source is loading; the transaction list was not changed here.
Report lists and enforcement reads are smaller
Repositories: Partners, Partners API. Status: Released through the linked GitHub branches; authenticated production timing remains to verify.
What’s Changed
Reports Directory and Person Profiles now read only the report fields needed for their lists. Bans and Watchlists use a focused enforcement response. These reads retain the existing partner permissions, shared watchlist grants, and adopted report access.
The EMS event list appears as soon as authorized access resolves, while registration and waitlist counts fill in afterward. Enforcement saves keep the list visible and automatically retry the saved-state read if a refresh fails; repeat actions stay paused until confirmation.
Impact
Partner staff can use event and report lists sooner, with less unrelated data downloaded. Saved enforcement work no longer interrupts the list view.
Upgrade Notes
No action is needed. Saved-state checks happen automatically.
Validation
Local type checks, production builds, API authorization fixtures, and responsive browser fixtures passed. Authenticated hosted route timing and full sitewide save certification remain open.
Report pages read only the report you open
Repositories: Partners, Partners API. Status: Released through the linked GitHub branches; authenticated production timing remains to verify.
What’s Changed
Report Detail and Edit now request the selected report from a scoped API read instead of downloading every visible operational row. Detail receives its history and related network-ban context; Edit skips those supporting reads. The Reports overview also uses the smaller activity response.
Profile setup checks username and phone eligibility together on final Save. The dashboard downloads legal documents and notice formatting code when a notice needs them, while checking for notices immediately. A blocking legal notice stays unavailable for acceptance until its full content has loaded and been read.
Impact
Partner staff should see report pages and profile save results sooner. Ordinary dashboard visits download less code when there is no legal notice to show.
Upgrade Notes
No action is needed. Saved-state rechecks after uncertain profile writes remain automatic, and report visibility still follows API authorization.
Validation
Local type checks, production builds, scoped API route tests, and focused browser fixtures passed. Authenticated hosted route timing and complete sitewide save certification remain open.
Rego Home and dealer registration open sooner
Repositories: Rego, Partners API. Status: Released through linked GitHub branches; authenticated hosted timing remains to verify.
What’s Changed
The Rego Home page starts its public event read while the page code loads, so anonymous visitors can see events sooner. Signed-in visitors continue to get a fresh list for their account. Approved Dealers Den applicants can open table registration from the event information response without waiting for a second full application read. Old registration bookmarks redirect directly to the current transaction detail page, including when profile setup is needed.
Impact
Visitors may spend less time waiting for event cards, table registration, and saved registration details. No action is needed; existing bookmarks continue to work.
Validation
Local type checks, builds, API authorization checks, and mobile browser fixtures passed. In controlled local tests, the Home page showed live event content at a 1,808 ms median versus 2,112 ms before, and the Dealers Den package form opened in 389 ms versus 1,433 ms with a delayed legacy application read. These timings are local comparisons, not hosted or authenticated performance proof. The linked Partners API and Rego deployments passed. The hosted Home page and warmup asset returned HTTP 200; public event discovery returned HTTP 200, and an anonymous Dealers Den information read exposed no owner registration projection. Authenticated hosted journeys and comparative timing remain to verify.
Dashboard entry and settings become responsive sooner
Repositories: Partners, Partners API. Status: Released through the linked GitHub branches; authenticated production timing remains to verify.
What’s Changed
The dashboard loads account recovery, profile setup, and legal pages only when opened, reducing the code needed for other pages. Protected sign-in checks access and authenticator status together and avoids a repeated access read after verification. Dashboard activity uses a smaller API response with only the records needed for its metrics and recent reports.
Event notification settings become usable when their saved configuration arrives while chat destinations continue loading. Report editing shows its page structure during the authorized read and no longer waits for organization directory details.
Impact
Partner teams should reach protected workspaces with fewer startup requests and see useful content sooner. Opening notification settings and report editing no longer waits on unrelated reads.
Upgrade Notes
No action is needed. Saved-state checks after uncertain writes remain automatic, and report editing still waits for authorization before showing fields.
Validation
Local production builds, type checks, and focused browser checks passed. A protected sign-in fixture reached the workspace with two access reads instead of three, and the dashboard overview used one compact activity read. Authenticated hosted timing and the complete sitewide save audit remain open.
Public Rego event lists check capacity sooner
Repositories: Partners database, Partners API. Status: Released through the database migration and linked API build; authenticated and comparative hosted timing remains to verify.
What’s Changed
Public event lists now read event details and registration and gift capacity counts at the same time. If an event appears between those database reads, the API retrieves its exact count before returning the list. The capacity count also covers events with no registrations and the event visibility used by the list.
Impact
People browsing events can receive the list sooner. Event capacity remains accurate while event publishing changes are in progress. No attendee action is needed.
Upgrade Notes
No action is needed.
Validation
An isolated database and API fixture checked 17 events, 2,515 registrations, 40 gifts, hidden-event behavior, and the missing-count fallback. Alternating 40-call local measurements lowered the list median from 18.1 ms to 12.4 ms. Partners database commit f06bff1 was published; Partners API commit 39d1c05 passed its linked Workers Builds check. A hosted public discovery check returned HTTP 200 on all 10 requests. Its nine warm application measurements had a 143 ms median; those requests used different conditions from the earlier baseline, so they do not establish a hosted speed gain. Authenticated list behavior and comparative hosted timing remain to verify.