Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Attendee Rego Gifting
Repositories: partners-api, partners.furries.ph, rego.furries.ph, docs.furries.ph
Status: Ready for deployment
What’s Changed
- Added attendee rego gift records, API routes, dashboard review, and attendee gift purchase/redeem surfaces.
- Added Rego Config controls for disabled-by-default gifting and gift capacity behavior.
- Kept gift purchase on the same paged tier, add-on, payment, proof, and review pattern as regular rego, including platform fees and configured payment-fee rules.
- Gated receiver redemption on gift payment confirmation using the event’s existing rego confirmation behavior.
- Added receiver inbox and email notifications, optional gifter markdown-ext messages, and receiver-facing anonymity while preserving internal gifter audit records.
- Documented gift review, receiver redemption, and API route expectations.
- Updated Rego Config, Attendee Coupons, and Affiliates Tracking docs to make disabled-by-default gifting, gift capacity handling, receiver-owned form details, payment-confirmed redemption, and per-code gift applicability explicit.
Impact
Partners can opt into username-only rego gifting. Receivers redeem through the normal rego flow with their own details and forms, without paying again after gift payment is confirmed. The feature package is ready for deployment behind the disabled-by-default Rego Config switch.
Upgrade Notes
- Run the rego gift migration before enabling gifting for any event.
- Deploy API, dashboard, regosite, and docs changes together so gift quote, payment review, receiver redemption, notifications, and docs stay contract-compatible.
- Before enabling gifting for a live event, verify gift create, payment review, receiver redemption, duplicate blocking, capacity behavior, coupon/affiliate gift applicability, receiver-form collection, and anonymity copy.
Build-Stable Page History Manifest
Repositories: docs.furries.ph
Status: Released
What’s Changed
- Added a committed page-history manifest generated from full local Git history so Cloudflare Pages shallow clones no longer collapse first-created dates to the deploy commit.
- Updated page history lookup to prefer the manifest before falling back to Git or filesystem timestamps.
- Added automatic history generation to the build scripts, including an unshallow fetch step when Cloudflare Pages checks out a shallow repository.
- Kept
pnpm history:generateavailable for refreshing the manifest directly.
Impact
Documentation pages keep their original created dates on hosted builds even when the deployment checkout starts with shallow Git history.
Upgrade Notes
- Deploy normally. The build command regenerates page history before Astro renders the site.
Workspace Third-Party License Notices
Repositories: cms.furries.ph, docs.furries.ph, fph-lan-ems, furries-ph-cron, furries.ph, partners-api, partners.furries.ph, pawsport.furries.ph, rego.furries.ph, report.furries.ph
Status: Released
What’s Changed
- Added
THIRD_PARTY_NOTICES.mdto Furries PH-related local repositories with dependency and bundled-library license notices that require copyright, permission, attribution, or notice preservation. - Added third-party notice pages to the partner dashboard legal area and the regosite legal area, with buttons that open modal license text for each listed notice.
- Added a workspace-wide Third-Party License Notices reference page to the docs site, with modal license text for each listed repository notice.
Impact
Maintainers now have one repo-level notice file per Furries PH-related project and one docs-site inventory for release review. Public legal surfaces expose required notices and the license text needed for review.
Upgrade Notes
- No runtime action required. Review
THIRD_PARTY_NOTICES.mdwhen dependencies or bundled vendor assets change.
Stable Docs Page Dates on Static Builds
Repositories: docs.furries.ph
Status: Released
What’s Changed
- Changed docs page SEO date metadata to emit date-only values so Cloudflare Pages builds do not expose UTC-midnight timestamps as shifted calendar dates.
- Changed page history updates to prefer Git history for both first-created and last-updated values instead of filesystem modified times that can be reset during static deployment.
- Kept visible history timestamps available for readers while using Manila-time formatting for build-stable server-rendered labels.
Impact
Docs pages should keep their intended created and updated dates after Cloudflare Pages deploys instead of showing the deploy filesystem date or a timezone-shifted calendar day.
Upgrade Notes
- No operator action required. Redeploy the docs site so generated HTML uses the corrected date metadata.
Platform API Docs Naming
Repositories: docs.furries.ph
Status: Released
What’s Changed
- Renamed the platform API documentation area to Platform API Docs across navigation, breadcrumbs, SEO metadata, Open Graph labels, docs content, task references, and release notes.
- Cleaned generated Platform API docs wording so guide prose refers to Platform API work instead of treating the docs label as the operational object.
- Renamed the EMS LAN and Platform API docs rewrite task file so future task references use the current section name.
Impact
Readers now see one consistent name for the Platform API documentation section across the docs site.
Upgrade Notes
- No runtime change. Use Platform API Docs when referring to the platform API documentation area.
Dual-Mode Furries PH Android Dashboard
Repositories: fph-lan-ems, partners.furries.ph, docs.furries.ph
Status: Released
What’s Changed
- Extended the Android app startup shell with Online Dashboard and Local EMS LAN modes.
- Added the hosted dashboard native compatibility contract at
/.well-known/fph-dashboard-native.json. - Kept LAN
.localdiscovery/manual fallback while separating online and LAN remembered origins and routes. - Added native probe/trust-policy separation and the
pnpm task016:certifyaudit gate.
Impact
Android users can choose the hosted dashboard or onsite LAN at startup. Online mode is HTTPS-only; LAN mode retains existing event-day compatibility.
Upgrade Notes
- Deploy
partners.furries.phso the well-known native contract is available to APK online mode. - Rebuild/sync the Android project before packaging.
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.
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.
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.
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-subsidiesfrom 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-resourcesfor the corresponding active surfaces.