feat(merge): implement open-chain collection for pull requests passing individual CI #9804

Open
opened 2026-04-15 16:14:49 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit Message: feat(merge): implement open-chain collection for pull requests passing individual CI
  • Branch: feat/merge-chain-open-collection

Background and Context

The open merge-chain collects pull requests that have already passed individual CI. This is the entry point for the merge-chain batching system. Without a well-defined open chain, PRs cannot be grouped into batches for validation against master. This issue implements the collection mechanism that feeds the rest of the merge-chain pipeline.

Parent Epic: #9757

Expected Behavior

When this issue is complete, the system accepts PRs that have passed individual CI into the open chain, tracks their CI status, persists the open chain state, and provides a CLI/API to view the current open chain contents.

Acceptance Criteria

  • Open chain accepts PRs that have passed individual CI
  • PRs are tracked in the open chain with their CI status
  • Open chain state is persisted across restarts
  • CLI/API command available to view open chain contents
  • Unit tests cover open chain entry and state persistence

Subtasks

  • Design the open chain data model (PR reference, CI status, timestamp)
  • Implement open chain collection logic (accept PRs with passing CI)
  • Implement state persistence for the open chain
  • Implement CLI/API command to view open chain contents
  • Write unit tests for open chain entry, rejection, and persistence
  • Commit implementation on branch feat/merge-chain-open-collection

Definition of Done

This issue is closed when:

  • The open chain collection is implemented and persists state
  • PRs with passing individual CI are accepted into the open chain
  • A CLI/API command displays the current open chain
  • Unit tests pass with coverage >= 97%
  • A pull request is submitted, reviewed, and merged to master
  • All acceptance criteria above are independently verified

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Metadata - **Commit Message**: `feat(merge): implement open-chain collection for pull requests passing individual CI` - **Branch**: `feat/merge-chain-open-collection` ## Background and Context The open merge-chain collects pull requests that have already passed individual CI. This is the entry point for the merge-chain batching system. Without a well-defined open chain, PRs cannot be grouped into batches for validation against `master`. This issue implements the collection mechanism that feeds the rest of the merge-chain pipeline. **Parent Epic**: #9757 ## Expected Behavior When this issue is complete, the system accepts PRs that have passed individual CI into the open chain, tracks their CI status, persists the open chain state, and provides a CLI/API to view the current open chain contents. ## Acceptance Criteria - [ ] Open chain accepts PRs that have passed individual CI - [ ] PRs are tracked in the open chain with their CI status - [ ] Open chain state is persisted across restarts - [ ] CLI/API command available to view open chain contents - [ ] Unit tests cover open chain entry and state persistence ## Subtasks - [ ] Design the open chain data model (PR reference, CI status, timestamp) - [ ] Implement open chain collection logic (accept PRs with passing CI) - [ ] Implement state persistence for the open chain - [ ] Implement CLI/API command to view open chain contents - [ ] Write unit tests for open chain entry, rejection, and persistence - [ ] Commit implementation on branch `feat/merge-chain-open-collection` ## Definition of Done This issue is closed when: - The open chain collection is implemented and persists state - PRs with passing individual CI are accepted into the open chain - A CLI/API command displays the current open chain - Unit tests pass with coverage >= 97% - A pull request is submitted, reviewed, and merged to `master` - All acceptance criteria above are independently verified ## Links - **Blocks**: #9757 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
Author
Owner

🏷️ Triage Decision — [AUTO-OWNR-3]\n\nStatus: Verified\n\nIssue Type: Feature (v3.2.0 merge-chain epic) \nMoSCoW: Must Have — Open-chain collection is the entry point for the merge-chain system \nPriority: High\n\nRationale: Collecting PRs that pass individual CI into open chains is the first step of the merge-chain batching workflow. Must Have for the epic.\n\nLabels to apply: State/Verified, MoSCoW/Must have, Priority/High, Type/Feature\n\n---\nAutomated by CleverAgents Bot\nAgent: automation-tracking-manager

## 🏷️ Triage Decision — [AUTO-OWNR-3]\n\n**Status:** ✅ Verified\n\n**Issue Type:** Feature (v3.2.0 merge-chain epic) \n**MoSCoW:** Must Have — Open-chain collection is the entry point for the merge-chain system \n**Priority:** High\n\n**Rationale:** Collecting PRs that pass individual CI into open chains is the first step of the merge-chain batching workflow. Must Have for the epic.\n\n**Labels to apply:** State/Verified, MoSCoW/Must have, Priority/High, Type/Feature\n\n---\n**Automated by CleverAgents Bot**\nAgent: automation-tracking-manager
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#9804
No description provided.