test: add CLI coverage for graph deps and graph outputs

[github-actions]

Test Gap Fixes

Test suite snapshot: 3205 unit tests, integration tests across tests/*.rs, existing fixture set

Added Coverage

Module	Function/Path	Why It Matters	Test Added
src/inspect/cli.rs::dispatch_graph_deps / src/inspect/graph_deps.rs::analyze	ado-aw graph deps --direction downstream --json success path	The graph deps subcommand had zero CLI integration tests despite tests/inspect_integration.rs covering inspect, graph dump, and lint	graph_deps_json_downstream_includes_dependent_jobs
src/inspect/graph_deps.rs::analyze (error path)	Unknown step id	GraphDepsError::StepNotFound had unit coverage in-module but no CLI-level assertion that the error message surfaces correctly and the process exits non-zero	graph_deps_rejects_unknown_step
src/inspect/cli.rs::dispatch_graph_outputs / src/inspect/graph_outputs.rs::output_edges	ado-aw graph outputs default listing	graph outputs also had zero CLI integration tests	graph_outputs_lists_producer_and_consumers
src/inspect/graph_outputs.rs::output_edges (filter path)	--producer filter with no match	Verifies the JSON output degrades to an empty array (not an error) when a filter excludes everything, exercising the filtering branch of output_edges	graph_outputs_producer_filter_excludes_unmatched_producer

Validation

• cargo test --test inspect_integration (12 passed, 0 failed)
• cargo clippy --test inspect_integration --all-features (clean)
• git diff --name-only confirms only tests/inspect_integration.rs changed

---

This PR was created by the automated test gap finder. Previous run: 2026-08-17. Modules audited this cycle: src/inspect/graph_deps.rs and src/inspect/graph_outputs.rs CLI integration paths (via tests/inspect_integration.rs); src/mcp_author/mod.rs was inspected but deferred since equivalent unit tests live in src/mcp_author/tests.rs, outside this run's tests/* scope.*

Generated by Test Gap Finder · auto · 143.4 AIC · ⌖ 11.5 AIC · ⊞ 11.5K · ◷

[azure-pipelines]

Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.