Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Partners V2 feedback triage filters
Repositories: partners.furries.ph-v2
What’s Changed
- Event teams can now filter feedback by search, category, status, date range, rating, urgency, and contact availability; CSV export carries the same protected filter selection.
- Feedback details now label submitted answers from their server-owned question snapshot. Creating a safety report remains a separate explicit action.
- Filter entry is debounced before the protected server query is refreshed.
Upgrade Notes
- Authenticated-browser certification and debounced filter entry remain in progress.
Upgrade Notes
- Additional queue consumers, direct-recipient picking for global campaigns, inbox Markdown preview, and authenticated-browser certification remain in progress.
Impact
Event operators can prepare affiliate programs in the V2 dashboard while keeping payment and account data within the established protected backend boundary.
Upgrade Notes
- This is not yet deployed. V2 type-check, production build, source-drift verification, and diff checks passed. Authenticated browser certification, conversion point rules, share links, and atomic save handling remain work in progress.
Rego campaign quote reconciliation
Repositories: rego.furries.ph, partners-api
Status: Validated locally - release pending
What’s Changed
- Campaign-linked registration review now distinguishes the original subtotal from the subtotal after the one applied discount.
- Subtotal-only discounts keep their separately calculated payment surcharge; whole-total discounts remain the only mode allowed to reduce it.
- A campaign code left in an older affiliate cookie is recognized as campaign attribution instead of showing an invalid-affiliate warning.
Impact
Attendees opening a campaign link can review an auditable quote: item total, discount, post-discount subtotal, surcharge, and final amount now reconcile.
Upgrade Notes
- This change is not yet deployed. Local quote certification, API type-check, and Rego site type-check/build passed; deploy both the API and Rego site together before relying on the hosted flow.
Partners Dashboard V2 check-in camera scanning
Partners Dashboard V2 now includes opt-in camera and NFC scan controls for event check-in. Camera scanning uses the browser’s native barcode support where available and falls back to the same open-source ZXing scanner already used by the existing Partners dashboard. On NFC-capable Chromium devices, staff can scan Pawsport tags; unsupported browsers keep camera scanning and manual lookup available. Scanned registration references and supported Pawsport credentials open the same protected review flow; no partner API behavior changed. Local validation: V2 typecheck, production build, legacy-source drift check, and rendered route capture.
The V2 check-in review is also now staged like the existing dashboard: staff verify the protected record, complete handoff, record flags and notes, then review an explicit confirmation summary before the authoritative save.
Partners Dashboard V2 feedback triage safety parity
Partners Dashboard V2 feedback triage now preserves the existing dashboard’s explicit review boundary: changing a proposed status does not update a response until staff choose Update status. Feedback rows retain priority and contact cues, while the protected detail view shows submission context, timestamped internal notes, and safe formatted answer values. Creating a safety report remains a separate, deliberate action. No partner API behavior changed.
Partners Dashboard V2 registration upgrade queue parity
Partners Dashboard V2 registration upgrades now keep the operational review facts visible and searchable: resolved tier changes, newly requested add-ons, payment status and total, request timing, and payment deadline. Status filters retain lifecycle counts and review dialogs distinguish current from requested registration tiers. The existing approval, decline, notification, and event-scoped API boundaries remain unchanged.
Partners Dashboard V2 waitlist draft safety
Partners Dashboard V2 waitlist management now refreshes event queues only while the route is visible and no configuration draft or offer action is active. Staff must save or revert local tier configuration changes before offering the next attendee, preventing an offer from being sent against a different server configuration. Queue status filters show lifecycle counts and messaging remains event-scoped. No partner API behavior changed.
Partners Dashboard V2 refund decision contract repair
Partners Dashboard V2 refund review now sends the same structured add-on decision data as the existing dashboard. Unselected add-ons are explicitly zeroed, a full cancellation includes every requested add-on, and financial values are rounded before review. The dashboard continues to keep refund proof artifacts out of the browser surface; no partner API behavior changed.
Partners Dashboard V2 transfer review parity
The Partners Dashboard V2 transfer queue now preserves the full legacy operational review flow: searchable and counted request states, resolved event catalog labels, attendee follow-up, decision details, optional item-level transfer selection, required decline reasons, and guarded visible-page refresh. The native implementation uses shared form, dialog, feedback, and polling primitives; no Partners API changes were made. Type-check, production build, source-drift verification, and whitespace validation completed locally.
Partners Dashboard V2 waitlist offer safety
The V2 waitlist workspace now places a confirmation step before an operator sends the next attendee an immediate registration offer. It identifies the affected tier, queue head, and offer window, preserves unsaved configuration against in-flight refreshes, and shows offer/email timing alongside each queue entry. Existing Worker endpoints and Partners API behavior are unchanged.
Partners Dashboard V2 refund amount guard
V2 refund decisions now cap each approved add-on amount to its original requested value as the existing dashboard does. This prevents staff input from producing an over-refund while retaining the established Worker review payload and no raw proof-link boundary. No Partners API behavior changed.