FA-11287 / Media playlist lifecycle / Member archive

Play next queue: Consumes play-next requests in reverse insertion order · case 02

Consumes play-next requests in reverse insertion order and produces an incorrect media-control or presentation result.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case scope

Consumes play-next requests in reverse insertion order and produces an incorrect media-control or presentation result.

Why this case matters

A deterministic in-memory media application model with explicit playlist, timeline or synchronization semantics. Does not implement codecs, transport protocols, rendering hardware or concurrent playback.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
queue has priority	`["y", ["x"], "a"]`	`["x", ["y"], "a"]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.