[Follow-up] Unmet criteria from PR #166

[github-actions]

Source

• Original PR: #166
• Verifier verdict: FAIL
• Verifier run: workflow run

Scope

Address unmet acceptance criteria from PR #166.

Original scope:

• The verifier CI query (verifier_ci_query.js) currently makes a single API call to fetch workflow run results. If the GitHub API returns a transient error (rate limit, timeout, network hiccup), the query fails silently and the verifier sees missing CI results.
• This can cause false negatives where the verifier marks test-related criteria as NOT MET due to API failures rather than actual CI failures.
• ### Current Behavior
• - Single API call per workflow
• - Failures logged as warnings but not retried
• - Missing results treated as "not found"
• ### Desired Behavior
• - Retry transient failures with exponential backoff
• - Distinguish between "CI not run" and "API error"
• - Log retry attempts for debugging

Tasks

• Satisfy: Transient API failures (429, 500, 502, 503, 504) are retried up to 3 times
• Satisfy: Successful retry results in correct CI data being returned
• Satisfy: Max retry exceeded results in clear error message, not silent "not found"
• Satisfy: Tests cover retry success and retry exhaustion scenarios
• Satisfy: Selftest CI passes

Acceptance Criteria

• Transient API failures (429, 500, 502, 503, 504) are retried up to 3 times
• Successful retry results in correct CI data being returned
• Max retry exceeded results in clear error message, not silent "not found"
• Tests cover retry success and retry exhaustion scenarios
• Selftest CI passes

Implementation Notes

Original implementation in PR #166.

[github-actions]

Branch codex/issue-167 created from main.

Option 1 (Invite) is enforced on issue events. PR creation is disabled by design so you are the PR author. Codex only engages on human-authored PRs.

Please open the PR as the author so Codex can work on it:

• Compare link: https://github.com/stranske/Workflows/compare/main...codex/issue-167?expand=1
• Suggested title: Codex bootstrap for #167
• Suggested body (copy/paste):

<!-- meta:issue:167 -->

@codex Your objective is to satisfy the **Acceptance Criteria** by completing each **Task** within the defined **Scope**.

**This round you MUST:**
1. Implement actual code or test changes that advance at least one incomplete task toward acceptance.
2. Commit meaningful source code (.py, .yml, .js, etc.)—not just status/docs updates.
3. **UPDATE THE CHECKBOXES** in the Tasks and Acceptance Criteria sections below to mark completed items.
4. Change `- [ ]` to `- [x]` for items you have completed and verified.

**CRITICAL - Checkbox Updates:**
When you complete a task or acceptance criterion, update its checkbox directly in this prompt file. Change the `[ ]` to `[x]` for completed items. The automation will read these checkboxes and update the PR's status summary.

**Example:**
Before: `- [ ] Add validation for user input`
After:  `- [x] Add validation for user input`

**DO NOT:**
- Commit only status files, markdown summaries, or documentation when tasks require code.
- Mark checkboxes complete without actually implementing and verifying the work.
- Close the round without source-code changes when acceptance criteria require them.
- Change the text of checkboxes—only change `[ ]` to `[x]`.

Review the Scope/Tasks/Acceptance below, identify the next incomplete task that requires code, implement it, then **update the checkboxes** to mark completed items.