fix: restore Daily Issues Report Generator — AWF binary install + issues data fetch resilience (#24349)

* Initial plan

* fix: resolve Daily Issues Report Generator failures - AWF binary install and issues data fetch

Fixes 11 consecutive failures (March 24 - April 3, 2026) in the Daily Issues
Report Generator workflow.

Root cause 1 (current failure - April 3): install_awf_binary.sh was using
`which awf` for installation verification, which exits with code 1 when
/usr/local/bin is not in the user PATH on aw-gpu-runner-T4 GPU runners.
Also, DIFC proxy env vars (GITHUB_API_URL pointing to localhost:18443) were
present during verification, which could cause the AWF Node.js bundle to
attempt connections to the proxy and fail on startup.

Fix: Use absolute path ${AWF_INSTALL_DIR}/${AWF_INSTALL_NAME} and clear DIFC
proxy env vars with `env -u` when running the verification step. The binary
is always accessible via sudo in subsequent workflow steps.

Root cause 2 (early failures - March 24+): gh issue list was failing with
"the 'github/gh-aw' repository has disabled issues" when routed through
the DIFC proxy, crashing the Fetch issues data step and preventing the
workflow from running at all.

Fix: Wrap gh issue list in an if/else error handler. If fetching fails, log
a warning and use an empty dataset [] so the workflow can continue. The
downstream agent will detect empty data and call the noop safe output.

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

Agent-Logs-Url: https://github.com/github/gh-aw/sessions/c2d9057d-49d4-40a3-a40d-12faf02ee5ba

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: Peli de Halleux <pelikhan@users.noreply.github.com>

Author: Copilot

.github/workflows/daily-issues-report.lock.yml

@@ -49,11 +49,14 @@ steps:
         # Fetch all issues (open and closed) using gh CLI
         # Using --limit 1000 to get the last 1000 issues, unfiltered
         echo "Fetching the last 1000 issues..."
-        gh issue list --repo ${{ github.repository }} \
+        if ! gh issue list --repo ${{ github.repository }} \
           --state all \
           --json number,title,author,createdAt,state,url,body,labels,updatedAt,closedAt,milestone,assignees,comments \
           --limit 1000 \
-          > /tmp/gh-aw/issues-data/issues.json
+          > /tmp/gh-aw/issues-data/issues.json; then
+          echo "::warning::Failed to fetch issues data (issues may be disabled or temporarily unavailable). Using empty dataset. Downstream analysis will report zero issues — check repository Issues settings or retry the workflow if this is unexpected."
+          echo "[]" > /tmp/gh-aw/issues-data/issues.json
+        fi
 
         # Generate schema for reference
         /tmp/gh-aw/jqschema.sh < /tmp/gh-aw/issues-data/issues.json > /tmp/gh-aw/issues-data/issues-schema.json

.github/workflows/shared/issues-data-fetch.md

@@ -210,7 +210,15 @@ else
 fi
 
 # Verify installation
-which awf
-awf --version
+# Use the absolute path to avoid PATH issues on self-hosted or GPU runners
+# where ${AWF_INSTALL_DIR} may not be in the user PATH. The binary is always
+# accessible in subsequent steps via sudo (which includes /usr/local/bin).
+# Also clear DIFC (Data Integrity and Filtering Controls) proxy env vars
+# set by start_difc_proxy.sh. When the DIFC proxy is active, GITHUB_API_URL
+# and GITHUB_GRAPHQL_URL point to localhost:18443 and GH_HOST is overridden.
+# The AWF bundle may try to reach these endpoints on startup, causing the
+# version check to fail with a connection error if the proxy rejects the request.
+env -u GITHUB_API_URL -u GITHUB_GRAPHQL_URL -u GH_HOST \
+    "${AWF_INSTALL_DIR}/${AWF_INSTALL_NAME}" --version
 
 echo "✓ AWF installation complete"