deps: bump livetennisapi from 1.4.0 to 1.4.1

[dependabot]

Bumps livetennisapi from 1.4.0 to 1.4.1.

Release notes

Sourced from livetennisapi's releases.

v1.4.1 — the WS score frame is nested; the types now say so

Fixes for the 1.4.0 WebSocket types, verified against the server's frame builders:

• ScoreUpdate typed a frame that never existed. The wire nests the payload: {"type": "score", "match_id": N, "score": {sets, games, points, server, is_tiebreak, timestamp, win_probability_p1, danger}} — model fields inside score. The stream passes the raw frame through, so flat reads (frame.sets) compiled and returned undefined. ScoreUpdate is now {type, match_id, score?: Score}, with a regression test replaying the real nested wire shape verbatim.
• The CLI's watch read the flat fields and printed - for every score — fixed to read frame.score.
• BreakPoint.set / .game are wire strings ('1-1', '3-4'), not numbers — retyped.
• The subscribe frame drops the stray action: 'subscribe' key; it is now exactly the documented {topics, signals?}.

No behavioural change for consumers already reading frame.score; flat-field readers get a compile error pointing at the fix. Full details in CHANGELOG.md.

Changelog

Sourced from livetennisapi's changelog.

[1.4.1] — 2026-08-07

Fixed

• ScoreUpdate typed a frame that never existed. The wire NESTS the payload — {"type": "score", "match_id": N, "score": {sets, games, points, server, is_tiebreak, timestamp, win_probability_p1, danger}} — but the type extended Score and described the fields flat on the frame. The stream has always passed the raw frame through, so every flat read (frame.sets, frame.win_probability_p1) compiled and returned undefined. ScoreUpdate is now {type, match_id, score?: Score} with the model fields inside score, matching what actually arrives. A regression test replays the real nested wire shape verbatim.
• The CLI's watch printed - for every score for the same reason: it read the score fields off the frame instead of frame.score. Fixed.
• BreakPoint.set and .game are strings on the wire ('1-1', '3-4'), not numbers as typed since 1.2.0. Retyped to match.
• The subscribe frame carried a stray action: 'subscribe' key. The server ignores unknown keys, so it was harmless — but the documented frame is {topics, signals?} and that is now exactly what is sent.

Notes

• No behavioural change for consumers who were already reading frame.score (which always worked at runtime); consumers who read the flat fields were reading undefined and will now get a compile error pointing at the fix.

Commits

• 8ac506f 1.4.1: the score frame is nested — type it as the wire sends it
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)