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 201-210 of 243
2026-07-0909:10

Report System Docs Rewrite

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

Status: Released

What’s Changed

  • Rewrote the full Report System documentation set to match the Event Management documentation pattern.
  • Added a Report System route map covering every active Reports dashboard route and required query parameter.
  • Expanded every Report surface page with route-specific input and control explanations, state behavior, workflow diagrams, related pages, runbooks, and common mistakes.
  • Added source-backed workflow diagrams for report intake, review, local watchlist/ban handling, network ban recommendations, appeals, person profiles, records, role access, and certification.

Impact

Partner safety teams and FPH admins now have a complete operator reference for Report System routes, fields, permissions, network decisions, appeals, and identity-profile maintenance.

Upgrade Notes

  • No runtime change. Use the updated Report System docs when filing, reviewing, escalating, or auditing reports.
  • Current validation evidence: pnpm check, pnpm build, and git diff --check -- src/pages/reports src/lib/docs-nav.ts src/content/updates.md.
2026-07-0909:10

Event Snapshot Free-Plan Export Fix

Repositories: partners-api, docs.furries.ph

Status: Released

What’s Changed

  • Changed the Event Management LAN snapshot download path so attendee and Dealers Den detail records are gathered in batched snapshot queries instead of making one Worker subrequest per exported record.
  • Reduced redundant inventory-definition reads during snapshot export so the same event item/image lookup is reused for POS transaction attachment.
  • Kept the dashboard download action as one snapshot request while lowering the Worker-side Supabase subrequest count for Cloudflare Free plan deployments.

Impact

Event operators downloading LAN snapshots for larger events should no longer hit the Cloudflare Worker “Too many subrequests by single Worker invocation” failure during export.

Upgrade Notes

  • Deploy partners-api before using LAN snapshot downloads for large events on a Cloudflare Free plan.
  • Current validation evidence: npm run type-check, npm run event-shop:certify, and git diff --check -- src/routes/checkIn.ts src/routes/inventory.ts.
2026-07-0909:10

EMS LAN OTD Shop Order Operations

Repositories: fph-lan-ems, docs.furries.ph, tarsierdesk.com

Status: Released

What’s Changed

  • Added LAN EMS Shop Orders and Shop Order Claim coverage for on-the-day merch pickup operations.
  • Added offline snapshot import/export support for shop orders, order items, claim history, buyer-visible updates, and structured local reconciliation changes.
  • Added local Shop Orders review and Shop Order Claim surfaces with QR scan, pasted QR payload normalization, order reference lookup, buyer search, release, exception, and reversal flows.
  • Added local SQLite mirrors for shop orders, order items, claims, status updates, and local change provenance so venue-side actions survive offline operation and can be exported for dashboard reconciliation.
  • Integrated shop order demand into local inventory tracking and analytics without double-counting POS sales, inclusion claims, or registration add-ons.
  • Blocked unsafe claim paths for unpaid, cancelled/rejected, already released, delivery/courier-only, malformed, and wrong-event shop order QR payloads.
  • Closed the LAN OTD task index so current LAN operations tasks now show no in-progress or pending work, with TASK001, TASK003, TASK014, and TASK017 marked complete.

Impact

Venue teams can run merch pickup/release inside EMS LAN using imported shop snapshots, local QR/manual lookup, offline release recording, exception handling, and exportable reconciliation evidence.

Upgrade Notes

  • Export a fresh dashboard offline snapshot before event-day operations when shop pickup is enabled.
  • After the event, import the LAN reconciliation output before treating dashboard shop claim state as final.
  • Current validation evidence: pnpm launcher:self-test, pnpm check, pnpm task017:certify, pnpm build, git diff --check, and TASK014 strict PASS at reports/task014/20260620195412/full-surface-certification-20260620195412.md.
2026-07-0909:10

Event Shop Schema Foundation

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

Status: Ready for deployment

What’s Changed

  • Added the first partner dashboard schema foundation for event merch shops, including Shop Config, source-linked and manual listings, couriers and delivery rates, persistent carts, rego-linked shop orders, order status history, claim/release audit records, shop payments, and inventory reservations.
  • Added per-coupon and per-affiliate shop applicability flags that default off so existing registration behavior is preserved until partners opt programs into shop orders.
  • Added an initial event shop certification source gate for the migration and typed dashboard/regosite worker-client wrappers.
  • Mounted initial partners-api event shop dashboard endpoints for Shop Config, listings, categories, couriers/rates, Orders Dashboard analytics, Order Management status updates, buyer-visible updates, and claim/release workflows.
  • Added initial partners-api authenticated cart and checkout endpoints for persistent cart state, cart validation, profile-prefilled order snapshots, delivery-rate selection, coupon/affiliate shop applicability, platform-fee snapshots, same-event rego linkage, checkout-time payment proof/reference capture, and dashboard payment review.
  • Added public shop listing, buyer order lookup, and post-checkout buyer payment submission endpoints for the future regosite shop experience.
  • Added the first Event Management dashboard pages for Shop Config, Shop Orders Dashboard, Shop Order Management, and Shop Order Claim/Release, mounted in the event sidebar and wired to the event shop worker client.
  • Added the first rego.furries.ph event shop route at /:slug/shop with listing browsing, category filters, authenticated persistent cart actions, checkout validation totals, delivery/courier selection, coupon and affiliate fields, payment account selection, proof upload, purchaser detail prefill from profile/session where possible, and checkout receipt state.
  • Added buyer-facing event shop order history in rego.furries.ph transactions, including a shop order list and detail page with items, totals, fulfillment/delivery context, linked-rego marker, and buyer-visible ecommerce-style status updates.
  • Added per-coupon and per-affiliate dashboard settings to opt specific programs into event shop orders, with API persistence through finance programs and shop checkout validation enforcing only shop-enabled coupons and affiliate codes.
  • Added shop order ingestion to inventory tracking, inventory analytics, and finance analytics so source-linked shop order items affect stock demand/remaining counts while shop order gross revenue, platform fees, processing fees, provider totals, payment-account balances, and source counts are included in finance reports.
  • Added stronger persistent cart stale-state handling with item price snapshots, price-change checks, source-linked stock sellout/over-demand checks, delivery/payment blockers, and regosite checkout disabling when server cart validation reports unresolved blockers.
  • Added Shop Config source selection for registration add-ons and inclusions, backed by an API source-items endpoint, so partners can opt those items into the shop from Shop Config without adding shop controls to Rego Config.
  • Added Shop Config category and courier-rate controls for creating categories, assigning categories to listings at creation, adding couriers, and adding flat, administrative-region, or Philippines Luzon/Visayas/Mindanao delivery rates.
  • Added Shop Config listing lifecycle controls for editing listing name/price, activating/deactivating products, and deleting listings without affecting existing order item snapshots.
  • Added richer Shop Order Management details with item rows, buyer-visible update timeline, claim history, and controls for adding ecommerce-style buyer updates.
  • Added Shop Order Management filters for payment, order, and fulfillment statuses plus CSV export of the current filtered order result set.
  • Added settlement dashboard accounting for shop orders so shop order source counts appear in remittance summaries and shop platform fees are clearly included in event settlement balances.
  • Added buyer notification hooks for shop orders so checkout creation, payment submission, payment confirmation/rejection, buyer-visible updates, and claim/release can publish attendee notices and best-effort email.
  • Added Orders Dashboard logistics analytics for shop pickup, delivery, shipped, exception, and delivery-region queues, plus top item/category sales and courier delivery revenue.
  • Added richer shop Order Management operations for internal notes and status changes that sync fulfillment status plus ready/fulfilled/cancelled timestamps.
  • Added QR-aware shop order claim lookup with camera scanning where supported, pasted QR payload normalization, and buyer email/name search.
  • Added settlement history CSV export so shop-inclusive platform-fee remittance records can be reviewed outside the dashboard.
  • Added advanced Shop Config listing fields for quantity limits, rego requirement overrides, fulfillment mode, manual merch stock behavior, image URLs, and purchase windows.
  • Added partner/operator documentation pages and route/checklist/data-record references for Shop Config, Shop Orders Dashboard, Shop Orders, and Shop Order Claim.
  • Added the attendee-facing Use an Event Shop guide for public browsing, persistent carts, profile-prefilled checkout, no-rego/reg-required behavior, delivery/courier selection, payment submission, pickup release, and buyer order status timelines.
  • Updated Shop Config, Attendee Coupons, and Affiliates Tracking docs to make shop checkout configuration, fee review, and per-code shop applicability explicit.

Impact

This completes the event shop deployment package across schema, API, partner dashboard, regosite checkout, buyer order history, documentation, shop-specific coupon/affiliate controls, finance reporting, settlement accounting, inventory demand, notifications, and LAN pickup handoff.

Upgrade Notes

  • Deploy the API, dashboard, regosite, and docs changes together so checkout, order management, finance, inventory, and docs stay contract-compatible.
  • Before enabling shop for a live event, confirm payment accounts, delivery rates, pickup staff, coupon/affiliate shop applicability, settlement review, and LAN snapshot handoff.
  • Current validation evidence: pnpm event-shop:certify, pnpm event-shop:certify:production, pnpm exec astro check, pnpm build, pnpm supabase:publish:dry-run, npm run type-check, npm run event-shop:certify, and npm run event-shop:certify:production.
2026-07-0909:10

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.
2026-07-0909:10

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:generate available 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.
2026-07-0909:10

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.md to 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.md when dependencies or bundled vendor assets change.
2026-07-0909:10

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.
2026-07-0909:10

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.
2026-07-0809:10

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 .local discovery/manual fallback while separating online and LAN remembered origins and routes.
  • Added native probe/trust-policy separation and the pnpm task016:certify audit 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.ph so the well-known native contract is available to APK online mode.
  • Rebuild/sync the Android project before packaging.

All docs