Module hook 

Lifecycle-hook wire types and the prefix the platform calls them under.

Not client types. A consumer must never post to these paths — they are the platform’s, and /run in particular is the one route whose success is not repeatable — but the shapes belong here anyway, because a client generator reading the schema has to be told what the daemon accepts on them.

Structs

RunHook

The caller’s own payload, carrying the per-VM secret and an optional launch environment.

RunHookEnvelope

The envelope the platform posts to the run hook.

Enums

RunHookError

Why a runHookPayload string could not be read as a RunHook.

Constants

HOOK_PREFIX

Prefix the platform uses for every lifecycle hook. Fixed by the service.