Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Partners V2 browser verification
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Partners V2 now includes its browser verification dependency and runs the production-build route check through the installed Chrome channel. The standard check completed across 138 partner-owned routes with no page errors or external service requests. No customer data, Worker record, or deployment changed.
Partners V2 focused browser checks
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Focused Partners V2 browser checks now use the installed Chrome channel, matching the route smoke check. This removes a local dependency on separately downloaded Playwright browser binaries. Accounting, payment configuration, live-shift, and POS scanner synthetic workflows were rerun with no page errors or external service requests. No customer data, Worker record, or deployment changed.
Partners V2 local runtime recovery
Repository: partners.furries.ph-v2 — local verification, not deployed.
Partners V2 local verification now uses the donor dashboard’s configured isolated runtime. A scoped local operator completed credential sign-in and loaded the protected V2 dashboard through the Worker. The temporary account and local records were removed after verification. The local Event Management flow also created a scoped event draft after its reference-prefix check, opened its editable event-details workspace, saved scoped event fields, opened its registration roster, then removed the event with the fixture. No hosted data, provider session, or deployment changed. The scoped Event Planning workspace also rendered its real empty-plan state and creation controls through the same local session with no page errors. The same scoped local Planning command created a temporary event plan through the Worker and returned it in the scoped project list; the fixture was removed afterward. A single browser-process creation receipt remains pending.
Partners V2 Planning reminder readiness
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning Notifications now shows the legacy project-scoped readiness for personal email, Telegram, Discord, and SMS reminders, including masked destination and Worker-provided remediation. No channel link, verification, test, delivery, or deployment was performed.
Partners V2 route coverage verification
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Partners V2 now checks every current legacy dashboard page against its native route contract. This protects partner teams from a dashboard page being omitted during future parity work. The sign-in alias is also recorded against its own legacy source page for an exact route inventory.
The new coverage command, route execution check, and local type check passed. No customer data, Worker record, or deployment changed.
Partners V2 also now performs a production-build browser check across all 138 partner-owned routes. The local run completed with no page errors or external service requests; transferred administration pages retain their separate portal handoffs.
Partners V2 sign-in alias
Repository: partners.furries.ph-v2 — local implementation, not deployed.
The /login address now follows the legacy dashboard’s canonical sign-in redirect. The donor and V2 route behavior are covered by a focused local contract check. No account, Worker record, or deployment changed.
Partners V2 Planning meetings
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Authorized planning operators can now schedule externally hosted meetings in V2 with the legacy dashboard’s purpose, start and end times, platform details, participants, reminder policy, and weekly, biweekly, or monthly recurrence. The existing Worker remains the authority for access, calendar identity, and audit records.
Local type checking and a synthetic browser command check passed. No real meeting, Worker write, or deployment was created.
The same Planning Meetings workspace now lets authorized operators add governed agenda drafts, including presenter, duration, pre-read, and linked-work context. The Worker continues to control agenda order and publication.
Agenda publication can now move through draft, published, and locked states with the legacy dashboard’s version protection and recorded reason.
Authorized operators can also record a governed meeting decision, vote record, and follow-up actions through the same Worker-backed minutes workflow as the legacy dashboard.
The Meetings workspace also supports reusable agenda templates with ordered sections, an optional default duration, and project or partner scope.
Operators can now use the separate legacy workflow to record an externally hosted meeting that has already taken place, with the same governed meeting fields.
Authorized operators can now edit existing external meeting details, including time, platform, participation, reminder policy, and recurrence. Scheduling and access checks remain enforced by the existing Worker.
The Meetings workspace now also includes the legacy complete-minutes record: attendance, discussion summary, optional publishable Markdown, decisions, action items, facilitator notes, publication state, meeting version, and idempotency receipt are saved together through the governed Worker workflow.
Partners V2 Planning departments
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning Departments now restores legacy department and membership authoring. Authorized operators can define a department’s charter, accountable lead, capacity model, and effective date, then add a username-resolved member with their planning role, effective dates, weekly capacity, and allocation. The Worker validates scope and creates any matching member requirements.
Local type checking and a synthetic browser fixture passed. No live department or membership was created.
Partners V2 Planning department edits
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning Departments now also supports the legacy version-protected department profile edit and effective membership edit. Operators can update departmental identity, lead, capacity model, charter, and effective date, or move a member while updating their planning role, assignment dates, weekly capacity, and allocation.
Local type checking and a synthetic browser fixture passed. No live department or membership was changed.
Partners V2 Planning RACI
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning Departments now provides legacy work-item RACI assignment with accountable, responsible, consulted, and informed roles. The Worker validates the work-item version and assignment policy. A synthetic browser fixture and local type check passed; no live assignment was changed.