Platform Updates

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

Status: Implemented; validated locally

What’s Changed

• The retired public-registration previews formerly served by the Partners dashboard have been removed.
• Their legacy event and Dealers Den URLs now direct attendees to the canonical rego.furries.ph experience.

Impact

• Attendees will see one consistent registration experience, with the current event page, registration flow, and Dealers Den workflow.

Validation

• The Partners production build completed successfully (145 pages), and its deployed _redirects rules contain both legacy URL mappings.

Repository: rego.furries.ph

Status: Implemented; validated locally

What’s Changed

• Event details, registration tiers, and the main registration action now render as soon as the event record loads.
• Optional event tools—such as shop, Dealers Den, activities, feedback, and signed-in account actions—continue loading in the background.

Impact

• Attendees should reach the core event information and registration decision sooner, especially when optional event services respond slowly.

Validation

• Astro diagnostics completed with zero errors; the production build generated 114 pages successfully.

Repository: partners.furries.ph

Status: Preview; implementation validated locally

What’s Changed

• EPS pages no longer download and parse the dashboard’s large non-planning scene registry during startup.
• Schedule, Requirements, Meetings, and Risks warm their first register page before navigation, while shared planning reads remain cached for the active work session and invalidate after changes.
• EPS now paints usable workspace records before optional page, workload, and projection requests finish.

Impact

• Event operators should see planning pages become interactive sooner and repeated switches across the EPS sidebar feel immediate.
• Current records remain protected by session, partner-scope, and mutation-driven cache invalidation.

Validation

• Astro diagnostics passed with zero errors, the 151-page production build completed, and the EPS initial dashboard-shell JavaScript fell from 590.87 kB to 32.15 kB before compression (145.98 kB to 10.35 kB gzip).

Repositories: partners.furries.ph, partners-api

Status: Preview; foundation implementation in progress

What’s Changed

• Partner clients now have an isolated foundation for social account records, canonical drafts, per-destination delivery variants, and delivery-attempt history.
• The partner dashboard has a new Social Publishing workspace that shows the active client scope, destination health, and a client-filtered publishing queue.
• Client owners and publishers can now start a partner-scoped authorization flow for Facebook, Instagram, TikTok, and X. The service uses encrypted, single-use PKCE authorization state; provider tokens never enter the dashboard.
• Browser-visible data excludes provider credentials, webhook URLs, and Sanity source URLs; every Worker query rechecks the active client boundary.

Impact

• Organizations that use the future publishing service will keep their accounts, drafts, and delivery records separate from other clients, even for operators who belong to more than one client.
• A provider authorization still needs that provider’s configured app, approved redirect URL, destination selection, and sandbox validation before it becomes a live publishing destination. Discord and Telegram use their existing webhook/bot-chat setup rather than a user OAuth grant; existing event notifications continue unchanged.

Upgrade Notes

• Platform operators must configure and approve each provider application before asking partners to connect accounts. Once enabled, a partner owner or publisher connects only the account belonging to their active client scope.

Validation

• Worker TypeScript validation and dashboard Astro diagnostics passed locally. Provider sandbox, database migration, and browser workflow evidence remain release gates.

Repositories: partners.furries.ph, partners-api

Status: Preview; implementation complete

What’s Changed

• EPS requirements can be delivered through one or more linked work items instead of a single task relationship.
• Linked work-item status, progress, dates, and blocked state roll up to the requirement so operators can see whether delivery work is moving.
• Work items remain the scheduled records in Gantt and Calendar; requirements remain the evidence and approval gate, with submissions recorded against the requirement.

Impact

• Event operators can plan and manage the work behind a requirement without losing the requirement’s acceptance criteria, review history, or submitted evidence.
• Teams can identify a requirement that is in progress, at risk, blocked, or ready for submission from its linked delivery work.

Upgrade Notes

• Link each delivery task to its requirement, set its normal work status and dates, and submit final evidence from the requirement once all required work is ready.

Validation

• Dashboard and Worker contract checks, applied migration verification, and fixture-backed EPS browser checks passed at desktop and mobile widths.

Repository: partners.furries.ph

Status: Preview; implementation validated locally

What’s Changed

• EPS now selects the first active event plan for the current partner when an operator opens a planning workspace from an unscoped sidebar link.
• All EPS navigation keeps that selected plan in context, so Schedule, Requirements, Departments, Meetings, Files, Notifications, Risks & Issues, Gates & Handoff, Event Configuration, and Settings show the same event’s records.
• EPS reuses short-lived, in-memory planning data during page switches and preloads likely destinations on navigation focus or hover.
• The Test Partners seed now includes canonical EMS registration, shop, Dealers Den, programme, volunteer, and payment configuration data for the Event Configuration surface.

Impact

• Test Partners operators can move directly through the sample workspace without opening a blank planning surface, while common page transitions require fewer network calls.

Validation

• The unscoped Schedule route resolved an active plan, populated the Gantt records, retained its project ID in sidebar links, and reported no browser-console errors. Astro diagnostics passed locally.

Repository: partners.furries.ph

Status: Preview; implementation ready

What’s Changed

• EPS event plans now use one clear status: Draft, Active, or Archived.
• The partner portfolio opens active and draft plans by default, keeps archived plans out of day-to-day work, and provides an explicit archived filter.
• Each portfolio plan now opens its own EPS workspace, so active plans for every event in the selected partner scope remain reachable.

Impact

• Teams can distinguish potential planning from active event delivery and keep completed or abandoned plans out of the working portfolio.

Validation

• Dashboard and Worker type diagnostics passed locally; the database migration normalizes existing legacy plan states before enforcing the new status set.

Repository: partners.furries.ph

Status: Preview; test scope validated

What’s Changed

• The hosted Test Partners EPS preview scope now includes representative work, requirements, meetings, risks, gates, handoff records, files, notifications, controls, exercises, and configuration data.

Impact

• Event operators can navigate and exercise the preview UI with realistic populated records instead of empty states.

Validation

• The hosted Test Partners scope was checked for populated planning workspace collections.

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.