Platform Updates

Repositories: partners.furries.ph, docs.furries.ph

Status: Released

What’s Changed

• Validated stored dashboard session state before treating a returning browser as signed in.
• Made authenticated dashboard requests use the refreshed session immediately after token refresh.
• Added the release note entry for operators who may see session-expiry messages.

Impact

Partner admins and event operators should see fewer “Session expired” messages while signing in, returning to an older browser tab, or continuing after a token refresh.

Upgrade Notes

• If the login screen still reports an expired session, reload the page once so the browser clears old session state, then sign in again.

Repositories: partners-api, partners.furries.ph, rego.furries.ph, docs.furries.ph

Status: Released

What’s Changed

• Added or refreshed certification coverage for social integrations, Event Management, Dashboard Reports, SPA shell behavior, and dashboard data loading.
• Improved public registration SPA support, route loading, and API request headers.
• Added fuzzy search, Platform API docs wording, EMS LAN wording, and the shared Updates page in the docs site.
• Recorded certification and documentation work in one public release stream for operational teams.

Impact

Partner admins, event leads, registration operators, support leads, and teams adopting social integrations, report workflows, Event Management, or registration flows have a clearer readiness record before relying on changed systems.

Upgrade Notes

• Review the relevant guide before operating a changed workflow.
• Pay close attention to social account linking, dashboard reports, event setup, public registration, and search-driven documentation lookup.

Repositories: docs.furries.ph

Status: Released

What’s Changed

• Added a top-level Updates page to the docs site.
• Established the rule that Furries PH operational repos should add a public release note when a change affects behavior, setup, release process, documentation, or operator expectations.
• Excluded the main furries.ph site and CebuFurs properties from this shared operations log.

Impact

Partner admins, event operators, support leads, and maintainers now have one place to review meaningful operational changes across the workspace.

Upgrade Notes

• When a future repo change affects users or operators, add a dated release-note entry here.
• Keep entries public-facing and avoid secrets, internal-only signposting, or implementation chatter.

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

Status: Released

What’s Changed

• Improved SPA-style navigation, loader consistency, authentication reset usability, and contract checks.
• Refined Event Management typography and offline snapshot experience in the dashboard.
• Improved registration app route behavior and API body handling.

Impact

Attendees registering for events, event staff configuring registration, and dashboard operators moving through protected pages should see more consistent routing and live-operation behavior.

Upgrade Notes

• Before announcing registration or dashboard changes, confirm the correct event configuration is live.
• Walk through the affected attendee or operator path once.

Repositories: fph-lan-ems, partners-api, partners.furries.ph, rego.furries.ph, cms.furries.ph, furries-ph-cron

Status: Released

What’s Changed

• Expanded EMS LAN 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.
• 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.
• Improved registration and CMS communications settings, email preferences, legal/profile sections, markdown rendering, notice polling, studio inputs, scoped publishing checks, auto-linking, and hashtag handling.
• Added expired-event archive workflows and scheduled publishing updates.

Impact

Event operators, registration staff, CMS editors, partner admins, and maintainers responsible for scheduled jobs have broader offline and operational coverage.

Upgrade Notes

• For offline operations, verify the exact snapshot, device, import, and reconciliation path before treating LAN data as trusted state.
• For CMS and scheduled jobs, confirm publishing scope and automation timing after deployment.

Repositories: cms.furries.ph, furries-ph-cron

Status: Released

What’s Changed

• Improved content publishing support for Furries PH CMS-managed pages.
• Refined media, metadata, and site-setting workflows used by publishing teams.
• Continued scheduled publishing and automation updates for time-sensitive content.

Impact

CMS editors and maintainers responsible for scheduled publishing have a clearer history of content tooling and automation changes without mixing in unrelated projects.

Upgrade Notes

• Check public pages, media previews, and scheduled publishing windows after changing CMS-managed content.
• Confirm automation timing before announcing or relying on a scheduled update.

Repositories: pawsport.furries.ph, report.furries.ph

Status: Released

What’s Changed

• Added Pawsport developer documentation, assets, keyring and state exports, an 18-digit format, renamed RSA files, and an early alpha milestone.
• Improved the reporting microsite with responsive UI updates, section clear buttons, development tools, and placeholder cleanup.

Impact

Developers adopting Pawsport formats and staff reviewing reporting microsite tools have more setup history and project context.

Upgrade Notes

• Use these entries as historical context before reviving either smaller system.
• Confirm the current docs and setup files before relying on early scaffold behavior.

Affected repository: partners.furries.ph and partners-api
Asset operators can now import an offline audit count sheet against one named open audit. AMS validates the observed rows first and commits only a clean batch, retaining the signed-in counter and unexpected physical observations without creating false assets. Counters working in blind audits continue to receive no expected quantity or location. Local verification passed the database, API, and 107-check production-static browser certificate. This is ready for the normal reviewed migration release; no hosted deployment is claimed here.

Affected repository: partners.furries.ph
Asset operators now receive a clear, non-destructive manual retry state when a scanner identity cannot be matched, connectivity is unavailable, the device cannot decode camera/NFC input, or multiple labels are visible. A label already flagged as a possible clone or tamper attempt is blocked from every operational handoff and directed to verification and escalation. Successful asset, shipment, container, seal, and location routing is otherwise unchanged. Local production-static browser verification passed 107 checks with 158 UI captures.

Repositories: partners.furries.ph, partners-api

Status: Validated locally

What’s Changed

• Added focused Event Planning certification commands for source contracts, keyboard tab lifecycle, operation launches, workflow, recovery, responsive, conflict, and individual API domains.
• Kept the complete local manifest as the release gate while making it possible to verify an affected area first.
• Added a browser check for desktop and mobile keyboard navigation, remount-safe tab listeners, browser errors, and narrow-screen overflow with screenshots.

Impact

EPS maintainers can receive targeted feedback without waiting for unrelated workflows. Event operators see no product-flow change.

Upgrade Notes

• Use the focused command matching the changed surface during development.
• Run the complete local manifest before a release decision.