Platform Updates

Repository: partners.furries.ph — shared Markdown editor updated.

Markdown source text now keeps its normal reading weight while editing. Bold formatting appears only when an author uses Markdown syntax and views the sanitized preview.

Impact: Requirement instructions and other shared Markdown fields are easier to read and edit. Existing Markdown content is unchanged.

Repository: partners-api — Event Planning requirement policy updated.

FPH administrators, like the selected partner’s administrators, may now create or edit an EPS requirement without assigning a Responsible person. Department leads must still assign at least one Responsible person before saving.

Impact: Administrators can record and route requirements that need a later owner decision. The same server-side rule applies to both new requirements and edits, so the policy cannot be bypassed through another screen.

Repositories: partners.furries.ph and partners-api — Event Planning access is separated by purpose.

EPS gives team members one focused My Work space for their assigned tasks and requirement responses. Shared planning controls — including task assignment, reassignment, schedule changes, and other team coordination — are available only to department leads, planning administrators, partner administrators, and FPH administrators.

Impact: Team members no longer need to navigate leader tools to complete their own work. Existing assignments and requirement responses remain available in My Work.

Repository: partners-api — authentication email delivery updated.

Authentication email delivery now queues sign-in, invitation, and recovery requests in encrypted storage before the authentication service is acknowledged. This prevents a slow email provider from interrupting the request after five seconds. Delivery will use retry and audit states; requests with an unknown provider result will be held for review rather than automatically sending a possible duplicate.

Impact: Account emails may arrive shortly after the request instead of immediately. No action will be needed unless a support team needs to investigate a held delivery.

The dedicated production encryption secret and database migration are in place.

Repository: partners.furries.ph — Event Planning requirement controls updated.

The New requirement action remains available to FPH administrators for a scoped plan, including during a staged API rollout where the optional creation permission is not returned to the dashboard. The planning service still performs the final permission check before a requirement is made.

Repositories: admin.furries.ph, partners-api, and partners.furries.ph — platform account handling updated.

FPH administrators now have an attendee-detail action for permanently erasing a standard attendee account. It requires recent MFA, the account email, and a typed confirmation. The action removes eligible related records and the sign-in identity together; it refuses partner and administrator accounts. This cannot be undone, so use it only where permanent erasure is intended.

Repositories: partners.furries.ph and partners-api — administrator account cleanup controls updated.

FPH administrators can now remove a selected test account and its related fixture records from Users or Attendees. The action requires recent MFA and typing the account email exactly; it cannot remove the administrator taking the action. This is permanent, so use it only for fixture cleanup.

Repository: partners.furries.ph — dashboard notification management updated.

Partners can now open Notifications from the dashboard to review authorized EMS event alerts and EPS Telegram group reminder routes in one place. The page links back to the appropriate event or plan when a setting needs to change, and keeps private chat identifiers and credentials out of the overview. Personal reminder accounts remain private to each team member. No action is needed unless an operator wants to review or adjust an existing route.

Repositories: rego.furries.ph-v2 and partners-api — attendee transaction history updated.

Saved registration prefills now appear in Your transactions as their own clearly labelled record. They remain distinct from a submitted registration or payment and include an Edit prefill action to return directly to the saved event choices.

Repository: rego.furries.ph-v2 — event registration card corrected.

When an attendee already has a saved event prefill, the event card now shows Prefill saved and an Edit prefill action instead of inviting them to start again. Once registration opens, the same saved selections lead to Continue to rego for final review and submission.