cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

test(integration): workflow example 5 — database schema migration with safety nets (review profile) #1042

Merged
hamza.khyari merged 1 commits from test/int-wf05-db-migration into master 2026-03-31 11:26:28 +00:00
Conversation 1 Commits 1 Files Changed 6
+735 -6
hamza.khyari commented 2026-03-18 04:16:51 +00:00
Member
Copy Link
Copy Source

Summary

Integration test for Specification Workflow Example 5: Database Schema Migration with Safety Nets. Exercises the review automation profile with mixed resource types, custom skills with database tools, phased child plans, checkpointing, and rollback using mocked providers.

Closes #769

Test Cases (7)

Test What It Exercises
Register Custom Resource Type local/postgres-db with transaction_rollback sandbox, DB roundtrip
Review Automation Profile Behavior Autonomy thresholds: phases auto-start, decisions require approval, apply manual, safety requires sandbox + checkpoints
Create Custom Skill With Database Tools local/database-ops with query_db, execute_migration, backfill_column
Action With Review Profile 4 typed arguments, 4 invariants, plan creation
Checkpoint Creation And Rollback Filesystem snapshot, pre/post migration checkpoints, rollback verification
Phased Subplan Configuration 5-phase sequential migration, fail-fast, SubplanFailureHandler behavior
Plan Lifecycle With Review Profile Strategize -> complete -> execute transition

Files

  • robot/int_wf05_db_migration.robot — 7 test cases using helper pattern
  • robot/helper_int_wf05_db_migration.py — Python helper with command dispatch

Spec Reference

docs/specification.md ~lines 38244-38693 (Workflow Example 5)

## Summary Integration test for Specification Workflow Example 5: Database Schema Migration with Safety Nets. Exercises the `review` automation profile with mixed resource types, custom skills with database tools, phased child plans, checkpointing, and rollback using mocked providers. Closes #769 ## Test Cases (7) | Test | What It Exercises | |------|------------------| | Register Custom Resource Type | `local/postgres-db` with `transaction_rollback` sandbox, DB roundtrip | | Review Automation Profile Behavior | Autonomy thresholds: phases auto-start, decisions require approval, apply manual, safety requires sandbox + checkpoints | | Create Custom Skill With Database Tools | `local/database-ops` with `query_db`, `execute_migration`, `backfill_column` | | Action With Review Profile | 4 typed arguments, 4 invariants, plan creation | | Checkpoint Creation And Rollback | Filesystem snapshot, pre/post migration checkpoints, rollback verification | | Phased Subplan Configuration | 5-phase sequential migration, fail-fast, `SubplanFailureHandler` behavior | | Plan Lifecycle With Review Profile | Strategize -> complete -> execute transition | ## Files - `robot/int_wf05_db_migration.robot` — 7 test cases using helper pattern - `robot/helper_int_wf05_db_migration.py` — Python helper with command dispatch ## Spec Reference `docs/specification.md` ~lines 38244-38693 (Workflow Example 5)
hamza.khyari self-assigned this 2026-03-18 11:42:26 +00:00
hamza.khyari added the
Type
Testing
State
In Review
 labels 2026-03-18 11:42:49 +00:00
freemo approved these changes 2026-03-19 04:53:35 +00:00
Dismissed
freemo left a comment
Owner
Copy Link
Copy Source

Code Review — PR #1042 test(integration): workflow example 5 — db schema migration

Clean, well-structured integration test. The 7 Robot test cases cover custom resource type registration, review profile thresholds, skill creation, checkpoint/rollback, phased subplans, and the full lifecycle. Good use of in-memory SQLAlchemy DB for resource type persistence.

Approved with one process note:

  1. Missing milestone — The PR has no milestone assigned, but the linked issue #769 belongs to milestone v3.3.0. Per CONTRIBUTING.md §Pull Request Process item 11, every PR must be assigned to the same milestone as its linked issue. Please assign this to v3.3.0.
## Code Review — PR #1042 `test(integration): workflow example 5 — db schema migration` Clean, well-structured integration test. The 7 Robot test cases cover custom resource type registration, review profile thresholds, skill creation, checkpoint/rollback, phased subplans, and the full lifecycle. Good use of in-memory SQLAlchemy DB for resource type persistence. **Approved** with one process note: 1. **Missing milestone** — The PR has no milestone assigned, but the linked issue #769 belongs to milestone **v3.3.0**. Per CONTRIBUTING.md §Pull Request Process item 11, every PR must be assigned to the same milestone as its linked issue. Please assign this to v3.3.0.
freemo requested review from freemo 2026-03-19 05:21:10 +00:00
freemo requested review from brent.edwards 2026-03-19 05:21:10 +00:00
freemo added this to the v3.3.0 milestone 2026-03-19 05:28:38 +00:00
hamza.khyari force-pushed test/int-wf05-db-migration from f03bde7fe6 to 20e29d7407 2026-03-19 12:58:26 +00:00 Compare
hamza.khyari force-pushed test/int-wf05-db-migration from 20e29d7407 to 998074153a 2026-03-19 13:12:29 +00:00 Compare
hamza.khyari dismissed freemo's review 2026-03-19 13:12:29 +00:00
Reason:

New commits pushed, approval review dismissed automatically according to repository settings

hamza.khyari force-pushed test/int-wf05-db-migration from 998074153a to 8660182b6a 2026-03-27 14:30:47 +00:00 Compare
hamza.khyari force-pushed test/int-wf05-db-migration from 8660182b6a to 30d2d5a45a 2026-03-27 15:47:27 +00:00 Compare
hamza.khyari scheduled this pull request to auto merge when all checks succeed 2026-03-27 15:51:09 +00:00
hamza.khyari force-pushed test/int-wf05-db-migration from 30d2d5a45a to fa7be71b2b 2026-03-27 16:00:26 +00:00 Compare
hamza.khyari force-pushed test/int-wf05-db-migration from fa7be71b2b to a73dc37806 2026-03-27 16:00:35 +00:00 Compare
hamza.khyari force-pushed test/int-wf05-db-migration from a73dc37806 to f6206171db 2026-03-27 16:14:32 +00:00 Compare
hamza.khyari force-pushed test/int-wf05-db-migration from f6206171db to 68f934f8a4 2026-03-27 16:29:55 +00:00 Compare
hamza.khyari modified the milestone from v3.3.0 to v3.6.0 2026-03-30 10:37:56 +00:00
hamza.khyari force-pushed test/int-wf05-db-migration from 68f934f8a4 to d9bb72098d 2026-03-31 10:41:21 +00:00 Compare
hamza.khyari force-pushed test/int-wf05-db-migration from d9bb72098d to 75d508125c 2026-03-31 10:45:14 +00:00 Compare
hamza.khyari force-pushed test/int-wf05-db-migration from 75d508125c to 3f66221938 2026-03-31 11:03:28 +00:00 Compare
hamza.khyari merged commit 44e5eb9a94 into master 2026-03-31 11:26:28 +00:00
hamza.khyari deleted branch test/int-wf05-db-migration 2026-03-31 11:28:22 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
freemo
brent.edwards
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.
 overdue
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 Label
State
In Review
Type
Testing
Milestone
No items
No Milestone v3.6.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees hamza.khyari
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cleveragents/cleveragents-core#1042
Delete Branch "test/int-wf05-db-migration"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?