0.53.42 moved both native clients behind await import(), which is not enough: a
bundler resolves a LITERAL dynamic import exactly like a static one. It moves
the module into its own chunk and still has to load duckdb.node. Measured on
legal-agent, whose Worker build failed on the same two files after the lazy
change.

The specifier is now assembled at runtime, so a bundler cannot read it and
leaves the import to the runtime. Node resolves it; a Worker bundle never sees
it. The guard test now fails on a literal dynamic import too, and strips
comments first so the sentence explaining the rule is not read as a breach of
it.