Platform Updates

Repositories: Partners, Partners API. Status: Partners ae89ff5 linked Pages and API 0bc6809 linked Worker builds passed.

What’s Changed

EMS Affiliates & Tracking starts its event-scoped reads as soon as the current signed-in operator and event membership are confirmed, while the page code loads. Finance Custody keeps its current records and form visible while it automatically checks an uncertain save against fresh server data. The Reports overview API now reads the first ordered page once, avoiding a duplicate 1,000-row database read for large collections.

Impact

Event teams may see affiliate settings sooner on a direct visit. Finance operators can continue viewing their current work during a saved-state check without triggering a manual refresh. Large Reports overviews require one fewer database read per paged collection.

Upgrade Notes

No action is required. Local verification covered the authorized first-read order, automatic Custody reconciliation, and a 3,619-row Reports overview fixture; both linked builds passed. In separate signed-in visits, Affiliates started its three reads about 420 ms after access before the change and 5 ms after access on the released page. These samples confirm request order, not a controlled total-load improvement. A normal signed-in Test Event save stayed on the same page, and its original value was restored and confirmed after reload. Hosted interrupted-save behavior remains unverified.

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

Event Shop now starts its public catalog read alongside event details for linkable events, including unlisted links. It shows products and cart actions only after the current event confirms access and identity. A denied or missing event no longer repeats the same rejected request before showing a recovery message.

After an accepted authenticator verification or passkey registration, Account Security keeps the result visible while a background status read catches up. These saves stay on the current page. No action is required.

Rego typecheck and production build passed. Local mobile and desktop browser checks covered Shop request ordering, access denial, changed event IDs, transient retry, and stale Account Security reads; all stayed in one document. Four fresh read-only hosted Shop visits confirmed the catalog request started before event detail finished. A separate hosted trace still found event lookup to be the main remaining wait, so broader hosted signed-in speed and real device/provider completion remain to verify.

Repository: Partners. Status: Partners 306fe1a linked Pages release passed.

What’s Changed

Finance Outflows and EMS Registration Configuration begin their first scoped reads after authorized access, while their page code finishes loading. Cash-account choices are requested only for operators with disbursement capability. Registration configuration keeps the current draft mounted during saves and automatically checks exact saved state if a response is uncertain.

Impact

Finance and event teams may reach useful records sooner on a direct visit. Operators can continue from an EMS draft while its save is checked; another submission remains locked until the outcome is known.

Upgrade Notes

No action is required. Local held-chunk and EMS browser fixtures, Partners typecheck, production build, and linked Pages release passed. In separate signed-in post-release visits, Finance Outflows capability and queue requests began 3–4 ms after access finished, and all four EMS Registration Configuration reads began 4 ms afterward. Earlier separate visits showed gaps of about 350 ms and 634 ms, respectively. These samples confirm request order, not a controlled total-load improvement. Hosted interrupted-save behavior remains unverified.

Repository: Partners API. Status: dc364496 linked Worker build succeeded.

What’s Changed

The Enforcement Directory used by partner Watchlists and Bans no longer makes a redundant visibility-grants read. Independent scoped incident, adoption, and request reads now run together after access is checked.

Impact

Partner safety teams may see these directories sooner. The API still applies the current account, organization, and sharing permissions to returned records.

Upgrade Notes

No action is required. A 12-case local Hono fixture, API typecheck, Worker dry build, and linked Worker build passed. Separate hosted first and warm Server-Timing app samples were 1,017 ms, 385 ms, and 341 ms; an earlier separate sample was 766 ms. These visits show variable timing and do not establish a controlled speedup. Broader signed-in role and volume checks remain to verify.

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

Event Merch no longer repeats its event request when anonymous session startup reports no account change. Attendees returning to an activity proposal can keep typing answers while the current form refreshes, including after a temporary read failure. Friends privacy controls now retain an accepted change while a background settings read catches up.

Current form rules still control uploads and submission, and current account state controls Friends actions. No action is required.

Rego typecheck and production build passed. A hosted read-only Merch trace identified the duplicate request; local mobile and desktop browser checks covered the corrected request count, editable activity drafts, stale Friends reads, and one-document saves. Hosted signed-in timing and completed submissions remain unverified.

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

Renewing the same attendee session now keeps account views and saved form context in place. Switching accounts, signing out, and an expired session still clear private views. Returning to a volunteer application also keeps the selected role and typed answers visible while current eligibility is checked, including through a temporary read failure. Upload and submission wait for that check. No action is required.

Rego typecheck and production build passed. Browser checks covered session renewal, account switches, expiry, and volunteer drafts on mobile and desktop. The session-boundary suite passed. Hosted signed-in timings and completed volunteer submissions remain unverified.

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

Attendees opening a linkable event registration page can choose a tier while saved registration details load. Their choice carries into the form after the current details arrive. Approved Dealers Den applicants can choose a table package while their owned application and attendee roster load.

Current availability, existing registration, application ownership and capacity checks still control the next steps and final submission. No action is required.

Rego typecheck and production build passed. Local mobile and desktop browser checks held the saved prefill and Dealers Den application reads, then verified the selection survived in one document without a reservation or submission. Hosted signed-in speed and completed registrations remain unverified.

Repository: Partners. Status: Partners 74edf64 linked Pages release passed.

What’s Changed

Finance Transactions and individual Report Detail pages start their first authorized reads while their page code finishes loading. Report Detail reads the exact selected report and reuses that result when the page opens. Refresh still requests current data.

Impact

Finance operators and partner safety teams may see the records they opened sooner on a direct visit. Account, organization, report selection, and access checks continue to control which records appear.

Upgrade Notes

No action is required. Focused local browser checks covered first-read reuse and access gating; Partners typecheck, production build, and linked Pages release passed. In separate signed-in post-release visits, Finance Transactions began its reads 4–5 ms after access finished and Report Detail began its exact report read 4 ms afterward. Earlier separate visits showed gaps of 317 ms and 329 ms, respectively. These samples confirm request order; they do not establish a controlled total-load improvement. Broader role and save coverage remains to verify.

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.