Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Partner members enter Event Planning only
Repositories: Partners dashboard and Partners API. Status: Local checks passed; hosted access remains to verify after release.
What’s Changed
Partner members now land in Event Planning after sign-in. The dashboard hides other workspaces for that role and redirects direct dashboard links back to Event Planning. The API limits partner-member permissions to planning work, including older saved grants and separate asset, finance, and linked-operations assignments. Partner admins and other specialist roles keep their existing access rules.
Impact
Partner members can work within assigned event plans and departments without seeing unrelated partner operations. Account security remains available when needed for sign-in.
Validation
Local dashboard type checking, a mocked browser route and navigation check with a screenshot, API type checking, and 20 modular-permission checks passed. Hosted sign-in and authorization were not exercised.
Partners profile setup aligned with Rego
Repository: Partners dashboard. Status: Local type check, build, unified-profile contract, and desktop browser screenshots passed; hosted setup remains to verify after release.
What’s Changed
The dashboard setup now follows Rego’s Identity, Address, Security, and Review steps. It collects the shared attendee username, uses country-aware address choices and mobile-number validation, and lets people prepare an optional cropped profile photo. Security includes optional Discord and Telegram account links. The dashboard’s four required legal documents and account security checks remain part of setup.
Impact
People setting up dashboard access can complete the same personal profile used by Rego while reviewing the dashboard-specific agreements. Their details can prefill later attendee forms for review; event-specific answers and acceptances remain separate.
Validation
pnpm typecheck, pnpm build, and pnpm certify:v2-unified-profile passed locally. A mocked desktop browser run captured the Identity and Address steps with no page errors. Live account setup, media upload, and hosted behavior were not exercised.
Rego tier community benefits and account linking
Repositories: RegoSite and Partners API. Status: Local type checks and desktop/mobile browser fixture passed; hosted Discord and Telegram delivery remains to verify after release.
What’s Changed
Event tier cards now show any assigned Discord roles and Telegram group or member tag under Community access, separate from included items. On the attendee details step, a selected tier with community access suggests linking whichever Discord or Telegram account is missing. The controls use the same account linking flow as Friends.
Impact
Attendees can see community benefits before choosing a tier and link accounts during registration without losing their form progress. Linking is optional at this step; an account can also be linked later from Friends. Discord role names use a generic label when the provider cannot supply the current name.
Validation
Local API and RegoSite type checks, social integration certification, and a desktop/mobile browser fixture passed. The fixture checks tier labels, separate presentation, and provider-specific link prompts. Live OAuth callbacks and role or tag delivery were not exercised.
Discord role selection for registration benefits
Repositories: Partners dashboard and Partners API. Status: Local checks completed; hosted Discord permissions and role creation require verification after release.
What’s Changed
Registration tier and add-on benefits now show the current roles in the event’s selected Discord server. Organizers can choose assignable roles by name, refresh the list, and create a new server role from the same editor. Roles the bot cannot assign remain visible with their unavailable state.
Impact
Organizers no longer need to copy Discord role IDs when setting registration benefits. Creating a role changes the linked Discord server immediately; saving the registration draft still controls when that role becomes a tier or add-on benefit.
Validation
Local Partners and API type checks and a browser fixture cover role listing, selection, creation, and the editor layout. These checks do not confirm the live bot’s role permissions or hosted rollout.
Personal bot setup grouped on EPS Notifications
Repository: Partners dashboard. Status: Local type check and mobile browser flow passed; hosted staff and bot delivery need a fresh check after rollout.
What’s Changed
Each Telegram and Discord card on Planning → Notifications now contains its personal account link, private bot status, verification control, and Test DM action. Staff can repeat the bot permission check from the same card after a successful verification.
Impact
Staff no longer need to move between separate account and reminder sections to set up a bot DM for the selected event plan. Account links remain personal; the bot still needs a successful private send before EPS marks delivery ready.
Upgrade Notes
Select an event plan, link the personal account in its card, then use Open bot and Verify DM for Telegram or Check DM permission for Discord. Use Test DM after readiness is confirmed. Local browser checks used fixture data and did not prove a live provider send.
Clearer Discord private-message checks in EPS
Repositories: Partners API and Partners dashboard. Status: Local validation completed; hosted Discord delivery requires a fresh staff check after rollout.
What’s Changed
EPS now distinguishes a Discord recipient DM refusal from bot access, rate limit, account, and message-format failures. Notification settings show guidance for the actual delivery result instead of labeling every Discord 400 or 403 response as a blocked personal DM.
Impact
Staff can see whether to allow DMs in a shared server, re-link an account, wait before retrying, or ask an administrator to repair the bot. A Discord channel becomes ready only after the bot successfully sends a private permission check.
Upgrade Notes
On Planning → Notifications, select the event plan and run Check DM permission again after the API rollout. The previous “blocked” result did not identify which Discord error occurred.
EPS navigation follows the selected event plan
Repository: Partners dashboard. Status: Local type check, build, and mobile browser navigation check passed; hosted rollout is pending.
What’s Changed
Before an event plan is selected, the Event Planning sidebar shows Overview, My Work, and Notifications. Plan-specific coordination, files, readiness, and management links appear after a plan is selected and its coordination access is confirmed.
Impact
Staff no longer see plan-specific destinations before choosing a plan. Personal notification setup remains available before selection.
Upgrade Notes
Open an event plan from Planning Overview to reach its plan-specific workspace. The local browser check covered the sidebar before and after selection; it did not verify a hosted session.
Personal bot account links on EPS Notifications
Repository: Partners dashboard. Status: Local type check, build, and browser render passed; hosted provider consent remains a separate check.
What’s Changed
Staff can link, relink, or unlink their personal Telegram and Discord accounts directly on Planning → Notifications, including before selecting an event plan. The plan’s private bot readiness refreshes after a link changes. Bot permission and Test DM controls remain beside the event plan’s reminder channels.
Impact
Staff can complete the identity and private-message setup in one workspace. A linked account alone does not mark a bot route ready; the bot still needs to confirm a private send. Partner-admin notification preferences remain under their existing access control.
Upgrade Notes
Choose an event plan after linking to complete the bot’s private-chat check and send a test DM. The local browser render used mock account and plan data; live OAuth consent and provider delivery were not exercised by that check.
Personal Telegram and Discord links in Partner Account Settings
Repositories: Partners dashboard and Partners API. Status: Local type checks, dashboard build, and Account page browser render passed; hosted OAuth and bot delivery still require a signed-in canary.
What’s Changed
Staff can link, relink, and unlink their own Telegram and Discord accounts from Settings → Account security. The page displays each personal link beside the separate EPS private-bot readiness controls. Account linking is available to signed-in dashboard users without organization integration management access.
Impact
Staff can complete the identity step for personal EPS direct messages from their own account page. A linked identity still needs a confirmed private bot chat before EPS messages are ready. Organization chat and server integrations remain separate.
Upgrade Notes
After linking, open the Telegram bot and send /start, or allow Discord bot DMs, then confirm private delivery in the event plan. The account page change was checked locally with a mocked browser session; provider consent and hosted private sends were not exercised in that fixture.
Immediate Rego confirmation email corrected
Repository: Partners API. Status: Local email and registration checks passed; hosted mail delivery pending.
What’s Changed
The initial email for new Good faith registrations and free Hybrid registrations confirmed at submission now says Rego confirmed. Registrations awaiting payment review continue to have an email headed Rego received. The confirmed email includes the registration reference and total due.
Impact
Attendees can distinguish an immediately confirmed registration from one still awaiting review when the message arrives. Existing registration statuses and email preferences are unchanged.
Upgrade Notes
No operator action is needed. The affected registration was confirmed and its attendee was opted in, but historical provider delivery cannot be established from the registration record. Local rendering, route mail scheduling, and type checks passed; verify a real mailbox after release.