…uling)

alchemy-run/node-utils#6 fixes the import-time registration at the
source; no reclaimSignals is built. The engine-sole-listener test
stays as the detector that blocks D3 if the upstream chain has not
delivered. Install-footprint consequence marked accepted.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

…uling)

alchemy-run/node-utils#6 fixes the import-time registration at the
source; no reclaimSignals is built. The engine-sole-listener test
stays as the detector that blocks D3 if the upstream chain has not
delivered. Install-footprint consequence marked accepted.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

Two unrelated-looking changes that are one prerequisite: composer's
commands can only become engine handlers once the engine ships the
surface they need, and only if importing alchemy stops fighting the
engine for the process's signals.

Bump @prisma/cli-engine 0.0.2 -> 0.0.3 in both manifests (they are
released in tandem and check:cli-engine-pin holds them equal). 0.0.3 is
the first release carrying ctx.spawn, exitWithChildStatus, the maySpawn
declaration, `needs: { credentials: "child" }`, and the production
EnvironmentCredentialManager the rebuilt CLI wires.

Vendor alchemy-run/node-utils#6 as a pnpm patch. On 0.0.5 the shipped
lockfile calls exitHook(...) at module scope, so importing alchemy
registers a SIGINT, a SIGTERM, and an exit listener before any command
runs. The engine owns signal policy — first press aborts and waits for
teardown, second force-exits — and a listener that calls process.exit
on its own pre-empts that cleanup. The fix registers the hook on first
lock acquisition and drops it when the last owned lock is released, so a
bare import registers nothing. Applied to lib/lockfile.js and
src/lockfile.ts alike: the exports map sends bun to src/ and Node to
lib/, and this repo runs both.

The patch is upstream's, not ours; the exit condition and the one-liner
that tests for it are recorded in the alchemy upgrade skill. Delete it
when the release chain delivers.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>