Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Faster direct entries and automatic feedback save checks
Repository: Partners. Status: Linked release passed; signed-in request ordering verified.
What’s Changed
Direct visits to the Dashboard and Finance Payables begin their first approved data reads while the workspace code loads. Planning My Work does the same for the active partner. EMS Feedback Triage continues checking an uncertain note or status save automatically until it can confirm the saved state.
Impact
Operators should see these workspaces populate sooner. A feedback form stays in place during a save check, and repeat submission remains locked until the result is known. No action is required.
Validation
Focused browser checks covered slow workspace code, access denial, partner scope changes, fresh Refresh, and an uncertain feedback note with seven readback attempts and one write. Partners type checking, production build, and the linked release passed. On a separate signed-in hosted Dashboard visit, the home, open-report, and survey reads started 6–7 ms after access. This verifies request order on that visit; a controlled total-load improvement remains unproven.
Friends and Dealers Den drafts open sooner
Repository: Rego. Status: Linked Pages build passed.
What’s Changed
The Friends page now accepts a username draft while its first account settings load, then keeps the text and keyboard focus when search becomes available. A Dealers Den applicant can enter a table name and description after the current application information confirms the same published event, while the full event check continues.
Impact
Attendees can begin these fields sooner. Searching Friends still requires current enabled settings. Dealers Den steps, uploads and submission still require current event and account checks. No action is required.
Validation
Rego typecheck, production build and focused mobile/desktop browser fixtures passed. The fixtures covered disabled Friends, failed reads, account switching, held event details, denied or changed events, no early Dealers Den writes and one-document navigation. Hosted signed-in timing remains unverified.
Rego forms open sooner on first use
Repository: Rego. Status: Linked Pages build passed.
What’s Changed
After sign-in, the first destination can reuse the profile read that selected it, while the current MFA and account checks still run. Fursona details can be drafted while the saved list loads; saving and image uploads become available after the account read succeeds. Event feedback starts loading its question editors alongside the form request so opening a category has less to fetch afterward.
Impact
Attendees should reach profile setup or their destination with fewer duplicate reads, start a Fursona sooner, and begin a feedback form with less wait. A failed Fursona list check keeps the draft for retry. No action is required.
Validation
Rego typecheck, production build and focused mobile/desktop browser fixtures passed. The sign-in fixture covered complete and incomplete profiles, an MFA challenge, account switching, profile mutation invalidation and email-link callbacks. Fursona and feedback fixtures covered held reads, inline retry, retained drafts and one-document navigation. Hosted signed-in timing remains unverified.
Rego return visits keep useful content on screen
Repository: Rego. Status: Linked Pages build passed.
What’s Changed
Returning to an event’s Merch page now shows recently viewed item details while current availability and prices are checked. Opening a transaction from the attendee’s history shows that exact registration or order summary while its current detail loads. Affiliate payout fields can be filled during a same-account access check, and the typed draft remains in place when the fresh response arrives.
Impact
Attendees can recognize the item or transaction and prepare payout details without waiting on a blank page. Current event, account, price and payout checks still control Shop links, transaction actions and saving. No action is required.
Validation
Rego typecheck, production build, route contract and focused mobile/desktop browser fixtures passed. A held Merch read showed its preview in 53 ms on a same-account return, hid it after an account switch and removed it after a fresh denial. Transaction and affiliate fixtures confirmed account isolation, one-document navigation, no early save and retained typed fields. Hosted signed-in return timing remains unverified.
More partner workspaces start loading with access approval
Repository: Partners. Status: Linked release passed; signed-in request ordering verified.
What’s Changed
Finance Payables, Receivables, Budgets, and Close now begin their first records and event reads as soon as access is approved. EMS Event Details starts its details and linked-work reads together. Pawsport Overview and Registry begin their first scoped read while the page opens. These workspaces reuse the initial response when their page mounts.
Impact
Operators should spend less time waiting on direct visits. Refresh and saved-state checks still obtain current data while keeping existing work visible. No action is required.
Validation
Focused browser fixtures covered denied access, partner and event scope, slow reads, route loading, a late access callback, fresh Refresh, and automatic save checks. Partners type checking, production build, and the linked release passed. Separate signed-in hosted warm visits started Payables, Pawsport Registry, and Test Event Details first reads 3–4 ms after access. A first Payables visit still waited on cold code delivery, so a controlled whole-page speedup remains unverified.
Dashboard activity and Expenses open sooner
Repository: Partners. Status: Linked release passed; signed-in request ordering verified.
What’s Changed
The main Dashboard starts its survey and open-report activity reads while its overview loads. Finance Expenses starts its records, events, cash custody, and account reads together and reuses the event response. Upgrade reviews keep their loaded queue visible during refresh and automatic saved-decision checks.
Impact
Partner operators should see activity and expense information sooner on direct visits. Refresh obtains current data, and an uncertain upgrade decision checks its saved state automatically while further decisions remain locked. No action is required.
Validation
Focused access, scope, held-read, refresh, and save-reconciliation browser fixtures passed. Partners type checking and production build passed. On separate signed-in hosted warm visits, Dashboard activity reads began 6–7 ms after access and Finance Expenses’ four reads began 4–5 ms after access with one events request. First visits still waited on cold code delivery, so a controlled whole-page speedup remains unverified.
Dashboard access timing is easier to diagnose
Repository: Partners API. Status: Hosted timing headers verified.
What’s Changed
The access response now includes broad authentication timing alongside its existing data-loading timing. This helps the operations team identify where an occasional slow dashboard entry is spent.
Impact
There is no change to sign-in or partner access. Partners do not need to take action.
Validation
API type checking and focused Partners and Admin access fixtures passed, including unsuccessful access responses. A later signed-in hosted access response contained the new authentication timing fields alongside the existing total and data timings.
Event Shop item and category removal
Repositories: Partners, Partners API, Rego. Status: Released through Git-linked builds; authenticated hosted deletion remains to verify.
What’s Changed
Event operators can now choose a clearly warned force-delete option for shop items and categories that are still in use. The built-in All Items view is always available and shows every shop item, including uncategorized items. Deleting a category leaves its items in All Items; deleting an item removes it from active carts while past orders retain their item details.
Impact
Operators should review the warning before force deletion, especially where carts or inventory reservations exist. Attendees can continue browsing the full catalog through All Items.
Validation
Partners and API type checks, a three-width shop configuration browser fixture, the Partners build, and Rego and Docs checks passed. The targeted database migration was applied and its foreign key, nullable column, trigger and migration history were verified remotely. Linked API, Rego, and Partners builds passed. The hosted Partners shop route served the same entry assets as the validated local build. An authenticated hosted deletion remains unverified.
Faster Rego shops, event entry and profile saves
Repositories: Rego and Partners API. Status: Linked API Worker and Rego Pages builds passed; hosted public event readback passed.
What’s Changed
Published event pages now begin their current event read directly from the page while the rest of the app loads. Event Shop shows public item names and prices as soon as its catalog is ready, then enables cart and checkout only after the current event is checked. Attendee profile setup saves the chosen username with the profile in one request, so the saved form no longer waits for two follow-up calls.
Impact
Attendees can recognize the event and browse Shop items sooner, and profile saves complete with fewer network trips. Archived or draft events do not return a public Shop catalog. Current account, publication, event and checkout checks still control protected actions. No action is required.
Validation
API and Rego type checks, a Worker dry build, a Rego production build and focused mobile/desktop browser fixtures passed. The fixtures confirmed one document and current event, gift and Shop gates, plus one profile PUT that retained newer form edits. Both linked builds passed. Hosted event HTML contained the inline read, and three small mobile samples reached current event content in 461–596 ms; an earlier first sample took 1,189 ms. Authenticated profile saves and broader first-use timing remain unverified.
Faster Rego event returns and account pages
Repository: Rego. Status: Source pushed; linked Pages build passed.
What’s Changed
Returning to a recently viewed event shows its last public overview while current publication and registration details load. Account Security opens the password form while separate authenticator status loads and keeps a typed draft if that status read fails. Gift redemption no longer waits for unrelated saved registration prefill. The Profile event-registration card now opens the attendee’s registration list directly, while bookmarked links to a particular rego still open its detail.
Impact
Attendees see useful event and account content sooner, keep their password form in place, and avoid an error when opening registrations from Profile. Current account, gift, event and authenticator checks still govern protected actions. No action is required.
Validation
Local typecheck, sanitized build and focused mobile/desktop browser checks passed. A held event read showed the last viewed overview in 44 ms on same-document return, with no registration controls until the live response. Account Security retained typed password fields through a delayed or failed authenticator read and saved without a page reload. Gift redemption made no prefill request while current event and gift reads stayed required. The Profile card and historical redirect reached the right registration view in one document. Hosted signed-in timing remains unverified.