A verify node said PASS in 17 seconds. The build was broken.

Description and use

oh‑my‑graph’s verify node reported PASS while the branch failed to compile. Versions 0.5.0 and 0.11.0 introduced PASS qualifiers and mandatory build evidence, preventing false positives.

Problem

oh-my-graph reported a successful verify step while the branch did not compile, leading to a false sense of correctness.

Outcome

The fix introduced PASS qualifiers and required explicit build evidence, preventing false PASS reports and ensuring build checks are performed or waived.

Workflow

• 1. User points oh-my-graph at a Kotlin repo and requests a change.
• 2. Planner generates a graph of steps, including a verify node with Bash(git *) tool.
• 3. Verify node runs git commands, reports PASS (self‑reported).
• 4. Branch fails to compile but ledger shows PASS.
• 5. Release v0.5.0 adds PASS qualifiers to ledger entries.
• 6. Release v0.11.0 enforces build evidence via --verify-cmd or --accept-no-build-evidence, refusing to start otherwise.

Evidence

The last step, a verify node, replied PASS. It took 17 seconds and cost $0.13.

Source

Since v0.5.0 every PASS in the ledger carries one of four qualifiers...

Source

Since v0.11.0, auto refuses to start in a directory where it detects a build system unless you pass either --verify-cmd 'your build' or --accept-no-build-evidence.

Source