Platform Updates

Repository: rego.furries.ph-v2 — registration review updated.

Event responses in the registration review now show an explicit Question and Answer pair. This makes it clear which configured event prompt each response belongs to, including links and other free-text answers.

Repository: partners.furries.ph — current production application republished.

The Partners dashboard now displays its general workspace navigation when a specialized workspace rail does not apply. The current account-recovery client is also included in the published application, so password-reset requests from Partners identify the Partners dashboard as their return surface.

Repositories: partners-api and partners.furries.ph — profile assets are being transferred into the V2 media store.

Existing profile photos are copied into new platform-owned media assets and the unified profile now stores only the new canonical asset reference. The V2 API does not use prior profile-photo locations as a compatibility source. Photos become available as their verified transfer completes; no action is needed from account holders.

Repositories: partners.furries.ph and partners-api — production database correction published.

Completed attendee profiles now retain their recorded date of birth and prior terms acceptance after the unified-profile migration. This prevents people whose legacy record already held those details from being sent through setup again. Accounts whose original record genuinely lacks a required profile field or attendee username will still be guided to finish that missing information.

Repositories: partners.furries.ph, rego.furries.ph, partners-api, and docs.furries.ph — database, API, and the two main web applications published.

The shared database routines now use the V2 operational identity and unified profile records rather than retired profile tables. Dashboard scope is resolved from an admitted membership, and account creation stays identity-only until the existing profile and admission checks apply. This keeps Rego, Social, Moderation, reporting, registration, and finance workflows on the same V2 identity contract without reintroducing legacy endpoints or compatibility records.

The public API reference no longer advertises retired profile routes. Partners and event operators should use the documented /api/v2/profile contract. The main Partners and Rego sites now serve the V2 applications at their normal addresses; no separate V2 compatibility site is required.

Repositories: partners.furries.ph, rego.furries.ph, and partners-api — production migration and release published.

Every existing attendee record now has a preserved unified profile, including people who have not yet created a sign-in. When one of those people later verifies a matching email address, their existing profile is attached to that account instead of creating a second profile. Unverified sign-ins do not attach or create a profile, and uncertain matches remain untouched for review.

Attendee email, username, terms timestamp, profile-image reference, and notification choices are now also served from the unified profile in Rego. Rego profile completion, registration, saved prefills, waitlists, group-participant checks, and legal notices now read the same unified data. Dashboard-profile fields used by shared services have also moved to the unified profile under their final names; the retired V1 profile endpoints were removed rather than retained as compatibility shims. The former attendee table is now an explicitly named operational identity record for registrations, events, and Social history, while personal profile ownership remains unified. The published migration confirmed complete profile preservation, zero reconciliation mismatches, and no remaining references to either retired profile table.

Repositories: partners-api, partners.furries.ph, and admin.furries.ph — database migration and API deployment published.

The Admin Attendees cleanup now removes a reviewed disposable test-account set through one controlled database operation instead of attempting one network call per account. This prevents large fixture sets from stopping after a small partial removal because of Worker request limits. The confirmation, current FPH-admin authorization, recent MFA requirement, exact-count review, and protected-access exclusions remain unchanged. The final receipt continues to distinguish deleted sign-ins, purged attendee rows, retained operational records, and failures.

Repositories: partners-api, partners.furries.ph, partners.furries.ph-v2, admin.furries.ph, and signals.furries.ph — local implementation and verification complete; database migration and production publication remain separate.

Signals authors can now set a custom survey URL and choose both an overall response cap and a cap for each Furries PH account. A per-account cap automatically requires respondents to sign in before they can begin, and the completion service enforces the cap atomically so concurrent submissions cannot exceed it. Existing uncapped and public surveys remain unchanged.

Responses now use a familiar three-part review workspace in Partners V2 and Admin: Summary for aggregate progress and answer distributions, Question for one selected question, and Individual for a paged submission with its submitted answers. The respondent sign-in view also explains an active account cap. API, Admin, Partners V2, and Signals type checks/builds passed; the database-backed concurrency check awaits the pending local migration set.

Repositories: form-builder, partners.furries.ph-v2, admin.furries.ph, and signals.furries.ph — the Partners V2 and Admin releases are live; Signals site publication remains separate.

Partners V2 and the Admin Signals workspace now use the same Furries PH-branded form-authoring canvas. Its control rail follows the Google Forms question editor: add question, import questions, title and description, image, video, and section. Title-and-description content is saved with the survey and appears to respondents on Signals. Question descriptions are now an explicit More-options choice and choice questions can shuffle their displayed option order, as they can in Google Forms. Multiple-choice and dropdown answers can also route a respondent to a later section. Image, video, and import actions no longer create misleading questions; they are reserved for the authenticated asset and import flows. The V2, Admin, and Signals type checks all passed, and production builds passed. No survey response, media, provider, or hosted record changed.

The authoring canvas now also follows the editor’s active-item behavior: one contextual action rail moves with the selected section, and questions reorder from a visible drag handle instead of separate move arrows. The shared package release was inspected against the signed-in Google Forms editor and verified in a rendered browser preview; Partners V2 and Admin type checks passed after upgrading to the release. Partners V2 and Admin are now deployed; Signals site publication remains separate.

EMS form authoring in Partners V2 now uses that same canvas for registration, activity, Dealers Den, feedback, and volunteer forms. EMS continues to own its existing configuration, validation, conditional routing, managed option images, and response workflows; this update changes only the authoring interface. Its dedicated response types—including image upload, fursona, friend username, and multi-username collection—remain available without changing existing submissions.

Signals authors can now open a visual Flow workspace beneath the question canvas. It shows the default route through sections, shows answer-based routes, and lets an author select a destination section for supported answers. The shared graph contract flags missing destinations and circular paths before a flow can be treated as valid. It is live in both Partners V2 and Admin. Existing responses and publication permissions are unchanged.

The canvas has also been brought into the Furries PH dashboard language: calm white surfaces, blue focus treatment, compact rounded controls, neutral option rows, and clear uppercase section signposts. The authoring flow remains familiar to Google Forms without introducing Google branding or changing Furries PH question capabilities.

Section titles and descriptions now live together inside a single bounded section-details card, making the page hierarchy immediately clear before authors reach its question cards.

Every supported Furries PH question type now renders an appropriate authoring treatment. Authors can immediately recognize text, date/time, choice, dropdown, ranking, matrix, allocation, rating, slider, recommendation, and consent responses while preserving the existing survey contract.

The response-type picker now shows only the current Furries PH choices. It adds Links and Usernames: authors can set each to ask for one to twenty entries, and Signals renders the matching set of respondent fields with link and username validation. Existing published surveys remain readable; no response data changed.

The shared canvas now uses the Partners V2 spacing and surface scale throughout: 16px cards, 16/20px responsive padding, compact 8px controls, consistent field grouping, and the same quiet borders, focus ring, and elevation as other dashboard forms. Its mobile action rail stays compact instead of reserving an empty full-width panel.

All form-authoring action glyphs now use the matching Lucide icon set. On mobile, the active-section toolbar becomes a single, touch-friendly horizontal action row rather than a floating vertical strip; desktop keeps the nearby contextual rail.

Authors can now drag both sections and questions using visible grips. A clear insertion line distinguishes where the item will move, and stacked title, description, and response controls now use deliberate gaps rather than running together.

The drag treatment has been refined to match the rest of Partners V2: grips sit inside existing headings and insertion is a quiet blue line, rather than an additional floating label or card treatment.

The question-type picker now shows each current Signals response capability once. Earlier aliases such as the duplicate short-answer, paragraph, choice, dropdown, and username entries are no longer offered for new questions; EMS-only types are also hidden from Signals. An older saved question remains readable and is explicitly marked as legacy until an author selects a current type.

Signals authoring now uses one connected survey title and description editor. The disconnected duplicate canvas card has been removed, so authors only see metadata that is saved with the survey.

Repository: partners-api and status.furries.ph — deployment pending GitHub App scope verification.

The public Furries PH status collector is now started by the Partners API Cloudflare Cron Trigger every ten minutes. GitHub Actions still collects provider evidence and keeps the public incident history, but it no longer depends on GitHub’s own schedule. Operators should verify that the organization GitHub App has Actions permission for the status repository, then check the next collector run and the published timestamp on status.furries.ph.