Platform Updates

Repositories: Partners API, Partners and Rego. Status: coordinated production release of the API, Partners and Rego.

All sign-in methods now require confirmed account email before saving personal profile fields. Confirmation is a separate first step; requesting a message does not save a profile. Existing unconfirmed profiles must confirm before continuing, and the API rejects direct save attempts until live proof succeeds. A chosen contact address must match that confirmed email.

Focused SDK/API checks (272 profile/confirmation groups and 45 attendee-admission requests) and desktop/mobile browser fixtures verify missing, pending, mismatched and confirmed states without sending real emails or changing accounts. Isolated API, Partners and Rego typechecks and both frontend builds pass. Cloudflare release results and hosted asset/API checks verify publication; real inbox delivery and authenticated account acceptance remain separate checks. Existing unconfirmed users must complete email confirmation before saving or continuing.

Repositories: Partners and Partners API. Status: coordinated production release with 12 database migrations.

Event operators gain confirmed per-entry delete controls across registration, submission, application, feedback, prefill and waitlist lists, plus financial, operational, communications and BNPL history. Directory removal preserves the event and its public visibility. Retained financial and delivery records leave the organizer list without erasing their payment, stock or audit effects. Pending obligations and linked records must be resolved through their existing workflows first. The event-wide registration wipe remains in Admin.

Browser and executable database fixtures cover event permissions, confirmations, interrupted responses, stale lists and dependency guards. The 12 migrations passed a rollback rehearsal against the live schema, then were published atomically and verified in the migration ledger. API and Partners typechecks/build checks pass; hosted anonymous checks preserve public event access and reject protected deletion reads. No real entries were deleted during validation.

Repositories: Partners and Rego. Status: released in Partners and Rego.

Attendees at or above their event’s consent-age threshold skip guardian consent in registration and do not see an unnecessary consent section in transaction or organizer registration details. Dealer completion instructions now appear only when someone in the booking requires consent. Mixed-age bookings retain required guardian signatures; historical uploads do not make adult consent required.

Focused browser checks cover organizer records, adult attendee transactions, age boundaries and mixed-age dealer bookings. Partners and Rego typechecks/builds pass, as do 21 Rego consent browser groups and focused organizer-record checks. Organizers need no configuration changes. These checks use synthetic records; a separate pre-existing full consent-editor test still reports a rich-text entity comparison failure.

Repositories: Partners and Partners API. Status: validated release; new higher-tier controls default off.

What’s Changed: Staff and volunteer policies each have separate switches for paying only the difference on higher-priced tiers and extending partner-paid fees to those selections. Leaving the price switch off charges the higher tier’s full price. The fee switch is independent of the price choice and requires the main fee-absorption setting.

Impact: Organizers can offer a free base tier while deciding how much a team member pays for a higher tier. Add-ons remain payable, and member/department overrides retain priority. Existing settings keep their previous full-price behavior until the new switches are enabled.

Upgrade Notes: Save through HR Policy & subsidies. The API calculates the base-tier credit from canonical event prices at the same quote time. Clearing or importing event-bound tier settings resets the dependent policies. No database migration or new secret is required.

Repeated paid upgrades retain recorded payments and apply the tier credit once. Full-price mode records the new tier without the free-tier credit, while already accepted quotes retain their agreed totals. Mixed partner/member fee receipts preserve each party’s share.

Validation: API typecheck and Worker bundle pass, with pricing, settings/resolver, pending-payment, actual paid-upgrade/receipt and early-bird route checks, plus 40,000 finance property cases and 15 lifecycle checks. Partners typecheck/build, save/import contracts and desktop/mobile save-refresh-reload tests pass. Rego’s existing seven attendee-fee cases remain passing. These fixtures do not collect money or certify genuine payment settlement.

Repositories: Partners, RegoSite, Partners API, CMS, LAN EMS, Support, Social, Admin, Cron, Pawsport, Report and shared Docs. Status: validated changes pushed to main; database prerequisite applied.

What’s Changed: HR configuration separates departments and members from policy, shift locations and imports. Member details keep notes and subsidy overrides compact. Each account has one department and role per event. Separate staff and volunteer free tiers and organizer-paid fees carry through registration quotes, group summaries and saved payment details. Inventory analytics rows emphasize item names rather than descriptions and internal identifiers.

CMS validation excludes generated build and captured fixture output while continuing to check application source. The public site’s CMS input fixture resolves shared source imports correctly. Cron’s existing runner changes and Pawsport/Report attribution notices are committed. Rego’s local Worker database files are excluded from version control.

Impact: Event teams can configure staff and volunteer benefits with clearer attendee-payable totals and avoid duplicate assignments. Older local working copies have been reconciled with newer released code; original source snapshots and private test artifacts are retained locally. Planning-only roadmap documents remain plans.

Upgrade Notes: The single-assignment database migration is applied. Preflight found no conflicting assignments; database checks confirm three uniqueness indexes, two enforcement triggers and an API-service-only atomic replacement function. The migration does not discard existing organizer records. Local regression and build results are recorded with the release; no genuine payment, provider delivery or physical-device workflow is claimed from fixture checks.

Validation: API typecheck and Worker build pass, with 13 HR pricing cases, three pending-payment projection cases, executable SQL atomicity/permissions checks and 40,000 finance property cases. Partners typecheck/build, 120-module Rego preview parity, desktop/mobile HR checks, ten inventory browser groups and 632 analytics checks pass. Rego typecheck, 189-document build, seven fee cases and desktop/mobile stored-receipt checks pass. Admin, CMS, public site, Social, LAN and Support checks/builds pass; Cron’s isolated request checks pass. Older local source was preserved before reconciliation.

Repositories: Partners and shared Docs. Status: production analytics and Google Realtime ingestion verified.

What’s Changed: Partners uses its dedicated Google Analytics property and tag for canonical navigation, interface interactions, final workflow outcomes and browser performance. Enhanced Measurement is enabled with safe manual event equivalents. Reporting includes 24 custom dimensions, request/performance metrics and a non-monetary workflow-completion key event. Recognized search/social sources and platform referrals retain safe acquisition categories; direct visits do not receive a fabricated campaign.

Impact: Partner teams can analyze workflow use, completion, errors and performance across dashboard workspaces. Private records, entered search/form text, identifiers and sensitive URLs are excluded. Local fixtures and embedded attendee previews do not send analytics. Rego sales remain in their own property.

Upgrade Notes: No new API secret or database migration is required. Full typecheck and production build pass, alongside 569 runtime assertions across 163 routes, 24 transport checks covering 682 endpoint shapes and 39 performance assertions. Actual browser checks verify private-value exclusion, preview isolation and canonical SPA events; Google Realtime confirms live collection. Performance timing includes a bounded visible-page checkpoint after hydration. The stream administration warning has not yet refreshed despite received events. Ad personalization and BigQuery export remain off.

Repositories: Partners, Partners API, RegoSite, Admin, CMS, public site and shared Docs. Sibling operational sites and the LAN EMS release were also checked. Status: coordinated production releases verified; existing capability gates remain in place.

What’s Changed: Timed early-bird prices cover registration tiers, add-ons and dealer packages through authoritative checkout quotes. Expired or changed reviewed totals require review again. Purchased gifts and paid upgrade credit retain their recorded value. TailTally Signals supports finance-resolution dates, production reversals and planning/material-intake projections; Admin gains a reasoned, audited deletion confirmation with recent MFA, revision checks and replay protection. Media cleanup recovery preserves durable claims after uncertain outcomes.

Impact: Organizers configure discount windows in the event timezone; discounts do not open registration or alter existing paid records. Signals deletion remains an explicit Admin action and does not delete local dealer ledgers or public catalogues. No deletion, payment or synthetic revenue was executed during release verification. Existing feature gates, API authorization, browser privacy and analytics destination remain unchanged.

Validation: API, Partners, Rego and Admin typechecks and production builds pass. Focused money, browser and existing regression contracts pass. Native PostgreSQL checks cover deletion authorization/replay, finance and planning parity, plus 266 early-bird checks including concurrent lock expiry and checkout retries. Five service-only feature migrations are applied and their source versions match production; an already-applied monitoring migration is retained without rerunning it. The API keeps 48 private secrets.

Upgrade Notes: Refresh the dashboard to see configuration and review controls. Existing prices and collection policy remain authoritative until an organizer changes their configuration. CMS retains a guarded local-only editing fixture; full mounted Studio scenarios remain separately unverified. The public-site MCP document is a plan with implementation explicitly not started. Older local copies and private test configurations were preserved rather than overlaid onto newer deployed code.

Repositories: RegoSite and Partners API. Status: deployed through production database and linked site builds.

What’s Changed: Financial analytics adds committed staff POS receipts and dealer application fee receipts alongside registration, gift, group, dealer, shop and upgrade sources. Original fee quotes and committed POS items/totals are frozen. Financial discovery can measure offline and anonymous sales without assigning a staff member’s browsing identity to the buyer. Eligible original browser context remains separate campaign attribution.

Impact: Older financial facts appear in separate historical metrics with their original sale date and currency, rather than inflating today’s purchase revenue. Unknown legacy amounts or missing provenance appear as unresolved counts. Historical reporting does not repair old accounting records or invent old campaign attribution. Supported verified cash returns remain distinct from sales and cancellation. Standard Google reporting is retained; BigQuery remains disabled.

Validation: API typechecking, Worker dry-run, Rego typechecking/build, focused contract tests and actual PostgreSQL receipt/registry tests pass. All discovered production sources project without errors. Historical gross and sale counts reconcile against authoritative records by event, source, currency and original UTC date with no mismatches. Google Realtime confirms real historical sale and unresolved events. Supplementary fee observations preserve existing sale totals and counts. Five service-only migrations are applied; migration filenames match the production registry. The API retains 48 secrets and zero public text bindings. No synthetic revenue or live payment was used.

Upgrade Notes: Google’s processed reports can lag Realtime. The saved exploration separates PHP monetary totals from unresolved counts across all currencies; it includes 31 custom dimensions and 18 metrics. Missing legacy fee amounts remain unresolved. Do not merge historical custom metrics into current purchase revenue or infer cash returns from cancellations.

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

What’s Changed: Rego sends automatic usage, registration, checkout and campaign measurements to Rego Furries PH in the Furries PH Google account, using Measurement ID G-7K10917KTQ. The server credential is destination-bound and private; the retired credential was revoked. Browser and nonmonetary server events are visible in this property’s Realtime reports. This corrects the destination described in earlier entries; those earlier delivery checks do not certify the corrected property.

Shared instrumentation now distinguishes visible controls and dialogs, field interaction without values, media progress, native clipboard/share outcomes, resource timing and report delivery. Auth, profile, security, friends, applications, uploads, registration, groups, gifts, shop, addresses, guardian forms, payment submissions and pay-later commands report validated acknowledgements. These acknowledgements remain distinct from verified sales and refunds. Source-generated control identifiers and versioned manifests support technical diagnosis without labels, answers, identities or private URLs.

Impact: Operators can analyze behavior and failures alongside supported server-confirmed commerce. The correct property has 27 event dimensions, eight metrics and a nonmonetary successful-lead key event. Standard Google reporting is selected; BigQuery export remains disabled. High-cardinality identifiers are not registered as report dimensions, so standard reporting does not provide unlimited per-control raw-event analysis. Advertising identifiers, signals and personalization remain off. Browser blocking, offline operation and Google processing limits still affect delivery. No synthetic revenue or real payments were used to verify this release.

Validation: Production Rego and API builds succeed. A public reload, refresh and report-dialog open/close deliver safe events to the correct Google stream with HTTP 204 responses; Realtime shows the new resource-timing and report-activity families. TypeScript and production builds pass. Focused contract and actual Chromium fixtures cover normal success, invalid receipts, failures, retries, native operations, account changes, collector changes and privacy. BNPL collection passes 21 browser groups and 216 assertions; checkout passes 10 groups; guardian consent passes 19 groups. The shared report widget passes 11 new browser groups plus its existing regressions. The API retains 48 secret bindings, zero public text bindings and 16 free variable slots. Public runtime settings live in versioned source rather than secret storage.

Hosted visibility proof: The aggregation release delivers seven exposure events and seven resource samples representing 32 resources, each returning Google HTTP 204. Realtime in Rego Furries PH now shows the visibility event family as well.

Collection follow-up: Resource diagnostics now group one-second samples by safe categories: counts remain available, duration is a sample mean and public script/style bytes are summed. This reduces startup event bursts. The canonical stream uses custom measurement with enhanced automatic duplicates disabled. A subsequent fresh reload of the exact canonical stream confirms “Data collection is active in the past 48 hours” and “Data flowing”; the inactive warning is cleared. Google recommends Realtime/DebugView for collection checks, and reports may need 24–48 hours to process. No report-processing or warning-refresh deadline is guaranteed.

Repository: RegoSite. Status: deployed; broader action coverage remains in progress.

What’s Changed: Rego measures static control activations, field changes and validation without field contents; API requests report fixed operation categories, status and timing. Fixed error categories and document loading timings help diagnose broken journeys. Events respect Google’s parameter budget and existing preview/account boundaries.

Impact: This expands diagnostic coverage beyond checkout. A successful HTTP request is not a confirmed business outcome. Private values, error messages and raw URLs are excluded. Complete action outcomes, Core Web Vitals and additional Google reporting definitions remain in progress.

Validation: Browser privacy/listener fixtures, canonical transport and analytics contracts, TypeScript and production build pass. The Git-linked deployment succeeds; a public reload and refresh action deliver page-view, interaction, API-request and three document-timing events to the dedicated Google stream with HTTP 204 responses. The API remains at 48 secret bindings and zero text bindings. These delivery checks do not certify all business outcomes or processed reporting.