🤖 Update analysis doc - clarify --silent is intentional

Document that --silent is necessary for log hygiene with 64 parallel
workers, and can be bypassed for debugging via workflow_dispatch.

Author: ammar-agent

CI_SPEED_ANALYSIS.md

@@ -36,15 +36,16 @@ Total:                 228s
 - Jest config: `maxWorkers=200%` (64 parallel workers)
 - Test files: 17 files in `tests/ipcMain/` + `tests/runtime/`
 - Flags: `--coverage --maxWorkers=200% --silent`
+  - Note: `--silent` is necessary to prevent overwhelming log output from 64 parallel workers
 
 #### Potential Issues
 1. **Over-parallelization**: 64 workers on 32 cores may cause contention
    - Each test spawns child processes, file I/O, git operations
    - May be better to use fewer workers (100% or 150%)
 
-2. **Silent mode hides timing data**: Can't see which tests are slow
-   - Remove `--silent` temporarily to profile
-   - Add `--verbose` to see timing per test
+2. **Silent mode needed for log hygiene**: 17 test files × 64 workers = overwhelming output
+   - Silent mode suppresses per-test spam while keeping suite status, timing, and failures
+   - Can use workflow_dispatch with test_filter to run specific tests verbosely for debugging
 
 3. **Coverage overhead**: Jest coverage adds significant overhead
    - Consider running coverage only on specific files
@@ -55,9 +56,9 @@ Total:                 228s
    - Check if any tests can be simplified
 
 #### Action Items
-- [ ] Profile tests without `--silent` to identify slow tests
 - [ ] Experiment with `maxWorkers=100%` vs `200%` vs `150%`
 - [ ] Measure overhead of `--coverage` flag
+- [ ] Use workflow_dispatch with test_filter to profile specific slow tests
 - [ ] Review slowest test files for optimization opportunities
 - [ ] Check if test files can share more setup code