Platform Updates

Repository: partners-api

Status: Git release complete

What’s Changed

• The Event Page attestation, public discovery-preference, friendship, and standard moderation live certificates now intercept normal termination signals and finish their existing scoped cleanup before exiting.
• Cleanup removes only the disposable identities and records created by the interrupted certificate. It does not alter member content or operational event data.

Impact

• Operators can safely stop these Social certification checks without leaving fixture accounts, relationships, preferences, Event Pages, or moderation records behind.

Upgrade Notes

• No member action is required.
• The existing canonical CMS-event mapping and production-secret gates for Event Pages are unchanged.

Validation

• Each changed certificate passed Node syntax checks, a termination-cleanup source contract, and the API TypeScript gate locally.
• The Git-connected partners-api Worker build passed before merge.

Repositories: partners-api, social.furries.ph

Status: Git release complete

What’s Changed

• The two production moderation certification checks now intercept normal termination signals and run their existing cleanup before exiting.
• Cleanup soft-deletes temporary test posts and revokes temporary moderation roles and identities, keeping safety evidence intact without leaving public certification content visible.

Impact

• Operators can stop a certification run safely without creating avoidable public test-content residue.

Upgrade Notes

• No member action is required.
• The previously discovered public certification fixture still requires removal by an authenticated production operator; this release prevents a repeat.

Validation

• Both certification scripts pass Node syntax checks and the API TypeScript validation gate locally; the API Worker build passed before release.

Repositories: partners.furries.ph, partners-api, rego.furries.ph

Status: Deployment in progress; the database migration and all three application surfaces are released together

What’s Changed

• Event campaigns can carry one optional flat or percentage attendee discount, with separate switches for ordinary registration, gifted registration, and event shop use.
• Campaign links are standalone: they do not create or depend on an affiliate record.
• Registration, gifts, group registration, Dealers Den, and Event Shop select one eligible discount instead of stacking them. Campaign and affiliate attribution remain recorded independently.

Impact

• Event operators can run a direct promotional campaign without an affiliate reward arrangement.
• Attendees receive only the best eligible discount.

Repositories: social.furries.ph, partners-api, partners.furries.ph

Status: Public read launch complete; authenticated posting, account setup, and moderation certification remain separately gated

What’s Changed

• social.furries.ph now has a live, Git-connected Cloudflare Pages frontend backed only by the existing partners-api Worker.
• The reviewed Social database schema is published after a verified logical backup and scoped migration reconciliation.
• The public local timeline, topic timeline, and event discovery now return bounded success responses. The API uses explicit author relationships so the expanded shared-account graph cannot make post reads ambiguous.

Impact

• Visitors can load the public Social shell and browse its current empty-state timelines without a Pages Function, browser database connection, or a second Worker.
• The public API remains CORS-restricted to the Social site. A signed-in session is still required for account-specific actions.

Upgrade Notes

• No member action is required.
• Operators should keep account creation, posting, uploaded-content handling, and moderator workflows behind their existing authenticated launch checks.

Validation

• Cloudflare Git builds passed for Social Pages and partners-api.
• Production probes from social.furries.ph confirmed 200 responses for public timeline/topic/event endpoints and the expected 401 for an unauthenticated Social session.

Repositories: partners-api, social.furries.ph

Status: Git-connected Worker release completed; Social database migrations and authenticated launch checks remain required

What’s Changed

• The single Furries PH API Worker now serves the existing Social route module at /api/social, restoring the connection used by the Social Pages app.
• A focused route contract now checks that the Worker imports and mounts the Social module, preventing a future deployment from leaving those endpoints unreachable.
• Live cross-origin checks confirm Social requests now reach the API. The unauthenticated session endpoint returns its expected sign-in response, while public timeline and event discovery return a temporary-unavailable response from their handlers instead of a missing-route response.

Impact

• The Social frontend can reach its intended backend boundary without a Pages Function, browser database connection, or additional Worker.
• Social content and discovery are not yet available to members: the temporary-unavailable responses accurately preserve the existing database migration/RLS release gate.

Upgrade Notes

• No member action is needed. Platform operators must complete the verified Supabase backup, migration reconciliation/publication, and authenticated role checks before enabling Social account setup or posting.

Validation

• Social Page moderation route contract: 96 assertions passed.
• API TypeScript validation and Wrangler production dry run passed.
• Git-connected Worker build passed after merge to main; live API probes verified CORS and handler reachability.

Repositories: partners.furries.ph, partners-api, signals.furries.ph

Status: Local integration certificate passed; Git-connected release of the schema and certificate updates remains required

What’s Changed

• Signals now has a repeatable local certificate for the full account boundary: an FPH staff member creates and publishes an FPH-owned survey, an anonymous visitor completes it, then signs in with the same Furries PH account to claim a configured digital reward.
• The certificate also verifies the owner analytics projection and removes its disposable local Auth account. Its synthetic published survey is archived so immutable version history remains intact.
• Fresh databases now give the trusted API only the read access it needs for canonical partner scope, partner labels, and account-to-reward resolution. A completion-command repair also prevents an internal SQL naming collision from blocking public survey submissions.
• Deleting an account now preserves an already-published survey version while removing its publisher reference, so historic survey content does not retain the deleted account identifier.

Validation

• A clean local Supabase reset replayed every migration. The local certificate passed FPH staff authorization, anonymous completion, sign-in reward handoff, digital reward issuance, owner analytics, and disposable-account removal. API TypeScript validation passed.

Repository: cms.furries.ph

Status: Locally validated; deployment pending

What’s Changed

• Directly authenticated Sanity Project Administrators now retain the complete Furries PH Studio workspace even when they also have a scoped editor profile.
• Partner robot sessions remain limited to their signed partner scope. Native non-administrator accounts without a recognized scope now receive no Studio content or creation templates rather than an unrestricted workspace.
• Direct Studio entry remains protected by the existing Partner-dashboard handoff; this change does not weaken the CMS access gate.
• Removed the TarsierDesk attribution badge from the Furries PH Studio interface.
• Gallery batch uploads process up to 12 image optimization and upload jobs concurrently; the progress message now makes that visible.

Impact

• Furries PH administrators can use their native Sanity account without inheriting a partner editor’s document filters, reference-picker limits, required organiser/author validation, or Studio Settings block.
• The account must be a Project Administrator for the exact Sanity identity provider used at sign-in. Accounts from different providers are distinct even when they use the same email address.

Validation

• Studio TypeScript, lint, and production-build checks, plus documentation Astro diagnostics, passed locally. Deployment remains pending.

Repositories: rego.furries.ph, partners.furries.ph, partners-api

Status: Locally validated

What’s Changed

• RegoSite and Partner dashboard setup now require a full middle name rather than initials alone.
• The existing I have no middle name option remains available. Selecting it disables and clears the middle-name field, removes its required state, and suppresses the required marker.
• Profile saves, completion checks, and eligible RegoSite/Partner profile imports apply the same rule.

Impact

• Users with a middle name should enter the complete name, including multi-part names where applicable.
• Users with no middle name can continue using the explicit checkbox.

Validation

• RegoSite and Partner dashboard Astro diagnostics, Partner API TypeScript diagnostics, and documentation Astro diagnostics passed locally.

Repositories: rego.furries.ph, partners.furries.ph, partners-api

Status: Locally validated

What’s Changed

• RegoSite profile saves continue to require a contact number with an international country code.
• A Partner profile without a contact number is no longer treated as complete, so it remains in the required setup path until that detail is supplied.
• Returning Partner operators have their saved profile and address details restored in setup, so they can add the missing number without re-entering them.

Impact

• Attendees and Partner operators must provide a reachable contact number before completing their profile.
• Existing complete profiles with a saved number are unaffected.

Upgrade Notes

• No action is required unless your profile is missing a contact number. You will be returned to Profile setup with your saved details prefilled; add a valid number before continuing.

Validation

• RegoSite, Partner dashboard, and documentation Astro diagnostics, plus Partner API TypeScript diagnostics, passed locally.

Repositories: partners-api, partners.furries.ph

Status: Locally validated

What’s Changed

• New Partner-dashboard users can now copy the compatible personal and Philippine address details from their signed-in RegoSite profile directly into the setup form.
• The import is an explicit, reviewable prefill. It never carries across an attendee username, profile photo, Partner role, legal acknowledgements, or signature.
• The API only returns a candidate owned by the signed-in user, when that user has Partner-dashboard access. It is not cached and does not expose another attendee’s data.

Impact

• Operators with a complete Philippine RegoSite profile can start setup with fewer repeated fields, then review the values, enter their Partner role, accept the Partner agreements, sign, and complete any required MFA as usual.
• Users without a compatible RegoSite profile continue through the existing manual setup flow.

Upgrade Notes

• Deploy the Partner API and Partner dashboard together so the setup control can reach its authenticated import endpoint.

Validation

• Partner API TypeScript diagnostics, Partner dashboard Astro diagnostics, production build, and desktop/mobile visual checks passed locally.