Platform Updates

Repositories: RegoSite and Partners API. Status: deployed and activated.

What’s Changed: Rego starts usage and campaign measurement automatically. The private Google Measurement Protocol credential also enables verified sales and refund delivery. No visitor acceptance prompt is shown. Public API runtime configuration moved from Cloudflare text bindings into versioned source, with the same values supplied to HTTP, scheduled, queue, email and Durable Object entry points. Credentials remain private secret bindings.

Impact: The API now uses 48 secret bindings and zero public text bindings, leaving 16 slots below the combined 64-variable limit. Event teams can use the dedicated Rego stream, saved comparison, ten reporting dimensions, purchase key event and nonmonetary successful-lead key event. Advertising signals remain off.

Validation: Hosted binding inventory and analytics configuration are verified. Production Rego sends an automatic page view to the correct stream with a Google 204 response. Google DebugView displays the nonmonetary server diagnostic. Purchase/refund debug validation reports no errors and did not ingest revenue. Ten public configuration/constructor groups, API typecheck and Worker build pass; hosted CORS and authentication-provider discovery remain functional. No actual payment, refund or synthetic revenue was added for release verification.

Repositories: RegoSite and Partners API. Status: automatic browser measurement released; server-confirmed revenue delivery awaits Google’s private Measurement Protocol credential.

What’s Changed: Usage, sales and campaign analytics starts automatically when Rego’s production analytics configuration is enabled. There is no visitor acceptance banner or analytics opt-out control. Settings explains the required measurement policy. Previous optional choices do not govern this new policy. Browser measurement and first-party context binding do not wait for the server credential; the public configuration reports revenue sender readiness separately.

Impact: The required policy is recorded explicitly as version 2 rather than being represented as visitor opt-in. Private-data filters, account isolation, financial verification and exclusion of previews remain in place. Advertising signals and personalization remain disabled. Analytics failures do not block registration or payment actions.

Validation: Eleven foundation contract groups and nine actual-provider browser groups pass with intercepted traffic. Checks cover first-visit startup, previous rejection, reloads, one tag and page view, safe payloads, configuration outage/recovery and desktop/mobile layout. API checks verify the required policy and private context registration; no synthetic revenue was sent to production.

Repositories: RegoSite, Partners and Partners API. Status: implementation and local verification complete; production activation awaits the dedicated Google Analytics sender credential and release verification.

What’s Changed: Rego measures event discovery, registration and checkout steps, applications, gifts, shop purchases and campaign attribution through a dedicated Furries PH Google Analytics stream. Visitors choose whether to allow optional usage and sales analytics and can withdraw through Settings or the persistent privacy control. Accounts and purchases work without it.

Confirmed sales and supported refunds come from server-owned financial records, with immutable sale snapshots, consented source binding and a deduplicated delivery outbox. Pending payment submissions do not become revenue. Pay-later cash advances remain separate from recognized sales. Partners form previews never send tracking or bind real transactions.

Impact: Event teams can compare journey drop-off, completed sales, products and marketing campaigns. Google Analytics covers eligible consented activity; operational finance remains the system of record. Profile details, private answers, payment references and private URL parameters are excluded. Advertising signals and personalization remain disabled. Historical sales are not replayed.

Validation: Production builds and typechecks pass. Browser checks exercise consent, discovery, registrations, gifts, applications, shop and dealer flows; API checks cover financial projections, source ownership, withdrawal, leases, refunds and provider failure handling. The analytics migration is applied with eight private tables protected by row-level security; browser roles cannot read the outbox. Provider ingestion awaits the private sender credential. No synthetic revenue was sent to production.

Repositories: Partners, RegoSite and Partners API. Status: deployed through their production Git builds.

What’s Changed: Dealer applications explain that accepted applicants’ bios, table photos and links may be used for promotions. Applicants are encouraged to write a useful bio, supply a clear table photo when enabled and provide direct portfolio, catalogue, website and social links rather than relying only on a link hub. Link hubs remain allowed as an additional link.

Impact: Bios have a 160-character limit, with a visible count. Both ordinary fields and organizer-authored bio questions use the same validation. The API checks the canonical bio before creating, editing or resubmitting an application. Existing applications remain readable; a long existing bio must be shortened before its next save. Optional bios remain optional.

Validation: Typechecks and production builds pass, including all 112 canonical preview modules. Checks cover 24 API bio groups, 24 existing photo groups, 5 RegoSite bio scenarios, Unicode/helper contracts and 7 embedded bio groups. Desktop/mobile screenshots are verified. No database migration is required.

Repository: RegoSite. Status: deployed through its production Git build.

What’s Changed: Event descriptions and schedules stay within their content column beside attendee registration actions. Wide timetables scroll inside the schedule card rather than crossing into the registration panel. Mobile schedule lists retain their existing presentation.

Impact: Visitors can read event details, explore the schedule and use the registration actions without overlapping cards.

Validation: Seven responsive/account variants pass, including signed-in desktop/mobile, keyboard timetable scrolling and activity dialogs. The reproduced 106-pixel overlap now leaves a 24-pixel gap. Typecheck and production build pass.

Repositories: Partners, RegoSite and Partners API. Status: deployed through their production Git builds. The additive migration is applied; existing event settings remain off by default.

What’s Changed: Organizers can enable a dealer table photo in Dealers Den application settings and choose whether it is required. Dealers can upload, replace or remove a square photo while preparing or revising their application. Authorized organizers can view the photo when reviewing the application.

Impact: The field is off by default. When enabled, optional photos do not block submission; required photos must be supplied. Both the form and API reject non-square images. Photos use private, authenticated access.

Upgrade Notes: Open Dealers Den application settings, enable Dealer table photo and optionally require it, then save. Existing applications remain readable.

Validation: Typechecks and production builds pass. Checks include 24 API HTTP/helper groups, 12 PostgreSQL groups, 9 dashboard browser groups, 9 private loader contracts, 6 RegoSite scenarios and 6 embedded-photo preview groups. All 111 canonical preview modules match. Production schema permissions, protected photo endpoints and served dashboard/RegoSite feature assets are verified. A real signed-in production upload remains unverified.

Repository: Partners. Status: deployed through the production Git build.

What’s Changed: Adding or editing a campaign recognizes the server’s default UTM campaign code, trimmed text and equivalent timestamps. Changing usage statistics or response ordering no longer leaves a successful save checking forever. A confirmed mismatch returns an editable draft and an explanation.

Impact: Event operators can finish a campaign save while keeping other affiliate and reward drafts. Automatic recovery checks saved state without repeating the write.

Validation: Five new campaign browser groups and eleven existing affiliate groups pass, alongside typecheck and production build. The served campaign bundle is verified. A real signed-in production save remains unverified.

Repositories: Partners and Partners API. Status: deployed through their production Git builds; the API Worker is serving the release at 100%.

What’s Changed: Record and analytics lists share a dropdown for 25, 50, 100 or All rows on one page. Item forecasts now expose the choice beside their row count. Existing registration/review, asset, planning, finance, directory and other record lists use the same choices.

Impact: Operators can inspect more rows without repeatedly advancing pages. All respects the current filters and sorting and loads every matching authorized server page. Incomplete or failed reads do not present a partial list as All.

Upgrade Notes: The default is 25. Large All views can take longer to load. The coordinated API release adds bounded continuation metadata for financial, communication and shop lists; no database migration is required.

Validation: Desktop/mobile row-count and page-reset fixtures plus bounded multi-page, failure and cancellation contracts pass. Typechecks, production builds, 52 API pagination groups and served dashboard chunks are verified. Hosted signed-in list operations remain unverified.

Repositories: Partners, RegoSite and Partners API. Status: deployed to production through their linked Git builds.

What’s Changed: Required switches stay visible on collapsed question cards. RegoSite and the API honor explicitly required signature answers. Username questions now search the signed-in attendee’s accepted friends and collect removable selections instead of arbitrary text.

Multiple-choice, checkbox and dropdown options can be reordered by their grips or move buttons. Workspace cards, nested payment accounts and roster shifts also use dedicated grips, preserving normal selection inside text fields and keeping file uploads separate from ordering.

Impact: Organizers can choose required answers and arrange form choices without accidentally moving cards while editing. Attendees select existing friends for questions such as co-panelists.

Upgrade Notes: Save through each workspace’s normal controls. Review saved signature questions marked required: these flags were previously ignored. Optional signatures remain optional. No database migration is required.

The missing-preview build blocker came from an outdated sibling checkout. Current canonical Rego source contains the extracted preview modules; release verification passes all 109 module comparisons and the full production builds. Unrelated local changes were excluded from this release.

Validation: Both frontend typechecks/builds and the API typecheck/bundle pass. Local checks include 42 card, 38 option-order and 12 required-toggle browser groups, 659 React-source drag checks, friend-selection previews, 32 required-runtime cases, 22 friend-picker groups, branch and API contracts, signature/projection checks and roster move/resize/cancel behavior. Hosted user-operated configuration saves and attendee submissions remain unverified.

Release revisions: Partners 0e5e17f3, RegoSite dca2555c, Partners API 58be04e0. All three linked builds succeeded. The API’s deployed version serves 100% of traffic. Partners Pages deployment 2564cecd and RegoSite Pages deployment a1cf5f7a identify the matched frontend releases.

Repository: Partners. Status: deployed through production builds.

What’s Changed: Reorderable workspace cards now start dragging from a dedicated grip. Shop categories/listings, payment providers/accounts, catalog items, dealer packages, Conditions documents, Pawsport stickers, activity and feedback cards, planning boards and roster shifts preserve normal selection in their text fields. Roster shift resizing keeps its separate control.

Impact: Selecting or editing text no longer accidentally moves a card. Nested lists accept their own drag gestures, and upload boxes handle files separately from reordering.

Upgrade Notes: Use each card’s grip or existing move/status controls. Normal workspace save behavior is unchanged. No migration is required.

Validation: Forty-two desktop/mobile card browser groups, a 652-file TSX drag inventory, 38 option-order groups, 12 required-toggle groups, roster movement/resizing/ordering, typecheck and documentation checks pass without live writes. The missing preview donor was restored; the production build succeeds. Hosted saves and physical touch-device acceptance remain unverified.