[cli-tools-test] UX: `compile` tool uses `workflows` param but `logs` uses `workflow_name` — confusing inconsistency

[github-actions]

Problem Description

The compile and logs MCP tools use different parameter names for filtering by workflow, causing user confusion when switching between tools.

• logs tool: --workflow_name "my-workflow" ✅
• compile tool: --workflows ["my-workflow"] — array, not a string

When a user tries compile --workflow_name archie (by analogy with logs), the tool returns:

Unknown parameter 'workflow_name'. Did you mean 'workflows'?

The error message does suggest the correct parameter, but the inconsistency creates unnecessary friction.

Steps to Reproduce

1. Use logs --workflow_name archie (works correctly)
2. Try compile --workflow_name archie by analogy
3. Get error: Unknown parameter 'workflow_name'. Did you mean 'workflows'?

Expected Behavior

Either:

• Consistent parameter naming across tools (e.g., both use workflow_name or both use workflows)
• OR compile accepts workflow_name as an alias for workflows (with auto-wrapping into array)

Actual Behavior

compile rejects workflow_name and requires workflows (array type), unlike logs which uses workflow_name (string type).

Environment

• Repository: github/gh-aw
• Run ID: 26803166887
• Date: 2026-06-02
• Tested via: agentic-workflows MCP server

Impact

• Severity: Low
• Frequency: Always (affects all users switching between tools)
• Workaround: Use --workflows ["name"] array syntax for compile

Additional Context

Discovered during daily exploratory testing. All other aspects of compile, logs, and audit tools functioned correctly during this session.

Generated by 🧪 Daily CLI Tools Exploratory Tester · sonnet46 2M · ◷

• expires on Jun 9, 2026, 6:50 AM UTC