Struct CoordinationInput 

pub struct CoordinationInput<'a> {
    pub context: &'a GitContext,
    pub identity: &'a WorktreeIdentity,
    pub command: &'a ResolvedCommand,
    pub environment: &'a [(OsString, OsString)],
    pub timeout_ms: u64,
}

What: The inputs of one coordination. Why: Named fields keep the call readable and satisfy the parameter-object rule.

In TS you’d write (pseudocode):

coordinateIndexWriter({ command, gitPath, timeoutMs, environment })

Fields

context: &'a GitContext

Git context of the invocation.

identity: &'a WorktreeIdentity

The repository shape the invocation selects.

command: &'a ResolvedCommand

The resolved forwarded command.

environment: &'a [(OsString, OsString)]

The environment the invocation inherited, carrying any lease.

timeout_ms: u64

indexLock.unprovenOwnerTimeoutMs.