Reactive handle on the server-side submission queue.
Populated when submit() is invoked with
multitaskStrategy: "enqueue" while another run is in flight. The
returned entries signal is stable per snapshot so consumers can
feed it straight into Angular @for loops:
@for (entry of queue.entries(); track entry.id) {
<div>{{ entry.values | json }}</div>
}
Today the queue is maintained client-side; once the server starts emitting a dedicated queue channel (roadmap A0.3) the controller will mirror that state directly — the selector surface will not change.
interface InjectSubmissionQueueReturn