Furries PH Docs
Dashboard

Updates

Platform Updates

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

First created Last updated

Showing release notes 1011-1020 of 1463
2026-08-1406:37

EPS Date and Time Pickers

Repository: partners.furries.ph

Status: Preview; locally validated

What’s Changed

  • EPS date, time, and date-time fields now use the shared calendar picker throughout portfolio editing and planning workspace operations.
  • Date-only fields retain a date-only UTC value, while schedules and meetings continue to capture both date and time.

Impact

  • Planning operators have one consistent, keyboard-friendly date and time selection experience across EPS.

Validation

  • Astro diagnostics and the EPS responsive browser certificate passed locally.
2026-08-1406:37

EPS UTC Planning Timezone

Repositories: partners.furries.ph, partners-api

Status: Preview; locally validated

What’s Changed

  • New and edited EPS event plans now use an explicit UTC-offset timezone selector, defaulting to UTC+08:00 (Manila).
  • Planning dates are saved as UTC timestamps, and the API accepts only supported UTC offsets for project timezones.
  • Corrected portfolio event-plan edits so planning start and handoff dates save successfully.

Impact

  • Planning schedules, target dates, and handoff timing use one explicit UTC offset across EPS.

Validation

  • Dashboard and Worker TypeScript diagnostics, plus EPS browser workflow checks, passed locally.
2026-08-1406:37

EPS Event-linked Plan Defaults

Repositories: partners.furries.ph, partners-api

Status: Preview; locally validated

What’s Changed

  • The first field in the EPS New event plan form now links an existing EMS event.
  • Selecting an event copies its name and description into the plan, and locks the plan code to that event’s EMS registration reference prefix.
  • The API now enforces the same rule, so an event-linked plan cannot be created with a different code or without an EMS reference prefix.

Impact

  • Planning teams begin from the canonical EMS event details and retain one consistent event prefix across EMS and EPS.

Validation

  • Dashboard and Worker TypeScript diagnostics, plus EPS browser workflow checks, passed locally.
2026-08-1406:37

EPS New Event Plan Dialog Placement

Repository: partners.furries.ph

Status: Preview; locally validated

What’s Changed

  • The New event plan dialog now opens centered in the available viewport.

Impact

  • Planning operators can review and complete the form without it appearing pinned to the screen corner.

Validation

  • Astro diagnostics and the EPS responsive browser certificate passed.
2026-08-1406:37

Preview Systems Limited to Local Development

Repository: partners.furries.ph

Status: Preview systems are intentionally unavailable after deployment

What’s Changed

  • Pawsports, Asset Management (AMS), Event Planning (EPS), and Finance now show an Under Construction page on deployed hosts.
  • The same routes remain available from localhost and 127.0.0.1 for local development and verification.

Impact

  • Partner teams cannot enter these unfinished systems from production or preview deployments. Use the established released dashboard areas for operational work.

Validation

  • Route gating is centralized in the dashboard runtime and covers direct navigation plus persistent-dashboard navigation.
2026-08-1406:37

AMS Blind Audit Counts

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

Status: Preview; locally certified, with real-stack and hosted release gates still open

What’s Changed

  • Audit leads can now open a governed blind count that keeps expected quantity and location out of the counter’s receipt and result list.
  • Independent reviewers retain the expected values needed to reconcile and approve a variance.

Impact

  • Physical observations can be recorded without being influenced by the expected inventory state.

Validation

  • API/evidence/EPCIS/TypeScript certification passed 123 route contracts, 86 commands, and 134 OpenAPI operations, including the blind-result redaction boundary.
  • Production-static Playwright passed 106 checks across ten routes with 153 modal/scanner captures; the blind-count audit dialog was visually reviewed.

Next Step

  • Run real-stack role and hosted readback certification before release.
2026-08-1406:37

AMS Checkout Damage and Loss Control

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

Status: Preview; locally certified, with migration deployment, real-stack, and hosted release gates still open

What’s Changed

  • Operators can now report a named checkout as damaged or lost without incorrectly recording a physical return.
  • The controlled form requires an accountable outcome, reason, available evidence, and a destructive confirmation.
  • Damage quarantines the asset. Loss preserves the custody exception and marks an asset lost only when the full asset quantity is represented by that loss.
  • Overdue escalation now selects a named checkout and records its contact, appointment, notification, and independent-review evidence without exposing a raw identifier field.

Impact

  • Partner teams have an accountable, replay-safe exception record for custody incidents while keeping return reconciliation separate.

Validation

  • The disposable database certificate passes 30 reviewed AMS migrations and proves damage/loss transitions, quarantine/loss handling, and replay safety.
  • API/evidence/EPCIS/TypeScript certification passed 123 route contracts, 86 commands, and 134 OpenAPI operations.
  • Production-static Playwright passed 105 checks across ten routes with 152 modal/scanner captures; the damage/loss and overdue-escalation dialogs were visually reviewed.

Next Step

  • Apply the reviewed migrations, then run real-stack role, recovery, and hosted readback certification.
2026-08-1406:37

AMS Pinned Checkout Policy Eligibility

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

Status: Preview; locally certified, with migration deployment, real-stack, and hosted release gates still open

What’s Changed

  • New checkouts are now pinned to the effective approved custody-policy revision.
  • Renewals show the selected checkout’s policy version, maximum duration, calculated maximum due date, and renewal usage.
  • The database rejects a due date or renewal count beyond the pinned policy, even after a newer policy is approved for later checkouts.

Impact

  • Operators see the applicable rule before requesting a renewal, while historical custody remains governed by the policy that applied when it was issued.

Validation

  • The disposable database certificate passes 29 reviewed AMS migrations and proves policy pinning, duration rejection, and renewal-limit rejection.
  • API/evidence/EPCIS/TypeScript certification passed 122 route contracts, 85 commands, and 133 OpenAPI operations.
  • Production-static Playwright passed 102 checks across ten routes with 148 modal/scanner captures; the renewal-policy dialog was visually reviewed.

Next Step

  • Apply the reviewed migrations, then run real-stack role, recovery, and hosted readback certification.
2026-08-1406:37

AMS Checkout Receipt Acknowledgement

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

Status: Preview; locally certified, with migration deployment, real-stack, and hosted release gates still open

What’s Changed

  • A named Acknowledge receipt action is available for a checkout awaiting handoff acknowledgement.
  • The recipient or authorized custody operator confirms verified physical receipt; the service activates the checkout and records immutable acknowledgement history.

Impact

  • A transferred checkout no longer relies on a hidden API path or an informal note before entering active custody.

Validation

  • The existing authoritative checkout-acknowledgement endpoint is covered by the production-static browser certificate: 101 checks across ten routes and 147 modal/scanner captures.
  • The acknowledgement dialog was visually reviewed and keeps internal identifiers out of the operator-facing control.

Next Step

  • Apply the reviewed migrations, then run real-stack role, recovery, and hosted readback certification.
2026-08-1406:37

AMS Atomic Bulk Checkout Return

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

Status: Preview; locally certified, with migration deployment, real-stack, and hosted release gates still open

What’s Changed

  • Asset operators can now return one to 100 named eligible checkouts together when they share a receiving location and assessed condition.
  • The return is all-or-nothing: the service locks and validates the complete selection before restoring availability and recording immutable evidence for every checkout.
  • A safe retry returns the original completed result. Partial quantities or returns that need different conditions or locations continue through the individual return workflow.

Impact

  • Coordinated physical handbacks are faster without allowing a partial batch, duplicate custody return, or a free-form identifier entry.

Validation

  • The disposable database certificate passes 28 reviewed AMS migrations and proves atomic completion, rejected partial selection, and replay safety.
  • API/evidence/EPCIS/TypeScript certification passed 121 route contracts, 85 commands, and 132 OpenAPI operations.
  • Production-static Playwright passed 99 checks across ten routes with 144 modal/scanner captures; the bulk-return dialog was visually reviewed.

Next Step

  • Apply the reviewed migrations, then run real-stack role, recovery, and hosted readback certification.

All docs