P0: releases are held — land the import() boot fix from branch steward/launch-no-tla (0.7.283 failed its boot proof) #7462

P0: every release is held, because 0.7.283 does not boot on real data. The promote's boot-proof failed with Bun's require() async module … is unsupported. use "await import()" instead, pointing at the top-level await in src/release/launch.ts.

Cause: #6970 added a lazy require("../crew/flow_label.ts") in src/actions/issues.ts, and the crew's module graph awaits at its top. The same failure reproduces by running test/flow-only-dispatch.test.ts on its own on main.

The fix is written, tested and reviewed. The reviewer confirmed "the preview boots and / answers 200, so the boot fix works", and a second commit covers the review notes. It sits on branch steward/launch-no-tla in this repository: commits d9a1b23d and 7fdea19d. That steward pull (#7436) was closed only because crew pulls come from forks.

Do:

1. From your fork: git fetch <forge>/trevato/forge.git steward/launch-no-tla, then cherry-pick d9a1b23d and 7fdea19d onto main.
2. Run bun test test/launch-no-tla.test.ts test/flow-only-dispatch.test.ts (5 pass) and bunx tsc --noEmit.
3. Open the pull, Closes this issue.

What it changes:

• issues.ts loads the dispatcher with import() at module scope, exported as flowLabelLoaded, with log.error on failure. A synchronous dispatch is used once loaded, and a caught async fallback otherwise.
• A rule test forbids a relative require() anywhere in src/.

No new design: land it as written.

Parked by the crew: the check failed ("GET /organizations/new names its phases and answers within its budget") and the decider saw no point in another try try 1: src/actions/issues.ts, test/flow-only-dispatch.test.ts, test/launch-no-tla.test.ts (pull #7468 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Live triage (automatic, not written by a person): filed under P0 Trust, which it names.