Fighting Game · Guides & deep dives

V2 Content Calendar Management

The management tool loads content-calendar.json and exposes:

4sections1 minread
Markdown source
On this page

This runbook covers TODOS.phase-72.72.12.2.13: a content calendar management tool to plan and schedule seasons, events, and patches months in advance.

The operator surface is apps/v2/web/live-service/content-calendar/. Its contract is V2/ue/Content/V2/LiveOps/ContentCalendarManagement_V2_Contract.json, the focused gate is V2/ue/Tools/check-v2-content-calendar-management.py, and the Playwright coverage is apps/v2/web/e2e/v2-web-content-calendar.spec.ts.

Runtime Surface#

The management tool loads content-calendar.json and exposes:

  • a forward plan window of at least six months
  • scheduled seasons, events, and patches
  • readiness states for draft, planned, approved, and locked work
  • filters for content type, readiness, search, and conflicts-only review
  • a selected-plan detail inspector
  • active schedule conflict review

The route is:

  • /live-service/content-calendar/

The manifest includes item ownership, region, lead time, milestones, dependencies, summaries, and conflict resolution notes. Operators use it to keep season starts, live events, and patch windows aligned before release work reaches certification.

Operator Flow#

  1. Review the eight-month planning window for upcoming seasons, events, and patches.
  2. Filter by content type or readiness to inspect draft, planned, approved, and locked work.
  3. Use conflicts-only mode to isolate schedule risks.
  4. Select an item to inspect owner, lead time, milestone, dependency, and window details.
  5. Resolve conflict notes before locking a patch or event window.

Required Gates#

  • content-calendar-management-surface
  • content-calendar-management-seasons
  • content-calendar-management-events
  • content-calendar-management-patches
  • content-calendar-management-months-ahead
  • content-calendar-management-conflicts
  • content-calendar-management-playwright
  • content-calendar-management-ci-wired

Verification#

sh
python3 V2/ue/Tools/check-v2-content-calendar-management.py
python3 V2/ue/Tools/check-v2-ci-workflow.py
python3 V2/tools/validate-v2-docs.py
pnpm --dir apps/v2/web exec playwright test e2e/v2-web-content-calendar.spec.ts