nobody-verifies-before-completion

To enforce verification before claiming completion, you must run specific test commands and analyze their full output to confirm the fix actually works. This prevents false positives and ensures accuracy in status reporting.

Task completion verification fails without checking command output because there is no evidence to confirm the bug fix or test passing. Analyzing the full command output prevents dishonesty and identifies common pitfalls or rationalizations.

The best way to prevent false positives when reporting a passing test is to apply a strict verification protocol that requires running the relevant test command and confirming the success status directly in its output.

Yes, you can use this verification process for general operational tasks beyond debugging. It applies to all development and operational tasks requiring confirmation of success before any status assertion is made.

To identify common pitfalls that lead to inaccurate task status reports, you must review the gathered evidence and command outputs against the original claims. This strict verification exposes rationalizations that lead to incomplete status updates.