Platform Updates

Repositories: partners.furries.ph-v2

What’s Changed

• V2 now shows protected shop-order revenue, fees, fulfillment logistics, queue worklists, product/category performance, and courier metrics.
• Payment and fulfillment decisions remain in the dedicated V2 Shop Orders and claim workspaces.

Upgrade Notes

• This is a local V2 implementation; authenticated-browser certification remains in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• Event operators can now enter the V2 Email and SMS campaign workspaces from a guarded event communication index.
• The index explains that recipient eligibility and delivery controls remain in protected server and native platform workflows.

Upgrade Notes

• Email campaign composition and Android SMS operations remain in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• V2 event operators can now review the existing settlement policy and immutable remittance history, then request a protected server quote before recording a settlement.
• Provider and account eligibility, fees, calculations, and persistence remain in the existing protected backend.

Upgrade Notes

• Settlement proof upload, CSV export, and authenticated-browser certification remain in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• V2 event teams can select protected audiences, inspect a sandboxed backend email preview, send with an idempotency key, and monitor or recover campaigns.
• Recipient eligibility, deduplication, delivery budgets, and final delivery outcomes remain server-owned.

Upgrade Notes

• Explicit attendee selection, richer preview states, and authenticated-browser certification are in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• Event teams can now create, edit, activate, remove, save, and revert the core activity-form snapshot in V2.
• Existing submission review remains separate, while the full shared form builder and preview continue in progress.

Upgrade Notes

• Conditions assignment, question builder controls, uploads, ordering, and authenticated-browser certification remain in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• Activity authors can now preview the same text, long-text, select, checkbox, required, and submit-button surfaces that attendees will receive.
• The preview is a reusable V2 primitive driven by the backend-owned activity snapshot, so authors can validate a form before saving it.

Upgrade Notes

• Conditional questions, uploads, drag-and-drop ordering, notifications, and authenticated-browser certification remain in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• V2 event teams can review the full retained saved-prefill audit: event context, selected tier and add-ons, saved form-answer count, timestamps, lifecycle, and an explicit revoke control.
• Revoked entries remain immutable audit records and cannot be reused for registration.

Upgrade Notes

• This is not yet deployed. Authenticated-browser certification and request timeout messaging remain in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• Upgrade reviewers now see event-aware tier and add-on names, payment context, lifecycle labels, request times, and the existing staff decision audit in V2.
• Existing protected review decisions remain server-owned; no API service was changed.

Upgrade Notes

• Attendee notifications, live queue refresh, separate read-only detail view, and authenticated-browser certification remain in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• Upgrade request inspection is now separate from the decision dialog, making completed and inactive request audit details available without exposing mutation controls.
• The live review queue refreshes only while the dashboard tab is visible.

Upgrade Notes

• The reusable attendee messaging composer is being ported separately for use across upgrade, refund, transfer, and other event queues.

Repositories: partners.furries.ph-v2

What’s Changed

• Upgrade reviewers can now open one reusable protected message composer for the attendee on a specific request.
• Email creates the existing inbox and email delivery through the Worker; SMS is explicitly queued to an active, verified, non-roaming Android SIM and never creates an inbox entry.
• Refund, Transfer, and Gift review now use the same composer; Gift preserves separate recipient and giver messaging actions.
• Volunteer Application and Activity Submission review use that same protected attendee-message surface.
• Waitlist staff can now use the composer from an individual queue entry without changing the protected offer workflow.