cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

fix(cli): add missing "✓ OK" footer to agents plan errors rich output #9448

Merged
HAL9000 merged 1 commit from fix/plan-errors-missing-ok-footer into master 2026-04-14 21:49:03 +00:00
Conversation 3 Commits 1 Files changed 2 +8
HAL9000 commented 2026-04-14 17:59:11 +00:00
Owner
Copy link

Summary

This PR fixes a formatting issue in the agents plan errors command output where the "✓ OK" footer line was missing from the rich text output. The footer is now consistently printed across all code paths to ensure proper visual formatting of error reports.

Changes

  • Added missing "✓ OK" footer to the agents plan errors rich output
  • Ensured consistent formatting across all error handling code paths:
    • No error recovery scenario
    • Error message only scenario
    • Full error recovery data scenario
  • Improved user experience by providing complete and properly formatted error output

Why This Matters

The "✓ OK" footer is an important visual element in the rich text output that signals the completion of the error report. Its absence was causing incomplete-looking output and inconsistent formatting across different error scenarios.

Testing

The fix has been validated to ensure:

  • The footer appears in all error reporting code paths
  • Rich text formatting remains intact
  • Output is visually consistent regardless of the error type or recovery data available

Issue Reference

Closes #9355

Automated by CleverAgents Bot
Agent: pr-creator

## Summary This PR fixes a formatting issue in the agents plan errors command output where the "✓ OK" footer line was missing from the rich text output. The footer is now consistently printed across all code paths to ensure proper visual formatting of error reports. ## Changes - **Added missing "✓ OK" footer** to the agents plan errors rich output - **Ensured consistent formatting** across all error handling code paths: - No error recovery scenario - Error message only scenario - Full error recovery data scenario - **Improved user experience** by providing complete and properly formatted error output ## Why This Matters The "✓ OK" footer is an important visual element in the rich text output that signals the completion of the error report. Its absence was causing incomplete-looking output and inconsistent formatting across different error scenarios. ## Testing The fix has been validated to ensure: - The footer appears in all error reporting code paths - Rich text formatting remains intact - Output is visually consistent regardless of the error type or recovery data available ## Issue Reference Closes #9355 --- **Automated by CleverAgents Bot** Agent: pr-creator
HAL9000 added this to the v3.2.0 milestone 2026-04-14 17:59:46 +00:00
HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-04-14 18:02:53 +00:00
HAL9000 commented 2026-04-14 18:13:03 +00:00
Author
Owner
Copy link

✅ Triage Decision [AUTO-OWNR-3]: Verified as a valid fix for #9355 (plan errors missing '✓ OK' footer). Adding the missing footer line is Could Have — minor UI completeness issue.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

✅ **Triage Decision [AUTO-OWNR-3]**: Verified as a valid fix for #9355 (plan errors missing '✓ OK' footer). Adding the missing footer line is `Could Have` — minor UI completeness issue. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
HAL9001 approved these changes 2026-04-14 19:39:53 +00:00
HAL9001 left a comment
Copy link

Code Review: APPROVED ✅

Summary

This PR correctly fixes the missing ✓ OK footer in the agents plan errors rich output, as specified in issue #9355. The implementation is minimal, targeted, and well-tested.

Checklist

Criterion Status Notes
Conventional Commit format ✅ fix(cli): add missing "✓ OK" footer to agents plan errors rich output
ISSUES CLOSED footer ✅ ISSUES CLOSED: #9355
PR description Closes #<issue> ✅ Closes #9355
Milestone assigned ✅ v3.2.0
Exactly one Type/* label ✅ Type/Bug
BDD test added ✅ New scenario in features/plan_cli_coverage.feature
All CI checks pass ✅ All 13 jobs succeeded (lint, typecheck, quality, security, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check)
Test coverage ≥ 97% ✅ CI / coverage job passed (15m21s)
Implementation matches spec ✅ Covers all 3 code paths per issue acceptance criteria
Issue state ✅ Issue #9355 in State/In Review

Code Review

src/cleveragents/cli/commands/plan.py — Two additions of console.print("[green]✓ OK[/green]") correctly placed:

  1. Line ~2829: After the "No error recovery records" panel (early-return path) — covers the case where there is no error recovery data and no error message.
  2. Line ~2861: After the main console.print(Panel(...)) call — covers both the "error recovery present" and "error message only" paths, since both fall through to this final panel print.

All three cases from the acceptance criteria are addressed. ✅

features/plan_cli_coverage.feature — New BDD scenario errors command prints OK footer in rich format added, using the existing mocked lifecycle service for plan-cov errors with empty details step and asserting ✓ OK is present in output. ✅

No Issues Found

The change is correct, minimal, and complete. No regressions introduced.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-9448]

## Code Review: APPROVED ✅ ### Summary This PR correctly fixes the missing `✓ OK` footer in the `agents plan errors` rich output, as specified in issue #9355. The implementation is minimal, targeted, and well-tested. --- ### Checklist | Criterion | Status | Notes | |---|---|---| | Conventional Commit format | ✅ | `fix(cli): add missing "✓ OK" footer to agents plan errors rich output` | | ISSUES CLOSED footer | ✅ | `ISSUES CLOSED: #9355` | | PR description `Closes #<issue>` | ✅ | `Closes #9355` | | Milestone assigned | ✅ | v3.2.0 | | Exactly one Type/* label | ✅ | `Type/Bug` | | BDD test added | ✅ | New scenario in `features/plan_cli_coverage.feature` | | All CI checks pass | ✅ | All 13 jobs succeeded (lint, typecheck, quality, security, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check) | | Test coverage ≥ 97% | ✅ | CI / coverage job passed (15m21s) | | Implementation matches spec | ✅ | Covers all 3 code paths per issue acceptance criteria | | Issue state | ✅ | Issue #9355 in `State/In Review` | --- ### Code Review **`src/cleveragents/cli/commands/plan.py`** — Two additions of `console.print("[green]✓ OK[/green]")` correctly placed: 1. **Line ~2829**: After the "No error recovery records" panel (early-return path) — covers the case where there is no error recovery data and no error message. 2. **Line ~2861**: After the main `console.print(Panel(...))` call — covers both the "error recovery present" and "error message only" paths, since both fall through to this final panel print. All three cases from the acceptance criteria are addressed. ✅ **`features/plan_cli_coverage.feature`** — New BDD scenario `errors command prints OK footer in rich format` added, using the existing `mocked lifecycle service for plan-cov errors with empty details` step and asserting `✓ OK` is present in output. ✅ --- ### No Issues Found The change is correct, minimal, and complete. No regressions introduced. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9448]
HAL9001 commented 2026-04-14 19:41:27 +00:00
Owner
Copy link

Code Review Decision: APPROVED ✅

All quality criteria satisfied. The fix correctly adds the missing ✓ OK footer to all three code paths in plan_errors(), a new BDD scenario validates the behavior, and all 13 CI jobs passed (including coverage ≥ 97%).

Key findings:

  • ✅ Conventional Commit format + ISSUES CLOSED: #9355 footer
  • ✅ Closes #9355 in PR description
  • ✅ Milestone v3.2.0 assigned
  • ✅ Exactly one Type/* label (Type/Bug)
  • ✅ BDD scenario added in features/plan_cli_coverage.feature
  • ✅ All 13 CI checks pass (lint, typecheck, quality, security, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check)
  • ✅ Implementation covers all 3 acceptance criteria code paths

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-9448]

**Code Review Decision: APPROVED ✅** All quality criteria satisfied. The fix correctly adds the missing `✓ OK` footer to all three code paths in `plan_errors()`, a new BDD scenario validates the behavior, and all 13 CI jobs passed (including coverage ≥ 97%). **Key findings:** - ✅ Conventional Commit format + `ISSUES CLOSED: #9355` footer - ✅ `Closes #9355` in PR description - ✅ Milestone v3.2.0 assigned - ✅ Exactly one Type/* label (`Type/Bug`) - ✅ BDD scenario added in `features/plan_cli_coverage.feature` - ✅ All 13 CI checks pass (lint, typecheck, quality, security, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, status-check) - ✅ Implementation covers all 3 acceptance criteria code paths --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9448]
HAL9000 force-pushed fix/plan-errors-missing-ok-footer from db9b0c9d06
All checks were successful
CI / push-validation (pull_request) Successful in 20s
Details
CI / helm (pull_request) Successful in 43s
Details
CI / build (pull_request) Successful in 3m21s
Details
CI / lint (pull_request) Successful in 3m22s
Details
CI / quality (pull_request) Successful in 3m43s
Details
CI / integration_tests (pull_request) Successful in 4m1s
Details
CI / typecheck (pull_request) Successful in 4m5s
Details
CI / security (pull_request) Successful in 4m7s
Details
CI / unit_tests (pull_request) Successful in 5m23s
Details
CI / e2e_tests (pull_request) Successful in 6m28s
Details
CI / docker (pull_request) Successful in 1m37s
Details
CI / coverage (pull_request) Successful in 15m21s
Details
CI / status-check (pull_request) Successful in 1s
Details
to 9aad085b74
All checks were successful
CI / push-validation (pull_request) Successful in 19s
Details
CI / helm (pull_request) Successful in 19s
Details
CI / build (pull_request) Successful in 20s
Details
CI / quality (pull_request) Successful in 41s
Details
CI / lint (pull_request) Successful in 47s
Details
CI / typecheck (pull_request) Successful in 53s
Details
CI / security (pull_request) Successful in 1m27s
Details
CI / e2e_tests (pull_request) Successful in 3m39s
Details
CI / integration_tests (pull_request) Successful in 4m10s
Details
CI / unit_tests (pull_request) Successful in 5m56s
Details
CI / docker (pull_request) Successful in 1m21s
Details
CI / coverage (pull_request) Successful in 10m52s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / push-validation (push) Successful in 19s
Details
CI / helm (push) Successful in 23s
Details
CI / build (push) Successful in 28s
Details
CI / e2e_tests (push) Successful in 3m13s
Details
CI / lint (push) Successful in 3m17s
Details
CI / quality (push) Successful in 3m38s
Details
CI / typecheck (push) Successful in 3m57s
Details
CI / security (push) Successful in 4m5s
Details
CI / integration_tests (push) Successful in 6m19s
Details
CI / unit_tests (push) Successful in 7m35s
Details
CI / docker (push) Successful in 1m21s
Details
CI / coverage (push) Successful in 10m48s
Details
CI / status-check (push) Successful in 1s
Details
2026-04-14 21:36:40 +00:00 Compare
HAL9000 merged commit 9aad085b74 into master 2026-04-14 21:49:03 +00:00
hurui200320 deleted branch fix/plan-errors-missing-ok-footer 2026-04-15 04:01:26 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.2.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#9355 bug(cli): agents plan errors missing "✓ OK" footer line after Plan Errors panel
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core!9448
No description provided.