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 51-60 of 243
2026-08-1409:10

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-1409:10

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.
2026-08-1409:10

AMS Accountable Checkout Handoff

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 transfer a named checkout to a named receiving party and accountable recipient.
  • The service verifies that the recipient belongs to the selected party, preserves prior custody in immutable history, and resets acknowledgement for the receiver to record separately.

Impact

  • Custody handoffs now have a controlled, accountable record instead of relying on a note or an unverified user identifier.

Validation

  • The disposable database certificate passes 27 reviewed AMS migrations and proves valid party/recipient transfer plus mismatch rejection.
  • API/evidence/EPCIS/TypeScript certification passed 120 route contracts, 84 commands, and 131 OpenAPI operations.
  • Production-static Playwright passed 97 checks across ten routes with 141 modal/scanner captures; the handoff dialog was visually reviewed.

Next Step

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

AMS Accountable Checkout Recall

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 issue a controlled checkout recall from a named live checkout record.
  • A recall requires a reason, contact channel, future accountable return appointment, and confirmation; it moves custody to return pending without recording a false physical return.
  • The service retains the contact channel and appointment in immutable custody history and safely replays a retried command without duplicating the transition.

Impact

  • Teams can document and follow up an accountable return request while keeping physical quantity, condition, and receiving reconciliation in the separate return workflow.

Validation

  • The disposable database certificate passes 26 reviewed AMS migrations and verifies recall state transition, immutable evidence, and idempotent replay.
  • API/evidence/EPCIS/TypeScript certification passed 120 route contracts, 84 commands, and 131 OpenAPI operations.
  • Production-static Playwright passed 95 checks across ten routes with 138 modal/scanner captures; the recall dialog was visually reviewed.

Next Step

  • Apply the reviewed migration, then run real-stack role, recovery, and hosted readback certification.
2026-08-1409:10

AMS Review Receipt Privacy

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

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

What’s Changed

  • Review queues and applied-request receipts now keep internal workflow, policy, asset, and user identifiers out of the operator-facing dialog.
  • The receipt presents the readable request type, state, version, independent-review status, application time, and receipt type instead.
  • AMS route tables, exception rails, and pickers now use readable operational context or an explicit unresolved-state label instead of truncated internal identifiers when related data is unavailable.

Impact

  • Reviewers retain the information needed to verify a controlled decision without being asked to interpret or copy internal identifiers.

Validation

  • Production-static Playwright passed 93 checks across ten routes with 135 modal/scanner captures. The queue, applied-receipt, asset-detail, and accountable checkout-creation views are certified; the privacy views were visually reviewed.

Next Step

  • Complete real-stack role and hosted readback certification before Preview release sign-off.
2026-08-1409:10

AMS Unexpected Audit Observations

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

  • Count operators can now record a readable physical identifier for an item that is not in the register.
  • The service stores it as an explicit unexpected audit observation, without creating a false asset or attaching the count to a different asset.
  • Count retries use the same idempotency boundary, so a lost response does not create a duplicate unexpected observation.

Impact

  • Audit teams can preserve evidence of unregistered physical property while keeping the asset register and reconciliation trail accurate.

Validation

  • The disposable database certificate passes 25 reviewed AMS migrations, including unregistered-count identity, rejection of mixed registered/unregistered input, replay-safe persistence, and immutable independent-review evidence.
  • API/evidence/EPCIS/TypeScript certification passed 119 route contracts, 83 commands, and 130 OpenAPI operations.
  • Dashboard diagnostics passed with zero errors. Production-static Playwright passed 93 checks across ten routes with 135 modal/scanner captures, including the unexpected-observation count and maintenance outcome screens.

Next Step

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

AMS Independent Audit Variance Review

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

  • Audit teams now review one authoritative unresolved variance at a time instead of sending remediation fields through a cosmetic audit-close action.
  • Each review records root cause, remediation, accountable owner, due date, and review reason. The original counter cannot review their own result.
  • Audit posting is now separate and is rejected until every variance has an independent review.

Impact

  • Audit discrepancies retain their accountable remediation trail before an audit can be closed.

Validation

  • API/evidence/EPCIS/TypeScript certification passed 119 route contracts, 83 commands, and 130 OpenAPI operations.
  • Dashboard diagnostics passed with zero errors. Production-static Playwright passed 93 checks across ten routes with 135 modal/scanner captures, including reviewed audit-variance, unexpected-observation count, and maintenance-outcome screens.

Next Step

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

AMS Controlled Maintenance Outcomes

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

  • Completing a work order now persists actual parts cost, labor cost, downtime, test outcome, next service date, and required follow-up context.
  • A failed test keeps the asset in a maintenance hold and quarantine instead of returning it to service.
  • Actual parts and labor are associated with the work order as lifecycle-cost records; they remain operational data until the separate finance controls apply an accounting treatment.

Validation

  • The disposable database certificate proves idempotent outcome replay, cost persistence, and failed-test hold behavior across 24 AMS migrations.
  • API/evidence/EPCIS/TypeScript certification passed 119 route contracts, 83 commands, and 130 OpenAPI operations.
  • Production-static Playwright passed 93 checks across ten routes with 135 modal/scanner captures; the completion outcome screen was visually reviewed.

Next Step

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

EPS Recovery Feedback

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

Status: Preview; locally certified, with database and hosted release gates still open

What’s Changed

  • EPS now gives planning operators a clear unavailable message and a retry action if access is temporarily denied or the planning service cannot be reached.
  • EPS now also checks every planning surface at a 390px mobile width, including the primary Work Item dialog, for contained layouts and usable actions.
  • A Schedule Board move now restores its previous choice and offers a refresh if another operator changed that work item first.

Impact

  • Operators can recover in place without losing their selected planning project or guessing whether a page is still loading.

Validation

  • Playwright injects transient forbidden, service-unreachable, and optimistic-version conflict responses, verifies the appropriate recovery actions, then confirms successful recovery. It also verifies all ten EPS surfaces and the primary dialog at 390px without horizontal overflow. Desktop recovery/conflict and mobile planning states were visually reviewed.

Next Step

  • Complete the remaining real database, Worker, and hosted release evidence.
2026-08-1409:10

EPS Approved Workspace Consolidation

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

Status: Preview; locally certified, with database and hosted release gates still open

What’s Changed

  • The former EPS workspace URL now opens the approved Schedule workspace and keeps the selected planning project in context.
  • Older duplicate workspace forms were retired, so planning work uses the current controlled workflows only.

Impact

  • Planning teams retain their project scope when moving between EPS pages and no longer encounter an outdated action surface.

Validation

  • Playwright verifies the scoped redirect and persistent navigation; the resulting Schedule workspace was visually reviewed.

Next Step

  • Complete the remaining real database, Worker, and hosted release evidence.

All docs