[HumanBean17]

Summary

Fixes three reported CLI bugs. All three reproduce on master and are verified fixed end-to-end on the bank-chat fixture.

Fixes #473
Fixes #474
Fixes #475

#473 — CLI crash with a wrong option value

jrag dependents "X" --detail minimal produced a raw chained traceback and exit 1. Root cause: _EnvelopeArgumentParser routes argparse errors to main(), whose usage-error handler re-read --format/--detail from raw argv through a pre-parser that deliberately has no choices validation — the very token that triggered the error was fed to render(), raising ValueError inside the except block, outside every guard.

Fix: _FORMAT_CHOICES/_DETAIL_CHOICES are now shared constants (single source of truth for the real parser's choices= and for a clamp in the usage-error path). Invalid values now yield the clean status: error envelope, a terse stderr line, and exit 2 — for both --detail and --format. A drift-guard test (per the repo's enum-choices pattern) keeps the constants in sync with the render layer, which validates independently.

#474 — flow does not resolve method-level FQNs

flow_payload resolved its entry with hint_kind="route" only, and the resolver searches only the hinted kind — so method FQNs returned not_found even though callees resolved the identical FQN fine.

Fix: route resolution stays first (route path/topic behavior unchanged); a route not_found retries as a Symbol:

• method/constructor FQN → breadth-first walk over CALLS (LadybugGraph.trace_symbol_flow, one frontier query per hop); each edge carries hops = minimum BFS distance (rendered hop= in text)
• class/type FQN (class, interface, enum, record, annotation) → expands to declared method/constructor members (DECLARES) with a warnings[] note
• file Symbol → clean error pointing at jrag outline (no silent empty flow)

A review pass caught that the initial retry swallowed route ambiguous results (a topic prefix like banking.chat. returned a false not_found instead of its candidate list); ambiguity now propagates immediately, with a regression test.

#475 — outline cannot find a class

_cmd_outline resolved its argument only as a path on disk, so an FQN fell through to file-not-found. An FQN (class or method) now resolves as a Symbol and outlines the declaring file — verified to return the identical symbol set as the file-path form. Identifier-like misses surface the resolve envelope (closest symbols, jrag search pointer); path-like misses keep the familiar file-not-found error. Ambiguous names surface their candidates (no silent pick).

Verification

• New tests: graph-layer BFS semantics (min-hops, dedup, cycle safety), payload-boundary contract, CLI subprocess coverage for all three fixes plus ambiguity contracts and the render-flag drift guard.
• Heavy golden suite (JAVA_CODEBASE_RAG_RUN_HEAVY=1): 16/16 byte-identical — the route flow output is unchanged.
• Full suite: 2145 passed / 40 skipped; all 9 failures verified pre-existing or environmental on pristine master (bench grade service, .claude→.agents rename fallout in test_publish_skill_runbook, release_sh requires a clean tree).
• Ruff: no new findings vs master (same-binary comparison).
• Docs/help updated (en + ru); skills/ + agents/ artifacts re-synced (sync_agent_artifacts.py --check passes).

Reviewed by a three-scope reviewer team (CLI fixes / flow backend / docs-artifacts); the one Critical and all Important findings are addressed in this commit.