Christian PillsburyandClaude Opus 4.8 bc617eb1e7 refactor(spf): inline the resolve task, keep resolve-track close to main ...

The createResolveTask factory was a single-call hoist (the RecurringRunner
clones the task itself), so inline the task back into runner.schedule(...) as
on main, and inline the shouldLoadTrack gate the same way. Restore the
surrounding comments and formatting to main's, deviating only where the
refactor changed meaning: the gate now reloads resolved-but-incomplete (live)
windows (resolved→complete), and the obsolete scheduler/commit-time-id-check
notes are dropped. Net diff against main: 131+/70- down to 33+/18-.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-25 09:59:44 -07:00

..

core

refactor(spf): drop the vestigial reschedule retry-on-error path

2026-06-25 09:59:25 -07:00

media

refactor(spf): rename startSequence engine config to presumedStartSequence

2026-06-25 09:59:44 -07:00

network

feat(spf): multi cdn failover (#1671)

2026-06-17 08:20:43 -07:00

playback

refactor(spf): inline the resolve task, keep resolve-track close to main

2026-06-25 09:59:44 -07:00

all.ts

feat(spf): text tracks switching (#1687)

2026-06-22 07:54:51 -07:00

CLAUDE.md

feat(spf): multi cdn failover (#1671)

2026-06-17 08:20:43 -07:00

dom.ts

fix(spf): conventions, per-type specialization, config threading (#1537)

2026-05-19 11:38:47 -07:00

globals.d.ts

…

index.ts

feat(spf) discrete signals and behavior objects (#1508)

2026-05-08 08:32:44 -07:00