midnight-verify:verify-tooling

Verify CLI tooling claims by classifying the statement type and routing behavioral assertions to a CLI execution tester that runs commands and inspects stdout, stderr, and exit codes, while routing architectural claims to source investigation methods.

The best way to determine if an error message stems from the CLI or the compiler is to classify the claim and concurrently dispatch both a CLI execution tester to capture the output and a source investigator to trace the internal origin.

You need source investigation when verifying internal or architectural claims about Compact CLI behaviors, whereas CLI execution is preferred for behavioral claims about flags, output structure, error messages, and exit codes.

You can check version reporting and installation method claims by dispatching a source investigator to examine the codebase internally, though running the CLI execution tester provides direct verification of reported version strings and filesystem artifacts.

CLI claim verification routes incorrectly when claim classification fails to distinguish between behavioral claims requiring CLI execution and architectural claims requiring source investigation, leading to misrouting and wasted effort.