Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Partners V2 Planning scenarios
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning teams can now compare and review venue, date, capacity, and budget alternatives inside the schedule workspace. These scenarios stay separate from the linked event until a later governed event-change process is used.
Local type checking and a browser fixture passed with synthetic planning data. No real scenario, EMS change, Worker write, or deployment was created.
Partners V2 Planning baseline approval
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning operators can now create the same protected schedule baseline used by the legacy dashboard. The dialog requires a label, scope, reason, and explicit approval before the existing Worker validates and freezes the schedule snapshot.
Local type checking and a browser fixture passed with synthetic planning data. No real baseline, Worker write, or deployment was created.
Partners V2 Planning calendar export
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning schedules now offer the same iCalendar and JSCalendar downloads as the legacy dashboard. Each export remains scoped to the current event plan and uses the existing authorized Worker calendar feed.
Local type checking and a browser fixture passed with synthetic calendar bytes. No real calendar, planning record, Worker write, or deployment was created.
Partners V2 report creation field parity
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Safety-report filing now includes the active partner’s event link, investigation details, victim context, local-ban duration, shared-review notes, and an operator-selected declaration date. The existing scoped confirmation and duplicate-outcome recovery remain in place.
Local type checking and an actual-component browser fixture passed with synthetic reports and no Worker write. Hosted safety-report authorization and production acceptance remain required before use.
Partners V2 finance settings review
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Finance Settings now shows the active partner role and granted finance capabilities alongside the existing cash and payment-account configuration. It also shows each Worker-supplied accounting period, its close state, and any recorded close or reopen reason before an operator uses the existing period control.
Local type checking and a browser fixture passed with synthetic settings data and no finance or Worker write. Hosted role and accounting-period acceptance remain required before production use.
Partners V2 finance automation route review
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Finance notification destinations can now be filtered by event scope, platform, flow, status, and text. Selecting a route shows its target, inheritance, verification result, and delivery scope before an authorized operator opens the existing governed edit flow.
Local type checking and a browser fixture passed with synthetic destinations and no notification delivery or Worker write. Hosted role and destination acceptance remain required before production use.
Partners V2 finance integration review
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Finance integration profiles can now be filtered by category, direction, health, and search text. Selecting a profile presents its Worker-supplied format, version, direction, and health before a governed profile action.
Local type checking and a browser fixture passed with synthetic profile data and no provider or Worker operation. Hosted integration acceptance remains required before production use.
Partners V2 planning risk pagination
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning risk, requirement, and meeting registers now provide Next and Previous controls for the existing Worker cursor feed. Navigation retains the scoped search and status filter, and keeps the current page visible if the next read fails.
Local type checking and an actual-component browser fixture passed with synthetic records and no Worker writes. Hosted access acceptance remains required before use.
Partners V2 finance personal-work filter
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Finance operational registers now include the same My records saved view and 8/16/32-row pagination as the legacy Partners dashboard. The personal view shows records created by the signed-in operator across payables, receivables, expenses, budgets, and close controls. Rejected, blocked, awaiting-approval, overdue, late-due, and policy-flagged records also remain visible in Needs attention.
Local type checking and a browser fixture passed with synthetic finance responses and no Worker writes. Hosted role and finance-policy acceptance remain required before use.
Partners V2 finance record lifecycle actions
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Approved cash receipts can now move through collection, and approved advance-liquidation and petty-cash-count records can move through liquidation. Each action retains the existing accountable checkout, version check, and required reason before the Worker records the transition.
Changing partner scope also clears the prior finance register and releases an open record checkout before the new scope loads.
Local type checking and a browser fixture passed for all three actions using synthetic requests. No finance record, lock, or Worker write was created. Hosted role and finance-policy acceptance remain required before use.