Platform Updates

What This Page Tracks

This page gives partner teams one place to review meaningful product, operations, and documentation changes across Furries PH operational systems. It is written for readers who need to know what changed, why it matters, and what action they may need to take next.

The main public furries.ph site and CebuFurs properties are intentionally excluded. Those sites have different audiences, brands, event schedules, and update rhythms, so their release notes should live with their own projects instead of this Furries PH operations log.

Workspace Change Log

2026-07-05 - Active platform certification and docs refresh

Affected repos: partners-api, partners.furries.ph, rego.furries.ph, and docs.furries.ph.

The July platform work focused on certifying operational systems before they are relied on by partner teams. The partner dashboard added social-integration certification coverage, abortable social-link flows, Event Management production checks, Dashboard Reports production checks, SPA shell certification tooling, and fixes around dashboard data loading, signing, cleanup, password reset, set-password, and search behavior.

The public registration app completed SPA conversion support work, improved route loading and API request headers, and added certification reports so registration behavior can be reviewed with stronger proof. The docs site added fuzzy search, refreshed platform adoption wording, standardized EMS LAN wording, and created this update log so changes in sibling repos are visible from one place.

Who may notice it: partner admins, event leads, registration operators, support leads, and teams adopting social integrations, report workflows, Event Management, or registration flows.

What to do next: review the relevant guide before operating a changed workflow, especially social account linking, dashboard reports, event setup, public registration, and search-driven documentation lookup.

Validation evidence from git history: certification commits, SPA support commits, search integration commits, and docs build/check validation in docs.furries.ph.

2026-07-05 - Docs updates page and workspace update rule

Affected area: docs.furries.ph and Furries PH operational repos.

The docs site now has a top-level Updates page. Future changes in Furries PH operational repos should add a short, public-facing entry here when they change behavior, setup, release process, documentation, or operator expectations.

Who may notice it: partner admins, event operators, support leads, and maintainers reading docs before adopting or operating Furries PH tools.

What to do next: when a repo change is made, add a dated entry to this page with the affected repo, user-facing impact, and validation evidence.

Validation: pnpm check and pnpm build in docs.furries.ph.

2026-07-04 - SPA navigation and live event readiness

Affected repos: partners-api, partners.furries.ph, and rego.furries.ph.

The platform and dashboard history shows a push toward SPA-style navigation, loader consistency, authentication reset usability, and contract checks. The dashboard also refined Event Management typography and offline snapshot experience, while the registration app improved route behavior and API body handling.

Who may notice it: attendees registering for events, event staff configuring registration, and dashboard operators moving through protected pages.

What to do next: before announcing registration or dashboard changes, confirm the correct event configuration is live and walk through the affected attendee or operator path once.

Validation evidence from git history: SPA conversion commits, offline snapshot UX commits, registration app commits, and dashboard contract commits.

2026-06 - LAN operations, partner API foundations, CMS publishing, and scheduled automation

Affected repos: fph-lan-ems, partners-api, partners.furries.ph, rego.furries.ph, cms.furries.ph, and furries-ph-cron.

EMS LAN work expanded the offline event system with Android wrapper support, packaging workflows, in-shell communications, calls UI, operator documentation, HR mirrors, inventory mirrors, POS mirrors, local API documentation, and certification tooling. Partner API and dashboard work added LAN snapshot import/export, sync history, LAN release proxy support, offline HR and inventory snapshots, partner data-silo configuration, partner role helpers, and dashboard UI for audit workflows.

Registration and CMS work improved communications settings, email preferences, legal/profile sections, markdown rendering, notice polling, studio inputs, scoped publishing checks, auto-linking, and hashtag handling. Supporting automation added expired-event archive workflows and scheduled publishing updates.

Who may notice it: event operators running offline check-in, registration staff, CMS editors, partner admins, and maintainers responsible for scheduled jobs.

What to do next: for offline operations, verify the exact snapshot, device, import, and reconciliation path before using LAN data as trusted state. For CMS and scheduled jobs, confirm publishing scope and automation timing after deployment.

Validation evidence from git history: LAN runtime commits, snapshot import/export commits, data-silo commits, CMS scope-fix commits, and scheduled workflow commits.

2026-05 - Content tooling, classroom tooling, and gallery updates

Affected repos: classroom.sekailens.com, cms-classes.sekailens.com, cms.furries.ph, furries-ph-cron, and gallery.furdu.com.au.

Sekai Lens classroom and CMS work added articles, simulator improvements, pan/reframe controls, composition and exposure target evaluation, EXIF and metadata support, feedback previews, image fields, orderable lists, and site settings. Gallery and content repos imported FurDU photo updates and wording changes.

Who may notice it: content editors, photo gallery visitors, classroom learners, and maintainers responsible for scheduled publishing.

What to do next: treat these updates as content operations changes. Check public pages, media previews, and classroom content before sending users to a changed route.

Validation evidence from git history: classroom simulator commits, CMS schema commits, scheduled workflow commits, and gallery upload commits.

2026-04 - Media guides, photo tooling, and classroom metadata

Affected repos: classroom.sekailens.com, cms-classes.sekailens.com, ConvoMetrics, furcon-photo-separator, furdu.sekailens.com, gallery.furdu.com.au, and rego-astro.

FurDU media pages received schedule refinements, outage notes, offload-window changes, Open Graph metadata, glossary/table-of-contents improvements, timers, and layout updates.

Classroom and CMS updates added EXIF preservation, cropping guides, metadata support, histogram support, Open Graph image fields, and lesson schema refinements. Photo tooling added a Lightroom Classic plug-in for fursuiter, pup-mask, and human classification. ConvoMetrics was refreshed into a Streamlit dashboard and analytics interface. rego-astro remained an early registration scaffold.

Who may notice it: media volunteers, content editors, classroom authors, photo-processing staff, and users viewing public assets or galleries.

What to do next: confirm media schedule pages, exported assets, and metadata-heavy content still match the event plan before sharing links publicly.

Validation evidence from git history: media-guide commits, EXIF/metadata commits, Lightroom plug-in commits, and dashboard overhaul commits.

2026-03 - Pawsport developer docs, reporting microsite, and bot setup

Affected repos: Bakunawa, pawsport.furries.ph, and report.furries.ph.

Pawsport work added developer documentation, assets, keyring and state exports, an 18-digit format, renamed RSA files, and an early alpha milestone. The reporting microsite gained responsive UI improvements, section clear buttons, development tools, and placeholder updates. Bakunawa added bot scaffolding, scripts, deployment guides, troubleshooting documentation, interactive credential collection, and feature planning details.

Who may notice it: developers adopting Pawsport formats, staff reviewing reporting microsite tools, and maintainers setting up bots or small studio projects.

What to do next: use these entries as historical context before reviving any of these smaller systems. Confirm the current docs and setup files before relying on early scaffold behavior.

Validation evidence from git history: initial scaffold commits, developer documentation commits, responsive UI commits, and bot setup commits.

2026-02 and earlier - Older analytics history

Affected repos: ConvoMetrics.

Older ConvoMetrics history records the move from simple Python files into a maintained app with emoji support and later analytics interface work.

Who may notice it: maintainers reviewing analytics tooling history.

What to do next: treat this as historical context before reusing the analytics tooling.

Validation evidence from git history: older analytics app commits.