Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Release Notes
Fursona Selector in Configurable Forms
Repositories: partners.furries.ph, rego.furries.ph, partners-api
Status: Ready for deployment
What’s Changed
- Event organizers can add a My fursona question to registration, activity, and volunteer form builders.
- Attendees see only their own saved fursonas, with name and species, and the platform verifies ownership when the form is submitted.
- Dashboard previews include a representative fursona option so organizers can review the attendee experience before saving.
Impact
Attendees can reuse a saved fursona without retyping it, while organizers receive a stable fursona reference with each answer.
Item-specific Question Placement in Registration Preview
Repositories: rego.furries.ph
Status: Ready for deployment
What’s Changed
- Registration previews now show tier and included-item questions with the selected tier, while selected add-on questions appear in the Add-ons step.
- Required answers remain part of the same registration submission; no event configuration or attendee records are changed by previewing.
Live Event Forecasting for Registration, Finance, and Logistics
Repositories: partners.furries.ph, partners-api
Status: Requires database migration
What’s Changed
- Registration, Finance, and Logistics Analytics now show conservative event forecasts separately from actual/committed values, including 80% and 95% ranges, evidence maturity, exact as-of time, previous-vintage movement, and data limitations.
- Forecasting starts after 24 valid live hours, even when evidence is sparse. Early forecasts carry a prominent low-evidence warning and become more informed as live data accumulates.
- Open analytics pages recalculate immediately and refresh every 15 seconds while visible. Material durable changes also create coalesced per-event invalidations, with a one-minute scheduled recovery backstop.
- Service-owned forecast vintages retain model/data/source provenance and later actual comparisons. Direct browser access is disabled; existing partner and event role checks remain in force.
- The first release forecasts active registration capacity, registration-linked finance, and registration-linked inclusion/add-on demand. It does not automate purchasing, capacity, pricing, or financial actions.
Impact
Event operators can see a grounded early expectation and likely range without confusing a forecast with money already collected or stock already committed. Unsupported areas—such as future walk-up/shop revenue, cancellation/no-show behavior, unconstrained sell-out demand, expenses, and supplier lead-time risk—remain explicitly excluded or observed-only.
Upgrade Notes
- Publish
20260811205417_event_forecasting_vintages.sql,20260811210724_forecasting_backstop_seed.sql, and the pending accounting-trigger update before relying on durable vintages/invalidation processing. Review the full ordered migration plan withpnpm supabase:publish:dry-run --include-allbecause other local migrations may also be pending. - Treat the 95% logistics quantity as a review threshold, not an automatic purchase order.
- The deterministic benchmark validates contract behavior and maturity narrowing; live accuracy labels remain conservative until enough completed partner events produce real held-out evidence.
Telegram Event Notifications and Bot Commands
Repositories: partners.furries.ph, partners-api
Status: Requires Worker secret configuration
What’s Changed
- Event notification settings can now deliver selected operational alerts to linked Telegram chats, alongside or instead of Discord webhooks.
- A selected Telegram chat may optionally target one forum topic by its topic ID; blank keeps alerts in the general chat.
- Sending
/statusin a Telegram topic shows the chat and topic IDs needed by the dashboard setting. - Notification Config includes a real sample-delivery button that verifies the current Discord and Telegram targets without changing event or attendee data.
- The Telegram bot now receives signed webhook updates and responds to
/start,/help, and/status; Telegram chat linking no longer disables the webhook to poll updates.
Upgrade Notes
- Set
TELEGRAM_WEBHOOK_SECRETonpartners-apiusing a 1–256 character value containing only letters, numbers,_, or-. Starting a Telegram chat link configures the webhook automatically.
Pawsport Hub Refinement
Repositories: rego.furries.ph
Status: Ready for deployment
What’s Changed
- Refined the attendee Pawsport hub into clearer credential, claim, machine-readable, lost-report, stamps, and history sections.
- Improved compact mobile layouts for credential details and history records.
Impact
Attendees can scan their bound Pawsport information and self-service actions more easily without changing what account data they can access.
Item-specific Registration Questions
Repositories: rego.furries.ph, partners-api, partners.furries.ph
Status: Requires database migration
What’s Changed
- Questions configured for a registration tier, add-on, or inclusion are now collected in the attendee flow where that item is selected.
- Dealers Den collects answers separately for every dealer or assistant slot; upgrades collect questions only for newly added items.
- Registration and Shop answers remain in their own forms. Transfers and refunds are not affected.
Upgrade Notes
- Publish
20260812093000_rego_item_custom_answer_snapshots.sqlbefore deploying the app and API changes.
Durable Prefill Management
Repositories: partners.furries.ph, partners-api
Status: Requires database migration
What’s Changed
- Event Prefills now use the same compact table pattern as other registration-management screens, with attendee, chosen tier/add-ons, answer count, save time, and lifecycle information.
- Prefills no longer expire. Partners can revoke a prefill, which blocks its use while retaining its audit record; permanent deletion is no longer available.
Upgrade Notes
- Publish
20260812110000_rego_prefill_retention_and_revocation.sqlbefore deploying the dashboard and API changes.
Event Accounting Cashflow
Repositories: partners.furries.ph, partners-api
Status: Ready for deployment
What’s Changed
- Added Accounting to Event Management’s Finance section.
- Partners can see confirmed income mapped to each configured receiving account, record operational deductions, and attach receipt images.
- Deduction records are append-only to preserve an audit trail; incorrect entries should be corrected with a new offsetting record.
Impact
Event finance teams have one event-scoped view of where recorded money was collected, what was deducted, and what remains accountable by receiving account.
Upgrade Notes
- Apply the accompanying database migration before using the page.
- Continue assigning receiving accounts during payment configuration so new income can be mapped accurately.
Named Inventory QR Tags
Repositories: partners.furries.ph
Status: Ready for deployment
What’s Changed
- Inventory logistics QR and barcode previews and downloaded PNGs now print the item name beneath the scannable code.
- Inventory Tracking can bulk-download Cricut-ready A5, A4, or A3 SVG tag sheets or open matching paginated print sheets. The compact layouts fit 18, 40, or 84 named QR/barcode tags per sheet while retaining an 18 mm minimum QR code.
- The QR payload remains the existing item UUID, so current scanning and NFC workflows continue to work.
Impact
Event logistics teams can identify physical stock tags at a glance without scanning them first, then print or cut a full set of tags in one operation. No configuration or data migration is required.
Coupon-Style Group Discount Types
Repositories: partners.furries.ph, partners-api
Status: Ready for deployment
What’s Changed
- Group Rego Config now uses the same two discount types as attendee coupons: Flat amount and Percentage.
- The API applies the same flat-or-percent choice when calculating the group subtotal and keeps the resulting total in the registration record.
- A database migration converts existing fixed-amount group discounts to the new
flattype without changing their configured value.
Impact
Event organizers can configure group discounts with the same language they already use for coupons. Existing group discount rules continue to give the same monetary amount after the migration.
Upgrade Notes
- Publish the pending database migration before releasing the dashboard and API changes.
- Review an existing group discount in Rego Config after release, then use the preview to confirm the expected amount.