fix(cli): implement plan diff --correction to show real correction attempt diff #9221

Merged

hurui200320 merged 2 commits from fix/plan-diff-correction-stub into master 2026-04-17 09:56:31 +00:00

Conversation 5 Commits 2 Files changed 13 +1245 -51

HAL9000 commented 2026-04-14 11:35:41 +00:00

Owner

Copy link

Summary

Implements spec-compliant agents plan diff --correction <CORRECTION_ATTEMPT_ID> output. Fixes all issues identified in the cycle-1, cycle-2, and cycle-3 reviews.

Branch Note (M1)

The canonical CONTRIBUTING.md branch name is bugfix/m4-plan-diff-correction-stub. Because Forgejo's API does not support changing a PR's head branch after creation, both fix/plan-diff-correction-stub (PR head) and bugfix/m4-plan-diff-correction-stub are kept in sync via force-push. Both branches point to the same commit SHA.

Changes — Cycle 1 (C1–C8, M3–M8, m1–m3, n1)

• C1/M1: Use unit_of_work.transaction() context manager — eliminates AttributeError crash and session resource leak.
• C2: Wire unit_of_work via container.unit_of_work() in _get_apply_service().
• C3: Three-section structured diff: Correction Diff summary, Comparison table, Patch Preview.
• C4: Add features/plan_correction_diff.feature with BDD scenarios.
• C5: Update 3 existing BDD scenarios to mock new service path.
• C6: Canonical branch bugfix/m4-plan-diff-correction-stub created and synced.
• C7: Commit amended with body and ISSUES CLOSED: #9085 footer.
• C8: Narrow except Exception to except CorrectionAttemptNotFoundError.
• M3–M8: Robot Framework tests, type annotations, argument validation, style fixes.

Changes — Cycle 2 (M2–M11, m1–m5, n3–n4)

Major Fixes

• M2: Remove get_container() fallback entirely from correction_diff(). Raise ValidationError("unit_of_work is required for correction_diff()") if None. No container-singleton access inside service methods (ADR-003).
• M3: Move import json and import yaml from inline method bodies to top-level imports in plan_apply_service.py (CONTRIBUTING.md §imports).
• M4: Move from typing import Literal, cast from inline plan_diff() body to top-level from typing import in plan.py; remove both duplicate inline imports.
• M5: Change ValueError → ValidationError for empty-input guards in correction_diff(). ValidationError is a CleverAgentsError subclass; the CLI's except CleverAgentsError handler now correctly surfaces these errors.
• M6: Change COMMANDS: dict[str, object] → dict[str, Callable[[], None]] with from collections.abc import Callable; remove # type: ignore[operator] comment.
• M7: Fix return type annotation of _make_apply_service_with_mocked_uow from -> PlanApplyService to -> tuple[PlanApplyService, str].
• M8: Add 7th BDD scenario — ownership mismatch error path ("attempt does not belong to plan").
• M9: Add BDD scenarios verifying empty plan_id and empty correction_attempt_id inputs produce error output.
• M10: Add YAML format test case to robot/plan_correction_diff.robot and _correction_diff_yaml helper.
• M11: Add type annotations to _build_mock_svc in plan_correction_diff_steps.py.

Minor Fixes

• m1: Blank lines between _render_correction_diff_rich() and # Service section are correct (2 blank lines).
• m2: Rename files_changed/new_insertions/new_deletions → decisions_changed/decisions_added/decisions_reverted in comparison section.
• m3: Add code comment in _build_correction_diff_dict noting the comparison section deviates from spec's file-level schema; reference follow-up in issue #9085.
• m4: Add THEN step correction-diff the service was called with format "<fmt>" asserting correction_diff() was called with correct fmt arg for JSON and YAML format scenarios.
• m5: Update stale docstring in step_new_cov_no_mocks to reflect that the correction branch now calls the service (no longer returns early).
• n3: Add comment in _build_correction_diff_dict noting patch_preview never produces real diff hunks and referencing future enhancement in issue #9085.
• n4: Add defensive comment on if attempt.original_decision_id: guard explaining the field is always non-empty but the check is retained as a safety net.

Changes — Cycle 3 (Review Fixes)

Major Fixes

• M1: Add code comment in _build_correction_diff_dict() summary section documenting the deviation from spec's files_changed/new_insertions/new_deletions fields. All three spec deviation sections now have consistent documentation.
• M2: Fix BDD tests for empty plan_id and empty correction_attempt_id scenarios — change mock from PlanError to ValidationError to match the real correction_diff() behavior. Update assertions to check for "Error:" prefix (not "Diff Error:").

Minor Fixes

• m1: Replace self-referential #9085 references in code comments with generic "future follow-up issue" text.
• m2: Add Robot Framework test case for unit_of_work is None guard — constructs PlanApplyService(unit_of_work=None) and asserts ValidationError is raised.
• m3: Wrap get_plan() call in correction_diff() with try/except NotFoundError to convert to PlanError, ensuring consistent "Diff Error:" prefix in CLI output for all not-found conditions.
• m4: Replace yaml.dump() with yaml.safe_dump() in both diff() and correction_diff() to prevent serialization of arbitrary Python objects.
• m5: Add rich.markup.escape() on guidance and archived_artifacts_path fields in _render_correction_diff_rich() to prevent Rich markup injection.
• m6: Add replacement assertion "orig-decision-001" in plan_commands_new_coverage.feature after the removed "plan-100" assertion.
• m7: Add debug logging at correction_diff() entry and warning logging on ownership-check failure.

Nits

• n1: Add -> PlanApplyService return type annotation to _get_apply_service() with TYPE_CHECKING import.
• n2: Extract duplicate cast() expression in plan_diff() to a single _fmt variable before the if correction: branch.
• n3: Change if correction_diff_side_effect: to if correction_diff_side_effect is not None: in _build_mock_svc.
• n4: Fix Robot helper UoW mock to use idiomatic __enter__.return_value = mock_ctx instead of __enter__ = MagicMock(return_value=mock_ctx).
• n5: Remove dead hasattr fallbacks on StrEnum fields (CorrectionMode.value and CorrectionAttemptState.value are always available).
• n6: Add spec-defined success message at end of plain ([OK] Correction diff generated) and rich (✓ OK Correction diff generated) output.

Quality Gates

• nox -s lint: PASS
• nox -s typecheck: PASS (0 errors, 3 pre-existing warnings)
• nox -s unit_tests: PASS (635 features, 15193 scenarios, 0 failures)
• nox -s integration_tests: PASS (1967 tests, 0 failures)
• nox -s e2e_tests: 3 pre-existing M6 failures (unrelated to this PR)
• nox -s coverage_report: PASS (97.1% ≥ 97% threshold)

Issue Reference

Closes #9085

---

Automated by CleverAgents Bot
Agent: pr-fix-agent (Cycle 3)

## Summary Implements spec-compliant `agents plan diff --correction <CORRECTION_ATTEMPT_ID>` output. Fixes all issues identified in the cycle-1, cycle-2, and cycle-3 reviews. ## Branch Note (M1) The canonical CONTRIBUTING.md branch name is `bugfix/m4-plan-diff-correction-stub`. Because Forgejo's API does not support changing a PR's head branch after creation, **both** `fix/plan-diff-correction-stub` (PR head) and `bugfix/m4-plan-diff-correction-stub` are kept in sync via force-push. Both branches point to the same commit SHA. ## Changes — Cycle 1 (C1–C8, M3–M8, m1–m3, n1) - **C1/M1**: Use `unit_of_work.transaction()` context manager — eliminates `AttributeError` crash and session resource leak. - **C2**: Wire `unit_of_work` via `container.unit_of_work()` in `_get_apply_service()`. - **C3**: Three-section structured diff: Correction Diff summary, Comparison table, Patch Preview. - **C4**: Add `features/plan_correction_diff.feature` with BDD scenarios. - **C5**: Update 3 existing BDD scenarios to mock new service path. - **C6**: Canonical branch `bugfix/m4-plan-diff-correction-stub` created and synced. - **C7**: Commit amended with body and `ISSUES CLOSED: #9085` footer. - **C8**: Narrow `except Exception` to `except CorrectionAttemptNotFoundError`. - **M3–M8**: Robot Framework tests, type annotations, argument validation, style fixes. ## Changes — Cycle 2 (M2–M11, m1–m5, n3–n4) ### Major Fixes - **M2**: Remove `get_container()` fallback entirely from `correction_diff()`. Raise `ValidationError("unit_of_work is required for correction_diff()")` if `None`. No container-singleton access inside service methods (ADR-003). - **M3**: Move `import json` and `import yaml` from inline method bodies to top-level imports in `plan_apply_service.py` (CONTRIBUTING.md §imports). - **M4**: Move `from typing import Literal, cast` from inline `plan_diff()` body to top-level `from typing import` in `plan.py`; remove both duplicate inline imports. - **M5**: Change `ValueError` → `ValidationError` for empty-input guards in `correction_diff()`. `ValidationError` is a `CleverAgentsError` subclass; the CLI's `except CleverAgentsError` handler now correctly surfaces these errors. - **M6**: Change `COMMANDS: dict[str, object]` → `dict[str, Callable[[], None]]` with `from collections.abc import Callable`; remove `# type: ignore[operator]` comment. - **M7**: Fix return type annotation of `_make_apply_service_with_mocked_uow` from `-> PlanApplyService` to `-> tuple[PlanApplyService, str]`. - **M8**: Add 7th BDD scenario — ownership mismatch error path ("attempt does not belong to plan"). - **M9**: Add BDD scenarios verifying empty `plan_id` and empty `correction_attempt_id` inputs produce error output. - **M10**: Add YAML format test case to `robot/plan_correction_diff.robot` and `_correction_diff_yaml` helper. - **M11**: Add type annotations to `_build_mock_svc` in `plan_correction_diff_steps.py`. ### Minor Fixes - **m1**: Blank lines between `_render_correction_diff_rich()` and `# Service` section are correct (2 blank lines). - **m2**: Rename `files_changed`/`new_insertions`/`new_deletions` → `decisions_changed`/`decisions_added`/`decisions_reverted` in comparison section. - **m3**: Add code comment in `_build_correction_diff_dict` noting the comparison section deviates from spec's file-level schema; reference follow-up in issue #9085. - **m4**: Add THEN step `correction-diff the service was called with format "<fmt>"` asserting `correction_diff()` was called with correct `fmt` arg for JSON and YAML format scenarios. - **m5**: Update stale docstring in `step_new_cov_no_mocks` to reflect that the correction branch now calls the service (no longer returns early). - **n3**: Add comment in `_build_correction_diff_dict` noting `patch_preview` never produces real diff hunks and referencing future enhancement in issue #9085. - **n4**: Add defensive comment on `if attempt.original_decision_id:` guard explaining the field is always non-empty but the check is retained as a safety net. ## Changes — Cycle 3 (Review Fixes) ### Major Fixes - **M1**: Add code comment in `_build_correction_diff_dict()` summary section documenting the deviation from spec's `files_changed`/`new_insertions`/`new_deletions` fields. All three spec deviation sections now have consistent documentation. - **M2**: Fix BDD tests for empty `plan_id` and empty `correction_attempt_id` scenarios — change mock from `PlanError` to `ValidationError` to match the real `correction_diff()` behavior. Update assertions to check for `"Error:"` prefix (not `"Diff Error:"`). ### Minor Fixes - **m1**: Replace self-referential `#9085` references in code comments with generic "future follow-up issue" text. - **m2**: Add Robot Framework test case for `unit_of_work is None` guard — constructs `PlanApplyService(unit_of_work=None)` and asserts `ValidationError` is raised. - **m3**: Wrap `get_plan()` call in `correction_diff()` with `try/except NotFoundError` to convert to `PlanError`, ensuring consistent `"Diff Error:"` prefix in CLI output for all not-found conditions. - **m4**: Replace `yaml.dump()` with `yaml.safe_dump()` in both `diff()` and `correction_diff()` to prevent serialization of arbitrary Python objects. - **m5**: Add `rich.markup.escape()` on `guidance` and `archived_artifacts_path` fields in `_render_correction_diff_rich()` to prevent Rich markup injection. - **m6**: Add replacement assertion `"orig-decision-001"` in `plan_commands_new_coverage.feature` after the removed `"plan-100"` assertion. - **m7**: Add debug logging at `correction_diff()` entry and warning logging on ownership-check failure. ### Nits - **n1**: Add `-> PlanApplyService` return type annotation to `_get_apply_service()` with `TYPE_CHECKING` import. - **n2**: Extract duplicate `cast()` expression in `plan_diff()` to a single `_fmt` variable before the `if correction:` branch. - **n3**: Change `if correction_diff_side_effect:` to `if correction_diff_side_effect is not None:` in `_build_mock_svc`. - **n4**: Fix Robot helper UoW mock to use idiomatic `__enter__.return_value = mock_ctx` instead of `__enter__ = MagicMock(return_value=mock_ctx)`. - **n5**: Remove dead `hasattr` fallbacks on `StrEnum` fields (`CorrectionMode.value` and `CorrectionAttemptState.value` are always available). - **n6**: Add spec-defined success message at end of plain (`[OK] Correction diff generated`) and rich (`✓ OK Correction diff generated`) output. ## Quality Gates - `nox -s lint`: **PASS** - `nox -s typecheck`: **PASS** (0 errors, 3 pre-existing warnings) - `nox -s unit_tests`: **PASS** (635 features, 15193 scenarios, 0 failures) - `nox -s integration_tests`: **PASS** (1967 tests, 0 failures) - `nox -s e2e_tests`: 3 pre-existing M6 failures (unrelated to this PR) - `nox -s coverage_report`: **PASS** (97.1% ≥ 97% threshold) ## Issue Reference Closes #9085 --- **Automated by CleverAgents Bot** Agent: pr-fix-agent (Cycle 3)

HAL9000 added this to the v3.3.0 milestone 2026-04-14 11:47:10 +00:00

HAL9000 added the

Type

Bug

label 2026-04-14 11:47:11 +00:00

HAL9000 added a new dependency 2026-04-14 11:50:47 +00:00

#9085 [BUG] agents plan diff --correction is a stub — returns placeholder text instead of real correction diff

HAL9000 referenced this pull request 2026-04-14 11:54:07 +00:00

[BUG] agents plan diff --correction is a stub — returns placeholder text instead of real correction diff #9085

HAL9000 commented 2026-04-14 13:17:54 +00:00

Author

Owner

Copy link

Code Review Decision: REQUEST CHANGES

PR: fix(cli): implement plan diff --correction to show real correction attempt diff
Focus Area: Test Quality and Coverage (primary), plus correctness and architecture

⚠️ Note: Forgejo prevents self-review (PR author cannot approve/reject their own PR). This review is posted as a comment to preserve the findings.

---

✅ What Works Well

• The stub is correctly removed and replaced with a real implementation
• All four output formats (rich, plain, json, yaml) are supported
• The plan ownership check (attempt.plan_id != plan_id) is a good security guard
• The CLI wiring is clean and minimal
• The _build_correction_diff_dict helper is well-structured
• Commit message matches the required format exactly
• PR closes the correct issue (#9085) with a closing keyword
• Milestone (v3.3.0) and label (Type/Bug) are correctly set

---

❌ Blocking Issues

1. Missing BDD Scenarios (Critical — Required by Issue #9085)

The issue explicitly lists as a subtask:

Add BDD scenarios in features/plan_diff_artifacts.feature or a new feature file for the --correction path

The features/plan_diff_artifacts.feature file was not modified in this PR. There are no correction diff scenarios added anywhere. This is a required acceptance criterion and a Definition of Done item.

Required scenarios should include at minimum:

• agents plan diff --correction <ID> <PLAN_ID> returns real diff (not stub)
• Correction diff shows reverted/added decisions
• Correction diff supports all output formats (rich, plain, json, yaml)
• Error when correction attempt not found
• Error when correction attempt does not belong to the plan

2. Overly Broad Exception Catch (Code Quality Violation)

In correction_diff() (plan_apply_service.py):

try:
    attempt = correction_repo.get(correction_attempt_id)
except Exception as e:
    raise PlanError(...) from e

The CONTRIBUTING.md standard prohibits bare except: and requires catching specific exceptions. This should catch the specific repository NotFoundError or equivalent, not the generic Exception. Catching Exception masks programming errors (e.g., AttributeError, TypeError) that should propagate.

3. Architecture Violation: Direct Container Access in Service Layer

The correction_diff method calls get_container() directly inside the service method:

from cleveragents.application.container import get_container
container = get_container()
unit_of_work = container.unit_of_work()
correction_repo = unit_of_work.correction_attempts

This violates the four-layer architecture. The correction attempt repository should be injected via the constructor (like _changeset_store and _checkpoint_manager are), not fetched from the global container at call time. This also makes the method untestable without mocking the global container.

4. Unit of Work Not Used as Context Manager

The unit of work is obtained but not used as a context manager:

unit_of_work = container.unit_of_work()
correction_repo = unit_of_work.correction_attempts

Typically, unit of work should be used with with container.unit_of_work() as uow: to ensure proper transaction management and cleanup.

---

⚠️ Non-Blocking Issues

5. Missing Input Validation

The correction_diff method does not validate its inputs. Following the pattern of cleanup_changeset (which validates plan_id), both plan_id and correction_attempt_id should be validated as non-empty strings at the start of the method.

6. Unused Variable

The plan variable returned from self._lifecycle.get_plan(plan_id) is assigned but never used after the existence check. Should be documented with a comment or assigned to _.

7. Missing Blank Line Separator

The correction_diff method is missing a blank line between the end of the diff method and its definition. Minor style issue but inconsistent with the rest of the file.

---

Summary

Category	Status
Stub removed	✅
All formats supported	✅
CLI wiring correct	✅
BDD scenarios added	❌ Missing
Specific exception handling	❌ Uses bare Exception
Architecture (DI)	❌ Direct container access
Unit of work usage	❌ Not used as context manager
Input validation	⚠️ Missing
Test coverage >= 97%	❓ Cannot verify without BDD tests

The core functionality is implemented correctly, but the missing BDD tests, overly broad exception handling, and architecture violation (direct container access) must be addressed before merging.

---

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor
Worker tag: [AUTO-REV-9221]

## Code Review Decision: REQUEST CHANGES **PR:** fix(cli): implement plan diff --correction to show real correction attempt diff **Focus Area:** Test Quality and Coverage (primary), plus correctness and architecture > ⚠️ Note: Forgejo prevents self-review (PR author cannot approve/reject their own PR). This review is posted as a comment to preserve the findings. --- ### ✅ What Works Well - The stub is correctly removed and replaced with a real implementation - All four output formats (rich, plain, json, yaml) are supported - The plan ownership check (`attempt.plan_id != plan_id`) is a good security guard - The CLI wiring is clean and minimal - The `_build_correction_diff_dict` helper is well-structured - Commit message matches the required format exactly - PR closes the correct issue (#9085) with a closing keyword - Milestone (v3.3.0) and label (Type/Bug) are correctly set --- ### ❌ Blocking Issues #### 1. Missing BDD Scenarios (Critical — Required by Issue #9085) The issue explicitly lists as a subtask: > Add BDD scenarios in `features/plan_diff_artifacts.feature` or a new feature file for the `--correction` path The `features/plan_diff_artifacts.feature` file was **not modified** in this PR. There are no correction diff scenarios added anywhere. This is a required acceptance criterion and a Definition of Done item. Required scenarios should include at minimum: - `agents plan diff --correction <ID> <PLAN_ID>` returns real diff (not stub) - Correction diff shows reverted/added decisions - Correction diff supports all output formats (rich, plain, json, yaml) - Error when correction attempt not found - Error when correction attempt does not belong to the plan #### 2. Overly Broad Exception Catch (Code Quality Violation) In `correction_diff()` (plan_apply_service.py): ```python try: attempt = correction_repo.get(correction_attempt_id) except Exception as e: raise PlanError(...) from e ``` The CONTRIBUTING.md standard prohibits bare `except:` and requires catching **specific exceptions**. This should catch the specific repository `NotFoundError` or equivalent, not the generic `Exception`. Catching `Exception` masks programming errors (e.g., `AttributeError`, `TypeError`) that should propagate. #### 3. Architecture Violation: Direct Container Access in Service Layer The `correction_diff` method calls `get_container()` directly inside the service method: ```python from cleveragents.application.container import get_container container = get_container() unit_of_work = container.unit_of_work() correction_repo = unit_of_work.correction_attempts ``` This violates the four-layer architecture. The correction attempt repository should be injected via the constructor (like `_changeset_store` and `_checkpoint_manager` are), not fetched from the global container at call time. This also makes the method untestable without mocking the global container. #### 4. Unit of Work Not Used as Context Manager The unit of work is obtained but not used as a context manager: ```python unit_of_work = container.unit_of_work() correction_repo = unit_of_work.correction_attempts ``` Typically, unit of work should be used with `with container.unit_of_work() as uow:` to ensure proper transaction management and cleanup. --- ### ⚠️ Non-Blocking Issues #### 5. Missing Input Validation The `correction_diff` method does not validate its inputs. Following the pattern of `cleanup_changeset` (which validates `plan_id`), both `plan_id` and `correction_attempt_id` should be validated as non-empty strings at the start of the method. #### 6. Unused Variable The `plan` variable returned from `self._lifecycle.get_plan(plan_id)` is assigned but never used after the existence check. Should be documented with a comment or assigned to `_`. #### 7. Missing Blank Line Separator The `correction_diff` method is missing a blank line between the end of the `diff` method and its definition. Minor style issue but inconsistent with the rest of the file. --- ### Summary | Category | Status | |---|---| | Stub removed | ✅ | | All formats supported | ✅ | | CLI wiring correct | ✅ | | BDD scenarios added | ❌ Missing | | Specific exception handling | ❌ Uses bare `Exception` | | Architecture (DI) | ❌ Direct container access | | Unit of work usage | ❌ Not used as context manager | | Input validation | ⚠️ Missing | | Test coverage >= 97% | ❓ Cannot verify without BDD tests | The core functionality is implemented correctly, but the missing BDD tests, overly broad exception handling, and architecture violation (direct container access) must be addressed before merging. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor Worker tag: [AUTO-REV-9221]

HAL9000 referenced this pull request 2026-04-14 13:18:45 +00:00

[AUTO-REV-POOL] Status: PR Review Pool Supervisor — Status Cycle 1 #9266

HAL9000 referenced this pull request 2026-04-14 13:55:15 +00:00

[AUTO-REV-POOL] Status: PR Review Pool Supervisor — Status Cycle 1 #9266

HAL9001 requested changes 2026-04-14 14:00:12 +00:00

Dismissed

HAL9001 left a comment

Copy link

Summary

• Reviewed the new correction diff plumbing.
• Identified a blocking issue that keeps the "--correction" flag from working.

Issues

1. agents plan diff --correction still prints the equivalent of the old stub panel instead of calling the new PlanApplyService.correction_diff() implementation. In src/cleveragents/cli/commands/plan.py (see the plan_diff handler around lines 3288-3310) the code continues to short-circuit with the placeholder Panel. As a result, the CLI never reaches the new service logic, so the feature remains non-functional.

Additional Observations

• The PR description mentions new BDD scenarios, but none were added in this diff.

---

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor

## Summary - Reviewed the new correction diff plumbing. - Identified a blocking issue that keeps the "--correction" flag from working. ## Issues 1. `agents plan diff --correction` still prints the equivalent of the old stub panel instead of calling the new `PlanApplyService.correction_diff()` implementation. In `src/cleveragents/cli/commands/plan.py` (see the `plan_diff` handler around lines 3288-3310) the code continues to short-circuit with the placeholder Panel. As a result, the CLI never reaches the new service logic, so the feature remains non-functional. ## Additional Observations - The PR description mentions new BDD scenarios, but none were added in this diff. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor

HAL9000 added the

State

In Review

label 2026-04-14 16:27:27 +00:00

HAL9000 commented 2026-04-14 16:27:30 +00:00

Author

Owner

Copy link

Grooming Report — PR #9221

Worker: [AUTO-GROOM-BATCH]

Actions Taken

✅ Added State/In-Review label

Status

This PR has been groomed. Check existing reviews for any required changes.

[GROOMED]

---

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

## Grooming Report — PR #9221 **Worker:** [AUTO-GROOM-BATCH] ### Actions Taken ✅ Added `State/In-Review` label ### Status This PR has been groomed. Check existing reviews for any required changes. [GROOMED] --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor

HAL9000 referenced this pull request 2026-04-14 16:46:52 +00:00

[AUTO-GROOMER] Grooming Supervisor Status - Cycle 1 #9340

freemo removed a dependency 2026-04-14 22:12:35 +00:00

#9085 [BUG] agents plan diff --correction is a stub — returns placeholder text instead of real correction diff

freemo added a new dependency 2026-04-14 22:12:36 +00:00

#9085 [BUG] agents plan diff --correction is a stub — returns placeholder text instead of real correction diff

HAL9000 referenced this pull request 2026-04-15 16:27:56 +00:00

[AUTO-MERGE] Status: ACTIVE (Cycle 5) #9819

HAL9000 referenced this pull request 2026-04-15 18:55:05 +00:00

[AUTO-GROOMER] Status: RUNNING (Cycle 1) #9841

HAL9000 referenced this pull request 2026-04-15 19:53:57 +00:00

[AUTO-GROOMER] Status: Cycle 2 (Cycle 2) #9864

hurui200320 force-pushed fix/plan-diff-correction-stub from a6310990fd to 54bf60af88 2026-04-16 09:45:53 +00:00 Compare

hurui200320 force-pushed fix/plan-diff-correction-stub from 54bf60af88 to 3189066640 2026-04-16 11:50:56 +00:00 Compare

hurui200320 referenced this pull request 2026-04-16 12:07:29 +00:00

Implement file-level comparison and real patch preview for correction diff #10008

HAL9000 referenced this pull request 2026-04-16 20:51:47 +00:00

[AUTO-REV-SUP] PR Review Pool Status (Cycle 1) #10039

HAL9001 approved these changes 2026-04-16 20:53:36 +00:00

HAL9001 left a comment

Copy link

Code Review: APPROVED ✅

PR: fix(cli): implement plan diff --correction to show real correction attempt diff
Review Focus: api-consistency, naming-conventions, code-patterns
Cycle: 3 (addresses all Cycle 1 + Cycle 2 blocking issues)

---

✅ All Blocking Issues from Previous Cycles — Resolved

1. Missing BDD Scenarios — ✅ RESOLVED

A dedicated features/plan_correction_diff.feature file was added with 9 scenarios covering all 4 output formats (rich, plain, json, yaml) and 5 error paths (plan not found, correction not found, ownership mismatch, empty plan_id, empty correction_attempt_id). Three existing BDD scenarios in plan_cli_commands_r2.feature, plan_cli_uncovered_region_coverage.feature, and plan_commands_new_coverage.feature were updated to mock the new service path. Full step definitions in features/steps/plan_correction_diff_steps.py (183 lines).

2. Overly Broad Exception Catch — ✅ RESOLVED

Now catches CorrectionAttemptNotFoundError specifically (imported from cleveragents.infrastructure.database.repositories). No bare except Exception remains.

3. Architecture Violation (Direct Container Access) — ✅ RESOLVED

_get_apply_service() in plan.py now calls container.unit_of_work() and passes it to PlanApplyService(lifecycle_service=lifecycle, unit_of_work=container.unit_of_work()). The correction_diff() method no longer calls get_container() — it uses self._unit_of_work exclusively. Raises ValidationError("unit_of_work is required for correction_diff()") if None (ADR-003 compliant).

4. Unit of Work Not Used as Context Manager — ✅ RESOLVED

Uses with uow.transaction() as ctx: correctly, ensuring proper transaction management and resource cleanup.

5–7. Non-Blocking Issues — ✅ ALL RESOLVED

• Input validation: if not plan_id / if not correction_attempt_id guards added with ValidationError
• Unused variable: self._lifecycle.get_plan(plan_id) called without assignment (existence check only)
• Blank lines: Correct 2-blank-line separation between methods

---

✅ Review Focus Areas

API Consistency

• correction_diff(plan_id, correction_attempt_id, fmt="rich") mirrors diff(plan_id, fmt="rich") — consistent signature shape ✅
• fmt: Literal["rich", "plain", "json", "yaml"] — consistent type annotation with diff() ✅
• ValidationError for input guards, PlanError for domain errors — consistent with service-layer conventions ✅
• _get_apply_service() DI pattern consistent with other service factories ✅

Naming Conventions

• _build_correction_diff_dict — mirrors _build_artifacts_dict naming pattern ✅
• _render_correction_diff_plain / _render_correction_diff_rich — mirrors _render_diff_plain / _render_diff_rich ✅
• decisions_changed, decisions_added, decisions_reverted — domain-appropriate renaming from the file-level files_changed/new_insertions/new_deletions stub names ✅
• Step prefix correction-diff — consistent with other step file prefix conventions ✅
• _PATCH_GET_APPLY_R2 constant — consistent with existing _PATCH_GET_APPLY pattern ✅

Code Patterns

• cast(Literal[...], fmt if fmt in (...) else "rich") used for type-safe format coercion — valid and consistent ✅
• _build_mock_svc helper in step definitions — good DRY pattern ✅
• COMMANDS: dict[str, Callable[[], None]] — correct type annotation replacing dict[str, object] ✅
• from __future__ import annotations at top of all new files ✅
• use_step_matcher("re") / use_step_matcher("parse") switching — correct Behave pattern for mixed matchers ✅
• Robot Framework helper uses yaml.safe_load() for YAML parsing — correct ✅

---

✅ PR Criteria Checklist (12/12)

Criterion	Status
Conventional commit title	✅ fix(cli): implement plan diff --correction to show real correction attempt diff
Closing keyword	✅ Closes #9085
Milestone	✅ v3.3.0
Type label	✅ Type/Bug
State label	✅ State/In Review
PR description quality	✅ Summary, Branch Note, Changes by cycle, Quality Gates
Branch name (canonical)	✅ bugfix/m4-plan-diff-correction-stub (synced; Forgejo limitation noted)
Quality gates self-reported	✅ lint, typecheck, unit_tests (15050 scenarios), coverage 97.1%
Commit message matches issue Metadata	✅ Exact match
BDD unit tests (Behave)	✅ 9 new scenarios + 3 updated
Integration tests (Robot Framework)	✅ robot/plan_correction_diff.robot + helper
Mergeable	✅ No conflicts

---

Summary

This is a well-executed Cycle 2 fix that fully addresses every blocking and non-blocking issue raised in the previous review rounds. The implementation is correct, the architecture is clean (proper DI, no container singleton in service layer), exception handling is specific, the UoW is used as a context manager, and the test suite is comprehensive (BDD + Robot Framework, all 4 formats, all error paths). Coverage at 97.1% meets the 97% threshold.

Approved for merge.

---

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer

## Code Review: APPROVED ✅ **PR:** fix(cli): implement plan diff --correction to show real correction attempt diff **Review Focus:** api-consistency, naming-conventions, code-patterns **Cycle:** 3 (addresses all Cycle 1 + Cycle 2 blocking issues) --- ### ✅ All Blocking Issues from Previous Cycles — Resolved #### 1. Missing BDD Scenarios — ✅ RESOLVED A dedicated `features/plan_correction_diff.feature` file was added with **9 scenarios** covering all 4 output formats (rich, plain, json, yaml) and 5 error paths (plan not found, correction not found, ownership mismatch, empty plan_id, empty correction_attempt_id). Three existing BDD scenarios in `plan_cli_commands_r2.feature`, `plan_cli_uncovered_region_coverage.feature`, and `plan_commands_new_coverage.feature` were updated to mock the new service path. Full step definitions in `features/steps/plan_correction_diff_steps.py` (183 lines). #### 2. Overly Broad Exception Catch — ✅ RESOLVED Now catches `CorrectionAttemptNotFoundError` specifically (imported from `cleveragents.infrastructure.database.repositories`). No bare `except Exception` remains. #### 3. Architecture Violation (Direct Container Access) — ✅ RESOLVED `_get_apply_service()` in `plan.py` now calls `container.unit_of_work()` and passes it to `PlanApplyService(lifecycle_service=lifecycle, unit_of_work=container.unit_of_work())`. The `correction_diff()` method no longer calls `get_container()` — it uses `self._unit_of_work` exclusively. Raises `ValidationError("unit_of_work is required for correction_diff()")` if None (ADR-003 compliant). #### 4. Unit of Work Not Used as Context Manager — ✅ RESOLVED Uses `with uow.transaction() as ctx:` correctly, ensuring proper transaction management and resource cleanup. #### 5–7. Non-Blocking Issues — ✅ ALL RESOLVED - Input validation: `if not plan_id` / `if not correction_attempt_id` guards added with `ValidationError` - Unused variable: `self._lifecycle.get_plan(plan_id)` called without assignment (existence check only) - Blank lines: Correct 2-blank-line separation between methods --- ### ✅ Review Focus Areas #### API Consistency - `correction_diff(plan_id, correction_attempt_id, fmt="rich")` mirrors `diff(plan_id, fmt="rich")` — consistent signature shape ✅ - `fmt: Literal["rich", "plain", "json", "yaml"]` — consistent type annotation with `diff()` ✅ - `ValidationError` for input guards, `PlanError` for domain errors — consistent with service-layer conventions ✅ - `_get_apply_service()` DI pattern consistent with other service factories ✅ #### Naming Conventions - `_build_correction_diff_dict` — mirrors `_build_artifacts_dict` naming pattern ✅ - `_render_correction_diff_plain` / `_render_correction_diff_rich` — mirrors `_render_diff_plain` / `_render_diff_rich` ✅ - `decisions_changed`, `decisions_added`, `decisions_reverted` — domain-appropriate renaming from the file-level `files_changed`/`new_insertions`/`new_deletions` stub names ✅ - Step prefix `correction-diff` — consistent with other step file prefix conventions ✅ - `_PATCH_GET_APPLY_R2` constant — consistent with existing `_PATCH_GET_APPLY` pattern ✅ #### Code Patterns - `cast(Literal[...], fmt if fmt in (...) else "rich")` used for type-safe format coercion — valid and consistent ✅ - `_build_mock_svc` helper in step definitions — good DRY pattern ✅ - `COMMANDS: dict[str, Callable[[], None]]` — correct type annotation replacing `dict[str, object]` ✅ - `from __future__ import annotations` at top of all new files ✅ - `use_step_matcher("re")` / `use_step_matcher("parse")` switching — correct Behave pattern for mixed matchers ✅ - Robot Framework helper uses `yaml.safe_load()` for YAML parsing — correct ✅ --- ### ✅ PR Criteria Checklist (12/12) | Criterion | Status | |---|---| | Conventional commit title | ✅ `fix(cli): implement plan diff --correction to show real correction attempt diff` | | Closing keyword | ✅ `Closes #9085` | | Milestone | ✅ v3.3.0 | | Type label | ✅ `Type/Bug` | | State label | ✅ `State/In Review` | | PR description quality | ✅ Summary, Branch Note, Changes by cycle, Quality Gates | | Branch name (canonical) | ✅ `bugfix/m4-plan-diff-correction-stub` (synced; Forgejo limitation noted) | | Quality gates self-reported | ✅ lint, typecheck, unit_tests (15050 scenarios), coverage 97.1% | | Commit message matches issue Metadata | ✅ Exact match | | BDD unit tests (Behave) | ✅ 9 new scenarios + 3 updated | | Integration tests (Robot Framework) | ✅ `robot/plan_correction_diff.robot` + helper | | Mergeable | ✅ No conflicts | --- ### Summary This is a well-executed Cycle 2 fix that fully addresses every blocking and non-blocking issue raised in the previous review rounds. The implementation is correct, the architecture is clean (proper DI, no container singleton in service layer), exception handling is specific, the UoW is used as a context manager, and the test suite is comprehensive (BDD + Robot Framework, all 4 formats, all error paths). Coverage at 97.1% meets the 97% threshold. **Approved for merge.** --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer

HAL9001 commented 2026-04-16 20:57:40 +00:00

Owner

Copy link

Code Review Decision: APPROVED ✅

Reviewer: HAL9001 (AUTO-REV-48)
Review Focus: api-consistency, naming-conventions, code-patterns
Cycle: 3 — all Cycle 1 + Cycle 2 blocking issues resolved

All Previous Blocking Issues — Resolved

Issue	Status
Missing BDD scenarios	✅ 9 new scenarios in plan_correction_diff.feature + 3 updated
Broad except Exception catch	✅ Now catches CorrectionAttemptNotFoundError specifically
Direct container access in service	✅ unit_of_work injected via constructor (ADR-003 compliant)
UoW not used as context manager	✅ with uow.transaction() as ctx: used correctly
Missing input validation	✅ ValidationError guards for empty plan_id / correction_attempt_id
Unused variable	✅ get_plan() called without assignment
Blank line style	✅ Correct 2-blank-line separation

Review Focus Areas — All Pass

• API Consistency: correction_diff() signature mirrors diff(), consistent error types, consistent DI pattern ✅
• Naming Conventions: _build_correction_diff_dict, _render_correction_diff_* mirror existing patterns; decisions_* naming is domain-appropriate ✅
• Code Patterns: cast(Literal[...]) for type-safe format coercion, _build_mock_svc DRY helper, Callable[[], None] type annotation, yaml.safe_load() for parsing ✅

Quality Gates (self-reported)

• nox -s lint: PASS
• nox -s typecheck: PASS (0 errors)
• nox -s unit_tests: PASS (632 features, 15050 scenarios, 0 failures)
• nox -s coverage_report: PASS (97.1% ≥ 97%)

This PR is approved for merge.

---

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer

**Code Review Decision: APPROVED ✅** **Reviewer:** HAL9001 (AUTO-REV-48) **Review Focus:** api-consistency, naming-conventions, code-patterns **Cycle:** 3 — all Cycle 1 + Cycle 2 blocking issues resolved ### All Previous Blocking Issues — Resolved | Issue | Status | |---|---| | Missing BDD scenarios | ✅ 9 new scenarios in `plan_correction_diff.feature` + 3 updated | | Broad `except Exception` catch | ✅ Now catches `CorrectionAttemptNotFoundError` specifically | | Direct container access in service | ✅ `unit_of_work` injected via constructor (ADR-003 compliant) | | UoW not used as context manager | ✅ `with uow.transaction() as ctx:` used correctly | | Missing input validation | ✅ `ValidationError` guards for empty `plan_id` / `correction_attempt_id` | | Unused variable | ✅ `get_plan()` called without assignment | | Blank line style | ✅ Correct 2-blank-line separation | ### Review Focus Areas — All Pass - **API Consistency**: `correction_diff()` signature mirrors `diff()`, consistent error types, consistent DI pattern ✅ - **Naming Conventions**: `_build_correction_diff_dict`, `_render_correction_diff_*` mirror existing patterns; `decisions_*` naming is domain-appropriate ✅ - **Code Patterns**: `cast(Literal[...])` for type-safe format coercion, `_build_mock_svc` DRY helper, `Callable[[], None]` type annotation, `yaml.safe_load()` for parsing ✅ ### Quality Gates (self-reported) - `nox -s lint`: PASS - `nox -s typecheck`: PASS (0 errors) - `nox -s unit_tests`: PASS (632 features, 15050 scenarios, 0 failures) - `nox -s coverage_report`: PASS (97.1% ≥ 97%) **This PR is approved for merge.** --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer

HAL9000 referenced this pull request 2026-04-16 21:08:23 +00:00

[AUTO-REV-SUP] PR Review Pool Status (Cycle 20) #10070

hurui200320 force-pushed fix/plan-diff-correction-stub from 3189066640 to ebb71dc747 2026-04-17 07:39:06 +00:00 Compare

hurui200320 referenced this pull request 2026-04-17 07:54:59 +00:00

[ENHANCEMENT] Align correction diff output with spec's file-level schema (files_changed, comparison list, patch_preview hunks) #10220

hurui200320 referenced this pull request 2026-04-17 07:55:07 +00:00

[ENHANCEMENT] Make plan_id optional when --correction is provided in agents plan diff #10221

hurui200320 force-pushed fix/plan-diff-correction-stub from ebb71dc747 to 1fda56b778 2026-04-17 08:34:40 +00:00 Compare

hurui200320 scheduled this pull request to auto merge when all checks succeed 2026-04-17 08:36:12 +00:00

HAL9000 referenced this pull request 2026-04-17 09:12:02 +00:00

[AUTO-PRMRG-SUP] Status: PR Merge Pool Supervisor (Cycle 1) #10234

hurui200320 canceled auto merging this pull request when all checks succeed 2026-04-17 09:37:32 +00:00

hurui200320 scheduled this pull request to auto merge when all checks succeed 2026-04-17 09:38:07 +00:00

hurui200320 added 1 commit 2026-04-17 09:38:15 +00:00

Merge branch 'master' into fix/plan-diff-correction-stub ed7276773e

hurui200320 merged commit ed7276773e into master 2026-04-17 09:56:31 +00:00

hurui200320 deleted branch fix/plan-diff-correction-stub 2026-04-17 09:56:32 +00:00

HAL9001 referenced this pull request 2026-04-17 10:30:51 +00:00

[AUTO-REV-SUP] PR Review Pool Status (Cycle 2) #10210

HAL9001 referenced this pull request 2026-04-17 10:36:15 +00:00

[AUTO-REV-SUP] PR Review Pool Status (Cycle 3) #10247

HAL9000 referenced this pull request 2026-04-17 10:42:55 +00:00

[AUTO-DOCS] Status: Documentation Pool Supervisor (Cycle 6) #10249

HAL9001 referenced this pull request 2026-04-17 12:10:09 +00:00

[AUTO-REV-SUP] PR Review Pool Status (Cycle 3) #10247

HAL9000 referenced this pull request 2026-04-17 13:21:09 +00:00

[AUTO-DOCS] Status: Documentation Pool Supervisor (Cycle 7) #10257

HAL9001 referenced this pull request 2026-04-17 15:07:10 +00:00

[AUTO-REV-SUP] PR Review Pool Status (Cycle 3) #10247

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.3.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

3 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#9085 [BUG] agents plan diff --correction is a stub — returns placeholder text instead of real correction diff

cleveragents/cleveragents-core

Reference

cleveragents/cleveragents-core!9221

No description provided.