Platform Updates

Repository: Partners. Status: deployed through production builds.

What’s Changed: Multiple-choice, checkbox and dropdown options have dedicated reorder handles and move controls. Question and section dragging starts only from its grip, restoring normal click-and-drag text selection inside fields. Image file drops remain separate from option and question ordering.

Impact: Organizers can arrange choices in the order attendees should see them without accidentally moving a question while editing text. Labels and images remain together when options move.

Upgrade Notes: Save through the surrounding form configuration. Finish or cancel an option image upload before reordering options. No migration is needed. RegoSite uses the saved order.

Validation: Thirty-eight desktop/mobile browser groups pass, including real mouse text selection, native handle drags, preserved option images, survey ordering and pending-upload protection. Twelve required-toggle regression groups, form-builder editing contracts, typecheck, shared textarea and documentation checks pass. The missing preview donor was restored; the production build succeeds. Hosted organizer saves remain unverified.

Repositories: Partners and RegoSite. Status: deployed through coordinated frontend builds.

What’s Changed: Usernames questions now show a search bar for the signed-in attendee’s accepted friends. Select results to add removable username chips. Single Friend username questions use the same picker. Search text is never submitted as an answer, and there is no global user-directory search here.

Impact: Attendees can select friends such as co-panelists without manually entering comma-separated usernames. Pending requests and other users do not appear. Existing answer formats and required/count rules are preserved.

Upgrade Notes: Add and accept friends through Friends before selecting them in a form. Partners previews use synthetic local friends. Release both frontend changes together; no migration or new API endpoint is required.

Validation: Twenty-two local browser groups cover desktop/mobile search and selection, keyboard interaction, chips, limits, loading/error/retry and account isolation. Partners desktop/mobile preview checks pass without network API calls. Both frontend typechecks, documentation checks and the shared textarea guard pass. The existing required-question suite still passes. The coordinated frontend production builds succeed after the preview donor and metadata build blockers were resolved. Hosted attendee submissions remain unverified.

Repositories: Partners, RegoSite, Partners API. Status: deployed through coordinated production builds.

What’s Changed: Partner form builders expose the Required switch directly on question cards, including collapsed cards. RegoSite and the API honor saved required flags for signatures, and optional signatures can be left blank. Questions skipped by branching remain excluded from completion checks.

Impact: Organizers can quickly choose which responses attendees must provide. Required fields show an asterisk and explain missing answers.

Upgrade Notes: Save changes through the surrounding form configuration. Before a coordinated release, review existing signature questions marked required: those flags were previously ignored. No database migration is needed.

Validation: Twelve builder/viewport groups, 32 question-runtime cases, desktop/mobile form interactions, 33 branch-parity cases, signature/projection and API regression contracts pass. Partners, RegoSite and API typechecks and documentation checks pass. The missing preview donor and metadata build blockers were resolved for the coordinated release; both production builds succeed. Hosted organizer saves and attendee submissions have not been certified.

Repositories: Admin and Partners API. Status: deployed to production.

What’s Changed: FPH admins can replace or remove attendee profile photos from Admin → Attendees. Photos use the platform’s existing image upload and proxy flow.

Impact: Only users with the fph_admin role can access the photo controls, and the API enforces that role when saving changes.

Upgrade Notes: No attendee action is required. Admin type-check/build and API type-check pass locally. The linked production API Worker and Admin Pages deployments both completed successfully. The protected endpoint remains unauthenticated for public requests; no real attendee photo was changed during verification.

Repository: Partners. Status: published through the linked Git deployment and verified in the signed-in hosted editor.

What’s Changed: The shared unsaved-changes bar has its own row above the Report a problem button, including the device’s bottom safe area.

Impact: Registration configuration and other dashboard editors keep Save, Revert and Report controls separate on desktop and mobile.

Upgrade Notes: Reload Partners to receive the change. Typecheck, production build and shared preview parity pass. Hosted checks at 280–1440px confirm 20–24px clearance, visible actions and no horizontal overflow. Save/Revert confirmations, Report opening and closing, and clearing the bar after Revert pass. Validation drafts were reverted without saving event settings or submitting reports.

Repositories: Rego and Partners. Status: published through linked Git deployments and verified on the hosted event page.

What’s Changed: Public registration statistics show positive counts only. A zero omits both its value and label, including prefills, waitlists, capacity, spots left, registrations and dealer applications. All-zero groups produce no statistics wrapper or shared application-count note.

Impact: Attendee and dealer pages retain the restored compact text styling without empty or zero-valued statistics. Organizer visibility switches still apply.

Upgrade Notes: Reload Rego to receive the update. Typechecks, production builds, existing statistics rendering checks and canonical preview parity pass. The hosted event page retains positive counts and omits zero values and their labels at 1280px and 390px, with no console errors or mobile horizontal overflow.

Repository: Partners. Status: deployed through its Git-linked build.

What’s Changed: Workspace navigation reveals the current page and its section on load, reload and navigation. The mobile drawer also reveals the current page when opened, including menus that arrive after sign-in checks.

Impact: Partner teams can find their current location in long menus without scrolling from the top. Manual scrolling, page position and keyboard focus are preserved. No operator configuration is needed.

Validation: Twelve real-component browser groups, desktop/mobile screenshots, typecheck and the normal 108-module Rego parity build pass. Signed-in production reload and navigation checks reveal the current page in EMS Finance, Logistics, Setup and the Finance workspace. Responsive screenshots use local synthetic fixtures; hosted mobile-device behavior is not separately certified. No operator settings or source records were changed; the original partner scope was restored.

Repository: Partners API. Status: deployed through its Git-linked build.

What’s Changed: Public website requests independently read the small build receipt when its short cache expires. A request that ends can no longer leave other requests waiting on its pending metadata work. Current-publication checks and static response streaming remain in place; no CMS or database queries are added.

Impact: Visitors and crawlers retain access to the current published website. No editor action is required. Simultaneous cold requests can read the static receipt separately.

Validation: Sixty-nine focused checks, six native Worker lifetime/disconnect cases, delayed-header recovery and repeated native Pages publication/removal pass. The deterministic ended-invocation fixture fails on the previous code and passes with the fix. Full API type checking and the complete Worker dry build pass. All 21 repeated hosted requests pass. A full crawl checks 145 pages, including all 68 reachable articles and 142 sitemap URLs, with zero technical errors or warnings. The observed article invocations on the new release complete with 200 and no cancellations. This is bounded availability evidence; the cause of the earlier hosted timeouts remains unproven.

Repositories: Partners and Partners API. Status: database and both linked releases deployed; signed-in stopped-state checks pass.

What’s Changed: Forecasting gains Inclusions, Add-ons and Store items views with quantities per item, source breakdowns, horizon estimates and weekly/monthly category outlooks. Store coverage includes manual listings and linked item variants.

Impact: Organizers can estimate future unit demand while seeing which items have enough evidence. Sparse items retain actual quantities and partial category coverage is explicit. Linked Store sales overlap the inclusion/add-on views; their totals must not be added together. Demand estimates do not change stock, purchasing, prices or packing work.

Validation: 1,435 unit-model checks, 98 API checks, 78 native SQL checks and 21 shared-cache lifecycle checks pass. Native fixtures cover more than 1,000 source/catalog rows and the real mixed identifier types. Live aggregates and service-only database permissions pass. Desktop/mobile item flows, both typechecks, the normal 108-module source-parity build and existing forecast regressions pass. Screenshots use synthetic data; predictive accuracy is not established by these fixtures. Signed-in hosted acceptance verifies all three item tabs, source links and preserved Overview controls with an existing stopped generation; no registration, order, gift or stock records were changed.

Next: Open an event’s new item tabs. Shared forecasting controls stay in Overview. Stopped events without saved item snapshots must be started there before calculations appear. Estimates have approximate, uncalibrated model ranges.

Repositories: Partners and Partners API. Status: database and both Git-linked releases deployed; signed-in stopped-state checks pass.

What’s Changed: Event Forecasting gains Prefills, Waitlists, Activity submissions, Dealer applications and Dealer registrations tabs. Overview retains attendee, finance and logistics forecasts and the shared Start/Stop/Reset controls. Each intake view includes observed records, projected totals, weekly/monthly values, horizon choices and source-record links.

Impact: Organizers can plan incoming workload by intake type. Counts are retained records, not unique people or remaining queue sizes. Sparse or inactive intake explains why no forecast is available. Approximate model ranges are explicitly uncalibrated. Stopped views use saved snapshots; reset retains history.

Validation: Model arithmetic, API authorization/lifecycle and native SQL fixtures pass, including more than 1,000 records and event-scoped dealer joins. Live aggregate reads and service-only database permissions pass. Both typechecks, the normal 108-module source-parity build, all six browser tabs, weekly/monthly horizons and narrow layouts down to 280px pass. Signed-in hosted checks verify all five tabs and source links with an existing stopped generation. Populated screenshots use synthetic data; predictive accuracy is not claimed.

Next: Open an event’s Forecasting page and choose an intake tab. Use Overview for shared controls and Refresh intake forecast for a new read. A stopped event without saved intake snapshots must be started in Overview before these outlooks can be generated. The five tabs share one short-lived read and add no background polling.