Platform Updates

Repositories: partners.furries.ph (schema), partners-api and rego.furries.ph-v2. Status: Local verification; production deployment pending.

What’s Changed: Sealed dealer fixtures can clean their own validated history through the existing guarded transaction without granting ordinary history deletion. POS teardown now removes inventory movements before their event so forecasting triggers remain valid. A separately approved local test recovery preserved the shared synthetic administrator.

Validation: 29 database permission/rollback checks, 13 real Dealers Den API checks and nine real POS checks passed. Both retained failed runs and fresh reruns completed cleanup. Provider settlement and complete rendered browser parity remain unverified.

Repositories: Admin, Partners, Partners-v2 and Partners API. Status: implemented locally; coordinated release and live verification pending.

What’s Changed

• Added a dedicated Admin portal using the Partners-v2 stack, including platform directories, access, policy, announcements, settlements, safety reviews, Pawsport lifecycle and controlled registration cleanup.
• Added Furries PH Signals form management and a protected, filtered Join waitlist view. Partner-owned workflows remain in Partners.
• Updated partner entry points to hand off platform functions. Partners-v2 parity instructions and inventories explicitly exclude migrated features; security review of source and handoffs stays enabled.

Impact

After coordinated release, platform staff will use Admin for these functions. Existing API roles and MFA checks remain authoritative. Local type/build, client/API contracts and representative browser fixtures have passed; this is not evidence of production deployment or provider delivery.

Upgrade Notes

Release the API changes and configured Admin site before enabling partner handoffs. Configure the hosted authentication return URLs and verify actual staff sign-in and sensitive workflows. The existing unavailable Social partner-scope service remains explicitly unavailable.

Planning tasks now cover native sponsorships, provider compatibility and an FPH-only advertising console in admin.furries.ph. Schema and API ownership stay in the existing ecosystem. Disclosure, consent, moderation, free-tier capacity and provider approval are release gates. No ads or tracking were enabled.

The staged Social location design passes an isolated replay of 437 repository migrations. It uses the account created by the existing Auth bootstrap, avoiding duplicate profiles. Tests verify sharing and logout-driven removal without giving the Auth writer access to coordinates. Managed-service and recovery validation remain required; location collection is still disabled.

The staged Social location commands now refuse database transaction modes that could retain an older consent snapshot. Eight isolated native checks cover all four commands, with existing lifecycle and race tests still passing. Location sharing remains disabled while Auth integration and recovery checks continue.

Repositories: signals.furries.ph, partners.furries.ph and partners-api. Status: Local migration and certification; not a production release.

What’s Changed: The React survey runtime now retains editable answers after validation errors, applies configured numeric/date/time constraints, preserves canonical translated answers, isolates drafts by survey version, and restores pending completion choices after returning from account sign-in. Server-side branch checks exclude skipped and hidden answers before completion and scoring.

Impact: Respondents benefit from clearer progress and recoverable errors on narrow screens. Owners keep the Partners survey editor and API-owned publication, access and reward rules.

Advanced local browser checks also cover single-page introductions, prefills, plain-text answer piping, stable randomized order after reload, optional answer clearing, storage restrictions, cooldowns and expired claim screens. Unanswered optional allocations no longer appear invalid, and unavailable claim actions are described accurately. Dashboard saves now omit unset validation values and respect cleared settings.

Additional staged claim repairs preserve an already-linked account and reject proofs that expire while a request waits for database locks. Focused SQL and native concurrent tests pass; the changes are not yet deployed.

Legacy numeric defaults now pass rendered mobile checks, including explicit zero bounds and API acceptance of submitted values. Text-pattern checks exposed an unresolved server validation gap; full configuration compatibility is not yet certified, and this local checkpoint does not change production behavior. Cleared legacy pattern settings now remain valid when stored as null, while invalid value types still reject. The local API now validates pattern syntax and submitted answers with a bounded JavaScript engine, preserving configured corrective messages. Pattern checks, type checking and the Worker bundle dry run pass. Browser matching now runs off-thread with a deadline and clear recovery guidance, so an expensive configured pattern does not freeze the response page. Focused desktop/mobile checks pass. A 200-question format-check regression now passes after limiting concurrent browser workers to four; all answers validate and no workers remain active afterward. Hosted assets, server load and full authenticated integration remain open. The correction has not been deployed.

The configured production artifact now passes 26 local Pages delivery checks and nine browser format-validation scenarios, with exact build fingerprints. An unset API URL was found to produce a build that could not load surveys; release builds must supply it. Three ignored SPA rewrite rules have now been removed; Pages accepts all five management rules without warnings. Deep links retain the native SPA fallback, with all 26 HTTP and nine browser checks passing again.

Partners survey and reward dialogs now intercept Cancel before form submission, so cancellation cannot create a record. The publish acknowledgement now tells owners to open or reload the public survey instead of waiting for a Pages build. Dashboard type checking, all 21 serializer/API cases and nine rendered dialog checks pass. The isolated baseline reproduced unwanted creation on Cancel; the repaired mouse/keyboard controls create no records. Full-shell visual and live authorization checks remain separate.

The current question-builder templates and real controller also pass 21 rendered checks for editing, clearing constraints and saving all 19 question-type values. This is local transport-isolated evidence. Survey creation now saves the selected access mode in the initial request, removing the second-request failure window. Twenty-two API route cases cover supported modes, defaults, invalid values and authorization/insert failures. Release the API before the updated dashboard; real authenticated integration and lost-acknowledgement recovery remain separate.

Builder compatibility evidence now includes 61 checks linking rendered edits to the actual API validators. All 19 configured types accept representative answers and reject missing required answers; cleared text restrictions stop applying. These checks remain local and do not establish live publication or database proof.

Pause/Resume now uses the API’s action contract. Resume restores the existing published version without publishing draft changes, and unavailable lifecycle actions are removed from draft/closed/archived views. Nineteen API fixture and eleven rendered interaction checks pass, including protection against a simulated stale resume after closure. API must release before dashboard; hosted and native concurrency verification remain separate.

Publishing now pins the saved definition and its returned revision, preventing another intervening edit from silently becoming the published survey. Missing revision metadata stops publication with a reload message. Twelve rendered interaction checks and 26 isolated publication SQL checks pass, including immutable versions and stale-edit rollback. Full authenticated integration remains open; concurrent draft-save conflict handling is a separate remaining check.

Dashboard save/publication notices now become visible when their text changes; the rendered regression checks visibility, not merely DOM text.

Upgrade Notes: Local type/build, behavioral validator and desktop/mobile fixture checks pass. Staged database repairs pass saved-draft, claim-proof and response-limit checks. Native PostgreSQL races now enforce the last available response slot for fresh, resumed and pending-perk submissions; stale-snapshot transactions are safely rejected. Invitation completion and use now commit together, with rollback and concurrent-retry tests passing so unsuccessful completion does not spend a one-use invitation. API checks preserve authorized retries after closure. Interrupted-request recovery now passes 37 API fixture scenarios and 17 rendered browser scenarios, including closure, capacity, exhausted invitations and publication changes. The browser retains private submission proof before dispatch, keeps account answers out of storage, and offers a focused completion-check retry without exposing old questions. Eight native claim/retry races also pass, including a repaired finalization deadlock. Full configuration parity, authentication integration and hosted validation remain in progress. None of these schema repairs is published. The React Pages build requires build/client; existing production behavior is unchanged by this local work.

Repositories: partners-api and rego.furries.ph-v2. Status: Locally verified; deployment pending.

What’s Changed: Corrected gift fixture teardown and restricted dealer checkout reservation release to the owning applicant. A fresh isolated gift journey passed 21 checks including cleanup; the dealer release check preserves another attendee’s hold and permits its owner to release it. API type-check passed.

Impact: These checks strengthen transaction verification without touching hosted attendee records. Full Dealers Den cleanup is still blocked by protected application history; an earlier local POS fixture also requires reviewed recovery. Full V1/V2 parity and provider settlement are not certified.

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

The design canvas now includes fourteen issue-reporting states using the shared reporter’s actual client. Its isolated rehearsal cannot submit reports, open example issue links or save downloads. Maintainers can inspect these states without creating support issues. The reporter now uses API-owned, read-only identity, including guest and failed/loading profile states. Fourteen integrated canvas scenarios and six route-lifecycle groups passed against a local production build; no real reports were submitted. Full dashboard parity and hosted/provider verification remain separate. Source monitoring also tracks the reporter’s upstream client and V1 integration without changing partners-api or automatically accepting donor changes.

Social’s held database design now uses account-scoped locks so unrelated account updates are not delayed by a location transaction. Isolated PostgreSQL tests verify both sharing/unfollow orderings and that re-following cannot restore a revoked location grant. Serial lifecycle checks also pass. This is groundwork in partners.furries.ph, not an enabled feature: members have no new location collection, and full Auth, recovery and device checks remain before rollout.

Repositories: rego.furries.ph-v2 and partners-api. Status: Local certification; no new production application changes.

What’s Changed: Local-only fixture checks now require successful cleanup before reporting success. Shop verification passed 33 checks; refund, transfer and upgrade verification passed 17 assertion groups. Local V2 auto-login also passed in a real browser against the isolated API.

Impact: Maintainers can verify these transaction states without modifying hosted attendee records or contacting payment providers. Rendered end-to-end transaction flows and provider settlement remain separate, unverified coverage; these results are not a full parity certificate.

Validation: Real isolated API/database tests, complete tracked-fixture cleanup, and browser authenticated-shell verification. Synthetic local baseline accounts remain for further development checks.