Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Event forecasting checks access with less waiting
Repository: Partners API. Status: API 543f688 linked Worker build passed; hosted timing unmeasured.
What’s Changed
Forecasting starts its independent event ownership and operator membership reads together when checking access to forecasts and controls. The same authorization decisions continue to apply.
Impact
Event teams may reach forecasting information and controls sooner. No action is required.
Upgrade Notes
API typecheck, modular permissions and forecasting certification, Worker dry build, and linked Worker build passed. Hosted latency remains to be measured.
Planning requirement save checks use the exact record
Repository: Partners API. Status: API 0911a19 linked Worker build passed.
What’s Changed
Planning can read one authorized requirement and its ordered approval stages directly. This lets an automatic save check use the exact record even when a project contains more requirements than its usual list returns.
Impact
Planning operators can keep an uncertain requirement edit open while the dashboard checks its saved state. Access remains limited by project membership, planning permissions, department, and classification.
Upgrade Notes
No action is required. Local access and large-project fixtures, API typecheck, Worker dry build, and linked Worker build passed. Hosted interrupted-save behavior remains to verify.
Check-in and Inclusion Claim prepare records sooner
Repository: Partners. Status: Partners 972e18c linked Pages build passed.
What’s Changed
Check-in and Inclusion Claim now start their first event-scoped read after current operator and event access are confirmed, while page code loads. Planning approval-flow edits now keep the draft open and recheck the exact saved state automatically after an uncertain response.
Impact
Event staff may reach attendee records sooner on a direct visit. Planning operators will not need to trigger a saved-state recheck or repeat an uncertain approval-flow write.
Upgrade Notes
No action is required. Typecheck, build, and targeted Check-in and Planning fixtures passed. In one signed-in Check-in visit, the admitted queue read began before the workspace chunk mounted; the helper chunk still delayed that read, so wider load improvement remains under review. Hosted interrupted-save behavior remains unverified.
Planning edits keep drafts through uncertain saves
Repository: Partners. Status: Partners 12d880f linked Pages build passed.
What’s Changed
Planning meeting and requirement edits keep their open drafts mounted while a save is checked. After an uncertain response, the page checks the exact saved record automatically, including when the server finishes the original save later. A confirmed result refreshes the relevant list in place without refreshing the whole page or repeating the write.
Impact
Planning operators can continue viewing their edits while an interrupted save is resolved. No manual saved-state recheck is needed.
Upgrade Notes
No action is required. Partners typecheck, production build, focused browser fixtures, and linked Pages build passed. Hosted interrupted-save behavior remains to verify.
Event payment settings start loading sooner
Repository: Partners. Status: Partners ca3d7cd linked Pages build passed; hosted interrupted-save behavior pending.
What’s Changed
EMS Payment Configuration starts its four event-scoped reads after the current operator and event access are confirmed, while the route finishes loading. A confirmed save releases the save bar when its receipt arrives, then checks the exact saved settings automatically. If a save response is uncertain, another submission stays locked while the page checks the result without repeating the write.
Impact
Event teams may reach payment settings sooner on a direct visit. Saving stays on the current page, and operators do not need to trigger a saved-state recheck.
Upgrade Notes
No action is required. Partners typecheck, production build, focused seven-group browser fixture, and linked Pages build passed. In separate signed-in visits, the first Payment Configuration reads started 320–321 ms after access before this change and 4–5 ms after access on the released page. These samples confirm request order, not a controlled total-load gain. Hosted interrupted-save behavior remains to verify.
Finance settlements read independent context together
Repository: Partners API. Status: API 8fd380c linked Worker build passed; hosted timing pending.
What’s Changed
After settlement access is confirmed, the API reads independent event and platform configuration together. Provider and policy reads begin as soon as their required inputs are available.
Impact
Finance operators may see settlement records sooner. Existing authorization and event scope still determine which records can be returned.
Upgrade Notes
No action is required. A local held-query route fixture checked overlapping reads and denied-request isolation; API typecheck, Worker dry build, and linked Worker build passed. Hosted settlement timing remains to be measured.
Event registration, Shop, receipts, and account pages keep work moving
Repository: Rego. Status: Linked Pages builds passed for the registration, Shop, receipt, and account changes; hosted signed-in verification remains pending.
What’s Changed
An unlisted Event Shop can start checking product availability while its event details load, using the event link’s public information. Products and purchase actions appear only after the current event confirms access. Profile editing can begin from the signed-in account’s cached details while a fresh profile loads; photo changes and saving wait for that fresh result, and typed edits stay in place. An accepted volunteer shift remains visible after moving to another page and returning, even when an older roster response arrives.
For an unlisted event link, registration can begin loading saved attendee prefill alongside event details. Once the current event supplies its registration tiers, attendees can choose a tier while saved prefill finishes loading. On a return to Shop checkout, cached cart and catalog details can show editable purchaser fields while fresh event data loads; the current event and quote must still be checked before later checkout actions.
A confirmed event rego receipt also starts preparing its QR renderer while the account-owned receipt loads, so the Show QR control need not wait for a separate module download after the receipt appears.
Impact
Attendees may see an Event Shop name, choose a registration tier, review checkout details, and start editing their profile sooner. Volunteers can return to their accepted shift without losing its current status. These actions stay within the page rather than refreshing the whole site.
Upgrade Notes
No action is required. Rego typecheck, production build, focused mobile and desktop browser checks, and linked Pages builds passed. Checks included changed accounts and event IDs, delayed reads, QR readiness, and one-page navigation. The local route timing audit now requires usable page content and reports routes it has not measured; legal-page entry and in-app return checks passed. Hosted signed-in timing, saves, QR scanning, and a complete route sweep remain to be verified.
Large Check-in attendee lists load with fewer waits
Repository: Partners API. Status: API ab2b28d linked Worker build passed; hosted large-event timing pending.
What’s Changed
Check-in now loads attendee profile details in up to three bounded groups at once for large result sets. Each group remains limited to 200 identities, and results keep their original order and linked account scope.
Impact
Event staff may see large Check-in attendee lists sooner. Access rules and the order of attendee records stay the same.
Upgrade Notes
No action is required. A local 1,001-identity fixture, existing Check-in fixture, API typecheck, Worker dry build, and linked Worker build passed. Hosted large-event timing remains to be measured.
Accounting, maintenance, and audit records start loading sooner
Repository: Partners. Status: Partners 871004a linked Pages build passed.
What’s Changed
EMS Accounting and Asset Maintenance start their first authorized, scoped reads while their route code loads. Finance Audit reuses its first read when the page opens instead of requesting the same records twice. Existing records and drafts stay in place during saves and automatic saved-state checks.
Impact
Event, asset, and finance operators may reach useful records sooner on a direct visit. Saving work does not refresh the whole page or require an operator to recheck it manually.
Upgrade Notes
No action is required. Local typecheck, production build, and focused Accounting, Maintenance admission, and Finance Audit browser checks passed. In separate signed-in visits, Accounting and Maintenance first reads began 316 ms and 629 ms after access before this release, then 9 ms and 6 ms after access on the released page. Finance Audit made one audit request in a signed-in visit. These samples confirm request order and count, not a controlled total-load improvement; wider role and save coverage remains open.
More dashboard records start loading sooner
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.