Platform Updates

Repository: Partners. Status: Locally verified; not yet deployed.

What’s Changed

Partner administrators can now invite a new person by email directly from Event Planning departments, giving them baseline partner access and the selected department role in one protected action. Department leads continue to add only people who already belong to their organization and only to the department they lead, while FPH administrators retain the canonical Admin user-access handoff.

Impact

Partner administrators can invite staff for any department in their organization. Department leads cannot admit new organization members or add anyone outside their own department. Every invitation records an access reason.

Upgrade Notes

Partners type-checking and the department-member browser fixture passed locally. The database migration and API route require release before the flow is available in the hosted dashboard; hosted sign-in and email delivery verification remain separate release steps.

Repositories: Partners and Partners API. Status: Live.

What’s Changed

Valid password-reset links now use dedicated recovery endpoints to check an enrolled authenticator. Authenticator verification keeps the credential limited to password reset and preserves it for password-save retries.

Impact

Partners users whose valid reset links showed “Recovery credentials cannot access this resource” can reach the password form after this repair is released. Existing signed-in sessions remain separate from recovery.

Upgrade Notes

The API was deployed before the Partners client. Local browser fixtures passed for valid/invalid links, rejected authenticator codes, completed reset submissions and retry after MFA. The live API route and Partners bundle were verified; hosted email delivery and a live account reset remain unverified.

Repositories: Admin and Partners API. Status: Local implementation and verification; hosted release not verified.

What’s Changed

• Admin setup and session readiness use canonical personal fields and Admin legal receipts. MFA refresh preserves entered details, and failed acknowledgement saves remain retryable.
• Display-name edits update only that field. Country-neutral address fields replace blanket barangay and numbered-street requirements.
• Attendee details use canonical linked or unlinked profiles, including subdivision codes and explicit no-middle-name state. Ownership mismatches stop the read safely.
• Platform communications reads canonical recipient names and preferences, including a fresh announcement opt-out check before delivery. Pawsport person lookups use canonical usernames.
• Event reminders link to their Partners workspace. Unused copied reminder clients and CMS token handoff code were removed from Admin.

Impact

Staff should see current unified-profile details consistently. Administrative roles, MFA, protected-account safeguards, Join consent and historical document records remain independently enforced.

Upgrade Notes

Apply 20260915152000_canonical_platform_communication_directory.sql in the target environment before releasing the coordinated API and Admin changes. It has been applied only to local development. Admin checks/build, the API typecheck and synthetic contract tests passed; canonical joins and bounded recipient pagination were also verified against the local database. No production email, identity erasure or deployment was performed by this audit. Hosted staff-flow verification remains a separate release step.

Repositories: Partners and Partners API. Status: Locally validated repairs; database migrations published through the coordinated release.

What’s Changed

• Partners setup now accepts international addresses without requiring a barangay, postal code or numbered street when those do not apply.
• Dashboard setup readiness reads the unified personal profile and recorded legal acknowledgements. Organization scope comes from authorized memberships.
• Migration checks now use retained historical source and the canonical Rego repository; current guidance recognizes Partners as the migrated V2 application.
• Roster, waitlist, check-in, HR, planning, activities, finance participant lookups, Wallet labels and partner exports now read current unified-profile details. Historical event and financial snapshots retain their original values.
• Offline walk-in creation has a prepared atomic profile/identity operation and guarded cleanup. Recorded consent is required; missing consent is not invented.
• Account and contact/address saves now update only the edited fields, preserving concurrent identity, legal and photo changes from other surfaces.
• Prepared report-resolution and reminder database changes use canonical identity links, contact details and explicit reminder consent.
• Planning department assignments now require existing organization access; they cannot grant organization roles, and revoked access cannot survive through an old department assignment. Arrange organization admission before assigning someone new to a department.
• Embedded image questions retain drag-and-drop and open the correct image picker once. Reviewed Rego runtime source checks and iframe browser tests pass.
• Event-detail save failures preserve the draft and stop later visibility changes; a successful retry saves both changes in order.
• Browser fixtures now use the current Partners session key. Representative Assets, Finance and Planning fixture checks pass after this correction.

Impact

These repairs address rejected valid profiles and obsolete migration checks. Focused tests verify current profile values when older identity copies disagree, and reject missing or mismatched owners without falling back to stale details.

Upgrade Notes

Focused desktop/mobile setup, settings, planning, API access and route checks pass locally. Partners and API typechecks and the Partners build pass. No deployment or database cutover is included. Operators do not need to change existing records as part of this local audit.

Remote migration history confirms the walk-in, incident-resolution, department-admission and reminder migrations are applied. Their local database tests use isolated fixtures and roll back all changes. An additional disposable full-schema rehearsal preserved foreign keys, triggers, policies and permissions; all four migrations and their required reminder prerequisites passed, and the temporary database was removed. Verify the coordinated API/frontend release and affected hosted workflows before claiming production application compliance.

Repositories: rego.furries.ph, partners-api

Status: Locally verified repairs; coordinated release pending.

What’s Changed

• Rego verification uses canonical nested profile responses and dedicated username, photo and notification routes. Current native route inventory includes gift receipts and clearly labels design references.
• Editing an unchanged address preserves its subdivision code. Pawsport reads require complete credential history, and Fursona reference-sheet failures remain visible inside the manager dialog.
• Legal document checks no longer require deleted source files; approved Terms and Privacy text is unchanged. Current instructions and fixture defaults use the canonical repositories.

Impact

These changes address profile consistency and recovery feedback for attendees. Rego API consumers now use current canonical names, usernames, contacts and preferences. A reproduced missing-email initialization defect for verified new accounts is fixed locally, including subsequent verified email changes.

Upgrade Notes

Rego typecheck/build, 10 account/profile suites, 22 consumer suites, nine new-account browser cases and 21 real local API/database checks pass. Canonical identity, consent, friendship and transactional SQL checks also pass. Browser mocks and local email confirmation do not certify hosted providers.

Apply 20260915154500_rego_canonical_profile_consumers.sql with its ordered prerequisites before the coordinated API/frontend release, then verify hosted signup, profile setup, prefill and registration. The migration is applied locally only; no production release was performed. The Rego V2 contract audit records scope and evidence.

Repository: rego.furries.ph

Status: Local verification; production rollout pending.

What’s Changed

• The new-account prefill recovery, profile setup return flow, and native V2 route checks now live in the canonical Rego repository. Existing account-creation error guidance is preserved.
• Repository guidance now identifies the current React application and archived checkout boundary.

Impact

Attendees receive the transferred setup and prefill improvements when this canonical application is released with its API dependencies.

Upgrade Notes

Use rego.furries.ph for future work and release preparation. Nine new-account browser fixture cases, four profile-return cases, prefill recovery and responsive save/reopen checks pass against its local server. API/database results in the earlier entry are historical evidence and were not rerun during this transfer. No deployment is claimed.

Repositories: partners-api, rego.furries.ph

Status: Local repair; production rollout pending.

What’s Changed

• Registration and prefill use the current account identity link and shared unified-profile validation. The old duplicate registration validator has been removed, fixing a path where newly created accounts could complete their profile but still be rejected at submission.
• Event forms wait until required profile details are confirmed. Incomplete accounts return to their event after profile setup.
• Failed profile or saved-choice reads offer a retry instead of opening an incomplete form. Recognized profile errors provide setup guidance.

Impact

New attendees should no longer need to repeatedly complete an already-finished profile because of an older identity link. Required details, consent, ownership checks, and the free nature of prefill remain enforced.

Upgrade Notes

Release the API and Rego frontend together with the existing profile-readiness changes. Frontend typecheck/build and nine desktop/mobile browser fixture groups pass, along with 122 API profile/identity/username fixtures. Twelve real local HTTP/PostgreSQL checks reproduce the old rejection and verify corrected prefill and free registration persistence, followed by fixture cleanup. Local email confirmation was simulated. Full API typecheck remains blocked by an unrelated existing planning-notification error. No production deployment or affected-account certification is claimed.

Repositories: partners-api, partners.furries.ph

Status: Deployed and verified with a fresh Admin sign-in email.

What’s Changed

• Sign-in email delivery runs independently, one email per queue invocation, while retaining the free plan and duplicate-send protection.
• Account-change notifications have explicit messages instead of blank verification-code emails.
• Authentication emails name the requesting site when available and no longer advertise account usage on other sites.
• Missing codes and unsupported email events are rejected before delivery is queued.

Impact

People signing in or managing account security receive wording appropriate to the request. When the request site is unavailable, the message uses neutral account wording.

Upgrade Notes

Fallback templates and subjects match the published configuration. The isolated API release passes TypeScript, build, signed-hook, queue-dispatch and delivery-state checks. A fresh Admin request was sent on its first attempt in about 18 seconds; its isolated queue execution succeeded and the recipient confirmed arrival. The live email names Admin only.

Release Notes

Repository: partners.furries.ph · Status: Deployed.

What’s Changed

• Requirement board cards now show a compact delivery count, due date, and named RACI assignments.
• Cards keep one Open requirement action. Delivery work, conversion, removal, review, and approval actions appear in the detailed requirement view.
• Coordinators can drag a requirement card to update its linked delivery tasks. This does not submit or approve the requirement.

Impact

Department leads, administrators, and team members can scan ownership and delivery progress without a crowded card. Detailed actions remain available in the requirement register.

Upgrade Notes

No operator setup is required. Browser checks cover RACI display, drag updates, authorization scope, conflict feedback, detailed actions, and phone layout.

Repository: partners-api · Status: Local implementation; not deployed.

EPS operational emails now use the Furries PH email card style and include the assigned work item or requirement, the recipient’s RACI role, the complete RACI roster, department, status, priority, progress, start time, deadline, and a direct workspace action. Dates use the planning project’s timezone. Email delivery stores this context as an immutable outbox snapshot; the workspace remains the live source of truth.

Impact: Assigned planners receive an actionable assignment or deadline message instead of a generic reminder line. Optional Telegram, Discord, and SMS messages remain compact.

Validation: A synthetic rendered email screenshot, EPS notification contract check, and API type check pass locally. No email was sent and no deployment is claimed.