Keepalive v2: turn “keepalive” into a real closed loop (Gate workflow_run -> Codex -> commit -> Gate -> repeat)

[github-actions]

Topic GUID: a7e4336a-0c86-5585-8e0c-373d60c8c0ca

Why

Context / problem:

• Current keepalive does one round, then you manually click “Update Branch” (or create/merge a branch) in the Codex website to continue.
• That manual step is the entire reason this doesn’t behave like a loop.
  Goal:
• Implement a loop that is entirely GitHub-native:
  • Gate finishes -> if tasks remain -> Codex runs next task -> commit/push -> Gate reruns -> repeat
• No Codex website clicking.
  Requirements:
• Single label policy:
  • Only label needed: agent:codex
  • keepalive and autofix behavior controlled by a config block in PR body (written by Agents 63 bootstrap) or a repo-level default.

Tasks

• Add a new workflow: .github/workflows/agents-keepalive-loop.yml
• Trigger conditions:
• on: workflow_run (workflows: ["Gate"], types: [completed])
• optional: on pull_request labeled (agent:codex) to “start the loop”
• Determine PR number from workflow_run payload
• Fetch PR body and parse:
• task list checkboxes
• keepalive_enabled flag
• autofix_enabled flag
• iteration counter + max iterations
• If Gate conclusion == success AND keepalive enabled AND tasks remain:
• call reusable-codex-run with prompt keepalive_next_task.md
• commit/push changes
• post/update a single “Keepalive summary” comment (update-in-place)
• Use concurrency:
• group: keepalive-${{ pr_number }}
• cancel-in-progress: false
• Stop conditions:
• tasks complete (all boxes checked) OR max iterations hit OR repeated identical failure
• when stopping, add a label like needs-human (or post a loud comment) and exit

Acceptance criteria

• A PR with a tasklist can advance multiple iterations without any manual Codex website interaction.
  • Gate green + tasks remaining reliably triggers the next iteration.
  • The loop stops safely and noisily when it can’t proceed.

Implementation notes

Not provided.

---

Synced by workflow run.

[github-actions]

Branch codex/issue-75 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-75?expand=1
• Suggested title: Codex bootstrap for #75
• Suggested body (copy/paste):

### Keepalive: OFF
<!-- meta:issue:75 -->

### Source Issue #75: Keepalive v2: turn “keepalive” into a real closed loop (Gate workflow_run -> Codex -> commit -> Gate -> repeat)

Base: main
Head: codex/issue-75

Source: https://github.com/stranske/Workflows/issues/75

> Topic GUID: a7e4336a-0c86-5585-8e0c-373d60c8c0ca
> 
> ## Why
> Context / problem:
>    - Current keepalive does one round, then you manually click “Update Branch” (or create/merge a branch) in the Codex website to continue.
>    - That manual step is the entire reason this doesn’t behave like a loop.
>    Goal:
>    - Implement a loop that is entirely GitHub-native:
>      - Gate finishes -> if tasks remain -> Codex runs next task -> commit/push -> Gate reruns -> repeat
>    - No Codex website clicking.
>    Requirements:
>    - Single label policy:
>      - Only label needed: agent:codex
>      - keepalive and autofix behavior controlled by a config block in PR body (written by Agents 63 bootstrap) or a repo-level default.
> 
> ## Tasks
> - [ ] Add a new workflow: .github/workflows/agents-keepalive-loop.yml
> - [ ] Trigger conditions:
> - [ ] on: workflow_run (workflows: ["Gate"], types: [completed])
> - [ ] optional: on pull_request labeled (agent:codex) to “start the loop”
> - [ ] Determine PR number from workflow_run payload
> - [ ] Fetch PR body and parse:
> - [ ] task list checkboxes
> - [ ] keepalive_enabled flag
> - [ ] autofix_enabled flag
> - [ ] iteration counter + max iterations
> - [ ] If Gate conclusion == success AND keepalive enabled AND tasks remain:
> - [ ] call reusable-codex-run with prompt keepalive_next_task.md
> - [ ] commit/push changes
> - [ ] post/update a single “Keepalive summary” comment (update-in-place)
> - [ ] Use concurrency:
> - [ ] group: keepalive-${{ pr_number }}
> - [ ] cancel-in-progress: false
> - [ ] Stop conditions:
> - [ ] tasks complete (all boxes checked) OR max iterations hit OR repeated identical failure
> - [ ] when stopping, add a label like needs-human (or post a loud comment) and exit
> 
> ## Acceptance criteria
> - A PR with a tasklist can advance multiple iterations without any manual Codex website interaction.
>    - Gate green + tasks remaining reliably triggers the next iteration.
>    - The loop stops safely and noisily when it can’t proceed.
> 
> ## Implementation notes
> _Not provided._
> 
> ---
> Synced by [workflow run](https://github.com/stranske/Workflows/actions/runs/20479513650).

@codex start

Codex, please derive and propose:
- Scope / key constraints
- Acceptance criteria / definition of done
- Initial task checklist to iterate through

Use the issue details above to draft the plan, then proceed with implementation.

---

Once the plan is posted, comment the snippet below to start execution and enable keepalive:

The following block should be pasted as a separate PR comment:

```markdown
@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. Mark a task checkbox complete ONLY after verifying the implementation works.
4. **POST A REPLY COMMENT** with completed checkboxes using the **EXACT TEXT** from the lists below.

**CRITICAL - Checkbox Format:**
When posting your reply, copy the **exact checkbox text** from the Tasks and Acceptance Criteria sections below. Do NOT paraphrase or summarize. The automation matches text exactly.

Example format for your reply:

Completed this round

Tasks

• Add an environment flag (e.g., TREND_PIPELINE_PROXY_SIMPLE) that, when set, skips GC scanning...
• Ensure default behaviour remains unchanged (GC scanning enabled) to preserve test friendliness.

Acceptance Criteria

• Setting the new env flag yields a direct-import proxy path; default continues to honour GC-scanned modules.

**DO NOT:**
- Commit only status files, markdown summaries, or documentation when tasks require code.
- Re-post checklists without making implementation progress.
- Close the round without source-code changes when acceptance criteria require them.
- Paraphrase or shorten checkbox text—copy it exactly for tracking to work.

Review the Scope/Tasks/Acceptance below, identify the next incomplete task that requires code, implement it, then **post a reply comment** with the completed items using their **exact original text**.

[stranske]

Codex belt dispatcher queued this issue and created branch codex/issue-75.

[github-actions]

PR #85 already exists for branch codex/issue-75. Updated PR body with issue content.

PR link: #85