Platform Updates

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.

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.

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.

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.

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.

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.

Repositories: docs.furries.ph

Status: Released

What’s Changed

• Removed Audience, Dashboard surfaces, and Records touched metadata cards from guide headers.
• Moved first-created and last-updated timestamps into a compact text line below the guide description.
• Changed page history labels to include both date and time, rendered in each reader’s local timezone without a visible GMT suffix.

Impact

Guide headers are less cluttered and now present update history closer to GitHub-style page metadata.

Upgrade Notes

• No operator action is required.

Repositories: docs.furries.ph

Status: Released

What’s Changed

• Added first-created and last-updated dates to documentation page headers.
• Added article date metadata for search engines and link previews.
• Fixed sidebar numbering so it uses each page’s explicit order value when valid, while missing or malformed values fall back to readable section numbering instead of huge internal numbers.

Impact

Readers can tell how fresh a guide is before relying on it, and sidebar order labels now match valid page frontmatter while staying readable when a page needs its order frontmatter repaired.

Upgrade Notes

• No operator action is required.

Repositories: docs.furries.ph, partners.furries.ph, partners-api, rego.furries.ph, cms.furries.ph, fph-lan-ems, pawsport.furries.ph, report.furries.ph

Status: Released

What’s Changed

• Added Powered by TarsierDesk attribution to Furries PH-facing web shells, local LAN operations, CMS studio, docs, Pawsport tools, and the legacy report generator.
• Added TarsierDesk attribution to partner and account email paths, including Supabase auth templates and Worker-rendered mail shells.
• Kept the main public furries.ph site out of scope.

Impact

Users, attendees, partners, and operators now see Furries PH as the branded licensed deployment while the underlying EMS product attribution points to TarsierDesk.

Upgrade Notes

• No operator action is required.

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

Status: Released

What’s Changed

• Added a shared post-commit recorder that writes each Furries PH workspace commit into the docs update log as it happens.
• Added install support through pnpm hooks:install in docs.furries.ph so local hook configuration can be restored after clone or checkout.
• Updated repository agent guidance to make the per-commit update-log requirement explicit and point to the hook that records it.

Impact

Maintainers and agents now get an automatic public trace for each Furries PH workspace commit. This prevents operational updates from disappearing from the shared docs history.

Upgrade Notes

• Run pnpm hooks:install from docs.furries.ph if commits are not being checked locally.
• Use FPH_SKIP_UPDATE_LOG=1 only for mechanical commits that intentionally should not appear in public updates.

Commit Log

• rego.furries.ph 9358c443 - feat(analytics): measure safe control, transport and runtime activity This section is updated by local workspace hooks so each Furries PH workspace commit has a public trace.