fix-failing-pipelines

# Fix Failing Pipelines Check GitHub Actions workflows on the `staging` branch of https://github.com/a5c-ai/babysitter/actions, identify workflows whose most recent run is failing, and dispatch `/babysitter:yolo` to fix each one. ## Workflow ### Step 1: Fetch Most Recent Run Per Workflow Use the `gh` CLI to list recent workflow runs on the `staging` branch: ```bash gh run list --repo a5c-ai/babysitter --branch staging --limit 50 --json databaseId,workflowName,status,conclusion,createdAt,headBranch ``` Group the results by `workflowName`. For each workflow, keep only the **most recent** run (by `createdAt`). Discard workflows where the most recent run is still `in_progress` -- we only care about completed runs. ### Step 2: Identify Failures From the grouped results, select only workflows where the most recent completed run has `conclusion: "failure"`. Skip workflows whose latest run succeeded, was cancelled, or is still running. If no workflows have a failing most-recent run, report that all staging pipelines are green and stop. ### Step 3: Get Failure Details For each failing workflow run, fetch the failed job and step details: ```bash gh run view <run_id> --repo a5c-ai/babysitter --json jobs --jq '.jobs[] | select(.conclusion == "failure") | {name, conclusion, steps: [.steps[] | select(.conclusion == "failure") | .name]}' ``` Then fetch the logs to understand the actual error: ```bash gh run view <run_id> --repo a5c-ai/babysitter --log-failed 2>&1 | tail -100 `...