The adapters register themselves with ClassFactory via @RegisterClass as a side effect of being
loaded. A bundler that sees no direct import of a module is free to drop it, which would leave
AIAgentHarness.DriverClass resolving to nothing at runtime — a failure that only appears in a
built artifact, never in dev. Calling this from a consumer's startup path keeps them reachable.
Tree-shaking guard.
The adapters register themselves with ClassFactory via
@RegisterClassas a side effect of being loaded. A bundler that sees no direct import of a module is free to drop it, which would leaveAIAgentHarness.DriverClassresolving to nothing at runtime — a failure that only appears in a built artifact, never in dev. Calling this from a consumer's startup path keeps them reachable.