fix(spf): preserve effect order across composition teardown
Replacing a MoQ player in the same page can leave its renderer idle while its subscriber receives decodable frames. Destroying the old composition calls Watcher.unwatch(), which swaps the last watched effect into the removed slot and can run the replacement renderer binding before setup. The binding returns without tracking the subscriber and never wires the renderer.
Keep live effects in registration order independently of watcher storage order. Disposing an effect also removes it from the flush iteration, so an earlier effect cannot cause a disposed body to run again.
Targets mmcc/moq at 8bf5170e1 directly. One commit, two files: the shared SPF scheduler and two regression tests. No publisher commits or publisher dependency are included. Supersedes https://github.com/a-bro/v10/pull/1.
Validation on this base:
- Both new regressions fail on the unchanged
mmcc/moqscheduler (2 failed, 3 passed). - The patched full SPF suite passes: 2,403 passed, 11 existing skips, no type errors.
- SPF dependency build (
pnpm exec vp run '@videojs/spf#build') passes; focusedvp checkhas zero errors and three existing warnings.
The same scheduler change previously passed a separate 11/11 live workflow gate on the broader publisher integration tree, including normal H.264 browser publication, actual MoQ20 playback, same-page replacement and rebind after gateway renewal. That supplemental integration evidence is recorded in https://github.com/muxinc/relay-dev/pull/255; it is distinct from the current-base test run above.