Platform Updates

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

Status: Validated locally - release gates pending

What’s Changed

• Added an optional, explicit Social-to-Rego account-link flow for the same Furries PH member account.
• Social starts a one-time confirmation that expires after five minutes. The continuation is passed in the browser fragment and is removed by Rego before the authenticated confirmation request.
• A successful link exposes only the revocable public label Furries PH account linked. It does not share passwords, sessions, private content, profile data, staff status, event eligibility, or event activity.
• Either Social or Rego can revoke the link. The local schema keeps only a digest of the one-time continuation, a minimal claim, and sparse audit entries behind service-only access.

Impact

Members can choose to show a limited account-link label without turning Social into single sign-on or granting additional privileges.

Upgrade Notes

• This is not yet deployed. The additive migration, hostile-case authorization and replay testing, hosted synthetic verification, security review, and normal reviewed Git-connected release are still required.

Repositories: social.furries.ph, moderation.furries.ph, partners-api

Status: Validated locally - release gates pending

What’s Changed

• Authorized enforcing moderators can now take a deliberately narrow action on public Social posts, profiles, and active Pages without losing the option to continue into the full moderation dashboard.
• The same focused control appears wherever a current public post is visible: Home, profiles, Pages, local topics, and post threads. It can hide an exact post, lock its direct replies, hide a profile, or archive a Page as allowed by that object.
• Every inline action creates the same recorded reason, notice decision, rationale, replay-safe receipt, and audit trail as the full dashboard. It does not reveal reports, reporter identity, private evidence, or raw media.

Impact

Moderators can deal with immediate, narrow public-content issues in context and can move to the dedicated dashboard when a case needs broader tools, evidence, reversal, or review.

Upgrade Notes

• This is not yet deployed. The staged database migrations, RLS and authenticated multi-role validation, then the normal reviewed Git-connected Pages release, remain required. No direct build upload or additional Worker is involved.

Repositories: moderation.furries.ph, partners-api

Status: Validated locally - release gates pending

What’s Changed

• Policy, media, appeals, staff, and audit roles can now load their own dashboard panels without being incorrectly blocked by the case-review gate.
• These roles still receive no case queue, case detail, Content Updates, or automatic polling unless they explicitly have case.view access.

Impact

Policy managers can maintain approved rules without gaining access to reported member content, and restricted roles do not consume the moderation poll budget.

Upgrade Notes

• This is not yet deployed. Hosted role/RLS checks and the normal reviewed Git-connected release remain required.

Repositories: partners.furries.ph

Status: Validated locally - release pending

What’s Changed

• The Partners dashboard now has a source-audited /design-canvas route with editable page, field, component, shell, dialog, workflow and source-ledger previews.
• The canvas currently derives its inventory from 149 page sources, 44 reusable components, 12 dashboard layouts, and 81 runtime UI producers.
• Route selection, native dialog previews, save-state feedback and responsive 390px layouts are tested locally; an executable parity check detects source inventory drift.

Impact

Partners and product teams have one in-dashboard reference for reviewing operational surfaces before implementation changes reach live workflows.

Upgrade Notes

• This is not yet deployed. Local Astro diagnostics, production build, source-parity check, and browser visual QA passed; the normal reviewed Cloudflare Pages release is still required.

Repositories: partners.furries.ph-v2

Status: Validated locally - release pending

What’s Changed

• The native Partners dashboard now has a guarded Affiliates & Tracking workspace for event enablement, campaign attribution, reward tables, and affiliate configuration.
• Approved activity submissions can also be browsed by form with searchable, read-only answer detail and approval context.
• Payment collection settings and provider drafts are now available through a guarded V2 dashboard workspace; account/QR and fee-calculation extensions remain in progress.
• Inventory operators can stage POS settings and on-hand stock counts in the V2 dashboard, with movement history kept available when the audit feed is reachable.
• Shop operators can now manage V2 event availability, checkout instructions, categories, and couriers. Product listing and checkout authoring remains in progress.
• Event staff can now use the V2 POS cash-sale workflow, which obtains totals from the existing backend before recording an inventory transaction.
• Shop order operators can now filter, inspect, review submitted payments, and mark paid orders ready for pickup from the V2 dashboard.
• Pickup desks can now search shop orders and record release, reversal, or exception outcomes through the guarded V2 claim workflow.
• Dealers Den organizers can now configure V2 application gates and package capacity/costs. Application-form authoring and review work remains in progress.
• Dealers Den staff can now inspect dealer registration/payment context and update dealer-specific registration status from V2.
• Dealers Den application reviewers can now filter applications and use the guarded V2 approve, request-changes, and denial decision workflow.
• Existing event and finance-program APIs remain the source of truth; payout account details are not exposed in the dashboard editor.

Repositories: partners.furries.ph-v2

What’s Changed

• Event operators can edit core V2 registration availability, capacity, age, workflow gates, reference prefixes, and group-registration settings using the existing protected backend contracts.
• The V2 page checks registration-reference availability before saving and keeps catalog inventory visible while richer catalog authoring continues.

Upgrade Notes

• This remains a local V2 implementation. Advanced registration form, catalog, preview, entitlement, and ZEP controls are still in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• Event teams can now view source-owned registration lifecycle totals, tier and add-on metrics, gift-reservation capacity context, and the Forecasting handoff in V2.

Upgrade Notes

• This is a read-only local V2 port. Browser certification remains in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• V2 now exposes the existing server-owned registration, finance, and production forecast bundle with guarded Start, Stop, and Reset controls.
• Stopped forecasts remain visibly frozen; reset keeps prior forecast generations as an audit history in the backend.

Upgrade Notes

• This remains a local V2 implementation. Detailed charts, period controls, and authenticated-browser certification are in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• V2 event operators can now view protected collection, fee, remittance, provider, and masked account-capacity analytics.
• Financial calculations remain in the existing backend; the V2 dashboard is read-only for this analytics view.

Upgrade Notes

• This is a local V2 port and authenticated-browser certification remains in progress.

Repositories: partners.furries.ph-v2

What’s Changed

• V2 now shows protected inventory demand, fulfillment, on-hand coverage, shortages, and item-level production-risk analytics.
• Inventory changes remain in the V2 Inventory Tracking workspace; this analytics view is read-only.

Upgrade Notes

• This remains a local V2 implementation. Pagination, sorting, and authenticated-browser certification are in progress.