Platform Updates

Repositories: partners.furries.ph-v2

Status: Local implementation; not deployed.

What’s Changed

• Copied RegoSite V2’s auth components and adapted its signed-out header, page spacing, and footer for Partners. Recovery and invitation forms reuse the same shell; Partners account policy and API contracts are unchanged.

Impact

• Operators get consistent method selection, password fields, and feedback across desktop and mobile. The source parity check now compares the full auth component, not a small set of styling markers.

Upgrade Notes

• No API change or account migration. Local source/type checks and desktop/ mobile browser checks cover method switching, password visibility, and simulated OTP feedback. These checks do not claim live credential issuance.

Repositories: partners.furries.ph-v2

Status: Local implementation and browser verification; deployment pending.

What’s Changed

• Attendee payment status changes now require an explicit save from a shared desktop/mobile editor. Failed saves retain the edit and show its error.
• HR application windows display the operator’s local time consistently. Initial loading errors now offer Retry.

Impact

Event operators can review payment changes before applying them and edit HR windows without shifting their time zone.

Upgrade Notes

No API or database changes. Local browser checks covered staged selection, simulated save failure, mobile access, and HR failure/retry. These notes do not indicate a production release.

Repositories: partners.furries.ph-v2

Status: Local implementation verified; no Partners API or production deployment changed

What’s Changed

• Finance Settings now supports the existing governed add/edit cash-account workflow, including ledger linkage, restricted-fund status, and the current account-control fields.
• The Finance service remains authoritative for audit history and values that become immutable after financial posting.

Validation Evidence

• Authenticated browser checks, type checking, route-execution coverage, and a production build passed locally without saving a cash-account record.

Repositories: partners.furries.ph-v2

Status: Local implementation verified; no Partners API or production deployment changed

What’s Changed

• Finance operators can parse bounded CSV/JSON statement files and submit the existing server-side validation preview from V2.
• A separate review-and-commit form accepts only validated batches, requires period balances and an explicit evidence-review attestation.
• Parsing is not posting: validation, maker-checker eligibility, and immutable reconciliation history remain owned by the existing Finance service.

Validation Evidence

• Authenticated browser checks, type checking, route-execution coverage, and a production build passed locally without creating a statement or reconciliation.

Repositories: partners.furries.ph-v2

Status: Local implementation verified; no Partners API or production deployment changed

What’s Changed

• The safety-report form now shows a live completion count and readiness percentage while an operator prepares a report.
• The signal uses only the fields already being edited in the browser. It does not save a draft, submit a report, upload evidence, or change any safety record.

Who May Notice

• Partners and FPH staff preparing a safety report.

What To Do Next

• Use the readiness meter near the submit action to identify remaining report details before opening the existing confirmation step.

Validation Evidence

• Authenticated browser checks, clean reload without console errors, type checking, and route-execution checks passed locally.

Repositories: partners.furries.ph-v2

Status: Local implementation verified; no Partners API or production deployment changed

What’s Changed

• Event operators can now inspect both the Dealers Den application and the post-approval registration journey using the configuration currently being edited, before saving it.
• The previews reflect the current package, registration tier, optional add-on, requirements, and custom-question settings. They are deliberately safe: they cannot submit an application, create a registration, reserve capacity, take payment, or grant an entitlement.

Who May Notice

• Partners configuring Dealers Den for an event.

What To Do Next

• Use the new Attendee form preview card in Dealers Den Config to check both journeys before publishing the underlying configuration.

Validation Evidence

• Authenticated desktop and mobile browser checks passed with a clean reload and no console errors. Type and route-execution checks passed locally.

Repositories: partners.furries.ph-v2

Status: Local implementation in progress; no Partners API or production deployment changed

What’s Changed

• V2’s owned and loaned Asset Management registers now include the existing governed CSV import workflow from the current Partners dashboard.
• Operators select a CSV, receive a Worker-authorized row-by-row validation preview, and must explicitly confirm a clean batch before it can create any asset records.
• Selected assets can now be submitted for a governed bulk move or lifecycle review. The request records its reason and requires a separate authorized reviewer before any represented asset operation can be applied.
• Asset Settings now includes the same independent review queue for pending asset workflow and policy requests. Operators cannot review their own submissions, and decisions remain version-checked by the existing service.
• Operators can now create governed asset categories, models, locations, external owners, and custody agreements from V2 Asset Settings. Relationship choices remain constrained to the active partner scope.
• Asset Settings now also has the current dashboard’s typed Identity profile policy form. Submitted policies stay pending until a different authorized reviewer approves them; they are not made active by the authoring step.
• The same Settings area now includes Checkout & custody, Depreciation & capitalization, and Permissions & approvals forms. All policy changes remain versioned and pending until independent authorization.
• Checkout operators can now select multiple open checkouts for the same controlled return location and condition. The service applies the return as one atomic action after a physical-verification confirmation.
• Overdue checkouts can now be escalated with documented contact details and a requested escalation level. The request remains governed and does not alter custody on its own.
• Hub Quality operators can now record a governed asset quality hold with quarantine, inspection, risk, disposition, and optional private evidence. Availability and release remain controlled by the existing service.
• Transit operators can now document an exception resolution for independent review. The service preserves the exception timeline and governs any closure.
• Maintenance operators can now submit a governed warranty or supplier claim against a named asset and vendor, with optional private evidence. Financial and maintenance follow-up remain controlled by the existing service.
• Maintenance operators can now submit inspection or calibration evidence with the applicable standard, measured readings, conditions, next-due date, and optional private evidence. The resulting review cannot directly change an asset’s compliance or maintenance state.
• Audit operators can now locally parse an observed-count CSV for a named open audit, receive Worker validation, and separately commit only a clean batch. Expected quantities remain excluded from the count-sheet input.
• Audit operators can now record a single observed count, independently document variance remediation, and post a fully reviewed audit. The service keeps expected quantities, review eligibility, and final posting controls.
• Transit operators can now dispatch a prepared shipment and record its named carrier handoff. Shipment readiness, carrier custody, and immutable history remain controlled by the existing service.
• Transit operators can now reconcile inbound receipts or report a transit exception with containment, accountable ownership, and optional private evidence. The existing service preserves the shipment timeline.
• Maintenance operators can now pause in-progress work or reassign eligible work orders with a documented reason. The existing service preserves the accountable maintenance timeline.
• Maintenance operators can now record verified work completion with actual cost, downtime, functional testing, follow-up, and optional private evidence. The existing service remains authoritative for the resulting work state.
• Owned and loaned Asset Management registers now offer the current dashboard’s quantity movement and consumption operation. Operators select named scoped stock, provide a reason, and select a destination for moves; the existing service prevents negative availability and preserves the stock history.
• The same registers now include controlled identity-carrier issuance and lifecycle actions. Existing carriers preserve their verification, replacement, lock, clone-review, revocation, and destruction history in the service.
• V2’s Logistics Hub now supports controlled bulk task allocation. Operators select named tasks, an eligible operator, a strategy, and a reason; the existing service applies the allocation atomically and keeps its history.
• V2 Asset Management now separates owned-asset disposition from return of loaned property. Both are governed requests with their respective receipts, evidence, and approval boundaries; neither directly changes the register.
• Transit operators can now create a controlled return-to-sender shipment for eligible received or exception records. The existing service validates the sealed container and physical verification, then keeps the reverse history.
• Transit operators can also repack verified contents between scanned containers or unpack a scanned received container to a controlled location. Existing service-side eligibility and immutable movement history remain in use.
• Asset Register rows now offer a read-only detail view before operators choose a separate controlled action. Identity, custody, availability, and carrier information continue to come from the existing scoped service projection.
• Asset Settings now supports detailed custody-agreement authoring, including owner, purpose, effective dates, permitted use, liability, maintenance, and return terms. Optional signed evidence stays private through the service.
• Asset Finance now has a separate independent approval queue for pending asset-finance review cases. Decisions remain version-checked and require a different reviewer; this local UI work does not change the service API.
• The change reuses the existing Worker validation and commit contracts. No API endpoint, database schema, or production configuration changed.

Impact

• Teams evaluating V2 locally can now review the same import safety boundary and selected-asset maker-checker workflow available in the current dashboard. Invalid imports remain uncommitted and bulk requests do not alter assets until independent review.

Upgrade Notes

• Keep using the current production dashboard until the remaining V2 authenticated record-state workflows are certified. No migration is needed.

Repositories: partners.furries.ph-v2

Status: Local implementation in progress; no Partners API or production deployment changed

What’s Changed

• V2 now has governed, reusable implementations for Finance disbursement settlement, Asset checkout issuance, Pawsport sticker issuance, and organization-owned Discord/Telegram account and destination linking.
• The same V2 pass adds Pawsport claimable issuance, checkout-policy renewal with its Worker eligibility preview, and Planning’s two-step reschedule preview/apply flow for dependency-aware date changes.
• Sensitive actions retain the existing Worker-owned capability checks, work locks, confirmation, version handling, idempotency, restricted evidence boundary, feedback, and authoritative reload behavior.
• The organization integration surface now covers the existing OAuth popup, Telegram mobile polling fallback, Telegram group deep-link polling, install links, and controlled unlink/remove actions rather than a partial disconnect-only control.
• All V2 platform-administration routes now use an explicit FPH-administrator UI guard; the membership register supports confirmed access removal through the existing Worker contract.
• Asset checkout recipients can now record the existing pending-handoff acknowledgement with explicit physical-custody confirmation; the Worker still authorizes the named receiver or an eligible custody operator.
• Event operators can now make the existing granular refund decisions in V2, including bounded partial tier/add-on amounts, registration cancellation, configured fee preview, payout reference, attendee-visible decline reason, and authoritative reload. Refund-proof upload remains unavailable until the shared governed-upload surface is ready.
• The current V2 batch adds reusable local-ban scope editing/removal, source-record-bound Asset checkout custody transfer, and Planning meeting note/minutes-with-actions authoring. Each uses the existing Worker contract, scoped selectors, confirmations where the original workflow requires them, feedback, and authoritative refreshes.
• V2 also now supports authorized Pawsport staff-note edits and checkout-bound Asset returns with named receiving records and private custody-evidence handling. Planning meeting note/minutes actions are now explicitly tied to the selected meeting record.
• Event operators can now author the full V2 attendee-feedback structure: ordered categories, sections, all 13 API-backed feedback question schemas, validation, choices, answer-routing rules, and versioned draft/publish controls. A native preview lets teams walk the attendee journey before publishing, while a version conflict now requires an explicit reload instead of silently overwriting another operator’s change.
• EMS Feedback Triage and Upgrade Review have completed their V1 contract audit. Feedback notes no longer carry between attendees, while upgrade review accepts the established event payload forms and correctly reports when upgrades are disabled.
• Gift and waitlist review flows now preserve their V1 lifecycle eligibility and authoritative refresh behavior. Refund approval also supports the existing optional proof-image workflow without displaying upstream media locations.
• EMS decision queues now retain the source transfer-review contract, clear stale volunteer-review errors on retry, and group rejected activity submissions by form with visible counts.
• Volunteer application review now includes complete applicant and answer details, bulk outcomes, direct messaging, and recovery controls. Gift payment review adds source-equivalent sorting, counts, pagination, decisions, and payment facts; waitlist parity is certified with guarded refresh and source-backed offer controls.
• Live EMS operations now include an interactive reusable staff-roster timeline (create, move, resize, reorder, location/person modes, duplication, and saved preferences) plus concurrent check-in/claim lanes that refresh without interrupting active desk work.
• Local V2 protected-route testing is working again through the existing development Worker session. Account Security now preserves setup return and MFA/passkey safeguards, while event management adds source-backed image editing, complete event facts, and live directory counts.
• EMS configuration now validates full coupon programs before save and offers the complete reusable volunteer application-form builder, including prior-event import and V1 question types.
• HR settings can now safely import reusable policy defaults and shift locations from an earlier event in the same partner scope, without replacing current roster publication or layout preferences.
• FPH administrators can now use V2’s guarded partner lifecycle surfaces to create or edit partners, manage Pawsport settings, confirm CMS credential lifecycle actions, and update scoped memberships. Every change continues through the existing server-authorized contract; raw CMS credentials are never shown.
• The public V2 design canvas no longer attempts a local dashboard sign-in while loading. Protected dashboard routes keep their existing local-only testing path.
• The editable Partners V2 design canvas continues to verify the full source inventory: 149 routes, 43 reusable components, 93 form-producing sources, and 92 named overlays.
• V2 inventory tracking now has the source-equivalent reusable QR, Code 128, NFC text/write, and A5/A4/A3 named tag-sheet exports. The public design canvas mounts that real local-only component with safe fixture stock, so operators can inspect every identifier control before using an authenticated event. Web NFC remains device/browser dependent; the downloadable NFC entry remains available as the fallback.
• The reusable V2 direct-attendee composer now sequence-guards protected email and SMS previews as well as aborting replaced requests. The canvas includes an editable single-recipient Email + inbox/SMS preview with the verified-device, SIM, country, inbox, and delivery-receipt states; it cannot deliver a message from the public canvas.
• V2 campaign email previews now show the same attendee inbox mirror as the existing dashboard. Markdown is sanitized before it renders, replaced previews cannot overwrite newer content, and the canvas includes the safe editable preview and recovery states. Delivery is still only performed through the existing protected Worker contract.
• V2 SMS campaigns now expose the existing safe web-side SIM country verification, country/exclusion readiness, per-recipient campaign review, and bounded failed-message retry controls. Android permissions, device registration, job leasing, and actual delivery remain in the native bridge and are not performed by the web dashboard.
• V2 survey operations now include owner-scoped draft creation, access selection, a reusable 23-type multi-page survey editor, protected save/publish and lifecycle actions, rewards, analysis, response-health summaries, and explicit publish-conflict recovery. The public design canvas includes the same editor as a safe local-only preview; it never creates surveys or responses.
• The V2 attendee-registration roster now keeps the complete existing operational record visible: gifted/staff markers, profile and fursona cards, ref-sheet access, uploaded form-image links, distinct address fields, and compact payment and attendee context across desktop and mobile.
• V2 saved-prefill audit now shows explicit lifecycle state and full event context, and consistently treats revocation as a destructive, audit-retaining action. Its local design-canvas preview supports the same filter and confirmation states without touching live records.
• V2 refund review now preserves the searchable lifecycle queue, request and payout facts, disabled-refunds state, saved-decision details, live refresh, and a complete fee-aware partial-approval outcome preview. The canvas includes a safe editable payout-calculation preview.
• V2 human-resources settings now include native event-policy import and reusable shift-location administration with local draft, activation, removal, and authoritative save/revert behavior. Department and membership authoring remains an explicitly tracked follow-up.
• HR settings now also provide native department policy drafts: event teams can add, edit, activate, remove, and set subsidy overrides for departments through the established saved HR snapshot. Member assignment remains separately tracked.

What To Do

• Keep using the current production dashboard until the remaining projection-dependent and authenticated mutation paths are certified. Developers can inspect the local V2 canvas at http://localhost:4421/design-canvas.

Repositories: partners.furries.ph-v2

Status: Local developer tooling only; no production behavior or API deployment changed

What’s Changed

• V2 local development now supports the existing dashboard development-session contract, so protected dashboard pages can be exercised with a local Worker session.
• The flow is deliberately restricted to Vite development mode, localhost or 127.0.0.1, an explicit local opt-in, and the local Worker. It is unavailable on production and preview deployments.
• The local V2 server uses the established dashboard development origin and a first-party development proxy so the Worker’s httpOnly session cookies work correctly during browser testing.
• Local build and protected-route verification have been recovered after clearing host capacity pressure and restarting a stalled local Worker development process; no deployed API or production behavior changed.

What To Do

• Developers can run the local Worker and V2 app, then open http://localhost:4421. Keep the opt-in disabled for normal production or preview work.

Repositories: partners.furries.ph-v2

Status: Local implementation in progress; existing Partners dashboard remains unchanged

What’s Changed

• V2 Settings now has a native platform-status screen that shows the active API target, signed-in account, visible-partner count, active scope, and each available partner identifier.
• The Organization settings entry is now limited to partner administrators and FPH administrators, matching the existing dashboard access policy.
• V2 Organization now has native identity, operational-notification policy, and partner data-silo policy surfaces using the unchanged dashboard Worker contract. Discord and Telegram account/link flows remain separately in progress.
• V2 now includes a native Event Management Crash Course with the event lifecycle, setup, registration, staffing, communications, finance, logistics, common failures, and responsible page ownership.
• Settings and guide surfaces now consistently use the dashboard authentication guard before showing protected workspace content.

What To Do

• Use the current production dashboard until V2 account, organization, and authenticated operational flows are fully certified.