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

test(e2e): verify M3 success criteria — decision tree and correction #439

Closed
brent.edwards wants to merge 2 commits from test/m3-e2e-verification into master
pull from: test/m3-e2e-verification
merge into: cleveragents:master
Conversation 2 Commits 2 Files changed 25 +5679 -5
brent.edwards commented 2026-02-25 21:27:35 +00:00
Member
Copy link

Summary

Closes #404

  • Added robot/m3_e2e_verification.robot (10 test cases) covering all M3 acceptance criteria
  • Added robot/helper_m3_e2e_verification.py (10 subcommands)
  • Verifies: plan execution generates decisions, decision tree view, decision explain, invariant add/list, correction dry-run, correction live revert, context snapshots, tree persistence, revert re-execution, invariant enforcement

Local checks: lint passed, typecheck passed (0 errors)

## Summary Closes #404 - Added `robot/m3_e2e_verification.robot` (10 test cases) covering all M3 acceptance criteria - Added `robot/helper_m3_e2e_verification.py` (10 subcommands) - Verifies: plan execution generates decisions, decision tree view, decision explain, invariant add/list, correction dry-run, correction live revert, context snapshots, tree persistence, revert re-execution, invariant enforcement **Local checks**: lint passed, typecheck passed (0 errors)
test(e2e): verify M3 success criteria — decision tree and correction
Some checks failed
CI / lint (pull_request) Successful in 30s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 32s
Details
CI / security (pull_request) Successful in 49s
Details
CI / build (pull_request) Successful in 29s
Details
CI / typecheck (pull_request) Successful in 1m13s
Details
CI / integration_tests (pull_request) Failing after 3m56s
Details
CI / benchmark-regression (pull_request) Successful in 20m57s
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
aeb5cc5110 
Robot Framework E2E test suite for M3 milestone verification covering:
- Plan execution generating decisions during Strategize phase
- Decision tree viewing with parent-child relationships and BFS traversal
- Decision explanation with full context snapshot verification
- Invariant add/list via CLI and InvariantService with scope filtering
- Dry-run correction via CorrectionService with impact analysis
- Live revert correction execution with decision re-creation
- Context snapshot round-trip serialisation assertions
- Decision tree persistence via model_dump/model_validate
- Correction revert re-execution from decision point
- Invariant enforcement during strategize with merge precedence

ISSUES CLOSED: #404
fix(test): correct patch target for CorrectionService in M3 e2e helper
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 20s
Details
CI / quality (pull_request) Successful in 20s
Details
CI / build (pull_request) Successful in 26s
Details
CI / typecheck (pull_request) Successful in 57s
Details
CI / security (pull_request) Successful in 1m2s
Details
CI / integration_tests (pull_request) Successful in 4m16s
Details
CI / unit_tests (pull_request) Successful in 23m40s
Details
CI / benchmark-regression (pull_request) Successful in 25m34s
Details
CI / docker (pull_request) Successful in 15s
Details
CI / coverage (pull_request) Successful in 1h40m2s
Details
2e53caaef1 
The CorrectionService import in plan.py is a lazy import inside the
correct() function body, so it does not exist as a module-level attribute.
Patch the class at its definition site instead:
  cleveragents.application.services.correction_service.CorrectionService

Fixes CI integration_tests failure for PR #439.
brent.edwards commented 2026-02-25 22:15:08 +00:00
Author
Member
Copy link

Do not merge this PR individually. All changes are consolidated into PR #442 (develop-brent-5). Please review and merge #442 instead.

**Do not merge this PR individually.** All changes are consolidated into PR #442 (`develop-brent-5`). Please review and merge #442 instead.
brent.edwards commented 2026-02-25 23:53:02 +00:00
Author
Member
Copy link

Code Review — PR #439: test(e2e): verify M3 success criteria — decision tree and correction

Reviewer: @brent.edwards | Review type: Comment-only

The helper is thorough, but a couple of the "E2E" checks don’t actually exercise the CLI/persistence paths they claim to validate.

P2:should-fix — "E2E" subcommands don’t call the CLI for tree/explain

robot/helper_m3_e2e_verification.py uses in-memory Decision objects for decision-tree-view, decision-explain, and decision-tree-persistence. Those subcommands never call agents plan tree or agents plan explain, so regressions in the CLI output or persistence layer won’t be caught. Consider invoking the CLI commands (with mocked lifecycle service if needed) so the tests validate real rendering and serialization paths.

P2:should-fix — "Plan generates decisions" doesn’t validate decision recording

plan-generates-decisions runs agents plan use, but then builds decisions directly via _build_decision_tree(). That bypasses the actual strategize/decision-recording code path. If decision recording breaks, this test still passes. Suggest asserting on CLI/service output that includes decisions, or on mocked lifecycle service interactions that indicate decisions were recorded.

Happy to re-review after those are addressed.

## Code Review — PR #439: test(e2e): verify M3 success criteria — decision tree and correction **Reviewer:** @brent.edwards | **Review type:** Comment-only The helper is thorough, but a couple of the "E2E" checks don’t actually exercise the CLI/persistence paths they claim to validate. --- ### P2:should-fix — "E2E" subcommands don’t call the CLI for tree/explain `robot/helper_m3_e2e_verification.py` uses in-memory `Decision` objects for `decision-tree-view`, `decision-explain`, and `decision-tree-persistence`. Those subcommands never call `agents plan tree` or `agents plan explain`, so regressions in the CLI output or persistence layer won’t be caught. Consider invoking the CLI commands (with mocked lifecycle service if needed) so the tests validate real rendering and serialization paths. --- ### P2:should-fix — "Plan generates decisions" doesn’t validate decision recording `plan-generates-decisions` runs `agents plan use`, but then builds decisions directly via `_build_decision_tree()`. That bypasses the actual strategize/decision-recording code path. If decision recording breaks, this test still passes. Suggest asserting on CLI/service output that includes decisions, or on mocked lifecycle service interactions that indicate decisions were recorded. --- Happy to re-review after those are addressed.
fix(test): route M3 E2E subcommands through CLI rendering path
Some checks failed
CI / lint (pull_request) Successful in 24s
Details
CI / typecheck (pull_request) Successful in 1m2s
Details
CI / security (pull_request) Successful in 1m1s
Details
CI / quality (pull_request) Successful in 42s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 25s
Details
CI / integration_tests (pull_request) Successful in 5m18s
Details
CI / unit_tests (pull_request) Successful in 30m5s
Details
CI / docker (pull_request) Successful in 15s
Details
CI / benchmark-regression (pull_request) Successful in 26m25s
Details
CI / coverage (pull_request) Has been cancelled
Details
4f079c20ea 
- decision-tree-view, decision-explain, and decision-tree-persistence
  now invoke 'plan status --format plain' via mocked lifecycle service
  so regressions in CLI rendering/serialization are caught
- plan-generates-decisions now asserts use_action was called by the CLI
  and verifies plan status renders the strategize phase after creation
- Updated robot test case documentation to reflect CLI integration
Merge branch 'master' into test/m3-e2e-verification
All checks were successful
CI / lint (pull_request) Successful in 30s
Details
CI / typecheck (pull_request) Successful in 58s
Details
CI / quality (pull_request) Successful in 29s
Details
CI / security (pull_request) Successful in 55s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 24s
Details
CI / integration_tests (pull_request) Successful in 6m2s
Details
CI / unit_tests (pull_request) Successful in 36m32s
Details
CI / benchmark-regression (pull_request) Successful in 24m5s
Details
CI / docker (pull_request) Successful in 16s
Details
CI / coverage (pull_request) Successful in 2h6m50s
Details
4d66674acc
brent.edwards closed this pull request 2026-02-26 23:53:52 +00:00
brent.edwards deleted branch test/m3-e2e-verification 2026-02-26 23:53:58 +00:00
All checks were successful
CI / lint (pull_request) Successful in 30s
Required
Details
CI / typecheck (pull_request) Successful in 58s
Required
Details
CI / quality (pull_request) Successful in 29s
Required
Details
CI / security (pull_request) Successful in 55s
Required
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 24s
Required
Details
CI / integration_tests (pull_request) Successful in 6m2s
Required
Details
CI / unit_tests (pull_request) Successful in 36m32s
Required
Details
CI / benchmark-regression (pull_request) Successful in 24m5s
Details
CI / docker (pull_request) Successful in 16s
Required
Details
CI / coverage (pull_request) Successful in 2h6m50s
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!439
No description provided.