Platform Updates

Repository: partners.furries.ph-v2 — local implementation, not deployed.

The social-publishing workspace now treats Discord and Telegram as partner destinations instead of OAuth providers. Operators can add a Discord webhook or Telegram chat and optional topic from the scoped workspace. Provider OAuth remains available only for Facebook, Instagram, TikTok, X, and Bluesky.

Local type checking and a mobile dialog fixture pass without browser errors. No social account, provider authorization, destination, post, or delivery was created; live connection and delivery acceptance remain required before use.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

When a sign-in or protected dashboard action needs an authenticator check, Partners V2 now keeps the current page open and requests the six-digit code in the inline security dialog. Account Settings is reserved for deliberate factor enrollment and account security changes, so it no longer receives sign-in MFA handoffs.

Local type checking and the MFA browser fixture pass. The fixture covered sign-in, protected-route retry, cancellation, navigation and account-change handling with synthetic HTTP only, with no browser errors or unexpected requests. No real MFA verification, Worker write, deployment or publication was performed.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

Payment configuration now keeps its event settings and provider snapshot tied to the current signed-in workspace. If a save loses confirmation, the dashboard holds additional saves until an operator refreshes and reconciles both records. This avoids a duplicate or conflicting repeat save while the current API keeps the two resources separate.

Typecheck and the production build pass. No live payment configuration, provider, financial, or upload operation was performed. Existing build size, dynamic-import and plugin-timing warnings remain; hosted multi-role acceptance is still required before operators should rely on this behavior in production. The local component recovery check made no external requests and reported no browser errors.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

Event operators can now correct a saved manual ledger record with a prefilled, opposite append-only entry. The original record remains in the audit trail. If the dashboard loses confirmation while recording an accounting change, it holds further entries and detail edits until the operator refreshes and reconciles the ledger.

Local component verification covers the correction form at 390px and an interrupted-write recovery flow with no live requests or browser errors. Typecheck and the production build pass. No ledger entries, uploads, Worker writes, or deployment were performed. Existing build size, dynamic-import and plugin-timing warnings remain; operators should wait for a published release before expecting this behavior on the hosted dashboard.

Repository: rego.furries.ph-v2 — local implementation, not deployed.

The attendee application now loads the same reporting control available on the legacy Rego site. People can review a redacted diagnostic snapshot and choose whether to submit an issue through the existing reporting service. Sign-in identity and GitHub delivery remain handled by the service, so the V2 browser does not receive reporting credentials.

Local mobile verification confirms a single reporter control stays available after in-app navigation. The check intercepted the external reporting runtime; it did not create a report, complete Turnstile, or publish a GitHub issue.

Repository: rego.furries.ph-v2 — local implementation, not deployed.

Group-registration receipts now show the event policy saved with the attendee record, including rendered document text after refresh. Friends can refresh a failed summary read without repeating a completed friend action. Activity and volunteer submissions now omit cleared optional checkbox answers, matching the existing V1 request contract.

Local verification covers 78 real group checks with policy rendering, four Friends recovery groups, and eight activity/volunteer branch and image groups across mobile and desktop. No provider or hosted operation was performed. The documented Shop stock race and gift-capacity error mapping remain separate backend repairs and are not resolved by this local update.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

Event operators now have the full V1-style registration roster controls: page sizes, sorting, visible mobile selection, safe partial bulk recovery, current payment review, follow-up-email receipts and reference downloads. The counter lane restores automatic camera scanning with optional NFC, current customer and basket eligibility, reviewable server quotes, payment-account context, complete receipt/history details and a clean next-sale reset.

If a checkout response is uncertain, the lane now holds it for operator reconciliation instead of attempting a duplicate sale. This is necessary because the current API does not provide idempotent or atomic checkout guarantees.

Validation: 19 production-component browser groups passed with synthetic data, including 30 registration owner races, 51 POS calls and 46 fake hardware sessions. Typecheck, production build, route/session/MFA/canvas/shared-source gates and scanner coexistence tests also passed. No real registrations, emails, payments, provider calls or hardware actions were made. Existing bundle-size and dynamic-import build warnings remain. Operators should wait for a published release before expecting these local changes on the hosted dashboard.

Repository: rego.furries.ph-v2 — local implementation, not deployed.

The photo editor restores continuous rotation, mouse-wheel zoom and two-finger pinch. Moving or zooming a rotated image keeps the exported crop covered. Registration entry now avoids reserving capacity when the attendee fails the existing age, date-of-birth or opening-time requirements.

Local mobile/desktop checks cover photo controls and decoded exports, reference sheet limits and Pawsport histories. Twelve controlled event-entry groups and the reservation regression pass. Group registration passes69 real local checks covering individual choices, owned receipts, reloads and access controls, with fixture cleanup. These checks do not establish provider settlement or hosted availability. Operators do not need to change configuration for these repairs.

A separate local test confirmed a shared Shop API stock-limit race under simultaneous checkout. That issue remains documented for a separate backend repair; this entry does not announce its resolution or full functional parity.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

HR settings and volunteer-position editors now receive account, partner and permission ownership from their routes. Their access-list reads can be canceled independently when leaving an editor, preserving requests owned by other pages. The inline authenticator flow remains the required MFA entry path. Both editors show the selected event’s public/internal identity. HR imports identify their source and report draft completion; section indicators track unsaved changes, and potentially partial saves require explicit saved-state review.

Volunteer positions can be created under existing inactive departments, matching V1. Imports regenerate form-item and branch identifiers. Save recovery preserves unfinished overrides, and uploads stop before submission when the editor loses its account or permission context. The full inline builder and attendee preview remain available.

Validation: 39 browser groups plus 13 builder assertions passed, alongside access/transport/route contracts, inline MFA scenarios, final typecheck/build and shared-source gates. Existing bundle-size and dynamic-import warnings remain. No live registrations, HR changes, uploads or provider writes were made in tests. These local checks do not establish hosted operational parity. Operators should wait for a published release before expecting the changes on the hosted site.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

Partner safety teams get the full report status and guest-standing choices, correct local date/time defaults, and officer profile prefill that preserves manual edits. Report review retains the submitted values and signature; an unconfirmed submission directs staff to review existing reports before repeating it. Enrolled users continue to enter MFA codes in the inline authenticator dialog.

Event teams retain current and upcoming location coverage while refreshing. The live tracker clears prior coverage after account, event or permission changes, coalesces repeated refresh clicks and explains stale data after a failed refresh. Staff roster saves now verify accepted row order and registered locations, preserve unsaved assignments during recovery, and require a saved-state check after an uncertain write. Placeholder drafts remain available; saving identifies missing usernames or registered locations before sending changes. Changing a shift start date selects the matching timeline day.

Validation: Seven report-creation, eleven roster and six live-tracker browser groups passed with synthetic data, including signature submission and desktop/mobile rendering. Route-owner, transport/date, roster stage/timeline and session-guard checks passed, along with final typecheck/build, shared-source checks and documentation diagnostics. Existing bundle-size and dynamic-import build warnings remain. No live operational records were created by these tests. Operators should wait for a published release before expecting these changes on the hosted dashboard.