test(coverage): exclude iocraft renderers (pending stuie migration)

The native iocraft module isn't available in CI, and the iocraft-
based renderers are being replaced by stuie (not yet published).
Excluding the four affected source files from coverage measurement
until the migration lands so they don't drag the aggregate down with
unreachable native-module-gated code paths. The replacement (stuie)
renderers will be tested fresh once they ship.

Files excluded from coverage measurement:
- src/utils/terminal/iocraft.mts
- src/commands/analytics/AnalyticsRenderer.mts
- src/commands/audit-log/AuditLogRenderer.mts
- src/commands/threat-feed/ThreatFeedRenderer.mts

Surrounding `output-*.mts` files keep their non-renderer logic
(markdown formatters, JSON serializers) under coverage; only the
Renderer.mts files themselves are doomed.

5534/5534 tests still pass.

Author: jdalton

packages/cli/vitest.config.mts

@@ -132,6 +132,19 @@ export default defineConfig({
         // Explicit root-level exclusions
         '/scripts/**',
         '/test/**',
+        // iocraft renderers — being replaced by stuie. The native
+        // iocraft module isn't available in CI and stuie isn't
+        // published yet, so coverage measurement is excluded until
+        // the migration lands. The Renderer.mts files here are all
+        // doomed; the replacement (stuie) renderers will be tested
+        // fresh once stuie is published. Only the *Renderer.mts
+        // files are excluded — the surrounding output-*.mts files
+        // contain non-iocraft logic (markdown / JSON formatters)
+        // that's still tested directly.
+        'src/utils/terminal/iocraft.mts',
+        'src/commands/analytics/AnalyticsRenderer.mts',
+        'src/commands/audit-log/AuditLogRenderer.mts',
+        'src/commands/threat-feed/ThreatFeedRenderer.mts',
       ],
       include: ['src/**/*.mts', 'src/**/*.ts'],
       clean: true,