Platform Updates

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.

Repositories: Partners, Partners API, Rego. Status: Database migration applied; all three Git-linked releases passed.

Event operators can choose which Rego inclusions are eligible for Event Shop in the Shop listing editor. Inclusions with active variants can be listed with a separate shop price and sale switch for each variant. Attendees choose a variant before adding the item to their cart; checkout checks its current eligibility and price. Existing shop items without variants continue to use their listing price.

Operators should review inclusion eligibility and variant prices in Event Shop before activating listings. Partners, API, and Rego type checks passed; browser fixtures covered variant selection, distinct cart lines, and desktop and mobile editor layout. A rollback database fixture covered eligibility, price, shared stock, reactivation, and historical order identity. The API’s Git-linked build passed after a fixed public mail sender was moved out of the Worker variable budget. The resulting Worker version is deployed at 100%. Hosted checkout and payment remain unverified.

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

The prepared Cloudflare sender now checks its account and From-address configuration before reporting email as available. It preserves each message’s Reply-To address. Payment-account report alerts now send a separate email to each partner admin, staying within Cloudflare’s recipient limit and letting delivery failures be reviewed individually.

Local provider tests, API type check, and dry build passed. Cloudflare sending remains inactive; sending-domain DNS and live delivery still need verification.

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

When the planned Cloudflare Email Sending switch is enabled, it will cover the remaining email workflows, including attendee notices, Admin and Join communications, registration reminders, contact-form forwarding, payment alerts, and Social notifications. Apps Script remains the active sender for now. Staff will review each message against Cloudflare’s transactional-mail scope before sending; a source label or recipient consent does not determine eligibility.

Validation: local provider-routing tests, API type check, and dry build. Cloudflare account setup, live sending, and inbox delivery remain unverified.

Repository: Rego. Status: Linked Pages build passed.

What’s Changed

On a publicly linkable event’s registration page, including an unlisted event, an attendee can see which event is being checked and an anonymous visitor can start sign-in while current options load. Tier prices and availability still wait for the live event response. Direct Shop checkout now starts saved purchaser and country reads alongside the event, catalog and cart checks. Current stock, totals and payment steps still require fresh validation.

Impact

Attendees have a useful next step sooner when opening registration, and saved purchaser details can be ready when direct checkout opens. Existing Shop browsing does not gain these account reads. No action is required.

Validation

Rego typecheck, isolated builds and route-contract verification passed. Local mobile and desktop browser checks covered held event and country reads, registration sign-in without a page reload, preserved checkout fields, and the full checkout-entry regression flow. A synthetic unlisted event also passed the held-read registration check. A read-only hosted check showed the public registration heading and sign-in link before its event response on mobile and desktop. Hosted signed-in timing, final registration and payment completion remain unverified. Public API samples still showed variable event lookup time.

Repository: Rego. Status: Linked Pages build passed.

What’s Changed

Profile preferences and Communications now show their page context while saved account details are checked. Communications lists what each preference controls before its current values arrive. A deliberate hover, keyboard focus or tap on a registration transaction link can start its current detail read before navigation. Saving an unchanged fursona edit now finishes immediately without a request.

Impact

Attendees see less animated waiting on account pages, can reach a transaction receipt sooner, and avoid a needless fursona save wait. Current account data still controls editing and transaction actions. No action is required.

Validation

Rego typecheck and an isolated production build passed. Mobile and desktop local browser checks covered held account reads, one transaction detail request after link selection, an unchanged fursona save, a changed fursona save with its draft retained, and a Communications save. Each flow stayed in one document. Hosted signed-in timing and saves remain unverified. A small read-only public event sample still found a long event API response.

Repository: Rego. Status: Linked Pages build passed.

What’s Changed

Event cards can begin checking current details after a deliberate hover or keyboard focus, so selecting one may open its live information sooner. Home now shows its current-event checking message in the first HTML when the published list has no upcoming cards. The first Pawsports visit shows the claim form immediately while credentials load. Affiliate payout Save is unavailable until details change, avoiding an unnecessary request.

Impact

Attendees can start a Pawsport claim without waiting for their credential list. Unchanged payout details no longer trigger a save wait. No action is required.

Validation

Rego typecheck and an isolated build with invented event metadata passed. Mobile and desktop production-preview browser checks covered event-card selection and account switching, Home’s HTML before JavaScript and live read reconciliation, Pawsport claim and return, and payout save/readback. Those flows stayed in one document. A deliberate hover without selection can make one extra event read; hosted timing and signed-in saves remain unverified.

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.

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.