[cli-tools-test] Workflow name matching inconsistency in logs command

[github-actions]

Problem Description

The agenticworkflows-logs tool requires using the GitHub Actions workflow display name (e.g., "CI Failure Doctor") rather than accepting the workflow ID (e.g., "ci-failure-doctor") that appears in the filename and is used throughout the codebase.

This creates a poor user experience where users must:

1. Look up the exact display name from the workflow frontmatter
2. Remember to use title case and spaces
3. Cannot use the simpler kebab-case identifier that's visible in file listings

Steps to Reproduce

1. List workflows to find a workflow ID:

   ls .github/workflows/*.md | grep ci-failure
   # Returns: .github/workflows/ci-failure-doctor.md

2. Try to filter logs using the workflow ID:

   agenticworkflows-logs --workflow-name ci-failure-doctor --count 5
   ````
   

3. Actual Result: Error message:

   workflow 'ci-failure-doctor' not found. Use the 'status' tool to see all available workflows
   

4. Must use display name instead:

   agenticworkflows-logs --workflow-name "CI Failure Doctor" --count 5

5. Expected Result: This works, but requires knowing the exact display name

Expected Behavior

The logs command should accept both:

• Workflow ID (kebab-case filename without .md): ci-failure-doctor
• Display name (from frontmatter): CI Failure Doctor

Impact

• Severity: Medium
• Frequency: Always (affects every workflow name query)
• Workaround: Use the status command to find the display name, then use that

Suggested Fix

Implement fuzzy workflow name matching that accepts:

1. Exact workflow ID (filename without .md)
2. Case-insensitive workflow ID matching
3. Display name from frontmatter (current behavior)

This would align with common CLI conventions where users can reference resources by their simple identifiers.

Environment

• Repository: github/gh-aw
• Run ID: 22045392962
• Date: 2026-02-15
• Command: agenticworkflows-logs

Additional Context

The compile and status commands handle workflow identification well, but logs (and potentially audit) require exact display names. This inconsistency creates confusion.

Generated by Daily CLI Tools Exploratory Tester

• expires on Feb 22, 2026, 11:56 PM UTC