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): workflow example 15 — disaster recovery, rollback a failed apply (trusted profile) #802

Closed
freemo wants to merge 1 commit from test/e2e-wf15-disaster-recovery into master
pull from: test/e2e-wf15-disaster-recovery
merge into: cleveragents:master
Conversation 5 Commits 1 Files changed 2 +520
freemo commented 2026-03-13 01:16:16 +00:00
Owner
Copy link

Summary

E2E test for Workflow Example 15 — disaster recovery: rollback a failed apply using the trusted profile. Tests plan rollback, plan correct (revert mode), correction diff, re-execution after correction, and the full recovery lifecycle.

Closes #761

ISSUES CLOSED: #761

Changes

  • Decision ID extraction (Major fix): Replaced generic Extract First Id From Text with dedicated Extract Decision Id From Tree keyword that uses a targeted regex ("decision_id"\s*:\s*"<ULID>") to avoid extracting plan_id from JSON tree output. This ensures plan explain and plan correct receive the correct decision ID.
  • Checkpoint ID extraction (Major fix): Replaced broken first-ULID extraction from plan artifacts with dedicated Extract Checkpoint Id From Status keyword that targets last_checkpoint_id / checkpoint_id fields in plan status --format json output. Removed the dangerous fallback that silently used plan_id as checkpoint. When no checkpoint is available, the test gracefully skips with a clear message via Skip If.
  • AC#9 final status assertion (Major fix): Removed tautological terms ('phase', 'errored', 'cancelled') from the terminal state assertion. After successful recovery, only 'applied' or 'completed' are accepted as valid terminal states.
  • Return code assertions on recovery steps (Major fix): Added Should Be Equal As Integers ${r_X.rc} 0 assertions to all critical recovery commands including plan diff (step 14), which previously lacked an rc check. The initial plan apply and plan artifacts still use expected_rc=None without rc checks since those may legitimately fail.
  • ROOT CAUSE annotation enforcement (Major fix — AC#4): Added a secondary plan tree --format plain request specifically for the ROOT CAUSE display annotation check. Also searches JSON tree and status output for root_cause/root cause references. Logs WARN (rather than failing) when not found, since LLM behavior is non-deterministic and may not annotate root cause.
  • Checkpoint skip with explicit documentation (Major fix — AC#6–AC#9): Replaced terse Skip If with thoroughly documented skip explaining when checkpoint absence is expected (LLM behavior) vs when it indicates a problem. Added guidance to investigate persistent skips.
  • Errored state verification (Major fix — Issue #3): Added dedicated assertion after initial apply/status to verify the plan entered an errored/failed state. Logs WARN when state is not errored (LLM may produce a successful plan), continuing with recovery steps regardless.
  • Correction ID extraction (Major fix — Issue #5): Replaced generic Extract First Id From Text on combined stdout+stderr with dedicated Extract Correction Id From Output keyword that targets the "correction_id" field specifically. Falls back to first ULID from stdout only (not stderr) to avoid extracting stray IDs.
  • Dead ELSE branch removed (Major fix — Issue #6): Removed unreachable IF/ELSE guard on correction ID extraction (rc==0 already guaranteed by prior assertion). Correction ID is now always extracted directly.
  • AC#3 status assertion tightened: Removed generic 'execute' term that matches field labels in every status output. Kept only specific state values: 'processing', 'errored', 'applied'.
  • AC#5 explain assertion improved (Issue #7, #20): Removed overly generic terms ('decision', 'question') that would match any explain output. Replaced with specific forensic content terms: 'rationale', 'snapshot', 'alternative', 'chosen', 'confidence', 'context'.
  • AC#7 correct assertion improved (Issue #7): Removed generic 'correct' (matches command name) and 'status'. Replaced with more specific terms: 'correction_id', 'corrected', 'applied', 'revert'.
  • AC#8 diff assertion strengthened (Issue #7): Replaced generic 'file' and 'change' with diff-specific markers: '---', '+++', 'original', 'modified'.
  • AC#6 rollback assertion tightened (Issue #12): Removed generic 'complete' from the disjunction. Kept 'rollback', 'restored', 'revert', 'checkpoint'.
  • plan correct — removed undocumented --plan flag (Issue #8): The spec signature for plan correct does not include a --plan flag. Removed to align with documented spec workflow.
  • Missing plan diff investigation step added (Issue #9): Added plan diff ${plan_id} --format plain step between tree (step 9) and explain (step 10), matching the spec WF15 workflow which shows investigating the diff before explain.
  • plan apply instead of lifecycle-apply (Issue #10): Changed both initial and final apply commands from plan lifecycle-apply to plan apply with --yes flag to match the spec-documented command.
  • Phase advancement verification (Issue #13): Added plan status check after strategize (step 5b) to verify phase transition before executing the execute phase.
  • Consistent explicit timeouts (Issue #14): Added explicit timeout=120s to steps 8, 9, 10, and 17 which previously relied on the default.
  • ULID regex consolidation comment (Issue #15): Added comment in Extract Plan Id keyword noting that M1 defines a similar keyword and consolidation is deferred to a separate ticket.
  • plan diff --correction spec alignment (Issue #16): Fixed plan diff invocation when correction_id is available to use plan diff --correction ${correction_id} without also passing plan_id, matching the spec's either/or notation.
  • Extract Plan Id fallback regex tightened (Issue #17): Replaced overly broad [\w-]+ regex with ULID/UUID-specific patterns: [0-9A-HJ-KM-NP-TV-Z]{26} and UUID 8-4-4-4-12 format.
  • Explicit expected_rc on steps 5 and 6 (Issue #19): Added explicit expected_rc=${0} to strategize and execute steps for consistency with other steps.
  • ULID regex corrected: Fixed Crockford Base32 regex from [0-9A-HJ-NP-Z] to [0-9A-HJ-KM-NP-TV-Z] which correctly excludes I, L, O, U.
  • Consistent Traceback/INTERNAL checks: Added Should Not Contain ... Traceback alongside all INTERNAL checks across all steps.
  • Git subprocess timeouts: Added timeout=60s on_timeout=kill to all three Run Process calls (git add, git commit, git rev-parse).
  • Test-case-level timeout: Added [Timeout] 30 minutes to prevent unbounded execution.
  • Keyword deduplication: Extract Plan Id now delegates to Extract First Id From Text for ULID/UUID scanning, keeping only its field-extraction fallback as additional logic.
  • Step renumbering: Sequential 1–17 (plus 5b for phase verification and 9b for investigation diff).

Manual Verification

Prerequisites

  • OPENAI_API_KEY or ANTHROPIC_API_KEY environment variable set

Commands

nox -e e2e_tests

What to Look For

  • WF15 test passes (or SKIPs gracefully if no checkpoint available)
  • Decision IDs correctly extracted from plan tree JSON via targeted decision_id regex
  • Checkpoint IDs extracted from plan status --format json via targeted field regex
  • Recovery commands (rollback, correct, re-execute, apply) assert rc == 0
  • plan diff also asserts rc == 0
  • Final status only accepts applied or completed — not errored or generic terms
  • No Traceback or INTERNAL in any command's output
  • Test skips gracefully when no LLM keys are present

Deferred Items

  • Inline Python fixtures refactor (nit #18): Moving inline fixture strings to .py files loaded at runtime is a substantial refactor outside the scope of this ticket.
  • Extract Plan Id consolidation (nit #15): Both M1 and WF15 define local Extract Plan Id keywords with different signatures. Consolidating into common_e2e.resource is deferred to a separate ticket to avoid touching unrelated test files.
## Summary E2E test for Workflow Example 15 — disaster recovery: rollback a failed apply using the trusted profile. Tests plan rollback, plan correct (revert mode), correction diff, re-execution after correction, and the full recovery lifecycle. Closes #761 ISSUES CLOSED: #761 ## Changes - **Decision ID extraction (Major fix):** Replaced generic `Extract First Id From Text` with dedicated `Extract Decision Id From Tree` keyword that uses a targeted regex (`"decision_id"\s*:\s*"<ULID>"`) to avoid extracting `plan_id` from JSON tree output. This ensures `plan explain` and `plan correct` receive the correct decision ID. - **Checkpoint ID extraction (Major fix):** Replaced broken first-ULID extraction from `plan artifacts` with dedicated `Extract Checkpoint Id From Status` keyword that targets `last_checkpoint_id` / `checkpoint_id` fields in `plan status --format json` output. Removed the dangerous fallback that silently used `plan_id` as checkpoint. When no checkpoint is available, the test gracefully skips with a clear message via `Skip If`. - **AC#9 final status assertion (Major fix):** Removed tautological terms (`'phase'`, `'errored'`, `'cancelled'`) from the terminal state assertion. After successful recovery, only `'applied'` or `'completed'` are accepted as valid terminal states. - **Return code assertions on recovery steps (Major fix):** Added `Should Be Equal As Integers ${r_X.rc} 0` assertions to all critical recovery commands including `plan diff` (step 14), which previously lacked an rc check. The initial `plan apply` and `plan artifacts` still use `expected_rc=None` without rc checks since those may legitimately fail. - **ROOT CAUSE annotation enforcement (Major fix — AC#4):** Added a secondary `plan tree --format plain` request specifically for the ROOT CAUSE display annotation check. Also searches JSON tree and status output for `root_cause`/`root cause` references. Logs WARN (rather than failing) when not found, since LLM behavior is non-deterministic and may not annotate root cause. - **Checkpoint skip with explicit documentation (Major fix — AC#6–AC#9):** Replaced terse `Skip If` with thoroughly documented skip explaining when checkpoint absence is expected (LLM behavior) vs when it indicates a problem. Added guidance to investigate persistent skips. - **Errored state verification (Major fix — Issue #3):** Added dedicated assertion after initial apply/status to verify the plan entered an errored/failed state. Logs WARN when state is not errored (LLM may produce a successful plan), continuing with recovery steps regardless. - **Correction ID extraction (Major fix — Issue #5):** Replaced generic `Extract First Id From Text` on combined stdout+stderr with dedicated `Extract Correction Id From Output` keyword that targets the `"correction_id"` field specifically. Falls back to first ULID from stdout only (not stderr) to avoid extracting stray IDs. - **Dead ELSE branch removed (Major fix — Issue #6):** Removed unreachable IF/ELSE guard on correction ID extraction (rc==0 already guaranteed by prior assertion). Correction ID is now always extracted directly. - **AC#3 status assertion tightened:** Removed generic `'execute'` term that matches field labels in every status output. Kept only specific state values: `'processing'`, `'errored'`, `'applied'`. - **AC#5 explain assertion improved (Issue #7, #20):** Removed overly generic terms (`'decision'`, `'question'`) that would match any explain output. Replaced with specific forensic content terms: `'rationale'`, `'snapshot'`, `'alternative'`, `'chosen'`, `'confidence'`, `'context'`. - **AC#7 correct assertion improved (Issue #7):** Removed generic `'correct'` (matches command name) and `'status'`. Replaced with more specific terms: `'correction_id'`, `'corrected'`, `'applied'`, `'revert'`. - **AC#8 diff assertion strengthened (Issue #7):** Replaced generic `'file'` and `'change'` with diff-specific markers: `'---'`, `'+++'`, `'original'`, `'modified'`. - **AC#6 rollback assertion tightened (Issue #12):** Removed generic `'complete'` from the disjunction. Kept `'rollback'`, `'restored'`, `'revert'`, `'checkpoint'`. - **`plan correct` — removed undocumented `--plan` flag (Issue #8):** The spec signature for `plan correct` does not include a `--plan` flag. Removed to align with documented spec workflow. - **Missing `plan diff` investigation step added (Issue #9):** Added `plan diff ${plan_id} --format plain` step between tree (step 9) and explain (step 10), matching the spec WF15 workflow which shows investigating the diff before explain. - **`plan apply` instead of `lifecycle-apply` (Issue #10):** Changed both initial and final apply commands from `plan lifecycle-apply` to `plan apply` with `--yes` flag to match the spec-documented command. - **Phase advancement verification (Issue #13):** Added `plan status` check after strategize (step 5b) to verify phase transition before executing the execute phase. - **Consistent explicit timeouts (Issue #14):** Added explicit `timeout=120s` to steps 8, 9, 10, and 17 which previously relied on the default. - **ULID regex consolidation comment (Issue #15):** Added comment in `Extract Plan Id` keyword noting that M1 defines a similar keyword and consolidation is deferred to a separate ticket. - **`plan diff --correction` spec alignment (Issue #16):** Fixed `plan diff` invocation when correction_id is available to use `plan diff --correction ${correction_id}` without also passing `plan_id`, matching the spec's either/or notation. - **`Extract Plan Id` fallback regex tightened (Issue #17):** Replaced overly broad `[\w-]+` regex with ULID/UUID-specific patterns: `[0-9A-HJ-KM-NP-TV-Z]{26}` and UUID 8-4-4-4-12 format. - **Explicit `expected_rc` on steps 5 and 6 (Issue #19):** Added explicit `expected_rc=${0}` to strategize and execute steps for consistency with other steps. - **ULID regex corrected:** Fixed Crockford Base32 regex from `[0-9A-HJ-NP-Z]` to `[0-9A-HJ-KM-NP-TV-Z]` which correctly excludes I, L, O, U. - **Consistent Traceback/INTERNAL checks:** Added `Should Not Contain ... Traceback` alongside all `INTERNAL` checks across all steps. - **Git subprocess timeouts:** Added `timeout=60s on_timeout=kill` to all three `Run Process` calls (`git add`, `git commit`, `git rev-parse`). - **Test-case-level timeout:** Added `[Timeout] 30 minutes` to prevent unbounded execution. - **Keyword deduplication:** `Extract Plan Id` now delegates to `Extract First Id From Text` for ULID/UUID scanning, keeping only its field-extraction fallback as additional logic. - **Step renumbering:** Sequential 1–17 (plus 5b for phase verification and 9b for investigation diff). ## Manual Verification ### Prerequisites - `OPENAI_API_KEY` or `ANTHROPIC_API_KEY` environment variable set ### Commands ```bash nox -e e2e_tests ``` ### What to Look For - WF15 test passes (or SKIPs gracefully if no checkpoint available) - Decision IDs correctly extracted from `plan tree` JSON via targeted `decision_id` regex - Checkpoint IDs extracted from `plan status --format json` via targeted field regex - Recovery commands (rollback, correct, re-execute, apply) assert `rc == 0` - `plan diff` also asserts `rc == 0` - Final status only accepts `applied` or `completed` — not `errored` or generic terms - No `Traceback` or `INTERNAL` in any command's output - Test skips gracefully when no LLM keys are present ## Deferred Items - **Inline Python fixtures refactor (nit #18):** Moving inline fixture strings to `.py` files loaded at runtime is a substantial refactor outside the scope of this ticket. - **`Extract Plan Id` consolidation (nit #15):** Both M1 and WF15 define local `Extract Plan Id` keywords with different signatures. Consolidating into `common_e2e.resource` is deferred to a separate ticket to avoid touching unrelated test files.
test(e2e): workflow example 15 — disaster recovery, rollback a failed apply (trusted profile)
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 18s
Details
CI / lint (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 38s
Details
CI / typecheck (pull_request) Successful in 41s
Details
CI / build (pull_request) Successful in 19s
Details
CI / e2e_tests (pull_request) Failing after 29s
Details
CI / unit_tests (pull_request) Successful in 5m9s
Details
CI / integration_tests (pull_request) Successful in 5m44s
Details
CI / docker (pull_request) Successful in 1m9s
Details
CI / coverage (pull_request) Successful in 7m42s
Details
CI / benchmark-regression (pull_request) Successful in 38m0s
Details
a0377ba8b1 
Add end-to-end Robot Framework test for WF15: Disaster Recovery —
Rollback a Failed Apply.  The test exercises plan execution with the
trusted automation profile, then investigates via plan status, plan tree,
plan explain (--show-context --show-reasoning), plan rollback, plan
correct (--mode revert with corrective guidance), and plan diff
(--correction) before re-executing and applying.

Zero mocking — real CLI, real LLM API keys, real subprocess execution.
Fixture code provides a connection-pool module with known exhaustion risk.

ISSUES CLOSED: #761
freemo added this to the v3.2.0 milestone 2026-03-13 01:16:26 +00:00
freemo force-pushed test/e2e-wf15-disaster-recovery from a0377ba8b1
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 18s
Details
CI / lint (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 38s
Details
CI / typecheck (pull_request) Successful in 41s
Details
CI / build (pull_request) Successful in 19s
Details
CI / e2e_tests (pull_request) Failing after 29s
Details
CI / unit_tests (pull_request) Successful in 5m9s
Details
CI / integration_tests (pull_request) Successful in 5m44s
Details
CI / docker (pull_request) Successful in 1m9s
Details
CI / coverage (pull_request) Successful in 7m42s
Details
CI / benchmark-regression (pull_request) Successful in 38m0s
Details
to 803fde3e97
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 18s
Details
CI / quality (pull_request) Successful in 25s
Details
CI / e2e_tests (pull_request) Failing after 25s
Details
CI / build (pull_request) Successful in 23s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 37s
Details
CI / integration_tests (pull_request) Successful in 2m59s
Details
CI / unit_tests (pull_request) Successful in 3m9s
Details
CI / docker (pull_request) Successful in 1m0s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 16:24:29 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from 803fde3e97
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 18s
Details
CI / quality (pull_request) Successful in 25s
Details
CI / e2e_tests (pull_request) Failing after 25s
Details
CI / build (pull_request) Successful in 23s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 37s
Details
CI / integration_tests (pull_request) Successful in 2m59s
Details
CI / unit_tests (pull_request) Successful in 3m9s
Details
CI / docker (pull_request) Successful in 1m0s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 8ef5722458
Some checks failed
CI / lint (pull_request) Successful in 14s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 15s
Details
CI / build (pull_request) Successful in 14s
Details
CI / security (pull_request) Successful in 28s
Details
CI / typecheck (pull_request) Successful in 34s
Details
CI / e2e_tests (pull_request) Failing after 40s
Details
CI / unit_tests (pull_request) Successful in 2m28s
Details
CI / docker (pull_request) Successful in 51s
Details
CI / integration_tests (pull_request) Successful in 3m46s
Details
CI / coverage (pull_request) Successful in 5m17s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 16:31:36 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from 8ef5722458
Some checks failed
CI / lint (pull_request) Successful in 14s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 15s
Details
CI / build (pull_request) Successful in 14s
Details
CI / security (pull_request) Successful in 28s
Details
CI / typecheck (pull_request) Successful in 34s
Details
CI / e2e_tests (pull_request) Failing after 40s
Details
CI / unit_tests (pull_request) Successful in 2m28s
Details
CI / docker (pull_request) Successful in 51s
Details
CI / integration_tests (pull_request) Successful in 3m46s
Details
CI / coverage (pull_request) Successful in 5m17s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 93827a0e26
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 13s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / security (pull_request) Successful in 32s
Details
CI / typecheck (pull_request) Successful in 33s
Details
CI / e2e_tests (pull_request) Failing after 32s
Details
CI / unit_tests (pull_request) Successful in 3m5s
Details
CI / docker (pull_request) Successful in 8s
Details
CI / integration_tests (pull_request) Successful in 3m29s
Details
CI / coverage (pull_request) Successful in 5m26s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 16:42:18 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from 93827a0e26
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 13s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / security (pull_request) Successful in 32s
Details
CI / typecheck (pull_request) Successful in 33s
Details
CI / e2e_tests (pull_request) Failing after 32s
Details
CI / unit_tests (pull_request) Successful in 3m5s
Details
CI / docker (pull_request) Successful in 8s
Details
CI / integration_tests (pull_request) Successful in 3m29s
Details
CI / coverage (pull_request) Successful in 5m26s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 0e17b080d4
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 14s
Details
CI / quality (pull_request) Successful in 17s
Details
CI / e2e_tests (pull_request) Failing after 26s
Details
CI / security (pull_request) Successful in 31s
Details
CI / typecheck (pull_request) Successful in 31s
Details
CI / unit_tests (pull_request) Successful in 2m17s
Details
CI / docker (pull_request) Successful in 9s
Details
CI / integration_tests (pull_request) Successful in 2m44s
Details
CI / coverage (pull_request) Successful in 4m54s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 17:00:52 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from 0e17b080d4
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 14s
Details
CI / quality (pull_request) Successful in 17s
Details
CI / e2e_tests (pull_request) Failing after 26s
Details
CI / security (pull_request) Successful in 31s
Details
CI / typecheck (pull_request) Successful in 31s
Details
CI / unit_tests (pull_request) Successful in 2m17s
Details
CI / docker (pull_request) Successful in 9s
Details
CI / integration_tests (pull_request) Successful in 2m44s
Details
CI / coverage (pull_request) Successful in 4m54s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 62dd9d81fd
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 17s
Details
CI / quality (pull_request) Successful in 20s
Details
CI / build (pull_request) Successful in 22s
Details
CI / security (pull_request) Successful in 32s
Details
CI / e2e_tests (pull_request) Failing after 31s
Details
CI / typecheck (pull_request) Successful in 46s
Details
CI / integration_tests (pull_request) Successful in 3m4s
Details
CI / unit_tests (pull_request) Successful in 3m16s
Details
CI / docker (pull_request) Successful in 10s
Details
CI / coverage (pull_request) Successful in 5m12s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 17:28:38 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from 62dd9d81fd
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 17s
Details
CI / quality (pull_request) Successful in 20s
Details
CI / build (pull_request) Successful in 22s
Details
CI / security (pull_request) Successful in 32s
Details
CI / e2e_tests (pull_request) Failing after 31s
Details
CI / typecheck (pull_request) Successful in 46s
Details
CI / integration_tests (pull_request) Successful in 3m4s
Details
CI / unit_tests (pull_request) Successful in 3m16s
Details
CI / docker (pull_request) Successful in 10s
Details
CI / coverage (pull_request) Successful in 5m12s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 47436aca0a
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 15s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 22s
Details
CI / typecheck (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 36s
Details
CI / e2e_tests (pull_request) Successful in 54s
Details
CI / integration_tests (pull_request) Successful in 3m4s
Details
CI / unit_tests (pull_request) Successful in 5m7s
Details
CI / docker (pull_request) Successful in 27s
Details
CI / coverage (pull_request) Successful in 5m15s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 17:46:51 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from 47436aca0a
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 15s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 22s
Details
CI / typecheck (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 36s
Details
CI / e2e_tests (pull_request) Successful in 54s
Details
CI / integration_tests (pull_request) Successful in 3m4s
Details
CI / unit_tests (pull_request) Successful in 5m7s
Details
CI / docker (pull_request) Successful in 27s
Details
CI / coverage (pull_request) Successful in 5m15s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to a0377ba8b1
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 18s
Details
CI / lint (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 38s
Details
CI / typecheck (pull_request) Successful in 41s
Details
CI / build (pull_request) Successful in 19s
Details
CI / e2e_tests (pull_request) Failing after 29s
Details
CI / unit_tests (pull_request) Successful in 5m9s
Details
CI / integration_tests (pull_request) Successful in 5m44s
Details
CI / docker (pull_request) Successful in 1m9s
Details
CI / coverage (pull_request) Successful in 7m42s
Details
CI / benchmark-regression (pull_request) Successful in 38m0s
Details
2026-03-13 18:13:02 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from a0377ba8b1
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 18s
Details
CI / lint (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 38s
Details
CI / typecheck (pull_request) Successful in 41s
Details
CI / build (pull_request) Successful in 19s
Details
CI / e2e_tests (pull_request) Failing after 29s
Details
CI / unit_tests (pull_request) Successful in 5m9s
Details
CI / integration_tests (pull_request) Successful in 5m44s
Details
CI / docker (pull_request) Successful in 1m9s
Details
CI / coverage (pull_request) Successful in 7m42s
Details
CI / benchmark-regression (pull_request) Successful in 38m0s
Details
to 0111d02d65
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / typecheck (pull_request) Successful in 31s
Details
CI / build (pull_request) Successful in 19s
Details
CI / e2e_tests (pull_request) Failing after 25s
Details
CI / security (pull_request) Successful in 35s
Details
CI / unit_tests (pull_request) Successful in 2m7s
Details
CI / docker (pull_request) Successful in 11s
Details
CI / integration_tests (pull_request) Successful in 3m1s
Details
CI / coverage (pull_request) Successful in 5m0s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 18:14:21 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from 0111d02d65
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / typecheck (pull_request) Successful in 31s
Details
CI / build (pull_request) Successful in 19s
Details
CI / e2e_tests (pull_request) Failing after 25s
Details
CI / security (pull_request) Successful in 35s
Details
CI / unit_tests (pull_request) Successful in 2m7s
Details
CI / docker (pull_request) Successful in 11s
Details
CI / integration_tests (pull_request) Successful in 3m1s
Details
CI / coverage (pull_request) Successful in 5m0s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 9884fbb4a5
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 34s
Details
CI / security (pull_request) Successful in 33s
Details
CI / e2e_tests (pull_request) Failing after 51s
Details
CI / unit_tests (pull_request) Successful in 4m32s
Details
CI / docker (pull_request) Successful in 9s
Details
CI / integration_tests (pull_request) Successful in 4m58s
Details
CI / coverage (pull_request) Successful in 5m57s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 18:25:18 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from 9884fbb4a5
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 34s
Details
CI / security (pull_request) Successful in 33s
Details
CI / e2e_tests (pull_request) Failing after 51s
Details
CI / unit_tests (pull_request) Successful in 4m32s
Details
CI / docker (pull_request) Successful in 9s
Details
CI / integration_tests (pull_request) Successful in 4m58s
Details
CI / coverage (pull_request) Successful in 5m57s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to a3ccdaba41
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / security (pull_request) Successful in 32s
Details
CI / typecheck (pull_request) Successful in 34s
Details
CI / e2e_tests (pull_request) Successful in 55s
Details
CI / unit_tests (pull_request) Successful in 2m7s
Details
CI / integration_tests (pull_request) Successful in 2m34s
Details
CI / docker (pull_request) Successful in 47s
Details
CI / coverage (pull_request) Successful in 5m27s
Details
CI / benchmark-regression (pull_request) Successful in 33m24s
Details
2026-03-13 18:36:45 +00:00 Compare
freemo force-pushed test/e2e-wf15-disaster-recovery from a3ccdaba41
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 16s
Details
CI / security (pull_request) Successful in 32s
Details
CI / typecheck (pull_request) Successful in 34s
Details
CI / e2e_tests (pull_request) Successful in 55s
Details
CI / unit_tests (pull_request) Successful in 2m7s
Details
CI / integration_tests (pull_request) Successful in 2m34s
Details
CI / docker (pull_request) Successful in 47s
Details
CI / coverage (pull_request) Successful in 5m27s
Details
CI / benchmark-regression (pull_request) Successful in 33m24s
Details
to cc07e67799
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 19s
Details
CI / quality (pull_request) Successful in 28s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 38s
Details
CI / e2e_tests (pull_request) Failing after 36s
Details
CI / integration_tests (pull_request) Successful in 2m57s
Details
CI / unit_tests (pull_request) Successful in 3m44s
Details
CI / docker (pull_request) Successful in 7s
Details
CI / coverage (pull_request) Successful in 5m9s
Details
CI / benchmark-regression (pull_request) Successful in 34m6s
Details
2026-03-13 23:19:50 +00:00 Compare
freemo commented 2026-03-14 04:43:43 +00:00
Author
Owner
Copy link

PM Review — Day 34

Status: Mergeable, 0 reviews, M3 (v3.2.0)
Author: @freemo

E2E test for WF15 (disaster recovery, rollback a failed apply). Most comprehensive test in the M3 batch — 15 sequential steps covering forensic inspection (--show-context --show-reasoning), rollback, correction (revert mode), diff --correction, re-execute, and lifecycle-apply.

See #799 for common review notes.

Action Items

Who Action Deadline
@hurui200320 Peer review Day 36
## PM Review — Day 34 **Status**: Mergeable, 0 reviews, M3 (v3.2.0) **Author**: @freemo E2E test for WF15 (disaster recovery, rollback a failed apply). Most comprehensive test in the M3 batch — 15 sequential steps covering forensic inspection (`--show-context --show-reasoning`), rollback, correction (revert mode), `diff --correction`, re-execute, and lifecycle-apply. **See #799 for common review notes.** ### Action Items | Who | Action | Deadline | |-----|--------|----------| | @hurui200320 | **Peer review** | Day 36 |
freemo commented 2026-03-16 09:34:32 +00:00
Author
Owner
Copy link

PM Status — Day 36 (2026-03-16)

Day 34 review assignment deadline check. This PR has been in review for 2+ days with 0 reviewer activity.

Reminder: Assigned reviewer — please post your review by Day 37 EOD or flag any blockers. These E2E test PRs are foundational for milestone acceptance gates and cannot remain unreviewed indefinitely.

If you are unable to review by the deadline, please comment so the review can be reassigned.

## PM Status — Day 36 (2026-03-16) Day 34 review assignment deadline check. This PR has been in review for 2+ days with 0 reviewer activity. **Reminder**: Assigned reviewer — please post your review by **Day 37 EOD** or flag any blockers. These E2E test PRs are foundational for milestone acceptance gates and cannot remain unreviewed indefinitely. If you are unable to review by the deadline, please comment so the review can be reassigned.
freemo commented 2026-03-16 22:21:27 +00:00
Author
Owner
Copy link

@hurui200320 I am going to have you take over this PR, it is mostly completed but is waiting on #628 and #966 One is yours and one is Brent's. Please be sure to get this PR and the two blocking PRs I listed in asap, thanks.

@hurui200320 I am going to have you take over this PR, it is mostly completed but is waiting on https://git.cleverthis.com/cleveragents/cleveragents-core/issues/628 and https://git.cleverthis.com/cleveragents/cleveragents-core/issues/966 One is yours and one is Brent's. Please be sure to get this PR and the two blocking PRs I listed in asap, thanks.
freemo commented 2026-03-17 18:23:08 +00:00
Author
Owner
Copy link

PM Status — Day 37 — Rebase Required

This PR has merge conflicts and cannot be merged in its current state. 42% of all open PRs (21 of 50) have conflicts — this is a project-wide issue that must be resolved.

@freemo — Please rebase this PR onto master by Day 39 EOD (2026-03-19). If you cannot rebase by then, please post a comment explaining the blocker.

PM rebase request — Day 37

## PM Status — Day 37 — Rebase Required This PR has **merge conflicts** and cannot be merged in its current state. 42% of all open PRs (21 of 50) have conflicts — this is a project-wide issue that must be resolved. @freemo — Please rebase this PR onto `master` by **Day 39 EOD (2026-03-19)**. If you cannot rebase by then, please post a comment explaining the blocker. --- *PM rebase request — Day 37*
hurui200320 force-pushed test/e2e-wf15-disaster-recovery from cc07e67799
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 19s
Details
CI / quality (pull_request) Successful in 28s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 38s
Details
CI / e2e_tests (pull_request) Failing after 36s
Details
CI / integration_tests (pull_request) Successful in 2m57s
Details
CI / unit_tests (pull_request) Successful in 3m44s
Details
CI / docker (pull_request) Successful in 7s
Details
CI / coverage (pull_request) Successful in 5m9s
Details
CI / benchmark-regression (pull_request) Successful in 34m6s
Details
to 700aef534c
Some checks failed
CI / lint (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 43s
Details
CI / quality (pull_request) Successful in 28s
Details
CI / security (pull_request) Successful in 48s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 17s
Details
CI / unit_tests (pull_request) Successful in 3m13s
Details
CI / integration_tests (pull_request) Successful in 4m32s
Details
CI / e2e_tests (pull_request) Failing after 4m57s
Details
CI / docker (pull_request) Successful in 58s
Details
CI / coverage (pull_request) Successful in 6m55s
Details
CI / benchmark-regression (pull_request) Successful in 39m56s
Details
2026-03-18 08:45:57 +00:00 Compare
hurui200320 force-pushed test/e2e-wf15-disaster-recovery from 700aef534c
Some checks failed
CI / lint (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 43s
Details
CI / quality (pull_request) Successful in 28s
Details
CI / security (pull_request) Successful in 48s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 17s
Details
CI / unit_tests (pull_request) Successful in 3m13s
Details
CI / integration_tests (pull_request) Successful in 4m32s
Details
CI / e2e_tests (pull_request) Failing after 4m57s
Details
CI / docker (pull_request) Successful in 58s
Details
CI / coverage (pull_request) Successful in 6m55s
Details
CI / benchmark-regression (pull_request) Successful in 39m56s
Details
to d0bf51d77d
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 39s
Details
CI / lint (pull_request) Successful in 3m20s
Details
CI / quality (pull_request) Successful in 3m47s
Details
CI / security (pull_request) Successful in 3m58s
Details
CI / typecheck (pull_request) Successful in 4m12s
Details
CI / integration_tests (pull_request) Successful in 6m42s
Details
CI / unit_tests (pull_request) Successful in 6m59s
Details
CI / docker (pull_request) Successful in 1m7s
Details
CI / e2e_tests (pull_request) Successful in 8m39s
Details
CI / coverage (pull_request) Successful in 12m15s
Details
CI / status-check (pull_request) Successful in 16s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-23 05:54:29 +00:00 Compare
hurui200320 force-pushed test/e2e-wf15-disaster-recovery from d0bf51d77d
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 39s
Details
CI / lint (pull_request) Successful in 3m20s
Details
CI / quality (pull_request) Successful in 3m47s
Details
CI / security (pull_request) Successful in 3m58s
Details
CI / typecheck (pull_request) Successful in 4m12s
Details
CI / integration_tests (pull_request) Successful in 6m42s
Details
CI / unit_tests (pull_request) Successful in 6m59s
Details
CI / docker (pull_request) Successful in 1m7s
Details
CI / e2e_tests (pull_request) Successful in 8m39s
Details
CI / coverage (pull_request) Successful in 12m15s
Details
CI / status-check (pull_request) Successful in 16s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 12c0e78854
Some checks failed
CI / docker (pull_request) Blocked by required conditions
Details
CI / status-check (pull_request) Blocked by required conditions
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 22s
Details
CI / lint (pull_request) Successful in 3m21s
Details
CI / typecheck (pull_request) Successful in 4m5s
Details
CI / unit_tests (pull_request) Successful in 6m44s
Details
CI / e2e_tests (pull_request) Successful in 9m16s
Details
CI / coverage (pull_request) Successful in 10m15s
Details
CI / integration_tests (pull_request) Failing after 17m57s
Details
CI / quality (pull_request) Failing after 17m59s
Details
CI / security (pull_request) Failing after 17m59s
Details
CI / benchmark-regression (pull_request) Failing after 4h39m1s
Details
2026-03-23 07:03:52 +00:00 Compare
hurui200320 force-pushed test/e2e-wf15-disaster-recovery from 12c0e78854
Some checks failed
CI / docker (pull_request) Blocked by required conditions
Details
CI / status-check (pull_request) Blocked by required conditions
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 22s
Details
CI / lint (pull_request) Successful in 3m21s
Details
CI / typecheck (pull_request) Successful in 4m5s
Details
CI / unit_tests (pull_request) Successful in 6m44s
Details
CI / e2e_tests (pull_request) Successful in 9m16s
Details
CI / coverage (pull_request) Successful in 10m15s
Details
CI / integration_tests (pull_request) Failing after 17m57s
Details
CI / quality (pull_request) Failing after 17m59s
Details
CI / security (pull_request) Failing after 17m59s
Details
CI / benchmark-regression (pull_request) Failing after 4h39m1s
Details
to 08878c03a1
Some checks failed
CI / build (pull_request) Successful in 31s
Details
CI / lint (pull_request) Successful in 3m18s
Details
CI / quality (pull_request) Successful in 3m43s
Details
CI / typecheck (pull_request) Successful in 4m21s
Details
CI / security (pull_request) Successful in 4m32s
Details
CI / integration_tests (pull_request) Successful in 6m7s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / unit_tests (pull_request) Successful in 7m28s
Details
CI / docker (pull_request) Successful in 1m1s
Details
CI / e2e_tests (pull_request) Successful in 9m53s
Details
CI / coverage (pull_request) Successful in 11m42s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Failing after 27m41s
Details
2026-03-23 13:22:08 +00:00 Compare
hurui200320 force-pushed test/e2e-wf15-disaster-recovery from 08878c03a1
Some checks failed
CI / build (pull_request) Successful in 31s
Details
CI / lint (pull_request) Successful in 3m18s
Details
CI / quality (pull_request) Successful in 3m43s
Details
CI / typecheck (pull_request) Successful in 4m21s
Details
CI / security (pull_request) Successful in 4m32s
Details
CI / integration_tests (pull_request) Successful in 6m7s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / unit_tests (pull_request) Successful in 7m28s
Details
CI / docker (pull_request) Successful in 1m1s
Details
CI / e2e_tests (pull_request) Successful in 9m53s
Details
CI / coverage (pull_request) Successful in 11m42s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Failing after 27m41s
Details
to 5d279081b8
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 19s
Details
CI / lint (pull_request) Successful in 5m2s
Details
CI / quality (pull_request) Successful in 5m39s
Details
CI / typecheck (pull_request) Successful in 5m43s
Details
CI / security (pull_request) Successful in 5m48s
Details
CI / integration_tests (pull_request) Successful in 8m29s
Details
CI / unit_tests (pull_request) Successful in 9m9s
Details
CI / docker (pull_request) Successful in 1m8s
Details
CI / e2e_tests (pull_request) Successful in 13m5s
Details
CI / coverage (pull_request) Successful in 11m23s
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / benchmark-regression (pull_request) Successful in 58m54s
Details
2026-03-24 05:40:51 +00:00 Compare
hurui200320 force-pushed test/e2e-wf15-disaster-recovery from 5d279081b8
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 19s
Details
CI / lint (pull_request) Successful in 5m2s
Details
CI / quality (pull_request) Successful in 5m39s
Details
CI / typecheck (pull_request) Successful in 5m43s
Details
CI / security (pull_request) Successful in 5m48s
Details
CI / integration_tests (pull_request) Successful in 8m29s
Details
CI / unit_tests (pull_request) Successful in 9m9s
Details
CI / docker (pull_request) Successful in 1m8s
Details
CI / e2e_tests (pull_request) Successful in 13m5s
Details
CI / coverage (pull_request) Successful in 11m23s
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / benchmark-regression (pull_request) Successful in 58m54s
Details
to 0d3371a274
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 37s
Details
CI / lint (pull_request) Successful in 5m52s
Details
CI / quality (pull_request) Successful in 6m39s
Details
CI / typecheck (pull_request) Successful in 6m41s
Details
CI / security (pull_request) Successful in 6m54s
Details
CI / integration_tests (pull_request) Successful in 11m48s
Details
CI / unit_tests (pull_request) Successful in 12m7s
Details
CI / docker (pull_request) Successful in 1m9s
Details
CI / e2e_tests (pull_request) Successful in 16m17s
Details
CI / coverage (pull_request) Successful in 11m34s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 1h30m39s
Details
2026-03-27 09:59:43 +00:00 Compare
freemo self-assigned this 2026-04-02 06:15:23 +00:00
freemo force-pushed test/e2e-wf15-disaster-recovery from 0d3371a274
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 37s
Details
CI / lint (pull_request) Successful in 5m52s
Details
CI / quality (pull_request) Successful in 6m39s
Details
CI / typecheck (pull_request) Successful in 6m41s
Details
CI / security (pull_request) Successful in 6m54s
Details
CI / integration_tests (pull_request) Successful in 11m48s
Details
CI / unit_tests (pull_request) Successful in 12m7s
Details
CI / docker (pull_request) Successful in 1m9s
Details
CI / e2e_tests (pull_request) Successful in 16m17s
Details
CI / coverage (pull_request) Successful in 11m34s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 1h30m39s
Details
to 91bcffe1b5
Some checks failed
CI / lint (pull_request) Failing after 5s
Details
CI / typecheck (pull_request) Failing after 5s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / security (pull_request) Failing after 5s
Details
CI / quality (pull_request) Failing after 5s
Details
CI / unit_tests (pull_request) Failing after 5s
Details
CI / docker (pull_request) Has been skipped
Details
CI / integration_tests (pull_request) Failing after 5s
Details
CI / e2e_tests (pull_request) Failing after 5s
Details
CI / build (pull_request) Failing after 4s
Details
CI / helm (pull_request) Failing after 4s
Details
CI / status-check (pull_request) Failing after 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Has been skipped
Details
2026-04-02 07:00:21 +00:00 Compare
freemo commented 2026-04-02 17:32:57 +00:00
Author
Owner
Copy link

🤖 Backlog Groomer (groomer-1): Closing as duplicate of #761.

Issue #761 (test(e2e): workflow example 15 — disaster recovery, rollback a failed apply) is the canonical version with full labels (MoSCoW/Must have, Priority/Critical, State/In Review, Type/Testing) and milestone v3.2.0. This issue is an exact title duplicate.

🤖 **Backlog Groomer (groomer-1):** Closing as duplicate of #761. Issue #761 (`test(e2e): workflow example 15 — disaster recovery, rollback a failed apply`) is the canonical version with full labels (`MoSCoW/Must have`, `Priority/Critical`, `State/In Review`, `Type/Testing`) and milestone `v3.2.0`. This issue is an exact title duplicate.
freemo closed this pull request 2026-04-02 17:33:07 +00:00
Some checks failed
CI / lint (pull_request) Failing after 5s
Required
Details
CI / typecheck (pull_request) Failing after 5s
Required
Details
CI / coverage (pull_request) Has been skipped
Required
Details
CI / security (pull_request) Failing after 5s
Required
Details
CI / quality (pull_request) Failing after 5s
Required
Details
CI / unit_tests (pull_request) Failing after 5s
Required
Details
CI / docker (pull_request) Has been skipped
Required
Details
CI / integration_tests (pull_request) Failing after 5s
Required
Details
CI / e2e_tests (pull_request) Failing after 5s
Details
CI / build (pull_request) Failing after 4s
Required
Details
CI / helm (pull_request) Failing after 4s
Details
CI / status-check (pull_request) Failing after 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Has been skipped
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
CoreRasurae
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.

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

Depends on
#627 Implement @tdd_expected_fail tag handling in Behave environment
cleveragents/cleveragents-core
#628 Implement @tdd_expected_fail tag handling in Robot Framework
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core!802
No description provided.