Platform Updates

Repositories: Partners, Partners API, Rego, Docs. Status: Variant database migration applied; Partners, API, and Rego linked releases passed.

Event operators can set each Rego inclusion variant’s Shop name, description, image, category, price, sale status, purchase window, stock and preorder behavior, quantity limits, registration requirement, fulfillment, order, and buyer questions. A variant inherits its listing setting until an override is set. Rego inclusion availability now has its own button and modal on the main Shop Config page.

Operators should review inclusion availability and variant overrides before opening an event shop. Attendees see each available variant in its effective category and checkout uses its own price, questions, limits, and fulfillment rules. Local Partners, API, and Rego type checks and builds passed. Browser fixtures covered the operator modal and variant buyer journey at desktop and mobile widths. A rolled-back PostgreSQL fixture covered transactional variant limits, stock, preorder, registration, and fulfillment; the published migration and remote ledger were verified. Partners, API, and Rego linked builds passed, and the newest Worker version is deployed at 100%. Hosted checkout and payment remain to verify.

Repository: Rego. Status: Local checks and linked Pages release passed.

After an accepted authenticator removal, Account Security now removes its card immediately while checking the latest security policy. Returning to more than one event confirmation can show each attendee’s last known details while current payment status refreshes; a temporary read failure leaves a retry on the same page. Feedback response fields become usable while Conditions of Entry code loads, and a failed code download can be retried without losing a draft or refreshing the page.

Attendees can continue working during these reads. Current account and event data still control protected actions, Conditions acceptance and submission. No action is required.

Rego typecheck and production build passed. Local mobile and desktop browser checks covered held and failed reads, stale account responses, two confirmation returns, feedback draft recovery, a held submission and one-document saves. Hosted signed-in timing remains unverified.

Repository: Rego. Status: Local checks and linked Pages release passed.

On a return to the gift form, attendees can edit the receiver username and message while current event options refresh. Receiver checks, prices and later steps still wait for current results. Transfer recipient search now discards older results when a newer query is entered, so an outdated match cannot replace the current choice. A completed transfer stays within the same page.

Attendees can prepare a gift during a slow read and can trust that a transfer search reflects their latest query. No action is required.

Rego typecheck and production build passed. Local mobile and desktop browser checks covered held and failed gift reads, draft retention, stale transfer searches, delayed transfer saves and one-document continuity. Dealer Den entry checks also confirmed that useful headings appear while event details load. Hosted signed-in timing and provider completion remain unverified.

Repositories: Rego and Partners API. Status: Source pushed; hosted behavior remains to verify.

Attendees now see free emphasized in the event page’s prefill action and eligible tier cards, during registration, and after saving. A prefill does not reserve a place or collect payment, and attendees can change their tier and add-ons when completing registration.

For events that reserve capacity for gifts, active unredeemed gifts now count before a waitlist place is offered. This keeps offers aligned with places already promised to gift recipients.

Validation: Rego typecheck and production build, local mobile and desktop event page, prefill, and gift browser fixtures, Partners API type check, and the gift source certificate. Real isolated database and hosted gift workflows remain unverified.

Repositories: Partners, Docs. Status: Partners e66ebd9 and Docs 7a7f83a linked Pages checks succeeded; the hosted /updates marker appeared.

What’s Changed

Watchlists, Bans, and Finance Reconciliation start their first scoped reads as soon as signed-in access is approved, while their page code finishes loading. EMS registration configuration now keeps the operator’s draft after an uncertain save response and automatically checks the exact saved state without sending the change again.

Impact

Partner safety teams and finance operators may see useful records sooner on a direct visit. Event operators can leave an uncertain registration configuration save to be checked automatically; repeat submission stays locked until its outcome is known.

Upgrade Notes

No action is required. Focused local browser fixtures covered access admission, first-read reuse, and save recovery; Partners typecheck and production build passed locally. Separate signed-in Test Partners direct visits started Watchlists, Bans, and Finance Reconciliation first reads 4–5 ms after access completed. These samples confirm request order, not a controlled total-load improvement. The interrupted EMS save remains verified by a local delayed-commit fixture; hosted interrupted-save proof and broader role and route certification remain open.

Repository: Partners. Status: Linked Pages release passed.

Profile Settings starts its account read as soon as signed-in access is approved. Reports Enforcement reuses that approved access check. Finance Reconciliation shows statement imports and rows while cash-account status finishes loading; controls that depend on that status wait for it. EMS Staff Roster keeps loaded shifts and unsaved drafts visible during refresh. If a roster save response is interrupted, saved state is checked automatically and another write stays locked until the attempted change is confirmed.

Partner teams can keep reviewing the current work while background reads finish. No manual saved-state recheck is needed.

Focused browser fixtures, an account and scope prefetch check, typecheck, and the Partners production build passed locally; the linked Pages release passed. On two signed-in Profile Settings reloads, its profile read began 3–6 ms after access finished, compared with a 316 ms gap in one earlier warm sample. Separate Watchlists and Finance Reconciliation visits still had about 0.3–0.4 s between access and their first reads while route code loaded. These individual visits show request order, not a controlled total-load gain. Hosted interrupted-save checks and broader route coverage remain open.

Repositories: Partners, Partners API. Status: Pawsport receipt migration published; linked source releases passed.

Survey Manage starts its detail read when an operator points to or focuses a survey. Organization bot status starts loading alongside settings after account admission. EMS linked work keeps current event links visible during refresh and clears them on a scope change. Finance record actions and Asset custody moves keep their confirmed state visible while background reads retry. Pawsport bound issuance and Asset custody moves check exact saved-state receipts after an interrupted response without sending the write again. Organization Settings and partner appeal requests also confirm valid saves when submitted values already match the saved record.

Partner operators can continue reviewing these workspaces while background checks finish. Repeat actions stay locked when a write outcome is uncertain, and saved-state checks run automatically. An Asset move is rejected before writing if the browser cannot safely retain its recovery key.

Focused browser, database, and API fixtures, both type checks, the Partners production build, and the Worker dry build passed locally. The Pawsport receipt migration is published and its table and functions are present; both linked builds passed. On one warm signed-in Organization Settings reload, settings and bot status requests began together 4 ms after access finished. This single visit verifies request order, not total-load improvement. Hosted interrupted-save verification and full route coverage remain open.

Repository: Rego. Status: Linked Pages build passed.

Notification pages now show a clear checking message on first visit. When an attendee marks one or all notifications as read, the page keeps the current items visible and shows the read state after the save is confirmed. Volunteer shift start and end actions update the existing shift card as soon as the save succeeds, while current roster details refresh in the background.

Attendees can keep reading notifications and shift details without a full page refresh. A slow roster refresh does not undo a confirmed shift action. No action is required.

Rego typecheck and production build passed. Local mobile and desktop browser checks covered delayed notification saves, failed and stale reads, account changes, volunteer shifts, and one-document continuity. Four transaction history aliases also passed direct-entry and return checks. Hosted signed-in saves remain unverified.

Repositories: Partners, Partners API. Status: Database migrations published; linked releases passed.

Reports Overview now starts loading its workspace code while account access is checked and requests its scoped summary as soon as access is approved. Planning baseline approval and full meeting minutes keep the submitted draft on screen after an interrupted response, lock repeat submission, and check an exact saved-state receipt automatically. EMS Conditions of Entry now releases a form after a definite validation rejection while continuing automatic checks when a save outcome is uncertain. Confirmed changes update in place without a full page refresh.

Partner operators may see Reports sooner and can leave an uncertain Planning dialog while its saved state is checked. A rejected EMS form can be corrected without reloading. No manual recheck is needed.

Focused browser, API, and database fixtures covered admission, one-write recovery, receipt isolation, and a definite EMS validation rejection. Both type checks, the Partners production build, API dry build, Docs check, and both linked builds passed. The published receipt migrations match the remote ledger. On one signed-in hosted Reports visit, its component code finished before access ended and the overview request began 4 ms afterward; this verifies request order under that visit, not a controlled total-load improvement. Hosted interrupted-response saves remain to verify.

Repository: Partners API. Status: Source prepared; sending provider unchanged.

Every email sent through the planned Cloudflare transport will use noreply@comms.furries.ph as its From address. Existing workflow Reply-To addresses remain available, and the active Apps Script sender is unchanged. Operators must onboard comms.furries.ph in Cloudflare Email Sending and verify its DMARC, SPF, bounce MX and DKIM records before switching providers.

Local transport tests, API type check and Worker dry build passed. Public DNS checks still show the comms sending records are missing, so live Cloudflare delivery remains unverified.