Platform Updates

Repository: partners.furries.ph

Status: Preview; locally validated

What’s Changed

• Meetings creation controls now live inside the meeting workspace card, matching Schedule.
• The blue action follows the active tab: schedule a meeting, record a past meeting, add an agenda item, add a meeting note, or record decisions and actions.
• Agenda items, notes, decisions/actions, full minutes, and reusable agenda templates now select their meeting and complete inside controlled dialogs. The decisions-and-actions dialog captures one accountable decision, approved/against/abstained votes from active department members, follow-up work items, and optional decision context rather than a full minutes form.
• Meeting notes, discussion summaries, published minutes, and facilitator notes now use the shared Markdown editor with preview, tables, task lists, footnotes, highlights, subscript, superscript, code blocks, and Mermaid diagrams.
• Published notes and minutes render through the shared sanitized Markdown pipeline. Draft and review minutes stay inside the controlled editor, and meeting Markdown does not accept pasted image uploads.

Impact

• Event operators can create the record implied by the current Meetings view without leaving the workspace or first opening a meeting row.
• Rich meeting records remain stored as editable Markdown while published content is rendered safely and private working content is not exposed in the detail panel.

Validation

• Astro diagnostics completed with zero errors and the 145-page production build passed. Browser certification exercised all five contextual Meetings actions, sanitized rich previews, raw Markdown preservation, meeting-bound agenda/note/decision-action dialogs, and the atomic decision/action command.

Repositories: partners.furries.ph, partners-api

Status: Preview; locally validated

What’s Changed

• EPS Departments → Members now provides partner-scoped access templates plus individual allow/deny permission overrides for each member.
• The Departments workspace now groups its views as Structure, People, Accountability, and Capacity, with member-access actions kept in the workspace card where they are used.
• The Add members action now searches all registered usernames before adding the selected account to both the active partner organization and the selected department, including planning role, capacity, and allocation. Search results and RACI/accountable-person pickers show each person’s profile photo when available, with initials as a fallback.
• New work items and requirements now require a RACI assignment at creation: exactly one accountable person and at least one responsible person. Consulted and informed people remain optional.
• EPS Schedule and Requirements are now cross-event registers by default. Each requirement explicitly selects its event plan, while each work item must select a requirement and inherits that plan automatically.
• Watching a department or RACI work item now switches immediately between Watch and Unwatch and keeps the selected record open. Watched records are labelled in their register.
• After the department membership is created, EPS immediately opens permission selection. The new partner member remains default-deny until an authorized administrator assigns templates or individual grants.
• The matrix now covers event and registration operations, commerce, finance, safety, Pawsports, assets, Event Planning, social publishing, CMS, and integrations.
• A deny override takes precedence, changes require a reason and audit record, and administrators can only delegate permissions they already hold.
• fph_admin remains a platform-only role and cannot be granted from EPS.

Impact

• Partner teams can give a member only the dashboard features needed for their event role instead of choosing one fixed all-or-nothing role.

Validation

• Astro diagnostics and Worker type checks completed with zero errors, the dashboard production build completed, and the 17-check modular authorization certification passed. The EPS Members dialog and Departments perspectives were exercised against the local fixture at desktop and 390px mobile widths; access changes are transactional and audit logged. Username search is limited to authorized partner member administrators and was verified against the local EPS fixture.

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.