Furries PH Docs
Dashboard

Updates

Platform Updates

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

First created Last updated

Release Notes

Showing release notes 211-220 of 243
2026-07-0809:10

EMS LAN and Platform API Docs Rewrite

Repositories: docs.furries.ph

Status: Released

What’s Changed

  • Rewrote the EMS LAN docs with route/surface scope, page-specific records, decision owners, operating sequence, verification evidence, common mistakes, related links, and Mermaid diagrams for workflow-heavy pages.
  • Rewrote Platform API docs foundations, getting started, authentication, route reference, workflows, schemas, security, operations, testing, reference, glossary, and start pages using adopter-facing capability language.
  • Added Mermaid diagrams for EMS LAN export/import/reconciliation paths and Platform API auth/capability decision paths.
  • Preserved the generated route inventory as the exact route lookup source while the surrounding Platform API docs pages explain how to use route evidence safely.
  • Removed the old repeated guide boilerplate from EMS LAN and Platform API docs pages.

Impact

EMS LAN and Platform API docs now follow the same operator/adopter structure as Reports and Event Management docs.

Upgrade Notes

  • No runtime change. Partner teams can use the rewritten docs as operating and adoption guides.
2026-07-0809:10

Event Management Lifecycle and Reference Rewrite

Repositories: docs.furries.ph

Status: Released

What’s Changed

  • Rewrote every Event Management lifecycle page so event, registration, payment/refund, check-in, staff/volunteer, and post-event maintenance flows now use concrete EMS states, affected surfaces, verification points, and handoff rules.
  • Added Mermaid flowcharts to every Event Management lifecycle page so operators can visually follow the event, registration, payment/refund, check-in, staff/volunteer, and post-event maintenance paths.
  • Rewrote the Event Management reference pages for route map, role access, data records, and certification so they match the practical route-specific style used by the newer foundations, basics, and surface docs.
  • Added route tables, record-impact tables, lifecycle state tables, common mistakes, and direct links to the specific surface pages operators need for each workflow.
  • Removed generic lifecycle/reference boilerplate from these pages.

Impact

Event Management lifecycle and reference docs now explain how work moves across the dashboard instead of describing abstract phases.

Upgrade Notes

  • No runtime change. Event teams and support leads can use the lifecycle/reference pages as operating guides for readiness checks, event-day handoffs, and closeout review.
2026-07-0709:10

Report Surface Input Audit

Repositories: docs.furries.ph

Status: Released

What’s Changed

  • Added a dedicated report-system surface audit task covering every active Report dashboard route, source page, layout link, SPA manifest entry, modal, form field, dropdown, and conditional state.
  • Replaced broad grouped Report System surface docs with route-specific pages for Reports Overview, All Reports, My Reports, Mine compatibility, New Report, Report Detail, Manage Report, Watchlists, Bans, Ban Appeals, Cross-Ban Requests, Network Ban Appeal, and Person Profiles.
  • Rewrote the New Report and Manage Report docs with source-backed explanations for severity, statuses, violation categories, action types, local action choices, ban scopes, people fields, evidence fields, markdown-ext fields, signatures, and cross-community ban controls.
  • Rewrote the Watchlists, Bans, Cross-Ban Requests, Ban Appeals, and Network Ban Appeal docs with source-backed explanations for adoption selectors, disabled ban-list options, FPH review requests, appeal submit/update/resubmit states, decision notes, scope radios, and confirmation controls.
  • Rewrote Person Profiles docs around profile creation, similar-report suggestions, report linking, search, unlinking, deletion risk, and identity uncertainty.
  • Removed old generic report surface boilerplate from the active surface docs.

Impact

Report System surface documentation now matches the same route-specific operator-reference pattern used by Event Management surface docs.

Upgrade Notes

  • No runtime change. Operators can use each Report System surface page as the control reference for its matching dashboard route.
2026-07-0709:10

Event Management Compatibility Routes Removed

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

Status: Released

What’s Changed

  • Removed the old Event Management compatibility pages for /ems/manage/config, /ems/manage/payments, /ems/manage/pos, /ems/manage/registrants, and /ems/manage/staff-subsidies from the partner dashboard.
  • Removed those compatibility routes from the SPA manifest, dashboard scene controllers, route certification fixtures, and stress-route inventory.
  • Cleaned dashboard documentation and the Event Management surface audit task so removed compatibility pages are not listed as active surfaces.

Impact

Partner operators should use the canonical Event Management pages from the sidebar. Legacy compatibility URLs are no longer documented or certified as supported dashboard pages.

Upgrade Notes

  • Use /ems/manage/details, /ems/manage/rego-config, /ems/manage/payments-config, /ems/manage/point-of-sales, /ems/manage/regos, and /ems/manage/human-resources for the corresponding active surfaces.
2026-07-0709:10

Event Surface Input Audit Task

Repositories: docs.furries.ph

Status: Released

What’s Changed

  • Added a dedicated task for auditing every Event Management surface input, option, modal, control, and conditional field from the partner dashboard source.
  • Defined the required surface-doc writing standard so each page explains what every input changes, what each option means, and what operational impact it can have.
  • Expanded the task with the complete active src/pages/ems/manage/ page inventory, including canonical sidebar surfaces, analytics pages, operation pages, and the current manage-root redirect.
  • Added the requirement to split Event Management surface docs into one route-specific docs page per active dashboard manage page.
  • Added the requirement for flowchart action steps to link to the matching route-specific surface docs when an action maps to a dashboard page.
  • Split the active Event Management surface docs into route-specific pages for each dashboard manage surface and removed the previous broad grouped surface articles.
  • Added surface-reference tables to the Create an Event, Active Event Workflow, Run Check-In, and Close Out an Event guides so flowchart actions link to their matching surface docs.
  • Expanded the setup surface reference pass for Details, Payments Config, Notification Config, and Google Wallet Config with source-backed options, validation rules, and operational impacts.
  • Expanded Rego Config, Dealers Den, and Conditions of Entry surface docs with source-backed option references for registration flow modes, item types, ZEP access, dealer packages, and required-document assignment targets.
  • Expanded the audit requirements so dropdowns, menu buttons, overflow menus, split buttons, context menus, comboboxes, autocomplete lists, item pickers, and command palettes must document every visible item, conditional state, and selection effect.
  • Updated Event Management flowchart requirements so surface docs links belong inside the relevant flowchart boxes or decision elements, not only in separate reference tables outside the diagrams.
  • Expanded Offline Snapshot and Offline Snapshot History surface docs with source-backed export/import controls, accepted file formats, confirmation behavior, applied-count status output, and LAN audit-history fields.
  • Expanded Check-In and Inclusion Claim surface docs with source-backed workflow settings, scanner/NFC controls, record sections, entry-card fields, modal details, flags, notes, checklist behavior, and submit actions.
  • Expanded Regos, Waitlist, Upgrades, Refunds, and Transfers surface docs with source-backed table filters, bulk actions, notification actions, modal fields, request statuses, waitlist offer settings, refund review controls, and transfer item-selection behavior.
  • Expanded Human Resources, Volunteer Positions, Volunteer Applications, Staff Roster, and Live Shift Tracker surface docs with source-backed import controls, subsidy hierarchy, department/member/location editors, form-builder controls, application review decisions, roster timeline controls, shift editor fields, and live location coverage states.
  • Revisited the first Event Management setup surface docs so Event Overview and Lists, Details, Rego Config, Dealers Den, Conditions of Entry, Payments Config, Notification Config, and Google Wallet Config now use the same input/option/state reference structure as the later surface pages.
  • Expanded Activities, Submissions Review, Approved Submissions, Communications, Attendee Coupons, and Affiliates Tracking surface docs with source-backed form-builder controls, review modals, notification actions, audience modes, attendee picker filters, email/inbox previews, coupon policy options, affiliate campaigns, reward tables, conversion rules, commission payout methods, generated links, and validation states.
  • Expanded Rego Analytics, Finance Analytics, Settlements, Inventory Analytics, Inventory Tracking, and Point of Sales surface docs with source-backed metric chips, provider/account reconciliation states, settlement quote fields, inventory stock controls, UUID/NFC/QR/barcode exports, POS scanner behavior, customer and basket controls, payment choices, surcharge options, order summaries, and recent transaction records.
  • Added explicit dashboard-route sections to every Event Management surface page and embedded route-specific surface references directly inside the Create an Event, Active Event Workflow, Run Check-In, and Close Out an Event flowchart nodes.
  • Completed the Event Management surface audit task with source inventory checks against the active manage pages, the EventEditLayout sidebar, and the SPA route manifest.
  • Added acceptance checks to prevent old generic surface-guide boilerplate from remaining in Event Management surface docs.

Impact

Event Management surface documentation now has route-specific operator references for every active manage page, with source-backed control and option descriptions.

Upgrade Notes

  • No runtime change. Operators can now use the Event Management surface pages as the route-specific control reference for active dashboard pages.
2026-07-0609:10

SPA Button and Modal Lifecycle Hardening

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

Status: Released

What’s Changed

  • Hardened SPA scene cleanup so route changes no longer remove global shell listeners needed by navigation, modals, confirm dialogs, and floating save controls.
  • Made the partner dashboard confirm dialog mount idempotently when SPA navigation re-executes document scripts.
  • Kept partner dashboard to Rego/Event Management transitions inside the SPA shell by adopting the next page sidebar chrome and routing management redirects through the shell navigation API.
  • Aligned the API SPA contract manifest with the Rego notifications inbox route so attendee certification no longer reports backend contract drift.
  • Added focused button and modal certification gates for partner dashboard/Event Management and attendee Rego surfaces, including source inventories for 237 partner files and 137 Rego files.
  • Added browser-visible control inventory commands for partner dashboard/Event Management and attendee Rego routes.
  • Local focused browser inventory now records and validates 803 visible partner controls and 267 visible Rego controls across desktop/mobile preview routes.

Impact

Buttons, modal triggers, and save controls should continue responding after modal close, route remounts, query-string navigation, and SPA document swaps.

Upgrade Notes

  • Validation passed with pnpm dashboard-buttons:certify, pnpm rego-buttons:certify, pnpm spa:routes:check, pnpm spa:inline:check, pnpm exec astro check for partners, npm run spa:contracts:check, npm run type-check, production builds for both apps, and local desktop/mobile browser route certification for partner dashboard/Event Management and Rego attendee previews.
  • Production aliases now run the production browser route loop first, then require authenticated desktop/mobile evidence reports before they can pass.
  • Production aliases also capture and require visible-control inventory reports for the same authenticated production routes before the button certification gates pass.
  • A fresh production certification state was minted through the hosted test-control API for button certification. Partner dashboard production route/control/navigation-pair certification now passes for 12 routes, 6 navigation pairs, desktop/mobile viewports, browser history, and 824 visible controls. Rego now has deployed static __spa fallback pages and Cloudflare Pages rewrites for event-scoped dynamic routes, with authenticated production certification passing for 11 routes, desktop/mobile viewports, browser history, and 261 visible controls.
2026-07-0609:10

BPMN-Style Mermaid Diagram Theme

Repositories: docs.furries.ph

Status: Released

What’s Changed

  • Updated docs Mermaid flowcharts to use straighter connector lines, sharper process boxes, clearer decision diamonds, and compact edge labels.
  • Reworked Mermaid colors back into the docs visual system instead of using a dark standalone diagram palette.
  • Added SVG-level styling so generated diagrams look closer to structured process maps while staying consistent with the docs cards, typography, and borders.

Impact

Guide flowcharts now read more like operational process diagrams and are easier to compare with event-management workflows.

Upgrade Notes

  • No authoring change is required. Existing fenced mermaid flowcharts pick up the new styling automatically.
2026-07-0609:10

Event Creation End Time Requirement

Repositories: partners.furries.ph

Status: Released

What’s Changed

  • Added a required Event ends at field to the partner dashboard New Event form.
  • Kept Event starts at required at creation time so every new event starts with both sides of its operating window.
  • Added client-side validation that blocks creation when the end date and time is not after the start date and time.

Impact

New event records now have a complete start and end schedule before teams move into event management setup, staffing, settlements, and public registration configuration.

Upgrade Notes

  • Event teams creating new events must enter both start and end date/time values before the event shell can be created.
2026-07-0609:10

Mermaid Markdown Rendering

Repositories: docs.furries.ph, partners.furries.ph, rego.furries.ph, fph-lan-ems

Status: Released

What’s Changed

  • Added Mermaid diagram support for fenced mermaid Markdown blocks in the docs site, partner dashboard markdown-ext renderer, attendee rego renderer, and EMS LAN markdown renderer.
  • Added browser-side Mermaid rendering that observes dynamically inserted markdown previews and stored markdown content.
  • Added a Mermaid insert button to dashboard markdown editors where the shared markdown-ext toolbar is available.
  • Kept Mermaid loading lazy so the large diagram renderer is only fetched when a page actually contains a Mermaid block.

Impact

Documentation and operational markdown fields can now show process flows, state diagrams, and handoff diagrams without relying on screenshots.

Upgrade Notes

  • Use fenced code blocks with mermaid as the language, for example ```mermaid followed by the diagram source.
2026-07-0609:10

Paginated Release Notes

Repositories: docs.furries.ph

Status: Released

What’s Changed

  • Changed the Updates page to render release notes as individual cards instead of one long continuous document.
  • Added Astro static pagination with 10 release-note cards per page.
  • Kept the update-log source in Markdown while moving it to src/content/updates.md so it can feed paginated routes, search, and commit hooks.

Impact

Readers can scan recent changes in a layout closer to GitHub releases without loading every historical note in one long page.

Upgrade Notes

  • No operator action is required.

All docs