review-test-skips

name	review-test-skips
description	Audit all SKIP statements in the test suite for correctness
user-invocable	true
disable-model-invocation	true

Audit every Log("SKIP: statement across all .ahk test files in tests/. For each one, determine whether it is a legitimate skip or a silent failure that should be FAIL + TestErrors++.

Classification Rules

A SKIP is legitimate when the test is genuinely not applicable in the current environment:

• Optional dependency not installed: komorebi not installed/running, komorebic.exe not found
• Compilation not done: compiled exe not found (smart-skip scenario)
• Elevation required: test needs admin and process isn't elevated
• Environmental data insufficient: not enough windows open, no multiwindow class found, system process not running
• Parallel worktree collision: mutex conflict from another test instance running concurrently (worktree-safe design)

A SKIP is a silent failure (should be FAIL) when test infrastructure that SHOULD be working isn't:

• Process startup failed (launcher/gui/pump didn't spawn)