Platform Updates

Repository: rego.furries.ph-v2. Status: Locally verified, not deployed.

Gift recipients can open bookmarked detail links without needing a direction hint to see Redeem gift. Sender views no longer display that recipient action when the URL hint is changed. The existing API still controls redemption authorization. Real local gift verification passes 75 checks with desktop/mobile coverage and complete cleanup; typecheck and transaction regressions pass. Full browser form submissions remain under verification.

An actual local PostgreSQL dump/restore exercise now verifies that stale restored location consent is suppressed before access resumes. The test uses synthetic data and a new disposable database; no existing database was overwritten. This does not certify managed backups, point-in-time recovery or production timings.

Repository: rego.furries.ph-v2. Status: Locally verified, not deployed.

Ordinary account notices now appear as a compact mobile summary. Attendees can open a full-message reader without notifications covering their forms; every message and acknowledgement remains available. Mandatory blocking notices are unchanged. Real local gift verification passes 63 checks, including reader accessibility and unobstructed claim actions, with complete cleanup. Typecheck, build and acknowledgement-retry regressions pass. Complete browser form certification remains in progress.

An offline recovery script now invalidates restored location consent and removes restored fixes before sharing can reopen. Isolated native and in-memory tests verify fresh eligibility is required and retries are safe. This is not full backup/PITR certification; no live recovery or location collection was enabled.

Read-only hosted metadata checks found an Auth permission assumption in the staged location tests. The draft now uses a private exact-session liveness check instead of requiring general Auth table reads. Corrected native and in-memory tests pass. No hosted permissions, schema or location collection were changed.

Rego V2’s controlled local certificates now check actual POS receipts and claimable/redeemed gift details at desktop and mobile sizes. Local passkey configuration was corrected without altering hosted authentication. POS passes 23 check groups and gift passes 53 checks, including browser health and fixture cleanup. Visual review still identified oversized mobile gift notifications obscuring actions; full browser form submissions remain under verification. Hosted data and production behavior are unchanged.

Native canonical-schema tests now verify sharing and viewing requests racing with logout. Logout revokes a newly started share, prevents a waiting start and leaves a waiting viewer read empty. These use a restricted synthetic Auth writer; managed-service and recovery checks remain before location sharing is enabled.

Repositories: partners-api, partners.furries.ph, rego.furries.ph, social.furries.ph, cms.furries.ph, and docs.furries.ph. Status: Local implementation, unreleased.

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: Once released, 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: Submission remains disabled pending service configuration. Configure the remaining backend-only credentials, deploy the API and site integrations, then verify an authorized report reaches the intended tracker. The organization-owned App is now registered and installed for the tracker only. All five site builds, API checks and local browser regressions passed; signing-key setup, production deployment and live delivery remain pending. See Report a website problem and the local API setup runbook at partners-api/docs/SITE_REPORTING.md for scope and release checks.

Social location groundwork now passes its 437-migration integration certificate on native PostgreSQL as well as the in-memory engine. Sharing, restricted Auth logout and block-restoration checks pass. This does not enable location sharing or certify managed Supabase Auth, concurrent full-schema behavior or recovery.

Six isolated canonical-schema checks verify that Social blocks, cross-site blocks and participation restrictions revoke existing location access for either member. Undoing the restriction does not silently restore that access. These are database integration checks; location sharing remains disabled pending further validation.