Platform Updates

Repository: partners.furries.ph-v2

Status: Local implementation; not deployed.

• The safety overview restores complete eligible reminders, report-based recent updates, linked recent bans and V1 counting rules. Admin appeal review links directly to Admin.
• Report detail restores formatted statements/evidence, safe contact links, filing organisation and event names, revision values and history controls. Network-ban records link to partner appeal requests. Report editing improves save/revert behavior and refresh recovery; eligible staff authors retain local enforcement actions, with duplicate submission protection.
• Watchlist and ban directories restore partner-facing list controls and metadata while keeping Admin decisions outside Partners.
• Pawsport issuance verifies the selected attendee and checks both the issued document and its active binding before reporting completion. Binding history and attendee searches stay with the active workflow.
• Functional validation passed 37 actual-component browser groups plus targeted projection/ownership checks using synthetic sources. Final layout capture, typecheck, production build, route/shared-source and Docs checks passed. Real issuance, enforcement writes and hosted authorization remain separate acceptance work. Operators have no deployment action yet.

Repository: partners.furries.ph-v2

Status: Local implementation; not deployed.

• Authenticator verification now opens a six-digit code prompt during sign-in and protected workflows, then continues to the requested destination. It no longer sends enrolled users to account settings to enter their code. Wrong codes can be retried in place; cancellation and account changes stop the pending continuation. Enrollment and security requirements remain unchanged.
• Registration analytics restores independent tier and add-on list controls. Finance analytics handles invalid dates and incomplete values explicitly.
• Report directories restore V1 search, metadata and list controls, including their distinct grouped and personal-reminder presentations.
• Partner Pawsport registries restore internal note creation and holder details; issuer lists regain numeric codes and paging. Admin lifecycle actions remain in the Admin app.
• Validation uses actual components with synthetic records and intercepted test responses: 36 browser groups passed, including eight for inline MFA. Type, production build, route, shared-source and documentation checks passed. Hosted authentication, operational writes and full migration acceptance remain separate checks. Operators have no deployment action yet.

Repository: partners.furries.ph-v2

Status: Local implementation; not deployed.

• Volunteer application and dealer registration queues regain paging, sorting, search and selection across matching pages. Review recovery keeps confirmed outcomes separate from remaining work.
• The event directory restores list controls and prevents older partner reads from replacing the current partner’s events.
• Inventory analytics restores All-row viewing, displayed item-type search and per-item progress. Refresh results stay with their event; its canvas now uses the actual analytics component with sample data.

Event operators can review these changes locally before release. Focused checks use synthetic records and block external requests; no live stock changes, registration decisions, deletions or messages were sent. Hosted authorization, persistence and delivery remain separate acceptance work. Full parity is open.

Repository: partners.furries.ph-v2

Status: Local implementation; not deployed.

• Transfer and upgrade queues restore page sizes, all-row viewing and meaningful sorting, with search and page recovery after records change.
• Activity submissions restore grouped queue controls and read-only details. Review results stay with their event and require a refreshed queue after save.
• Dealer applications restore status counts, the changes-requested filter, dealer sorting, paging, assistant counts and precise search. Bulk review retains remaining selections after a failure and excludes saved decisions. Rejected single decisions preserve notes; terminal records disable review.

Event reviewers can inspect the local queues before release. Focused browser checks use synthetic application, transfer and notification sources; no live decisions, payments or notices were sent. Hosted permissions, persistence and delivery remain separate acceptance work. Full V1 parity is still in progress.

Repository: partners.furries.ph-v2

Status: Local implementation; not deployed.

• Gift review restores all-row viewing, precise search, receiver ordering, gift identifiers, attendee fallback and notification completion receipts.
• Refund review restores paging and sorting. Entering a positive add-on refund amount selects its removal, matching the previous workflow.
• Event tier waitlists restore queue controls and local activation-date editing. Partial settings saves retain failed drafts; uncertain offers require queue reconciliation before another offer can be sent.

Event operators can review these changes locally before release. Focused browser checks use synthetic records with external requests blocked. Route, canvas and shared-component checks pass; these checks do not certify every function. No real payments, offers or notices were sent. Hosted permissions, persistence and delivery still require separate acceptance; full V1 parity remains open.

Repository: partners.furries.ph-v2

Status: Local implementation; not deployed.

• The forecast canvas now runs the actual workspace, including start/stop/reset, confidence and cash charts, horizons, production details and error recovery. Its five scenarios use isolated sample data.
• Saved prefills regain paging, page sizes, attendee and saved-date sorting, precise search and timeout recovery.
• Approved activity submissions regain per-form paging and username sorting, retain read errors until recovery and discard results from departed events.
• Social event verification requires a fresh review after revision conflicts and protects repeated decisions and stale actions after a failed receipt refresh.

Event operators can review these changes locally before release; no migration is required. Focused browser checks use synthetic records and block live requests. No attendee notices, revocations, verification decisions or forecast controls were sent against real data. Hosted authorization, delivery, signing and persistence remain separate acceptance work; source drift monitoring stays active without rewriting its baseline.

Repository: partners.furries.ph-v2

Status: Local implementation; not deployed.

• Forecasting restores attendance confidence bands, reserved-gift and capacity context, and cash-flow charts with inflows, outflows and negative cash positions. Charts follow the selected cadence and horizon. Control errors retain the outlook, while polling and event changes cannot overwrite a pending decision.
• Google Wallet settings validate required fields, URLs and colors through the shared save action, retain failed drafts and recover failed loading.
• HR settings guard duplicate saves/imports and reject another event’s snapshot.
• LAN snapshot imports show the selected filename and overwrite consequences before submission. Exports and history remain bound to their original event; failed imports retain the file and direct operators to check applied state.

Event teams can review these changes locally. No migration is required. Focused browser checks use synthetic data and block live requests; no class updates, pass issuance, forecast controls or LAN imports/exports ran against real data. Desktop/mobile evidence and per-workflow limits are recorded with the parity tasks. Partners typecheck/build, route execution, shared-source and current native canvas inventory checks pass. Hosted persistence, provider issuance and physical LAN round-trips remain separate acceptance work.

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

Status: Locally implemented and verified; not deployed.

• Settlement entry refreshes quotes before submission, preserves proof controls and local date/time, and checks history after an uncertain response before allowing another entry in the current session.
• Notification settings retain failed drafts, recover failed loads and allow removal of saved destinations that are no longer available. Concurrent save and sample operations are guarded against duplicate requests.
• Conditions of Entry restores description typing, native document ordering, selection after Revert and reliable load/save recovery across event changes.
• Rego and Partners now share the same Button icon sizing and shrink behavior.

Event teams can review these local changes before release. No migration is required. Twenty-six isolated workflow browser groups and four handler groups pass, along with Partners typecheck, build, route execution and exact shared primitive checks. Desktop/mobile screenshots are retained. No live remittances, notification samples or legal documents were written.

Hosted persistence and delivery remain unverified. Settlement retry protection does not survive a new session without a durable server replay contract. The reporter canvas verification and a separate Rego public-event prerender failure remain open; these checks do not certify full V1 functional parity.

Repository: partners.furries.ph-v2

Status: Local implementation and verification; not deployed.

What’s Changed

• Upgrade reviews retain staff-note and payment-window context, protect repeated actions, and recover a saved decision without sending it again.
• Shop-order claim results regain search, sorting, paging, currency and item quantity context. Reversal reasons survive supplementary notes, and saved release receipts remain protected through failed refreshes.
• Coupon editors recover failed loads, retain failed drafts, prevent duplicate saves and show errors inside the active dialog. Saves refresh other finance programs before merging coupon changes.
• Asset checkout renewal shows the pinned policy’s duration, renewal usage and maximum date. Eligibility can be retried in the dialog; duplicate clicks and obsolete responses are ignored. Same-draft retries retain their request key, and saved renewals require the list to confirm the requested due date.

Impact

Event and asset teams regain V1 workflow details with clearer failure recovery. The existing API continues to own authorization and operational records. Claim quantities remain whole-order; no partial-release API was introduced.

Upgrade Notes

No migration is required. Local browser checks use synthetic data and block live API requests and provider writes; desktop and 390px screenshots are retained. Hosted payment, claims, renewal and delivery are not certified by these local checks.

Coupon program updates still lack an API revision guard and an atomic combined settings/program save. A fresh read reduces stale overwrites but cannot prevent another operator’s concurrent write. Full functional parity remains tracked.

Validation passed: 36 focused browser groups, duplicate/transport contracts, Partners V2 type checking and production build, partner route execution, and documentation diagnostics. Current canvas-binding and shared-primitive drift remain open; this is not a full-platform parity certificate.

Repository: partners.furries.ph-v2

Status: Local implementation and verification; not deployed.

What’s Changed

• Survey links now reopen the selected survey across reload and browser navigation. The Responses tab shows the three latest analysis runs, and results from a previous survey no longer replace the current workspace. Repeated clicks cannot start duplicate survey, reward or analysis requests.
• Registration details recover reference sheets from older fursona records, place the selected profile first, and tolerate surrounding search whitespace. The roster grid also stays within narrow mobile screens.
• Transfer review offers approval and decline directly, prevents duplicate decisions, and keeps a saved decision locked while its queue refresh recovers.
• Component coverage checks compare actual source identities and account for the existing shared Issue Reporter preview.

Impact

Event teams regain missing V1 workflow details while keeping the existing API authorization and Admin ownership boundaries. Focused survey and transfer browser checks use synthetic data; registration checks use read-only local authorized data. No attendee message or durable payment/transfer change was performed for these checks.

Upgrade Notes

No migration or operator setup change is required. Full parity certification remains open: donor-source drift and a shared Button styling mismatch remain tracked, and local evidence does not establish hosted or provider-side results.

Validation passed: Partners V2 type checking, production build, route and canvas coverage; focused survey/transfer checks; authenticated read-only registration checks and mobile geometry; and documentation diagnostics. Build size warnings remain tracked separately.