#!/usr/bin/env node
export declare function runUpgradeShim(cwd: string): number;
/**
 * THE PROCESS ENTRY POINT — the thing whose absence made this whole bin a lie.
 *
 * Up to and including 0.4.588 this module ENDED at the closing brace above. `pnpm exec wp-upgrade-shim`
 * loaded it, defined two functions, and exited 0 having printed nothing and changed no file. Fault S
 * names this command as OPTION 1, the only option that repairs all three managed surfaces, so the
 * guard's own "THIS IS NOT A DEADLOCK" promise was false: OPTION 2 repairs one of three, and OPTION 1
 * did nothing at all. Twenty-one unit tests missed it because every one of them called
 * `runUpgradeShim()` as a FUNCTION — the defect lived entirely in what the module does when SPAWNED.
 *
 * `runMain` from @webpieces/rules-config is the repo-wide wrapper and is deliberately NOT used here:
 * this bin must load with fs+path only (see the header) so it still runs on the broken tree it exists
 * to repair. `main()` is the sanctioned exit site instead, and `bin-process-entry.spec.ts` spawns
 * this file as a process so a future refactor cannot silently drop the launcher again.
 */
export declare function main(): void;