In dev-packages/deno-integration-tests/suites/orchestrion-*, only orchestrion-mysql and orchestrion-postgres spawn a real deno run scenario. The other 22 publish the diagnostics channel by hand:
const channel = tracingChannel('orchestrion:openai:chat');
channel.start.runStores(ctx, () => undefined);
channel.end.publish(ctx);
That tests the subscriber, which is shared with Node and already covered there. It proves nothing about whether Deno's Module.registerHooks transform actually injects the channel into that package. The Deno-specific risk is exactly the part not covered.
Work item. Promote three or four suites to real scenarios: express (the most-used), redis, and one AI provider. Reuse the scenario.mjs + Deno.Command shape from orchestrion-mysql.
**Prior art **(related history only). No issue. #21827 (merged) created the deno-integration-tests package that these suites live in. #18635 (open) is the nearest umbrella.
In
dev-packages/deno-integration-tests/suites/orchestrion-*, onlyorchestrion-mysqlandorchestrion-postgresspawn a realdeno runscenario. The other 22 publish the diagnostics channel by hand:That tests the subscriber, which is shared with Node and already covered there. It proves nothing about whether Deno's
Module.registerHookstransform actually injects the channel into that package. The Deno-specific risk is exactly the part not covered.Work item. Promote three or four suites to real scenarios: express (the most-used), redis, and one AI provider. Reuse the
scenario.mjs+Deno.Commandshape fromorchestrion-mysql.**Prior art **(related history only). No issue. #21827 (merged) created the
deno-integration-testspackage that these suites live in. #18635 (open) is the nearest umbrella.