feat(merge): add visibility and status reporting for merge-chain state transitions #9812

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

Metadata

  • Commit Message: feat(merge): add visibility and status reporting for merge-chain state transitions
  • Branch: feat/merge-chain-visibility

Background and Context

Operators need to observe merge-chain state to diagnose stuck, failing, or repeatedly split chains. Without visibility into the queue state and state transitions, operators cannot determine whether the system is working correctly or identify which PRs are causing problems. This issue adds logging, CLI status reporting, and stuck-chain detection.

Parent Epic: #9757

Expected Behavior

When this issue is complete, all state transitions are logged at INFO level, a CLI command shows the current queue state, the status report covers open chain, queued chains, active validation, and recent results, and stuck chains are flagged after a configurable timeout.

Acceptance Criteria

  • State transitions are logged at INFO level with relevant context
  • CLI command available to view current queue state
  • Status report shows: open chain contents, queued chains, active validation, recent results
  • Stuck chains are flagged after a configurable timeout period
  • Unit tests cover logging, CLI output, and stuck-chain detection

Subtasks

  • Implement INFO-level logging for all state transitions
  • Implement CLI command for queue status display
  • Implement status report covering all queue sections
  • Implement configurable stuck-chain timeout and flagging
  • Write unit tests for logging, CLI output format, and stuck detection
  • Commit implementation on branch feat/merge-chain-visibility

Definition of Done

This issue is closed when:

  • All state transitions are logged at INFO level
  • CLI command displays full queue status
  • Stuck chains are flagged after configurable timeout
  • 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): add visibility and status reporting for merge-chain state transitions` - **Branch**: `feat/merge-chain-visibility` ## Background and Context Operators need to observe merge-chain state to diagnose stuck, failing, or repeatedly split chains. Without visibility into the queue state and state transitions, operators cannot determine whether the system is working correctly or identify which PRs are causing problems. This issue adds logging, CLI status reporting, and stuck-chain detection. **Parent Epic**: #9757 ## Expected Behavior When this issue is complete, all state transitions are logged at INFO level, a CLI command shows the current queue state, the status report covers open chain, queued chains, active validation, and recent results, and stuck chains are flagged after a configurable timeout. ## Acceptance Criteria - [ ] State transitions are logged at INFO level with relevant context - [ ] CLI command available to view current queue state - [ ] Status report shows: open chain contents, queued chains, active validation, recent results - [ ] Stuck chains are flagged after a configurable timeout period - [ ] Unit tests cover logging, CLI output, and stuck-chain detection ## Subtasks - [ ] Implement INFO-level logging for all state transitions - [ ] Implement CLI command for queue status display - [ ] Implement status report covering all queue sections - [ ] Implement configurable stuck-chain timeout and flagging - [ ] Write unit tests for logging, CLI output format, and stuck detection - [ ] Commit implementation on branch `feat/merge-chain-visibility` ## Definition of Done This issue is closed when: - All state transitions are logged at INFO level - CLI command displays full queue status - Stuck chains are flagged after configurable timeout - 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: Should Have — Visibility into merge-chain state is important \nPriority: Medium\n\nRationale: Status reporting for merge-chain state transitions helps operators understand the merge queue state. Should Have for operational visibility.\n\nLabels to apply: State/Verified, MoSCoW/Should have, Priority/Medium, Type/Feature\n\n---\nAutomated by CleverAgents Bot\nSupervisor: Project Owner | Agent: project-owner-pool-supervisor\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:** Should Have — Visibility into merge-chain state is important \n**Priority:** Medium\n\n**Rationale:** Status reporting for merge-chain state transitions helps operators understand the merge queue state. Should Have for operational visibility.\n\n**Labels to apply:** State/Verified, MoSCoW/Should have, Priority/Medium, Type/Feature\n\n---\n**Automated by CleverAgents Bot**\nSupervisor: Project Owner | Agent: project-owner-pool-supervisor\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#9812
No description provided.