Platform Updates

Repository: partners.furries.ph

Status: Preview; locally validated

What’s Changed

• The EPS Gantt and Calendar views now have a dedicated navigation and display area, separate from the Table, Board, Workload, Baselines, Hierarchy / WBS, and Scenarios workspace.

Impact

• Planning operators can focus on a visual timeline or calendar without it blending into the work-management views.

Validation

• Local browser verification confirmed the Gantt view renders as a standalone card.

Repository: partners.furries.ph

Status: Preview; locally validated

What’s Changed

• Reworked the EPS My Work summary into a responsive metric grid with compact, balanced work panels.
• Reduced empty-state whitespace while preserving clear separation between tasks, requirements, reviews, and meetings.

Impact

• Planning operators can scan their workload more quickly on desktop and narrow screens.

Validation

• Astro diagnostics and local browser visual verification passed.

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.

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.

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.

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.

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.

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.

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.

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.