Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Rego Home, Applications and communications respond sooner
Repository: Rego. Status: Linked Pages build passed.
What’s Changed
When the last published event list has no upcoming cards, Home now shows a clear checking state while the current list loads, instead of animated placeholders. Returning to Home keeps a current account’s last viewed list on screen, and account changes clear the old list. Applications displays the first 40 history cards, with more available on request. Communications skips Save when nothing changed and checks a fresh profile after an uncertain save response.
Impact
Attendees see useful context sooner on Home and large application histories. Preference saves avoid unnecessary waits and remain on the same page. No action is required.
Validation
Rego typecheck and an isolated build with invented event metadata passed. Focused mobile and desktop browser checks covered Home’s pending, new-event, empty, failed and account-switch states; a 180-record Applications history; and Communications saves with a delayed stale read. These flows stayed in one document. A separate read-only hosted event sample measured published preview and current event readiness separately; its mobile API-backed result still showed a long tail. Hosted signed-in timing and saves remain unverified.
Rego registration and transaction returns open sooner
Repository: Rego. Status: Linked Pages build passed.
What’s Changed
Registration returning from sign-in now reuses the recent profile check for the same account, avoiding a second profile request while the current event and saved draft still load. Transaction detail shows more of an attendee’s last viewed receipt or owned list summary during its fresh check. Current API data still controls transaction actions, and changing sessions clears private previews.
Impact
Attendees can reach registration choices sooner after sign-in and see more useful transaction information on return visits. No action is required.
Validation
Rego typecheck, a build with invented local event metadata, and focused mobile and desktop browser fixtures passed. The registration fixture reached an editable tier with zero additional profile reads and one document. The transaction fixture held fresh receipt reads and checked preview content, account isolation, and action gating in one document. Hosted signed-in timing remains unverified.
Planning opens sooner and more operations recover interrupted saves
Repositories: Partners, Partners API. Status: Database migrations published; linked releases passed.
What’s Changed
Planning Overview starts loading its workspace code while account access is checked. Meeting and agenda item creation now use exact request receipts to confirm an interrupted response automatically. Asset governed requests and quantity moves or consumption use the same automatic confirmation pattern. The database also prevents a repeated quantity request from applying stock changes twice.
Impact
Partner operators can keep their drafts on screen while an uncertain create or quantity action is checked. Repeat submission stays locked until the saved outcome is known. Planning Overview may open sooner on direct visits. No action is required after release.
Validation
Local browser fixtures covered route loading during access, access denial, retained drafts, and one write followed by read-only receipt checks. API and PostgreSQL fixtures covered scoped receipts and quantity replay protection. The migrations and linked releases passed. In one signed-in hosted reload, the Planning workspace code finished before the access check; this confirms request order, not a controlled whole-page speed gain. Hosted interrupted-response operations remain to verify.
Direct Rego Shop checkout opens while the cart is checked
Repository: Rego. Status: Linked Pages build passed.
What’s Changed
Opening a Shop checkout link now shows editable purchaser details as soon as the current event, shop and account cart are ready. The first live cart check runs alongside typing. Current stock, fulfillment, payment and final order checks still control progression.
Impact
Attendees with a saved cart can begin checkout sooner without waiting for the first cart quote to finish. No action is required.
Validation
Rego typecheck, production build and focused mobile and desktop browser fixtures passed. In a local built-preview fixture with a 1.2-second delayed first quote, purchaser fields appeared about 1.3 seconds sooner than the quote-gated Shop path. Changed stock, an empty cart, a closed or denied event, pending sync and account switching kept their existing gates; each flow used one document. Hosted signed-in timing remains unverified.
Profile setup checks interrupted saves in place
Repository: Rego. Status: Linked Pages build passed.
What’s Changed
If Profile Setup receives an uncertain save response, it checks the current saved profile while keeping the attendee’s form and newer edits on screen. Another save stays blocked until the result is confirmed or the attendee explicitly chooses to retry.
Impact
Attendees can recover a disrupted profile save without refreshing the page or immediately sending the same profile write again. No action is required.
Validation
Rego typecheck, production build and ten mobile and desktop browser cases passed. The cases covered an applied save, a rejected save, unavailable readback, optional address fields and a delayed commit; each sent one profile write and remained in one document. A late server commit can still race an earlier negative read, so Profile Setup keeps an uncertain result pending until another check or an explicit retry. Hosted signed-in save behavior remains unverified.
Asset master records recover interrupted creates automatically
Repositories: Partners, Partners API. Status: Linked releases passed.
What’s Changed
Asset categories, models, locations, parties, and custody agreements now record an exact request receipt when created. If a create response is interrupted, Partners keeps the form in place and checks the saved result automatically. The Worker and database scope each receipt to the partner and signed-in operator.
Impact
Asset operators can wait for confirmation without refreshing the page or submitting the same create again. Repeat creation stays locked while the original request is unresolved. No action is required after release.
Validation
Local browser fixtures covered all five master record types and custody agreement creation, with one write followed by read-only receipt checks. API route fixtures covered partner and operator isolation, duplicate-key rejection, and private uncached responses. Partners type checking and production build, API type checking and a dry build, and both linked releases passed. A hosted interrupted-response create remains to verify.
Linkable Rego events show their public details sooner
Repository: Rego. Status: Linked Pages build passed; hosted public preview verified.
What’s Changed
An event with a public link but no discovery card can now show its published title, poster and About summary while Rego checks current event details. The live event response replaces that preview and still decides registration access, prices and availability.
Impact
Attendees opening these event links see useful event information while the current check finishes. No action is required.
Validation
Rego typecheck, production build and focused mobile and desktop browser fixtures passed. The fixtures covered a delayed current event, denial, a missing event, campaign denial and an account change; the preview offered no registration action or pricing. A hosted read-only check held the event API response and saw the public preview in one document before the live result. A separate hosted sample compared cold and warm browser loads for one public event, with about 200 KB of JS and 19 KB of CSS transferred cold and no JS/CSS transfer on reload. Hosted signed-in timing and population-wide latency remain unverified.
Rego checks interrupted profile and Fursona saves
Repository: Rego. Status: Linked Pages build passed.
What’s Changed
Profile Preferences now checks the current username when that part of a save returns an uncertain result. Confirmed profile details stay on screen, and a retry does not repeat the completed profile write. If a Fursona create response is lost, Rego checks the saved list and keeps the draft in place. A still uncertain create requires an explicit choice before another save attempt.
Impact
Attendees can recover these saves without refreshing the page or reentering their details. No action is required.
Validation
Rego typecheck, production build, and focused mobile and desktop browser fixtures passed. The fixtures covered rejected and uncertain username responses, fresh readback failure, a delayed Fursona create, retained edits, one document, and no automatic duplicate create. A negative Fursona list read can still race a later server commit; guaranteed deduplication needs a server request receipt. A 62-route source inventory and read-only public event timing probe were added, but hosted signed-in save behavior and all-route latency remain unverified.
Faster workspace entry and automatic asset save checks
Repositories: Partners, Partners API. Status: Database published; linked releases passed.
What’s Changed
My Work, Asset Register, and EMS Waitlist now begin their authorized first reads while the page finishes loading. RSVP changes and Asset saved views keep their forms in place and check uncertain saves automatically. Hub Task, owned-asset, and Quality Hold creation use exact request receipts so an interrupted response can be checked without sending the create again.
Impact
Partner and event operators should see useful workspace content sooner on direct entry. During an interrupted save, the current draft stays visible and repeat creation remains locked until the original request is confirmed. No action is required.
Validation
Local browser checks covered delayed page code, first-read reuse, fresh refreshes, denied scopes, retained forms, and one create request followed by automatic read-only receipt checks. PostgreSQL receipt checks, API and Partners type checking, production builds, and linked releases passed. Signed-in hosted API reads returned private, uncached responses. On separate hosted visits, Asset Register and My Work began their first reads 6–7 ms after access finished; this confirms request order, while complete page-load and save certification remain open.
Interrupted event creation checks its saved result automatically
Repositories: Partners, Partners API. Status: Database published; both linked releases passed.
What’s Changed
Creating an event now records an exact request receipt. If the response is interrupted, Partners keeps the draft on screen and checks that receipt automatically. The form opens the created event only after the saved result is confirmed.
Impact
Event organizers do not need to submit a second event or refresh the page while the result is uncertain. The Create action stays locked until the original request is resolved. No action is required.
Validation
The database migration was published and confirmed in the remote migration ledger. Local checks covered repeated request IDs, changed requests, partner access loss, and one browser POST followed by five automatic receipt reads with no page navigation. API and Partners type checking, builds, focused browser and route checks, and both linked releases passed. A signed-in hosted lookup of a nonexistent receipt returned 404 with private caching disabled. A hosted interrupted-response creation remains to verify.