Fantasy League: Scoring, Lineup Locks and Weekly Standings

Fantasy League: Scoring, Lineup Locks and Weekly Standings

You've joined the team behind Gridiron League, a fantasy-football app. Managers draft real players, set a weekly lineup, and the app turns each player's game stats into points. Support has a ticket about wrong scores, and two features are queued behind it: lineups that lock when a player's game kicks off, and weekly head-to-head matchups with a standings table that has to stay correct when the league publishes stat corrections. All point values are integer tenths of a point inside the code (10 = 1.0 pt); clients see them as one-decimal strings such as "12.5".

Codebase

How your code is run

run(operations: list[list]) -> list executes the operations in order against a fresh league and returns one result per operation. Every operation is [name, ts, ...args]; ts is an integer timestamp (it never decreases). Errors are returned as "error: <code>" strings, never raised. An unknown name returns "error: unknown operation"; a wrong number of arguments or a non-integer ts returns "error: invalid arguments", as does an empty or non-string player, team or slot id. Every id is a case-sensitive string. Checks run in the order listed in the "Errors" column.

• pos is QB, RB, WR or TE. kickoff is a non-negative integer or null (no game); any other value is invalid arguments. A player can be drafted by one team only. Rosters have no size limit.
• stat adds amount to the player's running total for that stat (so a game arrives as many small updates). amount must be an integer (not a boolean) and may be negative or zero, else invalid amount. Stat names are in config.STAT_NAMES.
• team_score is the sum of the scores of the players currently in the team's lineup slots. Empty slots score 0. Scores render with points.format_points ("0.0", "-0.5", "21.0").

Part 1: Fix the scoring (SUP-4410)

Goal: make player_score and team_score follow the league's scoring rules.

Support has three kinds of complaints: "my 100-yard rusher didn't get his bonus", "my running back who lost two yards on the game was docked a point", and "my receiver caught 5 passes and was paid for 4". Scoring tables live in fantasy/config.py; the arithmetic lives in fantasy/scoring.py.

Rules (all in tenths internally)

1. Scoring uses a player's game totals for each stat, never individual updates.
2. pass_td = 4.0, rush_td = rec_td = 6.0, int = fumble_lost = -2.0, per occurrence.
3. Yardage pays 1.0 per full unit of the total: 25 passing yards, 10 rushing or receiving yards. Totals are rounded toward zero: 9 rush yards = 0.0, -9 = 0.0, -10 = -1.0.
4. Every reception is worth 0.5 (half-PPR).
5. Milestone bonuses: rushing or receiving yards >= 100 pay +3.0 and >= 200 pay +5.0; passing yards >= 300 pay +3.0 and >= 400 pay +5.0. Only the highest tier reached is paid (a 250-yard rusher gets +3.0, not +8.0). Each stat's bonus is separate, so a player can earn a rushing bonus and a receiving bonus in the same game.

Example

[["player",1,"qb1","QB",null],["player",1,"rb1","RB",null],["team",1,"sharks"],
 ["draft",2,"sharks","qb1"],["draft",2,"sharks","rb1"],
 ["stat",3,"qb1","pass_yds",312],["stat",3,"qb1","pass_td",2],["stat",3,"qb1","int",1],
 ["stat",4,"rb1","rush_yds",57],["stat",4,"rb1","rush_yds",47],["stat",4,"rb1","rec",3],
 ["player_score",5,"qb1"],["player_score",5,"rb1"],
 ["start",6,"sharks","QB","qb1"],["start",6,"sharks","RB1","rb1"],["team_score",7,"sharks"]]

returns [true,true,true,true,true,312,2,1,57,104,3,"21.0","14.5",true,true,"35.5"]. (qb1: 12.0 yards + 8.0 TDs - 2.0 INT + 3.0 bonus; rb1: 10.0 yards + 3.0 bonus + 1.5 receptions.)

Part 2: Lineup slots and kickoff locks (LGE-218)

Goal: make start enforce slot eligibility and lock players at their own kickoff, and add bench. Slots and their eligible positions are in config.SLOT_ELIGIBILITY: QB; RB1, RB2 (RB); WR1, WR2 (WR); TE; FLEX (RB, WR or TE).

Rules

1. A player is locked at operation time ts if his kickoff is not null and ts >= kickoff (the kickoff instant itself is locked). Lock status is computed from the player's *current* kickoff each time; the kickoff operation can move a game later (unlocking) or earlier.
2. start puts the player in the slot. The incoming player must not be locked (player locked), and neither must the player currently occupying the slot (slot locked; checked second). A rejected start changes nothing.
3. A displaced occupant goes back to the bench. A player fills at most one slot: starting a player who is already in another slot moves him, leaving the old slot empty. Starting a player into the slot he already holds succeeds and changes nothing.
4. bench empties a slot; the occupant must not be locked.
5. team_score is unchanged: it counts whoever is in the slots when it is asked.

Example (rb1 and qb1 kick off at 1000, wr1 at 1300; all three are on team t)

[["start",900,"t","FLEX","rb1"],["start",900,"t","FLEX","qb1"],["start",1000,"t","RB1","rb1"],
 ["start",1100,"t","FLEX","wr1"],["bench",1100,"t","FLEX"],["start",1100,"t","WR1","wr1"],
 ["start",1300,"t","FLEX","wr1"],["lineup",1300,"t"]]

returns [true,"error: not eligible","error: player locked","error: slot locked","error: slot locked",true,"error: player locked",{"QB":null,"RB1":null,"RB2":null,"WR1":"wr1","WR2":null,"TE":null,"FLEX":"rb1"}].

Part 3: Weeks, matchups, corrections and standings (LGE-231)

Goal: the app now plays a season. Stats and lineups belong to a week; teams are paired head to head; and the league publishes stat corrections after games, which must change old scores and therefore old results. Until now the league lived in an implicit week 1.

Rules

1. The current week starts at 1. advance_week closes it: every team's lineup is captured as that week's final lineup, every player's kickoff is reset to null (the new week's schedule is set with kickoff; until then nobody is locked), and the week number increases. Live lineups carry over unchanged into the new week; later changes to them never affect closed weeks.
2. stat adds to the current week's totals. Weeks are independent; a new week starts with no stats. correct overwrites one stat total for any week from 1 to the current one (invalid week otherwise, including non-integers) and value follows the amount rules.
3. player_score / team_score take an optional week (default: current). A past week's team score uses that week's captured lineup and that week's stats as currently corrected; the current week uses the live lineup. A team created after a week closed scores "0.0" for it.
4. pair records a matchup for the current or a later week, in the order given. Each team has at most one matchup per week. A week is evaluated for standings only once it is closed.
5. standings counts matchups in closed weeks, scoring both teams at the moment of the call. A higher score wins; equal scores tie. points_for is the sum of the team's scores in its matchup weeks (a bye adds nothing). Every team appears, even with no games. Order: more wins, then more ties, then higher points_for, then team_id ascending (plain string order).
6. Parts 1-2 behave as before within a week; hidden tests re-check them.

Example (rb1 starts for team a, wr1 for team b; both teams exist, own those players, and the lineups are set)

[["pair",2,1,"a","b"],["stat",3,"rb1","rush_yds",80],["stat",3,"wr1","rec",4],
 ["advance_week",4],["bench",5,"a","RB1"],["team_score",6,"a",1],["team_score",6,"a"],
 ["standings",6],["correct",7,1,"wr1","rec_yds",130],["standings",8]]

returns [true,80,4,2,true,"8.0","0.0",[["a",1,0,0,"8.0"],["b",0,1,0,"2.0"]],130,[["b",1,0,0,"18.0"],["a",0,1,0,"8.0"]]].

Notes

• points.py, validation.py, models.py and errors.py are known-good.
• You may use the AI assistant freely; you are expected to verify what it produces.
• Parts 1-2 is a solid result; Part 3 is the full ticket.