The V2 dashboard now includes a verification gate that checks all 149 audited route-contract targets resolve through native runtime handlers and reusable dashboard/admin guards. Local protected reads also confirmed the dashboard and safety-report workspace render without a route fallback or console error. Provider, device, upload, one-time-link, and governed-write checks remain separately controlled; no Partners API behavior changed.

2026-09-02 — Partners Dashboard V2 CMS handoff parity

Partners Dashboard V2 restores the sidebar Content Management action as a reusable, permission-aware CMS handoff. It requests a fresh, short-lived partner-scoped session from the existing Workers contract and shows in-place loading/error feedback without exposing a long-lived CMS credential. The shared navigation also restores Guide and Surveys destinations. Local protected-route verification, type checking, route coverage, and canvas parity checks passed; no partners-api change or external CMS launch was performed.

2026-09-02 — Partners Dashboard V2 global notices

Partners Dashboard V2 now includes the reusable dashboard-wide notice surface from the existing Partners workflow: deduplicated informational notices, blocking notice queues, scroll-gated legal acknowledgements, and fail-open refresh behavior. Existing Worker endpoints remain authoritative. The surface was verified locally without acknowledging a notice or changing partners-api.

2026-09-02 — Partners Dashboard V2 signals and commerce geography

Partners Dashboard V2 now restores the dashboard Signals panels for recent scoped safety updates and survey analytics. EMS commerce configuration also uses shared country and administrative-region controls from the existing operational data contract instead of free-text ISO fields. V2 type checking, route coverage, and canvas parity checks passed; no partners-api change was made.

2026-09-02 — Partners Dashboard V2 signals and commerce geography

Partners Dashboard V2 now restores dashboard Signals for recent scoped safety updates and survey analytics. EMS commerce configuration also uses shared country and administrative-region controls from the existing operational data contract instead of free-text ISO fields. Type checking, route coverage, and canvas parity checks passed; no partners-api change was made.

2026-09-02 — Event teaser visibility controls

Event Management in both Partners Dashboards now lets authorized organizers independently hide event dates, venue details, and registration prices during a public teaser. RegoSite replaces each intentionally withheld detail with a clear Coming Soon badge while canonical event data, registration operations, and payment rules remain intact. The feature is stored by the Partners API and defaults to showing all information for existing events. Local source validation is recorded with the implementation; deployment still requires the associated database migration.

2026-09-02 — Partners Dashboard V2 preview deployment

The current Partners Dashboard V2 build is deployed to its Pages preview after CMS handoff, global notices, dashboard Signals, and commerce geography updates. The public design canvas was opened from the deployed build with no browser console errors. Provider, device, and governed-write certifications remain separate controlled checks.

2026-09-03 — Partners Dashboard V2 Asset Management navigation

Partners Dashboard V2 now restores the Asset Management workspace context on the live Asset overview: grouped Registers, Operations, and Control links, the familiar workspace heading and actions, linked-work refresh/manage context, and governed import/bulk-operation entry points. Asset records, approvals, and cross-system links remain controlled by the existing service; operators do not need to migrate data or change their workflow. Local authenticated rendering, TypeScript, and route-execution checks passed. No Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 overview projections

Partners Dashboard V2 now matches the familiar dashboard overview metrics and report context: Partners, Events, Reports, Active bans, plus recent reports, updates, and bans. The calculation reuses the existing dashboard Reports projection and Worker-owned records; no data migration or permission change is needed. Type, route, and live dashboard checks passed.

2026-09-03 — Partners Dashboard V2 report update context

The Reports overview now distinguishes a report’s initial creation from a later update, matching the established dashboard behavior. Operators continue to have full revision history on the report record itself. Existing records, permissions, and service behavior are unchanged; type, route, and live browser checks passed.

2026-09-03 — Partners Dashboard V2 EMS directory controls

Partners Dashboard V2’s Event Management screen now includes the familiar Preview/Sandbox notice, event-setup guide link, and event-list sort and page-size controls. The notice can be hidden for the current session, while the event list continues to use the existing scoped records and management routes. Live local rendering, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Finance operational workflows

Partners Dashboard V2 now lets authorized Finance operators create operational record drafts and take the same accountable lifecycle actions as the existing Finance workspace. Each action uses the existing protected checkout, reason, and version-check workflow, so approvals and other decisions remain recorded by the finance service. Existing financial records and service behavior are unchanged. Local browser, type, route, and production-build checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 event workspace navigation

Event operators can now move through the familiar grouped Event Management workspace in V2: setup, registration, staffing, activities, communications, finance, and logistics. Each link keeps the selected event in context and opens the existing V2 workflow; no record migration, permission change, or Partners API change is involved. Live local navigation and route checks passed.

2026-09-03 — Partners Dashboard V2 event details authoring

Event details in Partners Dashboard V2 now use the same rich Markdown Write/Preview authoring surface and show an at-a-glance linked-work summary for plans, finance, and durable assets. Operators can open the existing selected-event linked-work view without changing any event record. Live local rendering, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 overview projections

Partners Dashboard V2 now matches the familiar dashboard overview metrics and report context: Partners, Events, Reports, Active bans, plus recent reports, updates, and bans. The calculation reuses the existing dashboard Reports projection and Worker-owned records; no data migration or permission change is needed. Type, route, and live dashboard checks passed.

2026-09-03 — Partners Dashboard V2 Asset route context

The restored Asset Management context now continues across every V2 Asset Management route. Operators see the same linked-work refresh/manage panel and route-specific action gallery when moving from registers to custody, transit, audits, maintenance, Hub, finance, or settings. The gallery leads to existing scoped controls, so permissions, confirmations, and service-side record checks remain unchanged. Local authenticated rendering, TypeScript, and route coverage checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 overview shortcuts

Partners Dashboard V2’s main overview again includes the familiar Dashboard heading, scope description, Workspace shortcut card, Partner Guide card, and permission-aware CMS handoff. The shortcuts use the existing dashboard routes and CMS session contract, so operators can continue using their normal workflow without a new sign-in or data migration. Local authenticated rendering, TypeScript, and route-coverage checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Reports navigation

The Safety Reports overview now restores the familiar Reports navigation and current-scope description. Operators can reach their reports, the full report directory, watchlists, bans, profiles, and cross-ban requests from the same overview screen, using the existing permission-aware routes and records. Live local rendering and V2 type/route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Event Planning navigation

Partners Dashboard V2 now restores the familiar Event Planning map on its Planning overview. Operators can move between overview, personal work, schedule, requirements, departments, coordination, readiness, and control surfaces while their selected event plan stays in context where applicable. The linked-work entry continues to use the existing source-owned operations projection, so no records, permissions, or service behavior changed. Type and route checks plus the production build passed. Local interactive confirmation will resume once the local Worker is running.

2026-09-03 — Partners Dashboard V2 Event Planning route context

The restored Event Planning navigation now remains visible across every V2 Planning screen, including schedule, requirements, departments, meetings, files, notifications, risks, readiness gates, configuration, and settings. Selected event-plan context remains with scoped work while My Work stays a cross-plan queue. This is a dashboard-only navigation improvement: existing records, permissions, and service behavior are unchanged. Type, route, and production-build checks passed; local interactive confirmation awaits the local Worker coming back online.

2026-09-03 — Partners Dashboard V2 Finance navigation

Partners Dashboard V2 now restores the Finance Management route map and the overview entries for the existing governed outflow-request and balanced-entry workflows. Existing records, approval rules, and service-side accounting stay unchanged. Type, route, and production-build checks passed; local interactive confirmation awaits the local Worker.

2026-09-03 — Partners Dashboard V2 Pawsports route context

Partners Dashboard V2 now keeps its Pawsports workspace map visible while moving between the document overview, registry, and issue-and-binding workflows. Existing identity-document permissions, issued records, and service-side actions are unchanged. Type and route checks passed; local interactive confirmation awaits the local Worker.

2026-09-03 — Partners Dashboard V2 EMS overview context

Partners Dashboard V2 now presents the familiar EMS heading and active-scope description above the existing event directory. Event creation, records, permissions, and service behavior are unchanged. Type and route checks passed; local interactive confirmation awaits the local Worker.

2026-09-03 — Partners Dashboard V2 shared dashboard frame

Partners Dashboard V2 now uses the familiar compact Partners dashboard frame: an always-available top bar, ordered icon navigation, current-scope identity, and a responsive mobile workspace menu. Existing dashboard records, permissions, CMS access, and every workspace route remain on their existing service contracts. Type, route, and live desktop/mobile checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Registration Configuration workflow

Event operators now encounter the event-wide registration form builder and default attendee-question inventory first in Partners Dashboard V2, before the existing availability and lifecycle controls. The reordering uses the shared components already backing the registration workflow; event records, permissions, and persistence contracts are unchanged. Live browser rendering, type checking, and route-execution verification passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Shop Configuration workflow

Partners Dashboard V2 now places Event Shop settings beside catalog and delivery controls, with the listing workspace below. Operators can clearly choose either manual merchandise or an existing registration add-on/inclusion; the latter requires a source selection before it can be saved. Event-shop records, permissions, and service contracts are unchanged. Local browser, type, and route-execution checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Payments Configuration workflow

Partners Dashboard V2 now presents payment collection, checkout fees, cash rounding, confirmation behavior, attendee instructions, VAT, and refunds in clearer task-focused groups. Existing payment providers, receiving accounts, fee calculations, records, permissions, and save behavior are unchanged. Local desktop/mobile browser evidence, type checking, route verification, and the production build passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 notification sample check

Operators can now use the existing safe sample-notification check against a current draft even while event notifications are turned off. The check does not save the draft or enable live delivery; existing destinations, permissions, and service behavior stay unchanged. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 LAN Snapshot History audit summary

Partners Dashboard V2 now shows the loaded LAN snapshot audit-record count and a dedicated refresh command before its history list. Existing snapshot export, import, event records, and service behavior are unchanged. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 LAN Snapshot operations guidance

Partners Dashboard V2 now keeps the same-event import boundary, authoritative airgapped format, shop-order conflict handling, and HR import scope visible beside LAN export/import controls. Existing snapshots, event records, and service behavior are unchanged. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Attendee Coupons feature settings

Partners Dashboard V2 now shows the attendee-coupon switch, discount policy, and surcharge-coverage choice in clearer task-focused groups. Existing coupon codes, schedules, redemption rules, event records, and service behavior are unchanged. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Affiliates and Tracking settings

Partners Dashboard V2 now uses clearer affiliate-tracking controls and the source-defined seven-day attribution-cookie fallback. Existing campaigns, affiliate links, rewards, event records, and service behavior are unchanged. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Inventory Analytics context

Partners Dashboard V2 now keeps the Item health guidance and current tracked-versus-below-demand summary visible above its inventory controls and table. Existing inventory records, fulfillment calculations, and service behavior are unchanged. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Shop Orders Dashboard context

Partners Dashboard V2 now keeps fulfillment-queue definitions and the Merch and Delivery analytics groups visible beside its existing shop-order totals and worklists. Existing orders, revenue calculations, and service behavior are unchanged. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Accounting controls

Partners Dashboard V2 now provides the complete accounting-ledger workflow: account review, CSV export, append-only manual entries, and source-document metadata completion. Existing financial records remain source-owned; the dashboard does not rewrite automatic transaction amounts. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 Settlement context

Partners Dashboard V2 now keeps settlement deadlines, policy facts, and the guarded remittance action’s live balance, shop-fee, and configured-method context visible. Existing settlement quotes, payment evidence, records, and service behavior are unchanged. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 disabled Point of Sale lane

Partners Dashboard V2 now keeps the counter workflow, scanner/customer guidance, and recent-sales context visible when an event has POS disabled. Every sale-affecting control remains disabled until an operator enables POS in Inventory Tracking. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 waitlist orientation and preview

Partners Dashboard V2 now explains the tier waitlist’s automatic 18-hour offer window and provides a safe attendee-form preview using the event’s current registration configuration. The preview cannot create a registration, hold capacity, move inventory, or take payment. Existing waitlist queues, offers, event records, and service behavior are unchanged. Local browser, type, and route checks passed; no Partners API behavior changed.

2026-09-03 — Partners Dashboard V2 communications navigation

Partners Dashboard V2 now presents Email Blasts and SMS Blasts as compact, direct channel cards that retain the selected event. Delivery rules, consent, audiences, campaigns, and messages are unchanged. Local desktop/mobile browser, type, and route checks passed; no Partners API behavior changed.

2026-09-10 — Expandable media buckets prepared

Partners Dashboard, RegoSite, and Social uploads can now be assigned to separate Sanity media projects through one server-only registry. Existing media continues to work while new buckets are provisioned; Social keeps the bucket identity with each asset so photos and future video buckets remain traceable. Visitors and operators will continue receiving Furries PH media proxy URLs, not provider URLs. The registry, database migration, and API type checks were validated locally; creating projects and adding their credentials remains an operator deployment step.

2026-09-10 — RegoSite V2 verified feedback clarity

RegoSite V2 now makes it clear when an event feedback response is linked to a verified attendee account, rather than describing that response as anonymous. Signed-out attendees now get one clear local sign-in action rather than an unusable Submit control. Optional follow-up contact remains opt-in. Local desktop and mobile feedback checks, identity readback, type checking, and the production build passed. Feedback drafts now refresh safely when an organiser publishes a revised form, so outdated answers are not restored. No hosted records or notification providers were used. Image attachments now clearly ask signed-out attendees to sign in instead of offering an upload that the protected media service cannot accept; anonymous text feedback remains available.

2026-09-10 — Signals event reward configuration fixed

Partners Dashboard Signals now saves the “Event or RegoSite access” reward as the supported event-entitlement type. Partners configuring digital, discount, event-access, or physical completion rewards can publish without the event option being rejected. A source-hashed isolated run exercised all four dialog choices through the real local Worker, Auth, database, dashboard, and Signals respondent app; the complete 42-check route and Partners type check passed. No hosted records or reward fulfillment providers were changed.

2026-09-11 — Scheduled campaign access controls

Partners Dashboard and Partners Dashboard V2 can now save standalone campaign rules with a start and end time, optional redemption limit, and controlled pre-fill or waitlist bypasses. RegoSite V1 and V2 use a valid, current campaign link to enter the corresponding registration path while still enforcing event end time, tier availability, capacity, attendee eligibility, payment, and the campaign limit. Campaign records are reloaded from the server after every save and after signing back in. Local dashboard diagnostics, Rego V1 diagnostics, Rego V2 type checks, and the API type check passed. The database migration must be published before the new bypass fields are available in a hosted environment.

2026-09-10 — Signals form-first authoring

Signals in the Partners Dashboard, Partners Dashboard V2, and Admin Dashboard now uses a Google-Forms-style authoring flow: Questions is the focused starting workspace, with direct question and section actions, pages as a compact step switcher, a clear saved state, and a persistent Publish action. Responses and operational settings are separate tabs, so reporting, sharing, lifecycle controls, and rewards do not interrupt form construction. Existing survey definitions and Worker/API behavior are unchanged. Admin type checks, tests, and production build passed; both Partners dashboard builds and diagnostics passed.

2026-09-10 — Dealers Den assistant invitations can now be answered

RegoSite V2 now lets an invited Dealers Den assistant accept or decline their own pending invitation. The invitation stays clear on phones, updates immediately after a response, and does not expose the representative’s table payment or reservation controls. Already answered invitations and invitations belonging to another attendee are safely rejected. Local desktop/mobile browser, API type, and 231-check isolated Dealers Den verification passed with complete fixture cleanup; no hosted records or payment providers were used.

2026-09-10 — RegoSite V2 registration parity and optional signatures

RegoSite V2 now treats signature pads as optional across attendee Rego, Shop, Activity, Vollie, Dealers Den, and pass-change forms. If someone chooses to draw a signature, it remains a strictly validated black-on-transparent SVG; leaving it blank never blocks the form. Conditions of Entry remains the shared required consent gate.

The wider attendee journey was rechecked locally across Rego, Shop, Gifts, Dealers Den, POS, feedback, refunds, transfers, upgrades, profile routes and account controls at desktop and mobile widths. These checks used sealed local fixtures and did not create hosted registrations, payments, uploads, or provider settlements. Deployment and live-provider verification remain separate release steps.

2026-09-11 — RegoSite V2 image-proxy compatibility

RegoSite V2 now keeps legacy image-proxy links working when an API response contains a relative or cross-origin /api/img/ address. Event posters and other proxied images resolve through the configured Furries PH API instead of the site page origin. The Worker normally sends absolute proxy links, and this protects older or mixed responses. Local mobile browser checks, type checking, and the production build passed. No hosted records or deployment were used.

2026-09-11 — RegoSite V2 attendee response boundary

RegoSite V2 now rejects organizer-only planning details if they ever appear in a public event or Shop response. Attendee screens keep using their existing safe recovery state instead of displaying private organizer data. Local mobile browser checks and type checking passed. No hosted records or deployment were used.

2026-09-11 — RegoSite V2 Shop recovery

RegoSite V2 now gives attendees a clear retry message when the public Shop catalog, saved cart, or cart validation service does not respond within the existing recovery window. Local browser transport checks and type checking passed. No hosted records or deployment were used.

2026-09-11 — RegoSite V2 Shop receipt recovery

RegoSite V2 now applies the existing Shop recovery window when loading order history and individual receipts. Local type checking passed. No hosted records or deployment were used.

• Rego platform: Local-only capacity repair prepared: concurrent Shop checkout now returns a recoverable cart-preserving conflict, and Gift capacity races return a readable capacity response. It has not been deployed; final local concurrency certification requires the local database runtime.

2026-09-11 — RegoSite V2 source parity verification

RegoSite V2’s local parity check now compares the active RegoSite V1 source files by content hash, including active working-tree changes. This makes future parity reviews flag source changes reliably before release work proceeds. The current V1 source scope is unchanged. This is a local verification improvement; it does not change the public site or deploy anything.

2026-09-11 — RegoSite V2 capacity conflict recovery

RegoSite’s registration and Shop services now give attendees a clear recoverable response when another attendee takes the final available capacity. Shop carts remain available for review after a conflict, and capacity cannot be reclaimed by reactivating a cancelled order after another attendee has taken its place. Local sealed concurrency checks confirmed one successful Shop checkout and one conflict, plus the same protection for gift registration capacity. No hosted orders, registrations, payments, or deployment were created.

2026-09-11 — RegoSite V2 local group and staffing verification

RegoSite V2’s group registration and volunteer/staff shift journeys have now been rechecked through real local browser and service flows. Group members retain their own choices and private receipts, while staff and approved volunteers can track shifts with the correct permissions and authorization records. These local checks used temporary fixture accounts and cleaned them up after completion. No hosted attendee records, payment settlement, or deployment occurred.

Partners Dashboard V2 now lets authorized planning operators start a Schedule work item directly from a requirement. The linked requirement is already selected in the work form, so delivery progress, evidence submission, and approval remain connected without re-entering the relationship. Local browser contract checks, type checking, and production build passed. No hosted planning records were created.

Partners Dashboard V2 Requirements, Risks, and Meetings now support saved register views. Planning staff can keep their current requirement search and status filters for themselves, while authorized editors can share a project view with the team. Local browser contract checks, type checking, and production build passed. No hosted planning records were changed.

Partners Dashboard V2 now lets authorized planning administrators record a final safety disposition for an uploaded planning artifact. The action requires a reason, is restricted to the existing sensitive-files and project-administrator permissions, and updates the governed artifact status. Local browser contract checks, type checking, and production build passed. No hosted files were reviewed.

Partners Dashboard V2 now shows the visible work relationships behind a schedule and lets authorized planners remove an obsolete dependency after confirmation. The schedule recalculation and audit record remain in the existing planning service. Local browser contract checks, type checking, and production build passed. No hosted schedule relationships were changed.

Partners Dashboard V2 can now attach an eligible event plan to its canonical EMS event. Authorized planners choose from events already visible in their active partner scope, allowing Planning, EMS, and Rego to use the same event identity. Local browser contract checks, type checking, and production build passed. No hosted plans were linked.

Partners Dashboard V2 now lets planning participants open an authorized meeting record to review its ordered agenda and its returned minutes revisions, including published minutes. The planning service continues to control access, revision history, and meeting content. Local browser contract checks, type checking, and production build passed. No hosted meeting records were changed.

Partners Dashboard V2 now gives planning participants a read-only timeline of the immutable events for a selected meeting. The existing planning service determines which records are visible and retains the complete audit trail. Local browser contract checks, type checking, and production build passed. No hosted records were changed.

Partners Dashboard V2 now provides the same read-only planning audit history for selected risks and governance gates as it does for meetings and scheduled work. The existing planning service keeps visibility and event history authoritative. Local browser contract checks, type checking, and production build passed. No hosted records were changed.

Partners Dashboard now resolves its API destination from the hostname before using a build-time setting. The live partners.furries.ph dashboard therefore continues to use the production Partner API even when a local development address was present during a build. This fixes dashboard sign-in and EMS loading from public pages; local development still uses its local API target.