Expand description
Extension dispatch with the Phase 1F guard sequence wrapped around the child spawn.
The eight steps the plan specifies (banner → requires_env → confirm →
secrets → audit-start → spawn → wait → audit-finish) are executed in
order; each step gates the next. Failures before spawn surface as
DispatchError without ever reaching the child.
Command::spawn (not exec) is deliberate: the dispatcher must outlive
the child to write the post-run audit entry, propagate exit codes, and —
on SIGINT/SIGTERM mid-run — forward the signal to the child via the
DispatchSignals handle the binary installs into its global signal
handler.
Structs§
- Dispatch
Options - Tunables and dependencies the dispatcher needs from the binary.
- Dispatch
Signals - Shared between the dispatcher and the binary’s ctrlc handler.
Enums§
- Dispatch
Error - Top-level error from
run. Each variant maps to a specific guard step or post-spawn failure mode so callers can render targeted diagnostics.
Functions§
- run
- Run an extension under the full guard sequence.