[cli-tools-test] Audit command: jq parameter not supported but should be

[github-actions]

Problem Description

The agenticworkflows-audit MCP tool rejects the jq parameter with an error, even though the agenticworkflows-logs tool supports it successfully. This inconsistency creates a confusing user experience.

Command/Tool

• Tool: agenticworkflows-audit
• MCP Server: agentic-workflows

Steps to Reproduce

1. Call the agenticworkflows-audit MCP tool
2. Provide a valid run ID: run_id_or_url: "21784234145"
3. Add a jq filter: jq: ".overview"
4. Observe the error message

Expected Behavior

The audit report should be filtered through the jq expression and return only the overview section:

{
  "run_id": 21784234145,
  "workflow_name": "Test Workflow",
  "status": "completed",
  "conclusion": "success",
  ...
}
```

This would be consistent with the behavior of the `logs` command, which successfully supports jq filtering.

## Actual Behavior

```
McpError: MCP error -32602: calling "tools/call": invalid jq filter expression
```

The command fails entirely, even though:
- The jq expression is valid
- The same tool signature (logs) supports jq filtering
- The audit output is JSON that would benefit from filtering

## Environment

- **Repository**: github/gh-aw
- **Run ID**: 21784347453
- **Date**: 2026-02-07
- **Testing Session**: Daily CLI tools exploratory testing

## Impact

- **Severity**: Low
- **Frequency**: Always (reproducible)
- **Workaround**: Call audit without jq, then filter the JSON in a separate step (e.g., using bash + jq)

## Why This Matters

1. **Consistency**: Users expect similar tools to have similar capabilities
2. **Token Efficiency**: Audit reports can be large; filtering reduces token usage
3. **Usability**: Being able to extract specific sections (overview, metrics, jobs) makes the tool more convenient

## Suggested Fix

Add jq filtering support to the audit command, similar to how the logs command implements it. This likely involves:
1. Accepting the `jq` parameter in the MCP tool definition
2. Passing it to the underlying `gh aw audit` command
3. Ensuring the command supports the `--jq` flag (or implementing it if missing)

## Additional Context

Working examples from the logs command:
```
agenticworkflows-logs --count 10 --jq ".summary"
agenticworkflows-logs --count 5 --jq ".runs | map({database_id, workflow_name})"
```

The audit command would benefit from similar patterns:
```
agenticworkflows-audit --run-id 123 --jq ".overview"
agenticworkflows-audit --run-id 123 --jq ".jobs"
agenticworkflows-audit --run-id 123 --jq ".key_findings"

AI generated by Daily CLI Tools Exploratory Tester

• expires on Feb 14, 2026, 6:02 PM UTC