Platform Updates

Repositories: partners.furries.ph, partners-api

Status: Released

What’s Changed

• Account Settings now recognizes when a registered passkey is protecting an account even if no authenticator app is configured.
• Before adding an authenticator app in that case, the page explains the requirement and offers a direct Confirm with passkey step.
• A successful passkey confirmation now authorizes authenticator-app enrollment, and generated setup details include an Open authenticator app button for compatible mobile authenticator apps.
• The API reports this account-level passkey state through the existing MFA status response and fails closed if it cannot verify the factor inventory.

Impact

• Accounts with no authenticator app can no longer appear to have no MFA while being blocked from adding one. Confirming the existing passkey refreshes the required security check, then QR-code setup can continue.

Upgrade Notes

• Reload Account Settings. If you see the passkey confirmation card, use the passkey already registered to your account, then select Generate QR code.

Validation

• Partner API authentication certification and TypeScript diagnostics, Partner dashboard Astro diagnostics, and production deployment checks passed.

Repositories: partners.furries.ph, partners-api

Status: Locally validated

What’s Changed

• FPH administrators now see each Partner user’s and attendee’s saved contact number directly in the Admin directories, and can search those directories by number.
• The protected attendee-directory API now returns the saved contact number instead of an empty placeholder.
• These details remain available only through the existing FPH-admin access boundary.

Impact

• Platform staff can identify and contact the right person without opening a separate profile panel or seeing a misleading dash for a saved number.

Upgrade Notes

• Deploy the Partner API before the Partner dashboard so attendee numbers are available when the updated directory is served.

Validation

• Partner API type checking and Partner dashboard Astro diagnostics passed locally. Documentation checks and static build also passed locally.

Repository: rego.furries.ph

Status: Released

What’s Changed

• RegoSite now reserves the account-link window immediately when a user selects Discord or Telegram, then opens the provider authorization page after the secure link request finishes.
• The fix covers Friends, Profile Setup, and Dealers Den application flows.
• Strict browser popup policies no longer block account linking merely because the authorization request is asynchronous.

Impact

• Signed-in attendees can link Discord and Telegram accounts again without changing callback settings.
• Existing linked accounts and registration-linked community access remain unchanged.

Upgrade Notes

• Reload RegoSite, then select Link Discord or Link Telegram again. Allow the browser popup if it is explicitly disabled in browser settings.

Validation

• RegoSite social integration source checks, browser regression checks, isolated Astro diagnostics, and production static build passed. The production Pages release contains the popup-reservation fix.

Repositories: furries.ph, partners-api, partners.furries.ph, rego.furries.ph, social.furries.ph, cms.furries.ph, and docs.furries.ph. Status: Released.

What’s Changed: Added a reusable bottom-center problem-reporting button and API-backed GitHub issue intake. The form fills username and display/furry name automatically from login, keeps them read-only, requires review of editable diagnostics and consent to public sharing, and is designed to let visitors report without a GitHub account. Diagnostic capture is bounded to browser context, recent debug/log/info/warning/error messages and failed-fetch metadata; it is not a full console history or remote debugging session.

Impact: Visitors can describe broken website behavior and share reviewed debugging context with maintainers. Reports belong in the public issue tracker, so confidential incident details, legal names, contact details and credentials must not be included. Existing safety-reporting workflows remain separate.

Upgrade Notes: The organization-owned App is installed for the tracker only. The API and site releases passed their build checks. A controlled delivery verification remains part of routine release monitoring. See Report a website problem for the reporting and privacy guidance.

Repositories: admin.furries.ph, partners-api, partners.furries.ph, partners.furries.ph-v2.

Status: Admin production build, API and database migration published; custom-domain DNS remains pending. No real email was sent during verification.

What’s Changed

• Protected Admin pages require a canonical FPH staff role, including Signals and account setup. Feature permissions and API authorization still apply.
• Join entries now have a selectable roster, mobile cards and grouped details.
• Separate sitewide and Join email workspaces support recipient selection, branded review, confirmation and delivery history.

Impact: FPH operators gain dedicated administration workflows. Partners parity goals exclude these Admin-owned surfaces; partner/event communications and security scans remain in scope.

Upgrade Notes: Client checks, synthetic browser workflows, API behavior tests and disposable PostgreSQL tests pass. Production database permissions and Auth callbacks are verified; the deployed API rejects unauthenticated Admin requests. Cloudflare DNS must point both Admin hostnames to the new Pages site before custom-domain use. Staff sign-in and provider email delivery remain unverified.

Repositories: social.furries.ph

Status: Settings clarity released; existing account, event, and retention policies are unchanged

What’s Changed

• Social Settings now explains that account setup needs only e-mail, profile name, username, and password.
• It makes clear that Rego asks for extra details only when a member selects a feature that needs them, with shared details shown as reviewable prefill.
• It also states that planned and past event activity is private until an eligible disclosure is chosen, and that registrations, payments, check-ins, and event answers are not copied into a Social profile.

Impact

• Members can understand the shared login without confusing it for a merged Social and event profile. This is an explanatory Settings improvement only; it creates no new data transfer, sharing setting, browser request, API runtime, or federation path.

Upgrade Notes

• Event disclosure remains optional and subject to existing member, organizer, audience, and safety rules. Broader retention/policy and human-release evidence remain separate controlled-alpha gates.

Repositories: partners-api, social.furries.ph

Status: Controlled alpha evidence refreshed; public-scale and federation boundaries remain unchanged

What’s Changed

• Re-ran the Social account export/deactivation, moderation role/RLS, bounded request-capacity, restricted retention, held-media, and encrypted recovery exercises from a clean API release worktree.
• Added a guarded mail/support transport check. It sends one controlled message only when an explicit local certification gate is set and verifies the configured support reply path plus provider acceptance.

Impact

• Staff can repeat the mail/support readiness check without adding a runtime, direct database client, Pages Function, Queue, KV store, or AI moderation path. The existing restricted-alpha safeguards remain fail closed.

Upgrade Notes

• Provider acceptance does not prove inbox placement or a human support reply. The bounded capacity check is not a claim of unlimited traffic, and ActivityPub federation, appeal outcomes, and destructive retention remain disabled.

Repositories: partners-api, social.furries.ph

Status: Hosted identity-link race proof completed; retention and broader human-release evidence remain separate

What’s Changed

• The Social-to-Regosite optional account-link certificate now races two rightful-owner confirmation requests for one fragment-only continuation.
• The deployed API accepted exactly one request and rejected the concurrent duplicate, proving its one-time database lock under an actual race rather than only a sequential retry.
• Existing cross-user denial, expiry, revocation, relink, and direct-table RLS checks remain part of the self-cleaning hosted exercise.

Impact

• Members retain the same explicit, optional account-link flow. The change adds no cross-domain session, additional Worker, credential transfer, signing key, direct database access, or data sharing.

Upgrade Notes

• The opaque continuation is randomly generated and stored only as a SHA-256 digest; ActivityPub/federation signing keys remain deferred. Retention/ deletion policy and broader human release evidence are still tracked separately.

Repositories: social.furries.ph, partners-api

Status: Certified for the limited local alpha; federation and destructive moderation remain disabled

What’s Changed

• Completed controlled readiness exercises for role/RLS isolation, staff grant expiry and revocation, held-media review/release, deterministic non-AI triage, configured mail-provider acceptance, bounded Worker request budget, encrypted logical export/recovery, and restricted retention handling.
• Furries PH Staff remains the collective moderation owner. The current launch profile rejects appeal-reviewer grants and retention-purge requests, so routine staff actions remain reversible and attributable.
• The operational certificate records what was proved and its limits, including cleanup of all temporary identities, content, logs, and encrypted drill artifacts.

Impact

• Support and moderation teams have a documented, tested restricted-alpha operating baseline without adding a Worker, Pages Function, Queue, KV store, direct database access, or AI moderation decision path.

Upgrade Notes

• This is not a broad public-scale capacity claim, a mailbox-delivery promise, an independent-reviewer workflow, or ActivityPub approval. Those changes require separate evidence and an approved operating decision.

Repository: social.furries.ph

Status: Policy baseline recorded; tabletop and controlled-alpha operating evidence remain required

What’s Changed

• Published the first Furries PH Social moderation policy for the restricted alpha. It sets clear rules for safety, harassment, privacy, consent, fraud, creator rights, sensitive-content warnings, reports, and staff recusal.
• The policy makes Furries PH Staff the collective policy owner, sets a 1 December 2026 review date, and defines a privacy-minimised retention target for moderation records and audit receipts.
• It confirms the current safety boundary: deterministic anti-abuse controls may prepare review work, but cannot decide subjective cases, remove content automatically, restrict accounts automatically, or use AI image/text triage.
• The restricted no-independent-reviewer profile remains in force. Appeal intake is available, while final appeal outcomes and retention purges remain disabled until their required separation-of-duties safeguard exists.

Impact

• Members have one readable Social-specific policy and can understand the available report, notice, correction, and comfort-control boundaries.
• Moderators have a documented proportional-enforcement and evidence-minimised operating baseline. The policy does not enable federation, a new runtime, direct data access, or automatic moderation.

Upgrade Notes

• Before a broader launch, Furries PH Staff must complete the documented moderator tabletop, evidence-access review, recovery exercise, and controlled-alpha operating approval. Any material policy change will receive a new version and effective date.

Validation

• Policy research reviewed current BARQ, Bluesky, Mastodon, and Community/IWAG public guidance and adapted it to the Furries PH local-alpha architecture.
• Social documentation whitespace validation passed locally.