[cli-tools-test] logs tool: workflow-name filter fails to find existing workflows

[github-actions]

Problem Description

The logs tool's workflow-name filter fails to find workflows even when they exist in the repository. When attempting to filter logs by workflow name, the tool returns an error indicating the workflow doesn't exist, despite the workflow being present and listed in the status command output.

Command/Tool

• Tool: logs
• Command: agenticworkflows logs --workflow-name "audit-workflows" --count 3 --max-tokens 3000

Steps to Reproduce

1. Run agenticworkflows status to confirm workflow exists (audit-workflows is listed)
2. Attempt to download logs for that workflow: agenticworkflows logs --workflow-name "audit-workflows" --count 3 --max-tokens 3000
3. Observe error: "could not find any workflows named audit-workflows"

Expected Behavior

The command should successfully download logs for the audit-workflows workflow, returning up to 3 recent runs filtered by that workflow name.

Actual Behavior

Error message returned:

Error [-32603]: calling "tools/call": failed to download workflow logs: ✗ failed to list workflow runs (exit code 1): could not find any workflows named audit-workflows

Environment

• Repository: github/gh-aw
• Run ID: §26145567529
• Date: 2026-05-20
• Workflow exists: Confirmed via agenticworkflows status (workflow: "audit-workflows", engine: "claude", compiled: "Yes")

Impact

• Severity: Medium
• Frequency: Always (reproducible)
• Workaround: Use other filters (engine, date) and manually filter results, or omit workflow-name filter entirely

Logs/Diagnostics

# Status command shows workflow exists
$ agenticworkflows status | jq '.[] | select(.workflow == "audit-workflows")'
{
  "workflow": "audit-workflows",
  "engine_id": "claude",
  "compiled": "Yes",
  "status": "active"
}

# Workflow file exists
$ ls .github/workflows/audit-workflows.md
.github/workflows/audit-workflows.md

# But logs filter fails
$ agenticworkflows logs --workflow-name "audit-workflows" --count 3
Error [-32603]: could not find any workflows named audit-workflows

Additional Context

• Other filters (engine, date range) work correctly
• The status command correctly identifies and lists this workflow
• This suggests a possible mismatch between how workflow names are resolved in the logs tool versus the status tool
• Possible causes:
  • Logs tool may be looking for .lock.yml files while status looks at .md files
  • Workflow name normalization may differ between commands
  • GitHub Actions API workflow name format may not match local naming

Generated by 🧪 Daily CLI Tools Exploratory Tester · ● 12M · ◷

• expires on May 27, 2026, 6:40 AM UTC