Platform Updates

Repositories: partners.furries.ph-v2

Status: Local implementation in progress; existing Partners dashboard remains unchanged

What’s Changed

• V2 now shows the same scanner-safe email-action handoff before an invite, recovery, magic-link, signup, or email-change confirmation continues. Operators must explicitly select Continue; link scanners do not complete the action automatically.
• The V2 email-code confirmation callback now validates its destination within the dashboard, rejects malformed and expired links with a clear recovery path, refreshes the existing session, and returns the operator using replace navigation.
• No partners-api behavior, schema, or deployment has changed. The larger account-setup and MFA completion flows remain in progress.

What To Do

• Use the current dashboard in production until the V2 authentication family is fully certified with real email links and authenticated-browser coverage.

Repositories: partners.furries.ph-v2

Status: Local implementation in progress; existing Partners dashboard remains unchanged

What’s Changed

• The V2 /login route now uses the shared protected-session sign-in surface instead of a placeholder. It supports the existing password, email-code, and passkey methods through the current Worker contract.
• After a valid V2 session is available, the route returns the operator to the dashboard; loading and session-start failures use the same reusable feedback states as protected routes.
• No partners-api behavior, schema, or deployment has changed. The larger account setup, email-confirmation, and MFA completion routes are still being ported separately.

What To Do

• Continue using the existing dashboard for production operations while the V2 auth family and authenticated-browser certification are completed.

Repositories: partners.furries.ph-v2

Status: Local implementation in progress; existing Partners dashboard remains unchanged

What’s Changed

• Unified V2 check-in can now record both an item’s availability and receipt in the same protected handoff save, matching the existing dashboard workflow.
• When an event separates inclusion claims, receipt remains controlled by the claim workflow while staff can still correct availability. The shared checklist surface retains the same server-owned payload.
• Check-in and claim desks now use role-specific queue categories with counts and refresh their protected entry list while the active dashboard tab is visible.
• Protected check-in review now exposes the attendee or dealer identity, payment, Pawsport, registration/package, slot, and existing check-in audit context before staff complete a handoff.

What To Do

• Continue using the existing dashboard for production operations while V2 on-site queues, scanner controls, and authenticated-browser certification are completed.

Repositories: partners.furries.ph-v2

Status: Local implementation in progress; existing Partners dashboard remains unchanged

What’s Changed

• V2 staff assignments now draw from active department members and accepted volunteer applications, preserving their department and volunteer-position context.
• Staff can choose registered locations and see free versus overlapping people before adding a shift; all roster data continues through the existing protected human-resources snapshot/save contract.
• The staff roster now renders event-day timeline tabs and clipped shift blocks across its saved planning window; selecting a block opens the controlled assignment editor.
• The timeline grid’s drag, resize, and row-order interactions are still being ported separately. No partners-api behavior or schema was changed.

Repositories: partners.furries.ph-v2

Status: Local implementation in progress; existing Partners dashboard remains unchanged

What’s Changed

• V2 registration records now retain the existing protected Worker’s attendee, fursona, registration, payment, Pawsport, timeline, and registration-form-answer data instead of reducing the roster to a minimal list.
• Event teams get separate read-only attendee and payment/proof views, named tier and add-on context, protected attendee messaging, canonical receipt resend, branded follow-up previews, and visible-tab refresh while retaining the existing sequential payment-status mutation contract. The roster now becomes an attendee-card workspace on narrow screens instead of forcing a wide table.
• FPH administrators additionally receive the existing confirmation-gated event registration wipe control and its returned deletion receipt; it is not shown to partner roles.
• The new shared read-only detail-list primitive is available for other operational dialogs. No partners-api behavior or schema was changed.

What To Do

• Continue using the existing dashboard for production operations. The V2 route has passed local typecheck, production build, source-drift, and diff checks; authenticated browser certification is still pending.

Repositories: partners.furries.ph-v2

Status: Local implementation in progress; existing Partners dashboard remains unchanged

What’s Changed

• Added a native V2 dashboard shell with desktop navigation, an accessible mobile drawer, active-partner selection, and session recovery/sign-in states.
• The V2 dashboard overview now reads the existing Partners Worker access and overview projections; no partners-api behavior or schema was changed.
• Added source-drift and implementation-parity audits. The current V1 baseline contains 149 pages, 43 reusable components, 74 native dialogs, and 41 confirmation call sites.

What To Do

• Use the existing dashboard for production operations. Review the V2 local implementation while EMS event directory, creation, and details are rebuilt next.

Repositories: partners.furries.ph-v2

Status: Local V2 preview available for design review; this does not cut over the existing Partners dashboard

What’s Changed

• The Partners canvas now lives in the V2 React Router application and is explicitly labelled as a V2 target design system rather than a completed legacy-dashboard migration.
• It exposes the 149 contracted V2 routes, 43 reusable source-component targets, 93 audited form-producing sources, 63 UI-emitting runtime sources, and 92 modal/drawer/popover targets, alongside all product families, form controls, responsive shell states, register states, and end-to-end registration, safety, planning, and asset workflows.
• The canvas now renders all 149 route boards and all 43 component boards as directly inspectable V2 design-language previews, with twelve end-to-end mutation-form journeys covering event, safety, asset, planning, finance, access, survey, communications, and profile operations.
• Its form-source ledger maps every legacy Astro file that produces form controls to the editable field library and matching contextual workflow.
• Each route target preserves its migration-source reference so implementation work can be traced without claiming that feature parity already exists.

What To Do

• Review the V2 design canvas before rebuilding individual product routes. No operator workflow or public registration behavior has changed.

Repositories: rego.furries.ph-v2

Status: Preview deployed for design and parity review; this does not change the current attendee site or partners-api

What’s Changed

• The native React Rego v2 canvas now provides editable previews for the full attendee-site route inventory, including payment-return and third-party notices pages that were previously outside the route index.
• The canvas now includes named reusable components, native input and dynamic question types, source-specific registration, commerce, Dealers Den, volunteer, transaction and account workflows, plus desktop and mobile modal and confirmation states.
• The final parity pass adds source-specific page compositions for every route, all 31 reusable source components, image-upload and conditional-question states, responsive 390 px verification, and an accessible link-copy surface for browsers that cannot use the clipboard.
• Runtime-only attendee UI is also represented: phone-country eligibility, conditions-scroll acceptance, payment-proof progress and retry, local QR generation, rich Markdown/Mermaid content, and SPA save/recovery states.
• The source-traceability ledger now names all 60 legacy page files, 31 reusable components and 36 UI-emitting runtime modules. Each runtime entry opens its own editable state and links to its complete page, workflow or dialog design instead of relying on a generic substitute.
• Passkey and authenticator flows describe the browser/device credential picker accurately and show all safe fallback, recovery and verification states.

What To Do

• Review the Rego v2 preview canvas before implementation starts. Operators and event teams do not need to change existing registrations, payments or account settings.

Repositories: partners.furries.ph, partners-api

Status: Local implementation verified; publish the database migration and deploy the dashboard and pricing API before using the new controls

What’s Changed

• Event teams can now set optional start and end times for a standalone campaign discount, as well as an optional whole-number redemption limit.
• The same campaign rules are enforced when a discount is quoted or redeemed through standard registration, gifted registration, Dealers Den, and Event Shop. Expired, not-yet-live, and exhausted campaigns cannot apply a discount.
• Leaving each new field blank preserves the existing always-available, unlimited campaign behavior.

What To Do

• Set the campaign schedule and redemption limit in EMS before sharing the campaign link. Publish the pending migration and deploy both applications so every registration path enforces the selected controls.

Repositories: rego.furries.ph, partners.furries.ph, partners-api

Status: Live attendee-site, event-dashboard, and pricing API update; re-copy campaign links before distributing or retrying them

What’s Changed

• Rego now retains recognised affiliate and UTM fields during SPA navigation, scoped to the event that received the link. Generated campaign and affiliate links also include first-party attribution mirrors, so privacy browsers that remove generic UTM fields cannot remove the registration discount.
• Standard registration, gifting, Dealers Den registration, and Event Shop read that shared attribution. Campaign discounts no longer depend on enabling an affiliate code for the attendee.
• When a held registration slot expires, Rego now explains the outcome and presents a clear Start again action instead of an inline text link.
• Campaign edits now reload the authoritative saved program before the dashboard clears its unsaved state, so the displayed discount always matches the stored campaign after Save.

What To Do

• Copy a fresh campaign link from the event dashboard, then reopen it and continue through registration. The campaign discount should appear in the quote when the campaign is eligible, even if the browser hides UTM fields.