Furries PH Docs
Dashboard

Updates

Platform Updates

Public-facing release notes for meaningful changes across Furries PH operational systems.

First created Last updated

Showing release notes 761-770 of 1462
2026-09-1015:53

Partners V2 shared shop order queue

The Partners V2 dashboard and design canvas now reuse one shop order queue with phone, region and fulfillment search, counted statuses, five sort modes and pagination. Selection sits on each order row and remains selected across pages; bulk selection covers all matching orders. The dashboard Claim Page link retains event scope, and CSV export covers the server-filtered order list.

Local verification passed 43 comparisons against current V1 query behavior, eight compiled browser groups, six gift-workflow regressions, typecheck and build. Desktop and mobile layouts were inspected. Canvas checks made no external requests or persistent writes. Order details, batch and CSV-scope examples remain explicitly non-persisting rehearsals; complete order workflow and authenticated verification are still in progress. No API code changed and no deployment is announced by this entry.

2026-09-1015:53

Partners V2 shop order workflow rehearsal

Partners V2 now lets event teams rehearse the actual shop-order detail, payment decision, fulfillment status, buyer update, internal note and batch forms in the design canvas. The shared detail makes item sources, unit prices, timeline visibility, claim exception text and empty records explicit. Saved local changes require a fresh read before another action, so a failed refresh stays read-only instead of repeating a decision.

The batch result now distinguishes each order: a failed write remains selected for an explicit retry, while an acknowledged write is removed from retry so it cannot be repeated. If the fresh source read is unavailable, the queue becomes read-only until Retry verifies it without sending another change.

Eight full workflow groups, eight queue groups and seven ownership groups passed locally, including desktop/mobile inspection and a two-order partial-batch visual check. The rehearsal uses fictional data; it does not contact the Partners API, notify buyers, download a CSV or change real orders. Authenticated production evidence remains open. This is a local implementation update, not a deployment announcement.

2026-09-1015:53

Partners V2 shared gift-payment workflow preview

Event teams can rehearse the actual gift-payment queue, details, payment review and separate giver/recipient messaging in the Partners V2 design canvas. Twelve fictional gifts cover all lifecycle statuses. Failed reviews retain staff notes; saved decisions with failed reloads require read-only recovery instead of another payment decision. Shared form, feedback and notification components are reused.

Local verification passed six compiled workflow groups, seven ownership groups (including 18 delayed-operation cases), eight refund regression groups, typecheck and build. Desktop/mobile layouts were inspected. The gift rehearsal made no external requests or persistent writes. This is not a deployment announcement; authenticated persistence and full dashboard parity remain unverified. API code was unchanged. Use the local preview to rehearse; it does not send messages or modify real payments.

2026-09-1015:53

Partners V2 full shop workflow preview

The Partners V2 design canvas now uses the actual shop settings, catalog, listing, image crop, buyer-question, courier and delivery-rate editors. Its scenario, failure, slow and reset controls rehearse these workflows with fictional local records only. Failed image/rate operations retain input for retry; source changes discard obsolete work. The existing shared UI components are reused throughout.

Local verification passed eight compiled shop workflow groups, five source-boundary groups, fourteen existing shop regression groups and fourteen refund/prefill canvas regression groups. No external requests or persistent writes occurred in the compiled shop rehearsal. This is not a deployment announcement; authenticated persistence and full dashboard parity remain in progress. API code was unchanged.

2026-09-1015:53

Rego V2 local attendee-flow certification

Repository: rego.furries.ph-v2. Status: Locally verified; not deployed. Local Rego testing now covers a complete ordinary free-Rego journey at desktop and mobile widths: tier selection, add-ons, saved profile details, Conditions of Entry, review, submission, attendee-owned record readback and cleanup. The local auth client also serializes sign-in, sign-out and token-refresh cookie updates so an older refresh cannot replace a newer account session. The isolated Shop certificate also now preserves saved delivery country and region in its controlled attendee profiles, proving profile prefill for courier delivery while collection-at-event keeps address controls absent. The shared API form contract now also accepts only the native signature pad’s compact black-on-transparent SVG for generic, activity, and Vollie questions; other SVG payloads and unbounded coordinates are rejected before persistence. Desktop and mobile local journeys now draw, scroll-gate, submit and read back that exact signature through both Activity and Vollie flows, with sealed cleanup. Public event detail now also carries configured tier, add-on and inclusion questions, so an organiser-defined Rego signature reaches the native form. The isolated standard Rego run proves all three scoped question sources at desktop and mobile, including exact submission payloads and cleanup. Dealers Den now has equivalent local application evidence: the native black-on-transparent signature is drawn, persisted and restored for a requested-change resubmission at both widths, then re-gated by Conditions. Its complete application-to-confirmed-receipt journey passes 210 isolated checks with cleanup. Shop now delivers organiser-configured listing questions to the native product surface and applies the same compact black-on-transparent signature rule at checkout. Its 82-check local desktop/mobile run proves exact persistence as well as delivery/pickup rules, Conditions and receipt handoff. Dealer table-registration submission now independently reloads and validates each selected tier, add-on and inclusion question contract, preserving only the validated answer snapshot for each crew member. Its local journey now draws distinct required signatures for the dealer and assistant slots before Conditions and submission.

Impact: This improves local confidence for attendee journeys without changing production data or payment providers. Local test runs create temporary isolated records and require zero-residue cleanup before a pass is reported.

Upgrade Notes: Run pnpm certify:isolated-standard-rego or pnpm certify:isolated-dealers only against the isolated local Worker and database. The broader parity and provider-backed certification work remains open.

2026-09-1015:53

Partners V2 shop drafts and schedules

Partners V2 event operators can now stage category/listing order with settings and apply or revert them together. Dragging alone no longer saves the order. Retrying a partially successful save retains acknowledged changes. Shop and listing schedules now use operator-local time consistently with V1.

Eight isolated browser workflow groups, six load-recovery groups and three timezone suites passed locally. This is not a deployment announcement; the full shop canvas and authenticated persistence verification remain in progress.

2026-09-1015:53

Partners V2 shop load recovery

Partners V2 shop configuration now displays an error and Retry action when its initial load fails, instead of remaining on Loading. Switching events resets the editor and prevents obsolete reads from replacing the new event’s data. Operators can retry the read without submitting a shop change.

Local validation passed six rendered recovery groups, typecheck/build and fourteen existing canvas regression groups. Desktop and mobile screenshots were inspected. This change is not yet deployment evidence; broader shop canvas parity remains in progress. No API changes were made.

2026-09-1015:53

Partners V2 refund workflow preview

Partners V2 event operators can now rehearse the real refund queue, details, partial approval, decline, proof retry and attendee messaging in the design canvas. All example records, proof and email/SMS actions stay local; nothing is paid, uploaded or sent. Pending decisions are isolated when the event/source changes, and a saved decision cannot be submitted again while its queue refresh is pending. Fee previews preserve V1 cent rounding.

Validation: six component browser groups including eighteen stale-operation cases, eight compiled canvas groups and calculation regressions pass. Typecheck/build pass; desktop/mobile screenshots were inspected. This is not a deployment or authenticated financial-operation certification; broader V2 parity remains open.

2026-09-1015:53

Partners V2 saved-prefill audit preview

Partners V2 event operators can rehearse the real saved-prefill audit page in the design canvas, including search, lifecycle filters, empty/loading states and revoke retry. Example actions stay in memory and retain audit rows. Confirmation failures remain visible in the dialog, and switching events or preview sources isolates pending results. No backend change or production deployment is included.

Validation: five component browser groups (including twelve ownership cases), six compiled canvas groups and seven fixture checks passed; typecheck/build passed. Mobile and dialog screenshots were inspected. Authenticated server verification and broader dashboard parity remain open.

2026-09-1015:53

Partners V2 roster draft isolation

Repository: partners.furries.ph-v2. Status: Locally verified; not deployed. Replacing a roster source or preview now discards the old editor safely, even while a save is pending. Late results cannot restore the old draft. Registered location and row-order saves still leave unsaved assignments untouched.

Next step: Use Slow roster operations and Reset in the design canvas to rehearse pending saves. Six ownership groups,18 delayed-save cases, roster helper contracts and compiled timeline/assignment checks pass with typecheck/build. No real roster or API was changed; authenticated production parity remains open.

All docs