Platform Updates

Repositories: Partners database tests and Social. Status: Local validation.

What’s Changed: Added isolated native PostgreSQL tests for duplicate session creation, simultaneous stop/update and cleanup of locked expired fixes.

Impact: The tested race cases pass, but the tests confirmed a shared-lock bottleneck affecting unrelated account updates. Location sharing remains disabled.

Upgrade Notes: PostgreSQL 17.10 run exited successfully and its temporary server stopped. Replace the shared lock and validate production schema/Auth, load and restoration before publishing the held SQL draft.

Repositories: Partners database draft and Social. Status: Local, not enabled.

What’s Changed: Added service-only cleanup of expired location fixes in bounded batches. Cleanup keeps fresh fixes and does not remove session records.

Impact: Location collection and automatic cleanup remain disabled.

Upgrade Notes: Isolated database checks pass batch caps, repeated empty runs, access denial and expiry enforcement before cleanup. Concurrent execution and restoration safeguards still require validation before publication.

Repository: partners.furries.ph-v2. Status: Local preview, not deployed.

Volunteer positions now follow V1’s expandable-card workflow: edit fields in the page draft, then Save positions or Revert. Existing records start collapsed; new records open immediately. Descriptions use shared Markdown authoring and Rego’s sanitized preview. Cards show unsaved changes and exclude section headings from question totals. Hidden cards retain pending controls and uploads.

Ten inline-editor and five timer-controlled upload browser groups pass, with no API requests or storage writes; the 539-file application type-check is clean. Import/nested-preview reruns and authenticated production verification remain open. No partner API changes or operator action are required for this local work.

Repositories: Partners database draft and social.furries.ph. Status: Local only.

What’s Changed: Fixed a draft location-access revocation gap affecting an old identity with another active login. Added database checks that block/unblock and restriction/reactivation cannot restore previously revoked sharing grants.

Impact: Location sharing remains disabled; no production location data is collected by this change.

Upgrade Notes: Isolated SQL checks pass. The draft remains excluded from automatic migration publication pending concurrency, Auth and retention validation.

Repositories: partners-api and social.furries.ph. Status: Staged, not enabled.

What’s Changed: Location-sharing command handlers now use bounded requests, login-session binding and private, explicitly filtered responses. Database transactions and revocation are being validated before any rollout.

Impact: Members are not being tracked; no location-sharing route is enabled.

Upgrade Notes: Typechecking and 181 local handler cases pass. The database prototype is excluded from automatic migration publication. Database, privacy, capacity and device validation remain required; deployment continues through Git integration only.

Repository: rego.furries.ph-v2. Status: Local certification safeguard validated.

The fixture-cleanup preflight now requires a loopback Supabase configuration, not just a localhost Worker. It refuses hosted targets before signing in or creating records. Fourteen URL-policy cases and a zero-network rejection check pass. Developers must use a verified isolated local stack for fixture mutations; the public site is unaffected. Local stack recovery and authenticated journey certification continue separately.

Repositories: rego.furries.ph-v2, partners-api and Partners database migrations. Status: Deployed; full end-to-end parity certification continues.

Rego V2 now includes the consolidated account, event, commerce, group, gift, waitlist and transaction improvements, shared form fixes and static event-sharing metadata. The API and database now bind slot reservations to attendees, serialize last-slot checkout decisions, redeem gifts atomically, and support narrowly scoped cleanup of newly sealed test fixtures. The separate dashboard repository is unchanged.

Both official Rego V2 domains now pass direct API CORS checks. Hosted public/auth deep links and 390px Shop rendering pass; the mobile Shop retains two-column cards. Full source-schema integration and native concurrent PostgreSQL checks passed before the two reviewed migrations were published. Unrelated pending media changes were excluded. Existing unsealed test records are not automatically adopted or deleted.

Attendees can use Rego V2. Controlled authenticated journeys and provider settlement still need further certification; deployment and public smoke checks are not a claim that every V1 workflow is fully certified.

Repository: partners-api. Status: Local validation and hosted public check passed.

Operators can run npm run build:check to validate the Worker bundle without uploading it. Typechecking, the bundle check and Page-discovery handler checks pass. Releases still use the existing Cloudflare Git integration. A subsequent successful API Git build and live HTTP 200 response close the Page-search 404 issue; local preflight success alone was not treated as a deployment fix.

Repository: partners.furries.ph-v2. Status: Local implementation, not deployed.

The canvas now uses the actual volunteer application list, review dialogs and email/SMS composer with isolated example data. One-shot failure controls support retrying inside an open dialog. Reviews and message rehearsals do not change live records or send notifications. Incomplete preview dependencies are rejected.

The final application-source integration passes project TypeScript checks. Six isolated source-contract groups and seven current-source browser groups pass, including partial bulk-review recovery, retained message drafts, empty/error states and the SMS form at 390px. The browser run made no API requests or storage writes. In-flight ownership and production-build verification remain open. No partners-api changes or operator action are required for this unreleased work.

Application-detail regression also passes eight local scenarios, including saved answers, full address fields, image fallback and keyboard/mobile behavior. V1 source monitoring now retains file-content hashes on disk and reports additions, removals and edits without automatically accepting changes. Maintainers should audit any reported donor change before updating the snapshot; an unchanged snapshot is not proof of complete V2 parity.

Repository: social.furries.ph. Status: Git-connected Pages deployment for badc045 succeeded; production navigation verified.

What’s Changed: Friends, Pages, Topics and Channels are now categories inside Discover instead of separate sidebar destinations. Friend requests and Page management remain available there; old directory links redirect safely. Impact: Desktop/mobile fixture checks cover navigation, management dialogs, private search and request isolation. Existing Tailwind brand tokens are retained. The complete local route certificate passes 172 assertions, and all 285 unit/ source tests pass after aligning the test journey with the new navigation. Upgrade Notes: Use Discover to reach these features. Publication uses main’s Cloudflare Git integration only. Page search still has a separate API release issue: its latest Workers Build failed and the public directory returns 404.