[Integration DoD][MW-05] Add connector parity test across schema/runtime/auto-enable maps

[github-actions]

This issue is auto-generated from INTEGRATION_DOD_MAP.md by the nightly DoD gap sync workflow.

Gap

• ID: MW-05
• Owner (area-owner): Runtime

Acceptance Criteria

• Connector IDs match across schema, runtime map, and auto-enable map.
• Drift is detected by test failures.

Verification Commands

bunx vitest run src/config/plugin-auto-enable.test.ts src/runtime/eliza.test.ts

Risk

• Silent connector onboarding/config breakage.

Source

• INTEGRATION_DOD_MAP.md:461

[hellopleasures]

Fix submitted in PR #765.

Root cause: Three test files (connector-parity.test.ts, plugin-auto-enable.test.ts, eliza.test.ts) that import from runtime/eliza.ts were completely dead (0 tests running) due to @elizaos/plugin-ollama importing MAX_EMBEDDING_TOKENS from @elizaos/core — an ESM named-export that Vitest cannot resolve at static-analysis time.

Fix: Added vi.mock() stubs for all 33 static plugin star-imports in each test file, unblocking 358 tests (65 connector-parity + 95 plugin-auto-enable + 198 eliza runtime). Also fixed stale connector count in connector-parity.test.ts ("18" → "19").

Verification: All three-way parity assertions (CONNECTOR_IDS ↔ CONNECTOR_PLUGINS ↔ CHANNEL_PLUGIN_MAP) now execute and pass.