Describe the bug

In single-cell-data/TileDB-SOMA, gh run view --log -j <job_id> erroneously exits 0 while printing no logs, for every job I've tried:

gh run -R single-cell-data/TileDB-SOMA view --log -j 41013280987  # exits 0, no output
gh run -R single-cell-data/TileDB-SOMA view --log -j 40986064176  # exits 0, no output
gh run -R single-cell-data/TileDB-SOMA view --log -j 41015499160  # exits 0, no output
gh run -R single-cell-data/TileDB-SOMA view --log -j 41001342582  # exits 0, no output

(41013280987, 40986064176, 41015499160, 41001342582)

However, corresponding jobs in my fork (ryan-williams/TileDB-SOMA) return logs, as expected:

gh run -R ryan-williams/TileDB-SOMA view --log -j 41020345782 | wc
#   17335  272882 3063392

(41020345782)

Both repos have "Artifact and log retention" set to 90d, under /settings/actions, and the jobs above were all run in the last 24hrs.

• I initially flagged this in #5011 (comment), and @williammartin suggested that it may have to do with the / character injected in job names by workflow_call/matrix (cc @babakks as well).
• However, job 41020345782 above, from my fork, returns logs despite being all the same attributes (same workflow, triggered at same commit by push to same branch).
• Meanwhile, other simple jobs in single-cell-data/TileDB-SOMA also fail to return logs (despite no workflow_call, matrix, or /s in job names, e.g. 41001342582 above).

Why does gh run view --log -j <job_id> silently fail, for all jobs in single-cell-data/TileDB-SOMA, but not equivalent jobs in ryan-williams/TileDB-SOMA?