Repository navigation
fix(path): route through a contains edge back out to its file (#3878) - #4004
ayushcodes10 wants to merge 2 commits into
0/1 PR-changed function(s) verified · 1 not verified (1 vacuous)
Compared merge-base d6eaa8aae8df155874ebb1044302c055c286342a (where this PR branched from the base branch) against head 6a7a720894f934fce199286817b40cf633ec1c92. Changes on the base branch since then are not attributed to this PR.
PR-changed functions: 0/1 verified (0 proven, 0 may-equivalent, 0 distinguished) · 1 not verified (1 vacuous)
| equivalent (proved) | distinguished | may-equivalent (sampled) | unsupported | error |
|---|---|---|---|---|
| 0 | 0 | 0 | 1 | 0 |
graphify/cli\.py· dispatch_command: unsupported (vacuous: never exercised, not verified) — no capturable inputs from the test suite; property tier: not verifiable: all 23 sampled inputs raised on both versions — the function never executed, so 'no divergence' would be vacuous (mostly SystemExit — names the real obstacle, not a…
Backend availability notices:
- none of the 0 changed id(s) matched a code node in the graph (0 known) — 1 changed function(s) recovered directly from the git diff instead (graph may be stale/unsynced; consider a rebuild)
Evidence certificates (JSON / Markdown): open in Graphify (sign-in required).
Formal verification is advisory: equivalent is a proof over a bounded sound subset; may_equivalent is sampled, not proven; unsupported and error are honest abstentions. A vacuous check (it never exercised the function) is counted as not verified. Only functions this PR changed are counted; context functions are listed separately.