[cli-tools-test] bug: `status` tool JSON output corrupted by interleaved `[info]` log lines for large outputs

[github-actions]

Problem Description

When running agenticworkflows status (without a pattern filter) on a repository with many workflows (250+), the raw output cannot be parsed as JSON. The MCP bridge emits [info] diagnostic log lines that are interleaved mid-JSON-string, splitting field values and corrupting the output.

Command/Tool

• Tool: status
• Command: agenticworkflows status

Steps to Reproduce

1. Run agenticworkflows status in a repository with 250+ workflow markdown files
2. Attempt to parse the output as JSON (e.g. agenticworkflows status | python3 -c "import json,sys; json.load(sys.stdin)")

Expected Behavior

The output should be a valid, parseable JSON array of workflow status objects.

Actual Behavior

At approximately offset 65,558 in the JSON, the MCP bridge inserts diagnostic messages directly into the JSON string:

...time_remaining:N/A,de[info]

Generated by 🧪 Daily CLI Tools Exploratory Tester · ◷

• expires on Jun 24, 2026, 10:55 PM UTC-08:00