Platform Updates

Partners V2 now has a prepared replacement profile model that keeps personal details separate from partner membership, including a user-entered country and country-neutral address fields. The same V2 profile contract now records whether someone has ordinary access, Partner access, or Admin access; that stored marker is migrated from User & Access roles and remains synchronized when those roles change, so completing a profile never grants a workspace. Membership admission and revocation are auditable so revoking a workspace role does not remove the person’s sign-in or event history. The local V2 interfaces are no longer hidden behind maintenance screens. This is a local pre-release stage only: the database migration has not been published, and production validation remains in progress.

The local migration rehearsal also now preserves every legacy profile-source record before any old table can be retired. Accounts already linked to sign-in profiles have a complete restricted snapshot in the unified profile. Attendee records without a sign-in are held intact for an approved identity-linking decision; they are not silently converted into accounts or deleted.

The attendee record itself remains in place for now because it is the stable identity used by historical registrations, payments, Pawsports, Social, and other operational records. The unified profile replaces mutable person details; the linked operational history will be retired only through a separate, verified dependency migration.

Event Planning now leads organizers through a simple four-step start: set the schedule, assign the team, capture requirements, then track readiness. The selected event plan stays visually prominent, personal work is the main next action, and the sidebar uses plain-language groups such as Plan the event and Collaborate. The refreshed controls are comfortable on phones while keeping all existing planning pages and governed records available. Type checks and route coverage verification passed locally.

Department setup now continues directly into adding the first department member: the new department remains selected, so organizers do not have to find it and select it again. Team cards now show their assigned people and provide an add-member action in context. Each membership is still independently validated and recorded by the planning service.

Department cards and the member register now show each person’s display name and username instead of an internal account identifier. The existing authorized member directory supplies this display-only profile information; membership authorization and records remain unchanged.

The same identity rule now applies to every EPS Planning surface. Change history resolves a recorded actor through the scoped member directory before displaying it, so operational audit records remain readable without exposing account IDs.

Only a partner administrator can now create an EPS event plan. Other authorized team members can still open and work in plans assigned to them; the API enforces the same boundary even if a browser request is modified.

EPS department membership now makes the person’s role explicit: Department lead, Team member, Reviewer, Compliance, or Auditor. Only an FPH administrator or the selected partner’s administrator can add, change, or remove those team assignments; the same rule is enforced by the planning service.

EPS now opens event-plan creation from a dedicated Add event plan button instead of keeping the form inline beside the plan list. The mobile-friendly modal uses clearer spacing, a focused two-field flow, and a separate action footer. Other EPS dialogs now share the same roomier padding, stronger focus treatment, and more distinct overlay.

The same modal-first pattern now covers the remaining EPS editors. Project settings open from an Edit settings button, and record discussions use Add comment or Reply buttons instead of inline composers. Existing role checks, audited saves, classifications, mentions, reactions, and watches are unchanged.

Each EPS department now has an Edit members modal. It lists every assigned person by name and username with their department role and capacity, while authorized administrators can add, edit, or remove members in the same scoped team view.

When adding a department member, EPS now searches the full account username directory regardless of account discoverability. The picker waits briefly for typing to pause, ignores searches shorter than two characters, reuses recent results, and cancels superseded searches to keep requests light.

The member form now keeps department role and allocation clearly separated, and places the two effective-date controls on their own spaced row before weekly capacity so every field remains easy to read at narrower desktop widths.

When more than one person has the Department lead role, the department member modal now names every lead in its summary instead of showing only the first.

Requirement setup now offers a direct continuation into its delivery work. The new work item keeps the requirement selected and visibly suggests its department, deadline, and RACI assignments for review, so planners do not have to repeat the same context across pages. The requirement and work item remain independently authorized and recorded by the planning service.

Meeting creation now carries organizers directly into the agenda-item form for the meeting they just scheduled. This keeps the agenda attached to the correct meeting without a second lookup; the existing agenda authorization and audit rules still apply.

Meeting actions now use the meeting state to name the next step: upcoming meetings offer Prepare agenda, while completed meetings offer Record outcome. Supporting actions now stay under a compact More actions control. The same scoped, governed agenda and decision forms continue to be used. Meeting notes and full minutes are now contextual actions for that meeting rather than a second register below the meeting list.

Schedule now opens in one focused Calendar view instead of rendering Calendar, Timeline, Board, and Work breakdown all at once. Organizers can switch views deliberately without losing their selected work item or the existing governed board and hierarchy actions.

The full work-item register is now available under Browse all work items, so it does not repeat the active schedule view on smaller screens.

Readiness Gates now puts unresolved gates ahead of completed ones, highlights their review state, and labels the next governed action. Completed gates remain available without competing with work that still needs a decision.

Each gate now leads with the valid next action—review criteria or record a decision—while history and the alternate governed action stay under More actions.

When an administrator adds a notification destination, EPS now opens the reminder-policy flow with that new destination selected. This avoids re-finding the route and preserves the separate audited policy decision.

Personal notification preferences now use three short steps: delivery channels, timing, then optional quiet time and snooze. Existing personal consent and the Worker-owned preference contract remain unchanged.

Planning Settings now keeps project identity and the required audit reason in the main flow. Calendar, agenda-template, retention, and access-role controls are available under one Operational defaults, retention and access disclosure.

My Work now identifies the nearest due personal action at the top of the queue. Its direct action opens the existing governed completion, response, or review form, rather than asking staff to locate the same item among several registers. Empty queue sections now stay out of the default view, keeping the mobile page focused on work that is actually available; they remain visible when a filter is being used to explain an empty result.

Risks now surfaces a Needs attention total and places unowned, untreated, overdue, or high-score records first with the next remediation called out. Lifecycle changes and risk scoring remain Worker-controlled.

Files and Evidence now places files with unresolved scans first and explains why they cannot yet be used downstream. Clean files remain available in the same register, with their existing access and retention controls unchanged.

File upload now starts with the file and security level. Optional access and retention choices sit under one clearly labelled disclosure, using a plain “Who needs access?” question while preserving the Worker-controlled policy.

Requirement authoring is now split into three short steps: define the request, assign its owners, then set its acceptance check. This is easier to complete on phones while retaining the same required RACI and review safeguards.

Schedule now keeps baseline, dependency, comparison, and scenario tools in an Advanced schedule controls disclosure. Day-to-day work remains focused while every existing governed planning control remains available on demand.

Handoff now shows unresolved gate decisions and selects the available approved baseline when the package form opens. Optional package-format choices sit under a short Package options disclosure. Organizers can still choose another eligible baseline, while the planning service continues to validate and freeze the final evidence package.

Repositories: admin.furries.ph, partners-api, partners.furries.ph (database migration) Status: Invitation admission repair released; Admin and API release tracking continues separately.

What’s Changed

Admin’s Users & access page is now Partner users. Staff can select a partner, see each user’s partner and role, and send or resend email invitations. Invitations use Supabase Auth through the API and keep platform-staff role assignment outside this page.

Impact

Partner access administrators have a dedicated team-membership view. New access records keep an audit reason; duplicate invitations cannot replace an existing role. Email-delivery outcomes are shown separately from saved partner access.

Upgrade Notes

The invitation admission migration is released. It records partner membership for a newly invited Auth account before that person completes their unified profile, so staff can safely retry a previously retained invitation. Admin typecheck, 27 tests and build passed, and desktop/mobile browser flows were checked with synthetic recipients. No real invitation email was sent during verification.

Additional validation: 35 invitation API cases and isolated PostgreSQL checks passed for partner scope, duplicate prevention, audit records and access restrictions.

Repositories: rego.furries.ph, partners.furries.ph Status: Local implementation verified; hosted release pending.

What’s Changed

People resetting a password on RegoSite or Partners can now complete their enrolled authenticator-app check when their recovery session requires it. The reset page asks for a six-digit code only for accounts that need the extra verification.

Impact

MFA-enabled accounts can finish a password reset without reducing the platform’s MFA requirement. Recovery links remain purpose-limited and are removed from the browser address after they are read.

Upgrade Notes

Rego typecheck and its local recovery fixture passed. Partners typecheck and production build passed. Rego’s full production build still needs a reachable local API for public metadata preparation; no reset email or production password change was sent during validation.

Repositories: partners.furries.ph, partners-api Status: Local implementation verified; template publication and hosted delivery remain pending.

What’s Changed

Account-security emails and Partner access invitations now share the clear Furries PH card style already used by Event Planning System (EPS) operational notices. This includes the same readable layout, blue action treatment, product identification, and quieter footer.

Impact

People receiving a sign-in, security, password, account-email, or Partner invitation should see a recognizably consistent Furries PH email instead of a plain invitation or mixed legacy visual treatments. Links, security notices, one-time codes, and account actions remain unchanged.

Upgrade Notes

All thirteen account template files were checked for preserved Supabase placeholders and action conditions. Partner invitation route tests, API type-checking, and representative local email rendering passed. No live email was sent and no production template was published during this work.

Footer update

Every account and operational email now ends with a small, centered Powered by TarsierDesk attribution. The email’s service and security wording remains unchanged; this only standardizes the footer treatment across account, Partner, EMS, EPS, and community messages.

Repositories: partners.furries.ph Status: Local implementation verified; hosted release pending.

What’s Changed

Event organizers can now select View payment proof from a registration payment record and review the uploaded receipt or screenshot in a protected Partners lightbox.

Impact

Payment review stays in the registration workspace instead of opening the proof in another browser tab. Organizers can close the image and continue reviewing or updating the payment status.

Upgrade Notes

Partners typecheck and the registration-roster browser fixture passed. The fixture verified the payment-proof dialog opens with the uploaded image and reported no page errors. No hosted deployment was performed.

Repositories: partners.furries.ph, partners-api, fph-lan-ems Status: Database published and source branches pushed; hosted verification pending.

What’s Changed

Event teams can configure and fulfil SKU-tracked inclusion variations without losing the exact allocated design behind a combined checklist line. If a fulfilled variation is returned, the inclusion-claim desk now requires a reason and records a linked correction instead of silently unchecking it.

Impact

The original claim remains visible for inventory and analytics. The correction restores the same variation SKU to the inventory ledger, keeps its allocation lineage for randomized designs, and reopens the attendee’s checklist line. LAN snapshot import/export also retains the allocation references, so it does not reinterpret an already-assigned random design.

Upgrade Notes

Local rollback certification covered fixed and random variation allocation, per-SKU stock capacity, claim and idempotent return movements. Partners and API typechecks passed. The migration has not been published, no hosted workflow was exercised, and reissuing a returned item is intentionally blocked until its separate audited workflow is implemented.

Repeat-enabled random selections also recheck tracked stock after every draw. A request that needs two units cannot receive the same design twice when only one unit is on hand; the entire allocation is declined without partial results.

When an attendee upgrades tiers, the previous unclaimed variation allocation is no longer presented or counted as the new tier’s reservation. Its historical allocation and any earlier fulfilment receipt remain preserved for audit and analytics.

Removing a future variation group now archives it instead of deleting the allocation history behind prior attendees. It no longer appears in future registration setup or allocations, while earlier randomized outcomes remain auditable.

Bundle inclusions now snapshot their base component at commitment as well. Later catalog edits cannot change the base item owed to an existing attendee; alternative selections explicitly retain no base component.

The pending database rules now also reject any attempt to rewrite those saved base-component facts, including a service-role maintenance write. Archived tier links and variation groups are excluded from the EMS configuration reader and Dealer Den’s future slot-question flow, so a retired offering remains historical rather than resurfacing for a new registration.

When two distinct random-design pools overlap, selection now considers the complete assignment. A flexible earlier draw cannot take the sole design required by a later pool when another valid complete combination exists; impossible pools still decline without issuing a partial promise.

For multi-unit fulfilment lines, check-in staff can record the quantity handed out instead of treating the line as all-or-nothing. Each additional unit is kept as a separate inventory receipt, and returning one portion restores only that SKU unit while the remaining handoff stays recorded. This remains pending database publication and hosted workflow verification.

Repositories: rego.furries.ph, partners-api Status: Local implementation verified; database publication and hosted release pending.

Attendees are now asked an inclusion’s questions for each variation they will receive, even when that variation replaces the base item. Bundle offerings ask about the base item separately. Multiple fixed units and random-design draws each keep their own answer. Organizers reviewing a group registration can see those answers under the correct attendee and item; other group members cannot see one another’s saved answers.

Gift redemption and accepted waitlist checkout use the designs already promised to the attendee rather than today’s edited tier selection. New promises now save the inclusion-question wording too, so later catalog edits do not change what their recipients are asked. Local database rollback tests, Rego browser fixtures, API question-scope tests, and typechecks passed. Older promises without a recorded question copy still use the current wording; the migration is published, but no hosted registration was certified.

Ordinary checkout also checks whether a tier offering changed since it was displayed. If so, the attendee reviews the current items; compatible answers remain filled, and payment details must be reconfirmed. This local optimistic recovery check is not an atomic guarantee against concurrent catalog edits. Gifts and accepted waitlist offers keep their original saved item promises.

If a standard or group rego cannot receive a configured design because variation inventory or its selection pool is unavailable, checkout returns to tier review with a safe item-specific explanation. Dealers Den returns to attendee choices. Answers remain saved, but payment and verification must be reconfirmed. This recoverable response is issued only when cleanup of incomplete regos is confirmed; uncertain outcomes tell the attendee not to retry and to contact event support. Local API cleanup checks and a Dealers Den browser fixture passed; hosted transactions remain unverified.

• partners.furries.ph 51966651 - fix: recheck dashboard saves automatically
• partners.furries.ph 715292ee - perf(dashboard): keep profile and forecast views responsive
• partners.furries.ph c7855b25 - perf: reveal dashboard activity and analytics sooner
• partners.furries.ph 0bfc39a3 - perf: keep account and notification workspaces responsive
• partners.furries.ph 4e553252 - perf: open event operations before initial data reads
• partners-api f2b500ef - perf: overlap dashboard admission checks
• partners.furries.ph 051081b3 - perf: reveal dealer and waitlist workspaces during initial reads
• partners.furries.ph 337f0654 - perf: open more dashboard tools during initial reads
• partners.furries.ph a55013eb - perf: reveal finance and asset records during initial reads
• partners.furries.ph 31bf7055 - perf: show partner workspaces during initial reads
• partners.furries.ph 0723ee77 - perf: open counter and scoped workspaces sooner
• partners.furries.ph 9d81b3e8 - perf: open EMS review and setup controls sooner
• partners.furries.ph 72c7cfeb - perf: load linked operations by active section
• partners.furries.ph f47e2ac1 - perf: reveal scoped settings and planning context sooner
• partners.furries.ph d23bf093 - perf: open core queues and profile setup during reads
• rego.furries.ph 87ef485f - perf(rego): keep registration choices ready during account checks
• docs.furries.ph-rego-speed-20260926 f0dad4d2 - docs(updates): record Rego registration and receipt speed release
• rego.furries.ph 22da6d66 - perf(rego): warm application history and preserve transaction context

TikTok verified the Partners site and the API media-transfer URL prefix through its issued public ownership signatures. Media downloads still require an expiring, scoped grant. Telegram Verify access now saves the formats returned by the bot permission check, so older connections show current image support. Local route and type checks cover the update; all 33 publishing suites passed before this follow-up. TikTok production review and live media delivery remain pending. No new public test posts were created.

Partners now checks current TikTok creator settings whenever an operator opens its publishing editor. The API returns only safe account/audience/interaction/duration fields within the authorized partner. If TikTok cannot provide current settings, sending stays disabled and the operator receives a retry or reconnect message. Direct Post uses explicit interaction choices, music consent and commercial-content classification; photo posts hide video-only controls. TikTok draft uploads remain a creator handoff. Already accepted TikTok jobs can continue status checks without sending media again or inventing consent. The new creator helper passes 52 bounded cases and authenticated route checks cover permission/error isolation; provider/browser checks remain distinct from live media acceptance and TikTok app approval. See TikTok’s requirements. No live test posts or media packs were created.

Validation: 34 local API certification suites passed, with the final provider mode-switch regression suite, full API type-check and Worker dry-run. Git-linked API release 858db934 succeeded; the authenticated hosted creator query returned 200 with private/no-store caching, only safe fields, current account privacy options and a 3,600-second limit. Public Direct Post approval remains false. This read-only proof sent no post.

UI validation: typecheck, production build and the focused desktop/mobile browser workflow passed, with current account reads, explicit choices, retry and client isolation. Screenshots were inspected. Documentation checks passed for all 27 files with no diagnostics. Git-linked UI release: 1a50aa81.