Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Faster edits and account setup in Rego
Repository: Rego. Status: Source pushed and linked Pages build passed; hosted signed-in timing remains to verify.
What’s Changed
Opening an existing Dealer application now uses that application’s event details to load the current requirements without waiting for a separate event lookup. Attendee profile setup starts its security-policy check alongside the profile read. Visible transaction action links preload their page code before a tap; each action still checks current data when opened.
Impact
Dealers may reach their edit form sooner, and attendees may spend less time waiting in profile setup or when opening a transaction action. Existing forms and saves stay on the same page. No action is required.
Validation
Rego typecheck, a sanitized build, the 62-route contract, and invented browser checks for Dealer edits and profile setup passed. Three controlled mobile transaction runs showed a faster tap to the action page with preloading, without starting its data request early. The linked Pages build passed and the three affected hosted entry documents returned successfully. Hosted signed-in timing remains to verify.
Event and account pages begin useful work sooner
Repository: Rego. Status: Source pushed and linked Pages build passed; hosted signed-in behavior remains to verify.
What’s Changed
Direct links to publicly linkable, unlisted events now begin the event-detail read as the page opens. Moving from My Vollie Work to an application status page can show the same signed-in account’s recently loaded roster immediately while a fresh read checks it. If marking a Pawsport lost has an uncertain result, the page checks its saved status before offering another action; a confirmed result updates the current page.
Impact
Attendees may spend less time waiting for an event or their Vollie application status. Pawsport holders get a safer recovery path after an interrupted lost-status request, without refreshing the entire page or accidentally repeating the action. No action is required.
Validation
Rego typecheck, a sanitized build, the 62-route contract, and invented browser fixtures for event entry, Vollie status, and Pawsport readback passed. The linked Pages build and Docs content check passed. In one hosted browser trace, an unlisted event began its detail read about 163 ms after navigation, compared with about 699 ms before this change. Signed-in hosted behavior remains to verify.
Cloudflare email transport prepared
Repository: Partners API. Status: Prepared; sending provider unchanged.
What’s Changed
The API now has a Cloudflare Email Sending adapter ready for explicitly classified transactional messages, operator-reviewed EMS event email blasts, and EPS planning operations, plus a guarded real-delivery check command before switching providers. EPS messages include assignments, deadlines and overdue reminders, RACI roles, and workflow or requirement changes for people involved in an event plan; department invitations needed to join a specific plan are transactional. Organizers will apply a manual policy so EMS blasts carry operational updates for existing event participants, such as venue changes or cancellations. Promotional invitations and other campaigns must use a campaign-capable provider. This preparation does not change how current messages are delivered.
Impact
No action is required from recipients or partner teams yet. Workers Paid is still required before Email Sending can be enabled. Operators must then onboard the sending domain, configure credentials, establish the EMS blast review policy, review EPS message templates and recipients, and complete delivery checks before switching transactional and eligible EMS/EPS operational mail. An EPS message with an unknown provider outcome stops for manual reconciliation instead of automatic replay.
Validation
Local EMS/EPS mocked transport checks, EPS wiring certification, Worker type checking and dry build, and Docs checking passed. The EPS unknown-outcome stop was reviewed in source; provider delivery remains unverified. A public DNS readiness check confirmed the existing routing SPF, MX, DMARC, and aggregate-report authorization and identified the missing Cloudflare sending records on two resolvers. A hosted Cloudflare send, inbox placement, and Yahoo delivery test remain required before activation.
Dealer entry and attendee history load with less waiting
Repository: Rego. Status: Linked release succeeded; hosted signed-in timing remains to verify.
What’s Changed
Dealers Den registration now checks the attendee session before downloading its form. A temporary form-download failure offers an in-page retry. Rego and Dealers Den receipts begin checking owned onsite purchases while the main receipt loads. Sending a Friends request updates the visible result immediately, then checks the friendship summary without rereading unchanged settings and event attendance.
Impact
Visitors reaching a dealer registration link before sign-in download less code. Signed-in attendees may see onsite purchase details sooner and can continue using Friends after a confirmed request without a page refresh. No action is required.
Validation
Rego typecheck, production build, and route contract verification passed. The dealer direct-route preload fell from about 754 KB to 501 KB in the local build; browser fixtures covered anonymous and signed-in entry, failed-download recovery, assistant acceptance, and one document. Held-receipt fixtures confirmed one owned onsite-purchase read began before each receipt completed. Mobile and desktop Friends fixtures covered a confirmed request, stale or failed readback, and no extra settings or attendance reads. The linked Pages build succeeded. Hosted signed-in timing remains to verify.
Reports and event shop respond sooner
Repositories: Partners and Partners API. Status: Linked releases succeeded; broader signed-in timing checks continue.
What’s Changed
Reports Overview now starts its authorized first data request while the page code downloads. The event shop displays acknowledged category, listing, courier, rate, and removal changes in the current page immediately, then checks their saved state automatically. The API overlaps independent access, survey, and event-shop reads after the relevant admission and ownership checks.
Impact
Partners and event operators can reach Reports activity sooner and see shop changes without a full-page refresh. When a save response or follow-up read is uncertain, the shop pauses dependent changes and checks again automatically; it does not repeat the write. No action is required.
Validation
Local held-read browser checks covered the Reports request order, Shop Config receipts, automatic retry, and draft preservation. Access, survey, and shop API fixtures, Partners typecheck/build, and API typecheck/dry build passed. Both linked releases succeeded. In the signed-in Test Partners workspace, Reports began its overview read shortly after access completed, and a disposable Test Event shop category was saved, removed, and confirmed gone after reload without leaving the page. Separate timing samples do not establish a total-load speedup; broader role and route checks remain open.
Event hub and notification actions respond sooner
Repository: Rego. Status: Linked release succeeded; hosted signed-in timing remains to verify.
What’s Changed
Signed-in event pages now begin attendee activity and staffing reads while the event overview loads. On a settled final unread-notifications page, marking one notice read updates the page without another list request. The inbox still reconciles a newly arrived notice and restores a row if saving fails.
Impact
Attendees may see their event information sooner and can keep using the notification page immediately after marking a notice read. No action is required.
Validation
Rego typecheck and a local production build passed. A browser fixture held the event overview and confirmed that activity and staffing reads each began before it completed, with no duplicate reads. Mobile and desktop notification fixtures covered delayed and failed saves, no redundant final-page list read, reconciliation of a new notice, and one document navigation. The linked Pages build succeeded. Hosted signed-in timing remains to verify.
Survey setup and event reviews respond sooner
Repositories: Partners and Partners API. Status: Both linked releases succeeded. Wider hosted timing checks continue.
What’s Changed
The dashboard downloads sign-in controls only when they are needed and keeps larger Event Planning data out of unrelated pages. Survey creation can use authorized partner choices as soon as they arrive, without waiting for its analytics summary. An acknowledged EMS registration-transfer decision appears in the existing queue immediately, while the page checks its saved state automatically. Event details now request two independent catalog sections together.
Impact
Operators can reach useful controls sooner and see a confirmed transfer decision without a full-page refresh. If a transfer response is uncertain, further decisions stay paused while the dashboard rechecks automatically; it does not submit the decision again. No manual saved-state check is needed.
Validation
Held-read browser fixtures covered Survey owner choices and transfer decisions, including stale reads and one write per decision. A local production preview confirmed smaller route downloads. Partners typecheck, build, and linked Pages build passed, as did the focused API fixture, typecheck, dry build, and linked Worker build. A hosted Test Event detail read succeeded after release, but separate timing samples do not establish a speedup; broader route and role coverage continues.
More dashboard results appear while checks finish
Repository: Partners. Status: Linked Pages release succeeded; hosted timing remains to verify.
What’s Changed
Survey response counts and analysis controls now appear while reward history loads. Event Planning Files shows an acknowledged upload immediately, then checks its scan status and access controls automatically. EMS Upgrade Review shows an acknowledged decision in its existing queue while the queue rechecks saved state. These changes keep the current page visible without a full refresh.
Impact
Survey, Planning, and EMS operators can continue reading or working sooner. Reward creation, file downloads, and follow-up upgrade decisions remain unavailable until their relevant authorized reads confirm the state. No manual saved-state recheck is needed.
Validation
Focused browser fixtures held the secondary reads and checked the early content, automatic retry, and action gates. Partners typecheck, production build, and linked Pages build passed. Hosted timing and broader role and save coverage remain to verify.
Rego forms recover without replacing the page
Repository: Rego. Status: Linked release succeeded; hosted signed-in behavior remains to verify.
What’s Changed
Registration, gifting, and event feedback forms can retry a failed form-code download within the current page. Registration also retries its workflow reads without repeating the event overview read. The ordinary gift and registration entries still download only one form bundle.
Impact
Attendees can use Try again after a temporary loading failure without losing the current page or draft. After repeated download failures, Refresh page remains available.
Validation
Rego typecheck and a local production build passed. Isolated mobile and desktop browser fixtures verified recovery after a failed form download, one document during retry, and no unexpected writes. The gift and registration entries each fetched one form bundle on their normal signed-in paths. The linked Pages build succeeded. Hosted signed-in performance and recovery remain to verify.
Event pages need fewer database trips
Repositories: Partners and Partners API. Status: Database migration and linked API release succeeded; hosted public overview verified.
What’s Changed
Public Rego event overview pages now obtain their catalog, availability, add-ons, campaign eligibility inputs, and social benefit labels through one database snapshot. The API still applies the same public visibility, media, and registration rules. Checkout continues to check current eligibility when an attendee acts.
Impact
Attendees may see the event choices sooner, especially when several related reads previously added latency. No action is required. This does not change registration limits or campaign eligibility.
Validation
The database dry run listed only the new function, publication succeeded, and a second dry run found no pending migrations. Anonymous and authenticated database roles could not execute the function. An isolated Worker fixture produced exactly the same public JSON for an open event and 11 campaign and intent cases, including nonzero registration, gift, and add-on usage. API type checking and the linked Workers build passed. Six read-only hosted overview requests returned 200 and reported the new snapshot path; five warm samples had a 129 ms median Worker duration. Signed-in browser timing and varied event sizes remain to verify.