List view
Goal: make TyperBot a season-aware, configurable Discord bot that can be invited into multiple servers and manage one isolated league per server. This release combines targeted architecture cleanup with the product features that need it: - seasons/competitions per server - per-season scoring rules - safer scoring and recalculation boundaries - clear first-run setup after the bot joins a server - reliable operations for one hosted bot serving many Discord servers Keep this practical: - one hosted bot application - many Discord servers/guilds - one league per server - one active season per server - one configured league/fixture channel per server - per-season scoring only - no self-hosting assumptions in server-admin-facing docs - no plugin system - no generic tenancy framework - no multi-league-per-server support - no broad config framework unless a concrete v3 issue requires it ## Recommended Order ### 1. Prep the codebase before product changes - #192 -- split oversized admin panel test module - #193 -- decompose oversized admin panel workflow modules - #201 -- simplify core boundaries for seasons and scoring - #216 -- centralize scoring and recalculation service ### 2. Add the season model - #51 -- season/competition management umbrella - #217 -- add season schema and active-season migration - #218 -- scope fixture workflows, week numbers, and standings by season - #219 -- add season management to the admin panel ### 3. Add per-season scoring rules - #50 -- configurable scoring umbrella - #220 -- add admin configuration for per-season scoring rules ### 4. Polish invited-server setup and operations - #52 -- polish invited-server setup and configuration - #114 -- enforce one configured league channel per guild - #214 -- add opt-in non-production database auto-seeding - #221 -- document invite-based multi-server setup and operator deployment ### 5. Verify the v3 contracts - #222 -- cover v3 season, scoring, and multi-guild contracts ## Cross-Issue Notes - Treat #50 and #51 as product umbrellas; concrete implementation should land through the focused issues listed above. - #216 should land before #50/#220 so every recalculation path uses one rule-aware scoring path. - #217 should land before #218 and #219. - #114 and #52 should keep the invite-based product model clear: server admins invite/configure the bot; they do not self-host it. - #221 should separate server-admin setup docs from operator deployment docs. - v3 is complete only when the milestone issues collectively prove guild isolation, season isolation, scoring-rule behavior, and safe setup for newly invited servers.
Overdue by 4 day(s)•Due by May 17, 2026•15/17 issues closed