Wire Alternating, Weighted, Marathon FillStrategies into schedule engine dispatch #3
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
#2
What to build
The fill algorithm implementations for Alternating, Weighted, and Marathon already exist in the domain crate, but the schedule engine's
resolve_blockfunction may not dispatch to them yet. Wire the three new FillStrategy variants so they are actually used during schedule generation.Verify the dispatch in
resolve_blockhandles all 6 variants. Seed the InMemoryLibraryRepository with multi-series data and generate schedules that exercise each strategy. The Alternating strategy cycles through N series round-robin per day. Weighted favors fresh (unplayed) content. Marathon burns through one series from episode 1 in a single block.Expose the new strategies via the MCP tools so an agent can create channels using them.
Acceptance criteria
resolve_blockdispatches to all 6 FillStrategy variants (BestFit, Sequential, Random, Alternating, Weighted, Marathon)Blocked by
None — can start immediately