Platform Updates

Repository: cms.furries.ph, partners-api, and furries.ph — deployment pending validation.

Scheduled Furries PH posts and guides are now processed by the Partners API Cloudflare Cron Trigger every five minutes. A due publishing batch requests one connected Pages rebuild, so newly released articles and guides reach the public site without a separate cron service. Editors keep using the existing Schedule action in CMS; operators should verify the next due publish and resulting Pages build.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

Reverting registration setup now also restores saved Zep access and event chat-bot assignments, alongside the existing event and group settings. The local type check passed. No event, registration, provider, or hosted record changed.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

The event-image crop dialog now stays quiet when no image is selected. A local event lifecycle opened and dismissed the A4 crop view, saved and reloaded event details, and removed its temporary event without browser errors or external requests. No media, provider, or live record changed.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

The event-setup guide now renders every launch requirement consistently. A local authenticated route check opened the dashboard, guides, legal pages, and every partner workspace without browser errors or external requests. No live records changed.

Repositories: partners-api and partners.furries.ph-v2 — local implementation, not deployed.

The Asset Finance workspace now loads its active accounting context correctly. The local authenticated check covered the Asset overview, owned and loaned registers, checkouts, transit, audits, maintenance, logistics hub, finance, and settings routes without browser or external-request errors. API and dashboard type checks passed. No asset, finance, provider, or hosted record changed.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

The Dealers Den registration preview now returns keyboard focus to the QR-code control after its dialog closes. The same local browser verification confirmed the full registration journey in both the canvas and EMS editor, including package selection, attendee questions, conditions, payment review, responsive layouts, and the local completion receipt. No registration, payment, provider, customer data, or deployment changed.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

Partners V2 now keeps supporting content such as an add-on price visibly attached to its selectable registration cards. The card remains one native selection control, so keyboard and touch selection stay unchanged. A focused mobile browser check confirmed the footer and selection state without external requests. No registration, payment, provider, or deployment changed.

Repositories: partners-api and partners.furries.ph-v2 — local implementation, not deployed.

The local Partners bootstrap now returns a controlled timeout when its local authentication service is unavailable, instead of leaving the dashboard waiting indefinitely. Partners V2 can also use an explicitly configured loopback Worker when the conventional local listener is unavailable, while hosted targets and the default local fallback stay unchanged. The local login and dashboard-session checks both returned successful responses. The Worker and V2 type checks passed. No customer data, provider session, or deployment changed.

Repositories: partners-api, rego.furries.ph, and rego.furries.ph-v2

Registration prefills can now save during their configured prefill window, even before standard registration opens. Price checks remain available in both registration experiences and use the same tier-specific prefill window rules as saving. No action is needed from attendees or organisers.

The API type check and both production builds passed; the updated API and both registration sites were deployed.

Repository: partners.furries.ph-v2 — local implementation, not deployed.

Partners V2 now uses the same API-owned issue-report widget as the partner dashboard. The shared widget continues to handle identity, verification, diagnostics, delivery and support receipts. A local mobile check confirmed its trigger renders without opening or submitting a report. No customer data, support report, Worker record, or deployment changed.