/** Env marker set on every pi the front door boots. Its presence means we are
 *  already inside a front-door-booted root, so a nested front-door launch must
 *  be refused — otherwise a removed/renamed subcommand that a child pi re-runs
 *  (e.g. `crtr node -h`) fork-bombs pi until the machine must be rebooted. */
export declare const FRONT_DOOR_ENV = "CRTR_FRONT_DOOR";
/** If this invocation is a front-door (root) launch, boot it and never return.
 *  Returns false when it's a recognized subcommand / help / unknown token (let
 *  the dispatcher handle it — for unknown tokens it errors cleanly).
 *
 *  Takes NO command tree: it decides from argv plus the static `SUBTREE_NAMES`
 *  list, so bare `crtr` never pays for assembling the full tree (measured 520ms
 *  of the front door's ~1.6s — every subtree's module graph plus external
 *  plugin/configured-CLI discovery, none of which a root boot reads). The one
 *  case that genuinely needs external command names — a bare word that is also
 *  an existing directory — builds the tree lazily, below. */
export declare function maybeBootRoot(argv: string[]): Promise<boolean>;