Platform Updates

Repository: Rego. Status: Linked release succeeded; hosted signed-in timing remains to verify.

What’s Changed

The Applications page now keeps its current cards visible until background reads finish, avoiding a brief empty list when one source responds before the others. Moving within the same signed-in page by query or anchor no longer repeats profile and MFA checks; opening a different page still checks admission.

Impact

Attendees can keep reading application status while the page refreshes. Same-page navigation sends fewer repeated account checks. Explicit retry feedback remains available when a foreground read fails.

Validation

Rego typecheck and a local production build passed. Mobile and desktop browser fixtures covered held and partial Applications reads, account isolation, one document, delayed profile redirects, waitlist offer rechecks, and route-change admission. The linked Pages build succeeded. Hosted signed-in performance remains to verify.

Repository: Partners. Status: Linked Pages release succeeded; dashboard index applied and verified. Wider hosted timing checks continue.

What’s Changed

Event Planning requirements now show their board as soon as the scoped requirement list arrives. Moving several requirements shows a confirmed result immediately. If a move is only partly saved or the response is interrupted, the board automatically checks the saved positions before allowing another move. Finance Overview shows its summary cards while event records load, and Finance Automation’s Add route dialog reuses choices already loaded by the page. Dealer application decisions show confirmed status before the queue refresh completes. An index was added for the Dashboard’s recent-report-update query when report histories grow large. Event detail forms now recognize that an empty optional field saved as null is still saved.

Impact

Planning, event, and finance teams can see useful content and confirmed changes sooner without refreshing the page or starting a saved-state recheck. Actions that need permission or supporting data stay unavailable until those checks finish.

Validation

Focused browser fixtures covered held reads, partial saves, automatic read-only reconciliation, and in-place feedback. Partners typecheck and production build passed, and the linked Pages build succeeded. A signed-in Test Partners requirement page returned its narrow list in about 430 ms while full project detail took about 1,960 ms before this release. A reversible Test Event venue save completed in about 545 ms without document navigation and its original value was restored; the released editor then showed the original empty venue as Saved. The database migration completed and the index reports valid and ready. A modeled local dashboard query with 200,000 revisions improved from 63.37 to 25.60 ms with the index; one post-release hosted Dashboard home request took about 667 ms, so hosted speedup is unproven. Wider route, role, and save checks remain open.

Repository: Rego. Status: Linked release succeeded; hosted signed-in behavior remains to verify.

What’s Changed

The attendee notice system now downloads formatted-text code only when a notice has a body. When a cached gift form cannot refresh current event options, the form stays visible with a retry button. Its choices and submission stay paused until the event details refresh successfully.

Impact

Attendees without notice text download less JavaScript. Gift senders can retry a failed event check without reloading the page. A draft from an earlier visit is not restored by this change.

Validation

Rego typecheck and a local production build passed. A signed-in browser fixture requested the notice API once and no markdown code when notices were empty; formatted notice text loaded the code on demand. Mobile and desktop gift fixtures confirmed one document, no writes during refresh failure, paused actions, and recovery after retry. The linked Pages build succeeded and the hosted gift route responded. Hosted signed-in latency and gift recovery remain to verify.

Repositories: Partners and partners-api. Status: Both linked releases succeeded; broader dashboard checks continue.

What’s Changed

For signed-in sessions that have already satisfied multi-factor authentication, dashboard access now reads partner, event, profile, and legal information while final security hints complete. Current membership and access checks still determine what can be shown.

EMS SMS campaign history and waitlist queue entries can appear while their supporting recipient, device, event, and tier reads finish. Sending, offers, and settings changes remain unavailable until the required data is ready. Confirmed Asset review decisions and email campaign changes now update the visible result without waiting for a second list read. Planning work-item edits update the Schedule from a verified save response; Planning record removal closes on a verified removal response. If a save or removal response is interrupted, the dashboard automatically checks the saved state before another write. Removal checks use a scoped exact-record status read.

Impact

Partner and event teams may see useful records sooner and regain the editor sooner after a confirmed save. Drafts stay visible during uncertain outcomes. No manual refresh or saved-state check is required.

Validation

Focused browser fixtures covered held supporting reads, immediate confirmed feedback, interrupted responses, automatic read-only reconciliation, and access changes. Partners typecheck, production build, and linked Pages build passed. API access and Planning status authorization fixtures, API typecheck, dry build, and linked Worker builds passed. Two signed-in access samples completed in 564 and 573 ms after the access release; they confirm overlapping work, not a controlled end-to-end speed improvement. Broader route, role, and save timing checks continue.

Repository: Rego. Status: Linked release succeeded; hosted signed-in timing remains to verify.

What’s Changed

The Transactions page now reuses its date and currency formatting work while drawing a list. Account ownership and current transaction data still come from the API; filtering, opening a record, and showing more rows keep the same behavior.

Impact

Attendees with many records may see the first set of transaction cards sooner. No action is needed.

Validation

Rego typecheck, the 62-route contract, a local production build, and mobile and desktop 40-row browser fixtures passed. In a controlled local comparison, median time from the fixture response to the first card fell from 112 to 71 ms on mobile and 94 to 64 ms on desktop across five runs each. The fixture confirmed one document and one rego list request. The linked Pages build succeeded and the hosted Transactions route responded. The comparison used different local servers, so hosted signed-in timing remains to verify.

Repository: Rego. Status: Linked release succeeded; hosted timing remains to verify.

What’s Changed

The route loading audit now distinguishes an immediately available published event link from refreshed event cards and a live, enabled registration action. This helps target the waits attendees actually experience across the current Rego routes. The site behavior itself has not changed.

Impact

Attendees do not need to do anything. The revised measurements help prioritize future speed work without treating an early page shell as a ready form.

Validation

The 62-route contract, script syntax, and local production build passed. Browser runs on an isolated invented event recorded published links before document loading finished, then timed live cards and an enabled event action separately on mobile and desktop. The linked Pages build succeeded. These three local samples per viewport do not establish hosted loading percentiles or real-account save performance.

Repositories: Partners and partners-api. Status: Both linked releases succeeded; broader dashboard checks continue.

What’s Changed

On a direct EMS visit, event counts now start as soon as dashboard access is confirmed, while the page finishes loading. Finance keeps its initial reads independent of the larger page data code. The Finance event portfolio API reads its event, posted journal, and disbursement information together and pages large portfolios completely.

An acknowledged Dealer registration or Finance cash-account save now updates the visible record without waiting for a second full list read. Uncertain saves continue automatic read-only checks before another write. Asset View shows its register details while identity and custody history load. Reports Overview keeps loaded cards visible and limits repeated background requests after a temporary read failure.

Impact

Partner teams and event operators should see useful content sooner and get faster feedback from these saves without refreshing the document. Normal use requires no action. An uncertain save still remains locked while the service checks what was stored.

Validation

Focused browser fixtures passed for Finance and EMS request order, partner switching, Dealer and cash-account saves, Asset View, and Reports refresh. Partners typecheck and production build passed. The API typecheck and a 1,000-plus-row, partner-isolated Finance portfolio fixture passed; a controlled 90 ms per-read scenario completed its parallel first reads in 90 ms versus 181 ms for staged reads. A read-only Supabase query accepted the joined filter, and both linked builds succeeded. A signed-in Finance Events visit rendered the Test Event portfolio after the API release. Separate signed-in request-order samples started Finance reads 3 ms and EMS counts 193 ms after access; their page and server timings varied, so these are not controlled total-load comparisons. The full range of roles and saves remains to verify.

Repository: Partners. Status: Linked release succeeded; wider dashboard checks continue.

What’s Changed

A direct Finance visit now prepares its first data reads while dashboard access is checked. The reads begin only after the current access decision and are shared with the page, so opening Finance does not send them twice. The shared dashboard downloads less code for other workspaces; EMS event navigation is loaded for event pages, and Planning still starts its own managed-project read promptly.

An interrupted EMS Inventory save now checks the saved state again automatically when the first read is stale. The draft stays visible and a second write is blocked while the result is uncertain. If repeated checks cannot confirm the save, the workspace stays locked for an administrator to review.

Impact

Finance may show its first data sooner on a direct visit. Event operators can stay on Inventory after an interrupted save without triggering another write. No action is needed for normal saves.

Validation

Local Finance, Planning, and EMS browser fixtures, Partners typecheck, and production build passed. The shared dashboard shell was 22.3 KB in the new build, down from 51.8 KB before this change. The Inventory fixture observed a stale read followed by automatic confirmation with only one write. The linked Pages build succeeded. On a signed-in, cache-disabled first visit to the new Finance assets, its three data reads started together 222 ms after access finished, before the Finance page chunk finished downloading. This is one request-order sample, not a controlled total-load comparison. Broader role/save journeys remain to verify.

Repository: Partners API. Status: Placement rollback linked release succeeded.

What’s Changed

Cloudflare Smart Placement was briefly enabled for the API and then rolled back after hosted samples from one vantage slowed when requests moved to another data center. Event responses continue to use the same current catalog and registration decisions. A larger invented event fixture now checks variation choices and linked social benefits across overview and full responses.

Impact

The placement trial has ended; it is not being treated as a speed improvement. There is no change to how anyone registers or saves. No action is needed.

Validation

API typecheck, Worker build dry run, and twelve local overview/full response pairs passed with matching public catalog, access, capacity, and campaign data. The isolated local database remained fast with the larger fixture. Hosted overview samples from one vantage measured roughly 560–616 ms after placement moved to London, versus roughly 259–374 ms in an earlier sample set, so the setting was rolled back. The rollback build succeeded, the placement header disappeared, and eight subsequent samples measured 287–369 ms. Wider geographic performance remains to verify.

Repositories: Rego and Partners API. Status: Linked releases succeeded; hosted signed-in timing remains to verify.

What’s Changed

The gift form now loads its optional Friends picker only when an attendee chooses to show it. Receiver lookup by username remains available immediately. If the picker download fails, the attendee can continue by username with their entered receiver and message still in place. The public event API now reports separate timing for event lookup, related reads and response assembly, making delays easier to locate.

Impact

Attendees can start entering a gift receiver without waiting for Friends settings or suggestions. The API timing change does not alter event data or eligibility. No action is needed.

Validation

Rego typecheck, route contract, production build and mobile and desktop gift fixtures passed locally. The fixture confirmed no Friends reads before opening the picker and preserved form input through a forced optional download failure without a document refresh. API typecheck and local overview and full-event responses passed with stage timings. Both linked builds succeeded, and the hosted event page and public API returned successfully with the new timing metrics. Hosted signed-in gift timing and real-account save performance remain to verify.