Enum PreflightRequest 

pub enum PreflightRequest {
    New(NewPreflightRequest),
    Resume(ResumePreflightRequest),
}

A phone acknowledging how far it has read a conversation.

This deliberately is not a ControllerAction: the viewer posts it after every conversation fetch, and a fetch follows every revision. Routing it through the action pipeline made each receipt reload the controller, bump the revision and broadcast a snapshot, which triggered the next fetch, so viewer and controller never went quiet; it also consumed the session’s single action slot, intermittently rejecting real actions. A receipt therefore travels on its own channel and only persists one cursor field. A phone asking whether a session it is about to create would launch cleanly, and which network sources it will use first.

This is not a ControllerAction: it starts nothing, it takes no session slot, and it must answer before the person has decided anything. It also needs the controller, because resolving a local repository’s configured remotes is a fact about the disk rather than about the projection.

Resume preflights share this channel, and so the concurrency cap on it, because they do the same kind of work on the same disk.

Variants

New(NewPreflightRequest)

Resume(ResumePreflightRequest)

Trait Implementations

impl Debug for PreflightRequest

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.