fix(spf): preserve effect order across composition teardown
Superseded by https://github.com/mmcc/v10/pull/65, evaluated against current mmcc/moq-publisher. Its source tree matches this tested fix; both regressions reproduce on the current base, and the patched core suite passes 141/141.
Replacing a MoQ player in the same page can leave its new 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 new renderer binding before its setup. The binding then returns without subscribing to either actor slot.
Keep live effects in registration order independently of the watcher’s storage order. Removing an effect also removes it from the flush iteration, so disposal by an earlier effect cannot run the disposed body again.
Validation: both new regressions fail on the unchanged scheduler. The full SPF suite passes: 2,732 passed, 11 existing skips, no type errors. With the unchanged scheduler, the same suite fails only the two new regression tests (2 failed, 2,730 passed). The player dependency build and focused formatting/lint checks pass. The live workflow gate passes 11/11, including same-page player replacement, automatic gateway credential renewal, rebind on the new gateway epoch, and worker retirement after closing the viewer.
The live reproduction uses normal H.264 browser publication, a demand-gated operator, MSF catalog decoder initialization, and MoQ20 over certificate-pinned WebTransport/QUIC. No transport mock or vendored bundle patch is involved.