[Spottq]

Before: the expanded driver row on the Live tab shows only the S1/S2/S3 sectors, so there is no way to see which tyres a driver has used or when they pitted. The standings list everyone alike, with nothing saying who can still win the title. There is no standings widget for the home screen or the lock screen. Nothing builds or tests the app on pushes or pull requests.

After: under the sectors, the expanded row shows the driver's tyre chain, one chip per stint with its laps (a dashed rim marks a used set), and in races and sprints "Pit stops 2 · L15, L38". Both standings tabs show "4 races + 1 sprint left · 108 pts to play for" and a dashed "Title out of reach below" line after the last driver or team who can still catch the leader ("Title decided" when only the leader is left). Three new home-screen widgets, each its own entry in the picker and resizable from 2x2:

• Drivers' standings and Constructors' standings: position, team colour, name (the driver code when narrow) and points, as many rows as the height holds, with the same title line.
• Title fight: the leader's points and wins, and the gaps of the drivers chasing them ("NOR −22 · VER −83" at 2x2, tiles from 4x2), with the line among the chasers.

The same three come as 2x2 Samsung lock-screen widgets on tablets and foldables: the top five with the title line, and the leader with the two nearest gaps and the points left, in the monotone style the lock screen recolours. Tapping any standings widget opens the Standings tab on the matching table. A GitHub Actions workflow runs the unit tests and a debug build on pushes to main and on pull requests.

How: stints come from TimingAppData Stints: the laps of a stint are TotalLaps - StartLaps, and the pit laps are their running sum, shown only when they agree with TimingData's NumberOfPitStops. TitleFight counts the races and sprints left in the calendar after the standings round, at 25 and 8 points for a driver and a one-two's 43 and 15 for a team; an entry stays in the fight while its points plus that total reach the leader's. On a sprint weekend the standings carry the same round number before and after the race, so that race keeps counting for a day after its start rather than dropping someone too early.

The home widgets are Glance, laid out for their exact size, and share one snapshot built by StandingsWidgetUpdater. The table only changes after a race or a sprint, so they fetch it 1, 3, 6, 12 and 24 hours after each one ends and otherwise once a day, on an inexact non-wakeup alarm through AutoFollowReceiver, never closer than 30 minutes apart; a table the app fetches reaches them at once through JolpicaStandingsRepository.updates. Before the season's first race they show last season's final table. They follow the session widget's colours and One UI blur settings and use its settings screen. The rules (rows that fit, where the line goes, when to fetch) live in the Android-free StandingsWidgetPlanner.

The lock-screen widgets are RemoteViews providers like the existing 2x2 lock widget: they ship disabled and StandingsLockWidget.syncEnabled switches them on for sw600dp and hinge devices only. They are drawn from the same snapshot whenever it is rebuilt, and StandingsLockPlan decides how many rows and small lines fit the slot at the system font size.

The workflow uses Temurin 21 with the Gradle cache and uploads the test reports when a job fails.

Tests: 42 new unit tests (4 for stint parsing, 14 for TitleFight, 19 for StandingsWidgetPlanner, 5 for StandingsLockPlan); the whole suite (233) passes and the debug APK builds in CI. Not yet tried on a device: the new screens and widgets want a look on a phone and a Samsung tablet or foldable before merging.