Platform Updates

The Admin Attendees test-fixture cleanup now clears the reviewed fixture set as one database dependency operation instead of repeating the work profile by profile. This prevents the timeout that could stop a large cleanup partway through, while keeping the same server-owned classification, review count, administrator approval, recent MFA, and final confirmation. A rollback-only production check confirmed that the current 188 eligible fixture profiles can complete with no failed records; that check did not remove any account.

The Admin fixture cleanup now recognizes the reserved-domain social-moderation race test identities used by certification runs. These role aliases were not covered by the generic test-name rule, leaving 39 unlinked test profiles after an otherwise successful cleanup. They now use the same reviewed, full-data purge path; a rollback-only production check confirmed all 39 complete with no failures. Real-domain aliases remain excluded from bulk removal.

The Admin cleanup now also removes reserved-domain certification identities that were created to exercise dashboard-administrator access. They remain strictly limited to the server-classified @example.invalid fixture set, so a real administrator account is not included merely because it has dashboard access. A rollback-only production check confirmed the current reviewed set can hard-delete 8 test Auth identities and fully purge 47 test profiles with zero failures; no account was removed by that check.

The Admin Attendees fixture counter now uses the same reserved-domain test identity rule as the permanent cleanup command. This fixes an incorrect zero count for dashboard-admin certification fixtures and social-moderation test role aliases. The existing final confirmation, FPH-admin authorization, recent MFA requirement, and exact-count recheck still protect permanent removal.

Registration-tier inclusions and that tier’s Discord, Telegram, and ZEP overrides now live in its Add/Edit dialog. Organizers can make the complete tier decision in one draft and apply it together. Add-on Discord, Telegram, and ZEP overrides now live in the matching Add/Edit dialog as well. The separate configuration cards have been removed; existing catalog save behavior is unchanged.

Opening Content Management from Partners V2 now uses the unified profile’s server-managed Admin or Partner access marker. FPH staff classified as Admin receive the normal native CMS handoff instead of being sent through a partner-scoped credential flow. Partner accounts remain limited to their exact approved organization scope. The CMS handoff security checks were also updated to validate the V2 dashboard rather than retired dashboard files.

Partners with an approved CMS permission can again open Content Management on the current Sanity Free plan. Each CMS launch creates a revocable, per-user Editor credential that is retained only by the CMS tab and is renewed or deleted by the Partners API. The CMS middleware continues to distinguish a native Furries PH administrator from a scoped partner session: scoped sessions remain filtered and guarded to their active partner, while only native admins receive full Studio access. Removing a membership or rotating a partner’s CMS access revokes every affected credential before the authorization change is completed.

Opening Content Management from Partners now bypasses Cloudflare’s script optimizer for the one-time scoped-session bootstrap only. This prevents the optimizer from changing the script after its security nonce is issued, which previously left some browsers on a blank loading screen. The handoff remains short-lived, no-store, and tab-only; the Studio then opens at its clean URL.

Volunteer role cards and their detail dialog no longer display a registration subsidy amount or percentage. The application flow still shows the role, application window, questions, and entry conditions. Registration receipts continue to show their actual financial adjustments.

Volunteer role selection cards no longer show subsidy badges, and the same amount or percentage is not shown in the role-detail dialog. Volunteers can still review the role, department, application window, questions, and entry conditions before applying. Registration accounting remains unchanged.