Platform Updates

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

Status: Released

What’s Changed

• Validated stored dashboard session state before treating a returning browser as signed in.
• Made authenticated dashboard requests use the refreshed session immediately after token refresh.
• Added the release note entry for operators who may see session-expiry messages.

Impact

Partner admins and event operators should see fewer “Session expired” messages while signing in, returning to an older browser tab, or continuing after a token refresh.

Upgrade Notes

• If the login screen still reports an expired session, reload the page once so the browser clears old session state, then sign in again.

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

Status: Released

What’s Changed

• Added or refreshed certification coverage for social integrations, Event Management, Dashboard Reports, SPA shell behavior, and dashboard data loading.
• Improved public registration SPA support, route loading, and API request headers.
• Added fuzzy search, Platform API docs wording, EMS LAN wording, and the shared Updates page in the docs site.
• Recorded certification and documentation work in one public release stream for operational teams.

Impact

Partner admins, event leads, registration operators, support leads, and teams adopting social integrations, report workflows, Event Management, or registration flows have a clearer readiness record before relying on changed systems.

Upgrade Notes

• Review the relevant guide before operating a changed workflow.
• Pay close attention to social account linking, dashboard reports, event setup, public registration, and search-driven documentation lookup.

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

Status: Released

What’s Changed

• Improved SPA-style navigation, loader consistency, authentication reset usability, and contract checks.
• Refined Event Management typography and offline snapshot experience in the dashboard.
• Improved registration app route behavior and API body handling.

Impact

Attendees registering for events, event staff configuring registration, and dashboard operators moving through protected pages should see more consistent routing and live-operation behavior.

Upgrade Notes

• Before announcing registration or dashboard changes, confirm the correct event configuration is live.
• Walk through the affected attendee or operator path once.

Repositories: fph-lan-ems, partners-api, partners.furries.ph, rego.furries.ph, cms.furries.ph, furries-ph-cron

Status: Released

What’s Changed

• Expanded EMS LAN with Android wrapper support, packaging workflows, in-shell communications, calls UI, operator documentation, HR mirrors, inventory mirrors, POS mirrors, local API documentation, and certification tooling.
• Added LAN snapshot import/export, sync history, LAN release proxy support, offline HR and inventory snapshots, partner data-silo configuration, partner role helpers, and dashboard UI for audit workflows.
• Improved registration and CMS communications settings, email preferences, legal/profile sections, markdown rendering, notice polling, studio inputs, scoped publishing checks, auto-linking, and hashtag handling.
• Added expired-event archive workflows and scheduled publishing updates.

Impact

Event operators, registration staff, CMS editors, partner admins, and maintainers responsible for scheduled jobs have broader offline and operational coverage.

Upgrade Notes

• For offline operations, verify the exact snapshot, device, import, and reconciliation path before treating LAN data as trusted state.
• For CMS and scheduled jobs, confirm publishing scope and automation timing after deployment.

Repositories: cms.furries.ph, furries-ph-cron

Status: Released

What’s Changed

• Improved content publishing support for Furries PH CMS-managed pages.
• Refined media, metadata, and site-setting workflows used by publishing teams.
• Continued scheduled publishing and automation updates for time-sensitive content.

Impact

CMS editors and maintainers responsible for scheduled publishing have a clearer history of content tooling and automation changes without mixing in unrelated projects.

Upgrade Notes

• Check public pages, media previews, and scheduled publishing windows after changing CMS-managed content.
• Confirm automation timing before announcing or relying on a scheduled update.

Repositories: pawsport.furries.ph, report.furries.ph

Status: Released

What’s Changed

• Added Pawsport developer documentation, assets, keyring and state exports, an 18-digit format, renamed RSA files, and an early alpha milestone.
• Improved the reporting microsite with responsive UI updates, section clear buttons, development tools, and placeholder cleanup.

Impact

Developers adopting Pawsport formats and staff reviewing reporting microsite tools have more setup history and project context.

Upgrade Notes

• Use these entries as historical context before reviving either smaller system.
• Confirm the current docs and setup files before relying on early scaffold behavior.

AMS audit count-sheet import

Affected repository: partners.furries.ph and partners-api
Asset operators can now import an offline audit count sheet against one named open audit. AMS validates the observed rows first and commits only a clean batch, retaining the signed-in counter and unexpected physical observations without creating false assets. Counters working in blind audits continue to receive no expected quantity or location. Local verification passed the database, API, and 107-check production-static browser certificate. This is ready for the normal reviewed migration release; no hosted deployment is claimed here.

AMS scanner recovery

Affected repository: partners.furries.ph
Asset operators now receive a clear, non-destructive manual retry state when a scanner identity cannot be matched, connectivity is unavailable, the device cannot decode camera/NFC input, or multiple labels are visible. A label already flagged as a possible clone or tamper attempt is blocked from every operational handoff and directed to verification and escalation. Successful asset, shipment, container, seal, and location routing is otherwise unchanged. Local production-static browser verification passed 107 checks with 158 UI captures.

Repositories: partners.furries.ph, partners-api

Status: Validated locally

What’s Changed

• Added focused Event Planning certification commands for source contracts, keyboard tab lifecycle, operation launches, workflow, recovery, responsive, conflict, and individual API domains.
• Kept the complete local manifest as the release gate while making it possible to verify an affected area first.
• Added a browser check for desktop and mobile keyboard navigation, remount-safe tab listeners, browser errors, and narrow-screen overflow with screenshots.

Impact

EPS maintainers can receive targeted feedback without waiting for unrelated workflows. Event operators see no product-flow change.

Upgrade Notes

• Use the focused command matching the changed surface during development.
• Run the complete local manifest before a release decision.

Repositories: rego.furries.ph

Status: Validated locally

What’s Changed

• Aligned local Regosite sign-in, refresh, and protected attendee requests to the same local API target.
• Removed the local-development state where a completed sign-in could be shown briefly before a protected request treated the session as absent.

Impact

Attendees and developers using the local registration site should remain signed in after authentication instead of bouncing between signed-in and signed-out states.

Upgrade Notes

• Restart the local Regosite dev server if it was already running, then sign in again.

Repositories: partners.furries.ph, partners-api, fph-lan-ems, docs.furries.ph

Status: Local Implementation Complete - Release Gates Pending

What’s Changed

• Completed the local partner-scoped Linked Operations implementation for reviewed typed links, effective-dated shared parties/places/accounting dimensions and Finance policies with custom axes, EMS-to-FinManage annotation approval/reconciliation, EPS procurement, Finance goods-receipt intake, AssetManage-to-FinManage journal posting and receipts, logistics/maintenance/damage/agreement/consumable cost handoffs, reviewed event-asset substitutions, search, timelines, structured telemetry, measured double-entry reduction, and an actionable exception queue.
• Added the private /operations-linkage/metrics, /coverage, /procurement, /intakes, /finance/cost-handoffs, /finance/dimension-policies, /finance/ems-reconciliation, deployment-substitution reads/actions, and typed exception retry/fix preview route families alongside Finance postings/receipts, shared-identity maker-checker actions, and permission-trimmed search/timeline reads.
• Finalized the dashboard/Worker contract: procurement sends planningProjectId, objective, unitOfMeasure, and estimatedAmount; asset intake selects one Finance goodsReceiptLineId; cost handoff sends handoffType and amount; and the dashboard reads sibling item.procurement and item.financeRecord, item.intake.status, and item.handoff.* fields instead of obsolete generic response shapes.
• Converted every current cross-system mutation family to an atomic database command that commits mutable domain state and its immutable action receipt together. Shared party/place transitions use explicit maker-checker enforcement through partner_cross_system_transition_identity.
• Finalized the governed linkage and correction contracts: typed allowlisted endpoints retain immutable source/target snapshots, target disposition, owner versions/digests, and verification time; EPS reads live Finance procurement projections and can cancel unsettled work with readiness rollback; intake corrections name the immutable prior event and return the Finance goods-receipt header; AssetManage batch reversals retain original/replacement link lineage; and EMS annotation approval binds an independent reviewer, Finance policy version, current digest, and per-payment-account reconciliation.
• Added bounded typed queue retries with preview and structured healed/no-op receipts. Added agreement/rental and consumable-movement cost allocation without treating durable asset movement as consumable use.
• Bound each typed exception fix operation and sanitized target/action payload immutably at exception creation. Operators preview the bound action, then submit only the exception version, reason, and idempotency key; the exact owner-system mutation, immutable fixed event, exception resolution, and receipt commit together. A changed fix requires a new exception.
• Allowed Finance policies to require up to eight unique governed custom dimension-axis slugs. Each submitted axis key must match an active/effective same-partner dimension’s exact dimensionType, and the value remains its UUID rather than a copied free-text code.
• Added LinkedWorkPanel context to EMS event, EPS planning, FinManage, and AssetManage layouts so operators can see the named owner, relationship, lifecycle/version, and owner deep link without re-entering the record.
• Added measured generated records, unmatched lifecycle work, duplicate candidates, AssetManage batch acceptance, and deployment-return reconciliation with permission trimming and an explicit cutoff. Estimated fields not retyped use the current source proxy of 7 per procurement request, 12 per asset intake, and 5 per cost handoff; this is not observed manual effort or financial savings.
• Added optional EMS LAN event snapshot support for AssetManage durable-asset deployments, approved scan aliases, shared event places, and FinManage record references.
• Added offline receive, stage, issue, custody handoff, move, return, missing, and damage commands through the existing generic LAN-sync route. The signed envelope carries full place, custodian, condition, occurrence, device, evidence, quantity, version/digest, and correction lineage; exact lost-ack replay returns already_applied, stores one immutable local receipt, and does not repeat the AssetManage effect.
• Added an Admin and Workspace Event Assets surface with keyboard-wedge scanning, explicit container-member confirmation, shipment ETA, custody and condition readbacks, pending-command correction controls, conflict resolution, close reconciliation, and safe FinManage deep links and warnings.
• Hardened deployment exception approval: approve_exception requires a non-final exception in the same partner and deployment, enforces the same deployment item when one is named, rejects the exception maker’s self-approval, requires non-empty opaque evidence, and atomically records the approved exception, immutable exception_approved event, and deployment receipt. The deployment dialog now exposes Exception ID and Evidence artifact ID, while inactive tabs remain hidden.
• Added governed deployment substitution. A proposal names one different same-partner asset, model, or container and does not change the manifest; a different AssetManage administrator reviews the pending proposal with current proposal/deployment versions. Approval atomically applies the canonical replacement and receipt, while rejection preserves the original item.
• Kept durable assets separate from EMS inclusion/add-on inventory and kept finance references separate from EMS accounting facts to prevent double counting.

Impact

Operators can create or link procurement, intake, cost, journal, shared-identity, deployment, and exception work through one governed local contract while each system retains its authority. Embedded linked-work panels and measured-reduction indicators make reused records and unmatched work visible. Event logistics and asset operators can continue deployment scans during WAN loss, then reconcile them with AssetManage without changing EMS sellable or entitlement stock.

Upgrade Notes

• Existing snapshots without assetDeployment remain compatible. Deploy the reviewed additive migrations first, then the backward-compatible API, dashboard, and EMS LAN package; do not enable dependent clients before their server contracts are available.
• Local validation passed the dashboard disposable-database/source certificate, including final custom-axis identity/policy, procurement/cancellation, EMS reconciliation, correction-lineage, retry/fix, reviewed substitution, LAN, telemetry, first-party GL, and governed deployment-exception contracts; 558 API contracts plus TypeScript; the EMS LAN 65/65 TASK026 certificate and 26/26 cross-system regression; and 37/37 focused documentation checks after the zero-diagnostic static build, including rendered guide, links, search, sitemap, and diagrams.
• The database migrations, API routes, dashboard, and LAN package are not deployed by this update. Hosted multi-role authentication, real production/provider data, physical devices and venue LAN, an authorized canary, deployed rollback/restore, production reconciliation, and Event Operations, Asset, Finance, security, and independent operator sign-off remain release gates.

Repositories: partners-api, partners.furries.ph

Status: Validated locally

What’s Changed

• Removed the fresh-MFA requirement from the CMS launch handoff.
• Routed the dashboard’s CMS card through that same authenticated handoff instead of opening the CMS directly.
• Corrected CMS edge handling when Cloudflare does not provide the client-IP header used for the optional handoff binding.
• Native CMS handoffs now finish with an HTTP redirect after the access gate accepts them, avoiding a browser-dependent bootstrap step.
• Kept dashboard authentication, active-partner selection, exact CMS permissions, active-partner status, short-lived scoped credentials, audit logging, and handoff encryption in place.
• Kept MFA required for administrative CMS credential provisioning, rotation, and revocation.

Impact

Authorized dashboard users can open the CMS without completing a separate MFA challenge at launch. Users without dashboard authentication or their partner’s CMS permission remain unable to access it; when the client-IP signal is present, its binding remains enforced.

Upgrade Notes

• No user action is required. Sign in to the dashboard, select the relevant organization, and choose Content Management.