Furries PH Docs
Dashboard

Updates

Platform Updates

Public-facing release notes for meaningful changes across Furries PH operational systems.

First created Last updated

Showing release notes 201-210 of 1437
2026-09-2819:32

EPS My Work board shows every RACI assignment

Repository: Partners. Status: Released.

My Work now places an event planning item in each Responsible, Accountable, Consultant, and Informed section assigned to the signed-in person. Someone who holds more than one role on an item can find it under every applicable role. Reviewer-only assignments remain in their review section.

Validation: local type check, production build, and a browser check of a two-role assignment on the desktop and mobile board. The Git-linked Cloudflare Pages deployment succeeded, and the hosted workspace serves the matching build manifest. An authenticated production session was not available for a personal assignment check.

2026-09-2819:32

Planning entry reads overlap

Repository: Partners API. Status: cd5a1d4 linked Workers build passed.

What’s Changed

For managed plans and the workspace timeline, the API now starts independent actor membership and partner-scoped project reads together. It still checks the user’s access and the existing processing limits before returning any plan or timeline item.

Impact

Partner managers may see their plans and timeline sooner on a cold visit. Access rules and returned data remain the same. No action is required.

Upgrade Notes

Admitted and denied route fixtures, API typecheck, Worker dry build, and linked Workers build passed. On one signed-in Test Partners visit, managed plans returned 200 in 275 ms and the workspace timeline returned 200 in 577 ms. Earlier separate visits took about 640 ms and 684 ms respectively; visit-to-visit variation prevents a controlled speed-gain claim. My Work remained around 735 ms on the same visit and is a separate path.

2026-09-2819:32

Dashboard returns and saves respond sooner

Repositories: Partners, Partners API. Status: Partners 1ae28b15 linked Pages and Partners API d19833ba and aa701ec8 linked Workers builds passed.

What’s Changed

On a same-session return to Asset Overview, Partners shows the last authorized read-only snapshot while it automatically checks for current data. Actions wait for verification, and an access denial or scope change clears protected data. Dashboard code downloads alongside the access check when the signed-in route is known. A confirmed EMS Feedback triage status appears in the mounted view, followed by an automatic exact detail readback; access loss clears the result. Forecasting now reads the newest saved result for each requested domain and transfers only the prior point needed while forecasting is running. Stopped forecasts still retrieve their complete saved results. Finance authorization starts scoped membership and assignment reads together and skips grants that the requested Finance view does not use.

Impact

Asset operators can return to a useful overview promptly, and EMS operators can see a confirmed triage change without refreshing the page or manually rechecking it. Event and Finance operators may receive their authorized views sooner. Current permissions and Forecasting freshness checks still apply. No action is required.

Upgrade Notes

Partners typecheck, production build, three focused browser fixtures, and linked Pages build passed. API typecheck, dry build, Forecasting certification, Finance security and focused read fixtures, and linked Workers builds passed. A read-only database comparison returned the same newest Forecasting IDs for all three domains while reducing the saved-result response from about 101 KB to 1 KB. On a signed-in Asset return, the previous snapshot appeared immediately with a checking label and ten fresh asset requests began automatically. On a separate signed-in Dashboard reload, its code download began alongside the access check; protected home data began only after access succeeded. A warm Forecasting return reported 812 ms of application work, including 387 ms for saved-result reads and 379 ms for source reads. A Finance overview visit reported 566 ms for summary work, including 126 ms for authorization and 440 ms for the summary query. These visits do not establish a controlled first-load speed gain; database reads still dominate both paths. Hosted EMS save recovery remains unverified.

2026-09-2819:32

Rego application history and upgrade responses stay responsive

Repository: Rego. Status: 22da6d66 pushed to main; linked Pages build passed.

What’s Changed

The Applications navigation link starts its three authorized history reads when an attendee deliberately approaches it, then reuses them on arrival. A confirmation page can show the attendee’s matching, last known transaction summary while its current rego record loads. If an upgrade submission loses its response, Rego checks the current API record in place and prevents an uncertain duplicate attempt.

Impact

Application history and confirmation context can appear sooner, without a page refresh. Payment instructions and follow-up actions still require a current authorized response. An upgrade with an uncertain result asks the attendee to inspect the transaction before another attempt. No action is required.

Upgrade Notes

Rego typecheck and production build passed. Local mobile and desktop browser fixtures covered one-document Applications navigation with one read per source, confirmation preview reconciliation and account isolation, and lost upgrade responses with exactly one submission. Route-specific readiness definitions cover 59 of 62 contract paths; the design canvas is excluded. The Shop checkout probe measures purchaser fields with a locally fulfilled validation response, not a real quote or checkout. Hosted signed-in timing and completed provider payments remain unverified.

2026-09-2819:32

Procurement saves appear promptly and Forecasting shows the last verified view

Repository: Partners. Status: ae140f61 and 40441d23 linked Pages builds passed.

What’s Changed

After a Finance procurement request is confirmed, Linked Operations validates the saved receipt and adds the request to the open list immediately. The workspace keeps its mounted view instead of rereading seven unrelated data lists. An uncertain save still receives automatic reconciliation, and a response from an old account or partner scope is ignored. On a same-session return to Forecasting, the last verified result appears while a fresh read runs automatically. Forecast controls wait for verification; temporary read failures retry, while denied access or a scope change clears protected data.

Impact

Finance operators can see a confirmed request without waiting for a broad dashboard refresh or manually rechecking the save. Event operators can read the last verified Forecasting view promptly on return while current data is checked. No action is required.

Upgrade Notes

Focused procurement and Forecasting session browser fixtures, Partners typecheck and production builds, staged diff checks, Docs check, and both linked Pages builds passed. In one signed-in Test Event same-page return, the last verified forecast appeared immediately with a checking label and one fresh forecast request began automatically. That request reported about 934 ms of application work. This is return-visit behavior, not a first-visit speed measurement. Hosted procurement save timing and interrupted-save recovery remain unverified.

2026-09-2819:32

Rego action drafts stay available during checks

Repository: Rego. Status: cff3cd03 pushed to main; linked Pages build passed.

What’s Changed

Refund and transfer pages now let attendees enter payout or recipient-search details while current ownership and policy checks run. Gift and Dealers Den registration forms can retry repeated download failures within the same page when the browser identifies the failed form file.

Impact

Attendees can begin drafting transaction changes sooner and keep the event page during recoverable form download failures. Search and submission still wait for current permission checks. No action is required.

Upgrade Notes

Rego typecheck and production build passed. Local mobile and desktop fixtures covered held refund and transfer reads, and repeated Gift and Dealers Den form download failures followed by recovery in one document. Hosted signed-in timing and completed transactions remain unverified. A page refresh can still be required when the failed form file cannot be identified.

2026-09-2819:32

Planning RSVPs confirm in place and Forecasting reads less

Repositories: Partners, Partners API. Status: Partners a8020971 linked Pages and Partners API e541e127 linked Workers builds passed.

What’s Changed

After a confirmed Planning Meeting RSVP save, Partners automatically checks the attendee’s response, note, and receipt time through authorized workspace reads. The meeting register stays visible and repeat actions stay locked until the result is current; lost access or a scope change clears protected state. Forecasting now reads only the saved-vintage fields needed for prior results, stopped forecasts, and generation checks. Its response behavior remains the same.

Impact

Planning members can see their saved RSVP without reloading the meeting register or manually checking it. Event operators may receive Forecasting results sooner. No action is required.

Upgrade Notes

A held-read RSVP browser fixture covering temporary, outdated, and denied reads, Partners typecheck and production build, vintage projection fixture, API typecheck and build check, forecast certification, staged diff checks, Docs check, and both linked builds passed. One separate signed-in Test Event forecast reported 1,108 ms of application work, including 527 ms for vintage lookup and 431 ms for source reads. Server work remains substantial, and this sample does not establish a controlled speed gain. Hosted interrupted-save recovery remains unverified.

2026-09-2819:32

Rego checkout and table drafts open during live checks

Repository: Rego. Status: a20426c2 pushed to main; linked Pages build passed.

What’s Changed

Shop checkout opens purchaser details while it checks the cart’s current price and availability. A Dealers Den application opens table name and description from the published event listing while current event requirements load. If the registration form download repeatedly fails, Rego can retry in the same page and keep the selected ticket tier.

Impact

Attendees can continue entering details during slow checks instead of waiting at a loading state. Payment and application submission still require current checks. No action is required.

Upgrade Notes

Rego typecheck and production build passed. Mobile and desktop local browser cases covered held Shop quotes, held Dealers Den reads, denied and changed events, and registration recovery after five failed form downloads. Each recovery stayed in one document. Hosted signed-in timing and complete transactions remain unverified. A page refresh may still be needed if the browser cannot identify the failed form download.

2026-09-2819:32

Maintenance completion rechecks itself; Forecasting reads overlap

Repositories: Partners, Partners API. Status: Partners 1ac43360 linked Pages and Partners API c47b7267 linked Workers builds passed.

What’s Changed

After a confirmed Maintenance work-order outcome, Partners automatically rechecks the exact authorized detail and current list. Existing rows remain visible and repeat actions stay locked during the check; an access denial clears protected data. A later evidence upload failure is reported separately without repeating completion. Forecasting now looks up the latest saved vintage while it reads current source data, then waits for that result before saving any requested domain. Requests that do not persist a result continue without a vintage lookup.

Impact

Asset operators can confirm completed work without manually rechecking or refreshing the page. Event operators may receive Forecasting results sooner. No action is required.

Upgrade Notes

Focused and existing maintenance browser fixtures, Partners typecheck and production build, a forecast deferred-read ordering fixture, API typecheck and build check, forecast certification, staged diff checks, Docs check, and both linked builds passed. One signed-in Test Event forecast reported 1,172 ms of application work, including overlapping source reads at 392 ms and vintage lookup at 550 ms. Server work and variation between visits prevent a controlled speed-gain claim. Hosted interrupted-save recovery remains unverified.

All docs