docs(cli): document --directed and --undirected options for path comm…

[shobhitagnihotri69]

Summary

Fixes #3712. The graphify path command is directed by default (since #2487) and supports --directed and --undirected flags, but these flags were not documented in the top-level graphify --help command list.

Changes

• graphify/__main__.py: Added --directed (default) and --undirected flag descriptions under the path "A" "B" command in the top-level help text.
• tests/test_path_cli.py: Added test_path_help_documents_direction_flags asserting help output includes direction options.

Verification

• Ran uv run pytest tests/test_path_cli.py: 11 passed in 1.27s.
• Ran uv run pytest tests/test_multigraph_diagnostics.py: 31 passed in 0.31s.

[graphify-labs]

Graphify reviewed this change.

Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).

---

Graphify review — findings

Documents the path command's --directed (default) and --undirected traversal flags in the top-level CLI help text, and adds a test asserting both lines appear in --help output.

No blocking issues surfaced.

Analysis details — impact, health, verification

Impact & health

Graphify review

Impact — 217 functions depend on the 43 functions this change touches.

Health — this change adds coupling hotspots:

• new: dispatch_command() — 2 callers, 125 callees
• new: test_poisoned_manifest_is_healed() — 0 callers, 6 callees

Verification — 217 functions in the blast radius were not formally verified this run (proofs are advisory here).

Gate & verification

graphify gate

PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.

Advisory (not blocking):

• verification_scope: 217 function(s) in the blast radius were not formally verified this run

Test selection

Test selection

21 of 290 test file(s) selected (7%) via static blast radius.

• tests/test_affected_cli.py — impact
• tests/test_agents_platform.py — impact
• tests/test_codebuddy.py — impact
• tests/test_devin.py — impact
• tests/test_explain_cli.py — impact
• tests/test_extract_cli.py — impact
• tests/test_global_add_tag_inference.py — impact
• tests/test_god_nodes_cli.py — impact
• tests/test_hollow_chunks_arm_shrink_guard.py — impact
• tests/test_incomplete_build_guard.py — impact
• tests/test_install.py — impact
• tests/test_install_references.py — impact
• tests/test_install_version_warning.py — impact
• tests/test_merge_chunks_validation.py — impact
• tests/test_multigraph_diagnostics.py — impact
• tests/test_no_dedup_flag.py — impact
• tests/test_path_cli.py — impact, changed-test
• tests/test_query_cli.py — impact
• tests/test_query_induced_edges.py — impact
• tests/test_skill_version_warning.py — impact
• tests/test_unverified_semantic_shrink.py — impact

Selection is safe under the controlled-regression assumption; always-run tests + a periodic full run are the backstops. Advisory — it never changes the check verdict.

· 2 more finding(s) on lines outside this diff (see the check run).