Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Shop transaction history opens with one account read
Repository: Rego. Status: Released through the linked GitHub branch; hosted signed-in history remains to verify.
What’s Changed
The attendee transaction page now loads Shop order cards through the account-wide summary API. Its first page no longer waits for public event discovery or requests orders separately for each event. Attendees can load older Shop orders on demand, while an individual event receipt still opens through its event-specific detail.
Impact
Shop history can appear sooner, especially for accounts with orders across several events. Retry keeps already loaded transaction cards visible while checking again; overlapping or late page responses cannot replace newer results.
Upgrade Notes
No action is needed.
Validation
Rego typecheck, a localhost-configured production build, and a synthetic mobile browser fixture for pagination, retry, and held responses passed. The fixture observed no legacy per-event Shop index requests. The linked Cloudflare Pages check succeeded. Hosted signed-in order history and production latency remain to verify.
Attendee Shop order summaries gain one API read
Repository: Partners API. Status: Released through the linked GitHub branch; Rego history integration and hosted authenticated checks remain open.
What’s Changed
The API now offers an account-owned list of Shop order summaries across events. It resolves the attendee from the signed-in session, returns only history-card fields and event labels, caps each page, supplies a next-page offset, and prevents response caching. Event-specific order detail remains the source for full records.
Impact
This prepares Rego transaction history to load Shop order cards without fetching orders one event at a time. The attendee history page has not yet switched to this endpoint.
Upgrade Notes
No action is needed.
Validation
API typecheck and an isolated local Worker/database fixture covered account isolation, signed-out rejection, pagination, limited response fields, invalid pages, and no-store headers. The linked Workers Builds check succeeded; a hosted signed-out request returned 401. Hosted signed-in order retrieval and Rego history integration remain to verify.
Shop orders and partner settings respond sooner
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Event Shop Orders, Finance Settings, and Planning Requirements now show scoped controls while their first data read completes. Loaded orders, requirement rows, selections, and drafts remain visible during later refreshes. When an account or order save response is uncertain, the workspace automatically checks current state with read-only requests and does not repeat the write.
Impact
Partners can navigate and start safe searches sooner. Repeat account and order actions stay locked until an attributable saved result is confirmed. A cash account creation with no identifiable receipt stays locked to avoid creating a duplicate.
Validation
Focused local browser checks covered slow first reads, retained drafts, and automatic save checks; the Shop Orders ownership fixture passed 30 cases. Partners typecheck and production build passed. Authenticated hosted route timing and full dashboard save certification remain open.
Rego event detail needs one fewer data read
Repository: Partners API. Status: Released through the linked GitHub branch; hosted latency remains to measure.
What’s Changed
The public event detail API reuses tier social-benefit fields already returned with the event instead of requesting the same tier records again. Its public response keeps the same shaped benefit information without exposing raw community identifiers.
Impact
Event detail can finish with one fewer backend read. Attendees see the same tier information and registration rules.
Upgrade Notes
No action is needed.
Validation
API typecheck, synthetic social-benefit parity and identifier-leak checks, inclusion-selection checks, and a local two-read versus three-read comparison passed. The linked Workers Builds check succeeded. A hosted read-only event detail returned 200 without raw community identifier keys. Hosted latency and active variation-group behavior remain to verify.
Rego registration and direct links open more smoothly
Repository: Rego. Status: Released through the linked GitHub branch; authenticated hosted timing remains to verify.
What’s Changed
The existing-rego check starts alongside profile and prefill reads when an attendee opens registration, then its result is reused in the form. Direct /404 links show the intended unavailable-page message. The route inventory identifies staffing and volunteering as signed-in pages, and the third-party notices table fits narrow screens with horizontal scrolling inside the table.
Impact
Registration can become ready sooner without skipping the current API check for an existing rego. Direct links give clearer guidance, and attendees can read legal notices on a phone without the whole page widening.
Upgrade Notes
No action is needed.
Validation
Rego typecheck, a localhost-configured production build, route-contract check, held-profile registration fixture, and anonymous direct-entry browser sweep across 62 routes at 390 px and 1440 px passed. The linked Pages check succeeded. A hosted read-only check confirmed the /404 message after hydration and no document overflow on the notices page at 390 px. Authenticated hosted registration timing remains to verify.
Rego notification counts and feedback stay current
Repository: Rego. Status: Released through the linked GitHub branch; hosted authenticated journeys remain to verify.
What’s Changed
After a notification is marked read, the inbox keeps its current content visible and checks the unread total again. A count response that started before the action cannot replace the saved count. Event feedback forms are isolated by event, and a late response from a previous event cannot fill the current form.
Impact
Attendees see a current unread count without a page refresh and can move between event feedback forms without carrying over another event’s data.
Upgrade Notes
No action is needed.
Validation
Local browser checks held older notification and feedback responses and inspected mobile layouts. Rego typecheck and a localhost-configured production build passed; the linked Pages check succeeded. Hosted authenticated notification actions and feedback journeys remain to verify.
Payments and planning controls open during reads
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Finance Reconciliation, event Payment Config, and Planning Schedule now show their scoped search, section, and view controls while the first data read is in progress. Loaded statements and schedule boards remain visible during refresh, and payment drafts stay in place. Uncertain payment settings and schedule changes automatically check saved state through read-only requests without repeating the write.
Impact
Partners can start safe searches and choose a calendar or board view sooner. A payment save unlocks only when both its settings and provider records match the submitted state. Schedule decisions remain locked while their outcome is uncertain.
Validation
Focused local browser checks covered slow first reads, refresh preservation, and automatic saved-state checks. Existing reconciliation and calendar workflow checks, Partners typecheck, and production build passed. Authenticated hosted route timing and full dashboard save certification remain open.
Accounting, shop, and finance pages open sooner
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Finance Payables, Receivables, Expenses, Budgets, and Close; EMS Accounting; and event Shop Config now show scoped navigation, search, and filters while their first records load. Loaded records, editors, and drafts stay visible during later refreshes. When a save response is uncertain, the workspace automatically checks current state with read-only requests without repeating the write.
Impact
Partners can start safe searches and move to the right section sooner. An uncertain financial entry stays locked when the API cannot identify the original writer, protecting against duplicate submissions. Shop changes unlock only after the submitted state is confirmed.
Validation
Focused local browser checks covered held reads, retained drafts, and automatic checks after uncertain saves. Partners typecheck and production build passed. Authenticated hosted route timing and full dashboard save certification remain open.
Rego home, profile setup, and Shop respond sooner
Repository: Rego. Status: Released through the linked GitHub branch; hosted authenticated journeys remain to verify.
What’s Changed
The public events home can show its published event cards or empty state before JavaScript finishes loading, then checks the live list. Profile setup starts profile, account-security, and social-setting reads together. After a successful save, new data reads use a fresh request. Event Shop checkout validation uses the current verification token and discards a validation response if the cart or checkout details changed while it was pending.
Impact
Attendees can see event choices and begin profile setup sooner. Saved changes no longer inherit a read that started before the save. Shop totals and checkout controls stay tied to the latest cart, details, and verification state.
Upgrade Notes
No action is needed. Published event cards are a starting view; current availability and checkout decisions still come from the API.
Validation
Rego typecheck, a localhost-configured production build, discovery snapshot checks, a held pre-save read fixture, profile setup checks, and paid Shop delivery and pickup fixtures passed. Sixteen first-paint browser cases covered 390 px and 1440 px routes. The linked Pages check succeeded; the hosted home, profile fallback, and a public event page returned 200. The current hosted home shows the published no-upcoming state. Hosted timing and authenticated checkout behavior remain to verify.
Finance, My Work, and EMS controls appear sooner
Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.
What’s Changed
Finance Transactions and Outflows, Planning My Work, EMS Coupons, and EMS Settlements now show scoped navigation, search, or filters while their first data read is in progress. Loaded records and drafts stay visible during later refreshes. Uncertain saves automatically check current state through read-only requests without repeating the write.
Impact
Partners can orient themselves and start safe searches sooner. Financial decisions remain locked until the saved response identifies the exact action. My Work decisions with no identifiable write receipt also remain locked when the outcome is uncertain, protecting drafts from duplicate submissions.
Validation
Focused local browser checks covered held reads and automatic saved-state checks. Partners typecheck and production build passed. Authenticated hosted timing and full dashboard save certification remain open.