test(e2e): workflow example 12 — large-scale hierarchical feature implementation (supervised profile) #817

Merged

hurui200320 merged 1 commit from test/e2e-wf12-hierarchical into master 2026-03-30 06:35:03 +00:00

Conversation 5 Commits 1 Files changed 2 +496

freemo commented 2026-03-13 17:10:57 +00:00

Owner

Copy link

Summary

E2E test for Workflow Example 12 — large-scale hierarchical feature implementation using the supervised profile. Tests multi-project setup (4 repos with per-project invariants), global invariant registration, spec-compliant action configuration with long_description, hierarchical plan tree inspection with hard assertions, plan correct (append mode) on non-root decision with post-correction verification, phased lifecycle-apply, and terminal state verification.

Closes #758

ISSUES CLOSED: #758

Changes

Test Structure (robot/e2e/wf12_hierarchical.robot)

• Suite Setup (WF12 Suite Setup): Initializes E2E environment with init --force --yes, generates UUID-suffixed names for all resources/projects/actions to prevent UNIQUE constraint collisions in parallel CI.
• Keywords: Create Project Repo (with git rc assertions and timeout=60s on_timeout=kill), Register Project With Invariant (per-project invariant per spec, with timeout on git calls), Select Non Root Decision Id (targeted "decision_id" regex using correct Crockford Base32 character class [0-9A-HJKMNP-TV-Z]{26}, requires ≥2 IDs to avoid returning root, defensive check ensures selected ID differs from first), Verify Plan In List (consistent with m6_acceptance pattern).
• Force Tags E2E at Settings level.

Spec Compliance

• All 4 projects passed to plan use (spec Step 3): protos, api, worker, frontend.
• Global invariant registered per spec Step 1 (invariant add --global) with hard assertion on rc=0 and content verification.
• Action YAML includes spec-required fields: estimation_actor, invariant_actor, automation_profile: cautious (ticket says 'supervised' but spec uses 'cautious' — following spec), long_description, action-level invariants, reusable, state.
• Per-project invariants on each project registration (spec Step 1).
• plan explain exercised per spec Step 4 with --format json and full assertion suite (rc=0, Traceback/INTERNAL checks, non-empty output, decision ID presence in output).
• Dynamic actor selection based on available API key (Anthropic preferred, OpenAI fallback).
• Skip If No LLM Keys for graceful CI degradation.
• 35-minute timeout for real LLM execution headroom.
• plan lifecycle-list verification after plan use (consistent with m6_acceptance pattern).
• lifecycle-apply --yes to skip confirmation prompt in automated test execution.

Assertion Quality

Every command is validated beyond rc=0:

• Traceback and INTERNAL error marker checks on all commands.
• Output Should Contain for resource/project/action names in registration output (including global invariant content assertion).
• Safe Parse Json Field to parse plan_id from JSON output.
• Hard assertion on "children" field for hierarchical decomposition (AC-3, AC-6), with non-empty children array check (WARN for flat LLM output since hierarchy depth is non-deterministic).
• Decision tree structural assertions: decision_id count ≥ 2 (root + child) using Get Length on regex match results.
• Correct Crockford Base32 regex for decision IDs: "decision_id"\\s*:\\s*"([0-9A-HJKMNP-TV-Z]{26})" — excludes I, L, O, U per spec.
• Post-correction verification: second plan tree call verifies correction effect, using consistent regex-based counting method.
• Pre-correction status check: verifies plan status (rc=0) before correction; gates correction on non-terminal state (skips with WARN if plan is already terminal).
• Correction output verification: checks for append/queued/"mode"+"append"keywords (NOT barecorrectionsubstring which would vacuously matchcorrection_idkey). Plus structural JSON field check forstatusorcorrection_id`.
• Post-strategize intermediate state assertion: verifies plan has non-empty phase or processing_state after strategize.
• Apply phase assertion: Should Contain apply with WARN log when phase is empty.
• Terminal state assertion: Phase checked against actual PlanPhase enum (apply); processing_state checked against actual ProcessingState enum terminal values for Apply phase (applied, constrained, cancelled — NOT complete, which is only for Strategize/Execute phases). Non-terminal states (queued, processing) produce WARN instead of failure (apply may be asynchronous). errored state produces separate WARN. Empty processing_state after phase='apply' fails the test (guarantees populated state after full lifecycle).
• plan diff checks rc=0, non-empty output, Traceback/INTERNAL, and plan_id presence.
• Explain output verified to contain queried decision ID.
• --format json on plan use, execute, tree, correct, diff, lifecycle-apply, status, and explain.

Known Limitations

• plan prompt not exercised: Spec Step 4 shows the supervised profile pausing on a low-confidence decision and the user providing guidance via plan prompt. This command is not yet implemented as a CLI subcommand. A documentation note in the test indicates this should be added once available.
• Action arguments/--arg omitted: Spec Step 2 defines args and Step 3 uses --arg. Both are omitted because plan use triggers a UNIQUE constraint error when the action defines arguments in its schema (pre-existing bug in PlanLifecycleService.use_action). TODO documented in test.
• Post-correction tree change: Correction queues a modification but may not immediately add new decision nodes visible in plan tree until re-execution. Assertion checks >= rather than >.
• Action invariants: Spec defines 4 action-level invariants; test includes 2 as simplification. TODO documented.
• Project invariants: Spec shows 2 per project; test includes 1 per project as simplification. TODO documented.
• Multi-resource projects: Spec shows api/worker linked to both own repo and protos repo. Test links each to only own repo. TODO documented.
• Non-deterministic hierarchy depth: LLM may produce flat sibling decisions rather than nested parent→child trees; test WARNs instead of failing in this case.

Quality Gates

All gates pass:

• nox -e lint ✅
• nox -e typecheck ✅
• nox -e unit_tests ✅ (498 features, 12822 scenarios, 0 failed)
• nox -e integration_tests ✅ (1825 tests, 0 failed)
• nox -e e2e_tests ✅ (58 tests, 57 passed, 0 failed, 1 skipped — skip is pre-existing WF04 LLM non-determinism)
• nox -e coverage_report ✅ (97%)

Manual Verification

Prerequisites

• OPENAI_API_KEY or ANTHROPIC_API_KEY environment variable set

Commands

nox -e e2e_tests  # runs the full E2E suite including this test

## Summary E2E test for Workflow Example 12 — large-scale hierarchical feature implementation using the supervised profile. Tests multi-project setup (4 repos with per-project invariants), global invariant registration, spec-compliant action configuration with long_description, hierarchical plan tree inspection with hard assertions, plan correct (append mode) on non-root decision with post-correction verification, phased lifecycle-apply, and terminal state verification. Closes #758 ISSUES CLOSED: #758 ## Changes ### Test Structure (`robot/e2e/wf12_hierarchical.robot`) - **Suite Setup** (`WF12 Suite Setup`): Initializes E2E environment with `init --force --yes`, generates UUID-suffixed names for all resources/projects/actions to prevent UNIQUE constraint collisions in parallel CI. - **Keywords**: `Create Project Repo` (with git rc assertions and `timeout=60s on_timeout=kill`), `Register Project With Invariant` (per-project invariant per spec, with timeout on git calls), `Select Non Root Decision Id` (targeted `"decision_id"` regex using correct Crockford Base32 character class `[0-9A-HJKMNP-TV-Z]{26}`, requires ≥2 IDs to avoid returning root, defensive check ensures selected ID differs from first), `Verify Plan In List` (consistent with m6_acceptance pattern). - **Force Tags E2E** at Settings level. ### Spec Compliance - **All 4 projects** passed to `plan use` (spec Step 3): protos, api, worker, frontend. - **Global invariant** registered per spec Step 1 (`invariant add --global`) with hard assertion on rc=0 and content verification. - **Action YAML** includes spec-required fields: `estimation_actor`, `invariant_actor`, `automation_profile: cautious` (ticket says 'supervised' but spec uses 'cautious' — following spec), `long_description`, action-level `invariants`, `reusable`, `state`. - **Per-project invariants** on each project registration (spec Step 1). - **`plan explain`** exercised per spec Step 4 with `--format json` and full assertion suite (rc=0, Traceback/INTERNAL checks, non-empty output, decision ID presence in output). - **Dynamic actor selection** based on available API key (Anthropic preferred, OpenAI fallback). - **Skip If No LLM Keys** for graceful CI degradation. - **35-minute timeout** for real LLM execution headroom. - **`plan lifecycle-list`** verification after `plan use` (consistent with m6_acceptance pattern). - **`lifecycle-apply --yes`** to skip confirmation prompt in automated test execution. ### Assertion Quality Every command is validated beyond rc=0: - `Traceback` and `INTERNAL` error marker checks on all commands. - `Output Should Contain` for resource/project/action names in registration output (including global invariant content assertion). - `Safe Parse Json Field` to parse `plan_id` from JSON output. - **Hard assertion** on `"children"` field for hierarchical decomposition (AC-3, AC-6), with non-empty children array check (WARN for flat LLM output since hierarchy depth is non-deterministic). - Decision tree structural assertions: `decision_id` count ≥ 2 (root + child) using `Get Length` on regex match results. - **Correct Crockford Base32 regex** for decision IDs: `"decision_id"\\s*:\\s*"([0-9A-HJKMNP-TV-Z]{26})"` — excludes I, L, O, U per spec. - **Post-correction verification**: second `plan tree` call verifies correction effect, using consistent regex-based counting method. - **Pre-correction status check**: verifies plan status (rc=0) before correction; gates correction on non-terminal state (skips with WARN if plan is already terminal). - **Correction output verification**: checks for `append`/`queued`/`"mode"+`"append"` keywords (NOT bare `correction` substring which would vacuously match `correction_id` key). Plus structural JSON field check for `status` or `correction_id`. - **Post-strategize intermediate state assertion**: verifies plan has non-empty phase or processing_state after strategize. - **Apply phase assertion**: `Should Contain apply` with WARN log when phase is empty. - **Terminal state assertion**: Phase checked against actual `PlanPhase` enum (`apply`); processing_state checked against actual `ProcessingState` enum terminal values for Apply phase (`applied`, `constrained`, `cancelled` — NOT `complete`, which is only for Strategize/Execute phases). Non-terminal states (`queued`, `processing`) produce WARN instead of failure (apply may be asynchronous). `errored` state produces separate WARN. Empty `processing_state` after phase='apply' fails the test (guarantees populated state after full lifecycle). - `plan diff` checks rc=0, non-empty output, Traceback/INTERNAL, and `plan_id` presence. - **Explain output** verified to contain queried decision ID. - `--format json` on plan use, execute, tree, correct, diff, lifecycle-apply, status, and explain. ### Known Limitations - **`plan prompt` not exercised**: Spec Step 4 shows the supervised profile pausing on a low-confidence decision and the user providing guidance via `plan prompt`. This command is not yet implemented as a CLI subcommand. A documentation note in the test indicates this should be added once available. - **Action arguments/`--arg` omitted**: Spec Step 2 defines `args` and Step 3 uses `--arg`. Both are omitted because `plan use` triggers a UNIQUE constraint error when the action defines arguments in its schema (pre-existing bug in `PlanLifecycleService.use_action`). TODO documented in test. - **Post-correction tree change**: Correction queues a modification but may not immediately add new decision nodes visible in `plan tree` until re-execution. Assertion checks `>=` rather than `>`. - **Action invariants**: Spec defines 4 action-level invariants; test includes 2 as simplification. TODO documented. - **Project invariants**: Spec shows 2 per project; test includes 1 per project as simplification. TODO documented. - **Multi-resource projects**: Spec shows api/worker linked to both own repo and protos repo. Test links each to only own repo. TODO documented. - **Non-deterministic hierarchy depth**: LLM may produce flat sibling decisions rather than nested parent→child trees; test WARNs instead of failing in this case. ## Quality Gates All gates pass: - `nox -e lint` ✅ - `nox -e typecheck` ✅ - `nox -e unit_tests` ✅ (498 features, 12822 scenarios, 0 failed) - `nox -e integration_tests` ✅ (1825 tests, 0 failed) - `nox -e e2e_tests` ✅ (58 tests, 57 passed, 0 failed, 1 skipped — skip is pre-existing WF04 LLM non-determinism) - `nox -e coverage_report` ✅ (97%) ## Manual Verification ### Prerequisites - `OPENAI_API_KEY` or `ANTHROPIC_API_KEY` environment variable set ### Commands ```bash nox -e e2e_tests # runs the full E2E suite including this test ```

freemo added this to the v3.5.0 milestone 2026-03-13 17:11:02 +00:00

freemo added the

State

In Review

Type

Testing

labels 2026-03-13 17:11:02 +00:00

freemo force-pushed test/e2e-wf12-hierarchical from 285c53efe0 to e7adeeb90e 2026-03-13 17:28:46 +00:00 Compare

freemo force-pushed test/e2e-wf12-hierarchical from e7adeeb90e to c348fd1bec 2026-03-13 17:46:56 +00:00 Compare

freemo force-pushed test/e2e-wf12-hierarchical from c348fd1bec to 073d543558 2026-03-13 17:51:49 +00:00 Compare

freemo force-pushed test/e2e-wf12-hierarchical from 073d543558 to 9627b0c3a9 2026-03-13 18:13:11 +00:00 Compare

freemo force-pushed test/e2e-wf12-hierarchical from 9627b0c3a9 to b196b87161 2026-03-13 18:27:07 +00:00 Compare

freemo referenced this pull request 2026-03-13 19:21:14 +00:00

test(e2e): workflow example 12 — large-scale hierarchical feature implementation (supervised profile) #758

freemo force-pushed test/e2e-wf12-hierarchical from b196b87161 to 6e60c9d7d8 2026-03-13 23:19:44 +00:00 Compare

freemo added the

Priority

Medium

label 2026-03-14 04:10:23 +00:00

freemo commented 2026-03-14 04:43:54 +00:00

Author

Owner

Copy link

PM Review — Day 34

Status: Mergeable, 0 reviews, M6 (v3.5.0)
Closes: #758 | Author: @freemo

E2E test for WF12 (large-scale hierarchical feature implementation). 4-project setup (core, api, frontend, docs), plan tree inspection, plan correct --mode append, phased apply.

[NOTE] Milestone v3.5.0 acceptance criteria require "4+ levels of subplans" and "10+ concurrent subplans." Verify the test actually exercises these thresholds — the manual verification steps don't include explicit depth/concurrency checks.

Action Items

Who	Action	Deadline
@CoreRasurae	Peer review — complex feature domain	Day 37

## PM Review — Day 34 **Status**: Mergeable, 0 reviews, M6 (v3.5.0) **Closes**: #758 | **Author**: @freemo E2E test for WF12 (large-scale hierarchical feature implementation). 4-project setup (core, api, frontend, docs), plan tree inspection, `plan correct --mode append`, phased apply. **[NOTE]** Milestone v3.5.0 acceptance criteria require "4+ levels of subplans" and "10+ concurrent subplans." Verify the test actually exercises these thresholds — the manual verification steps don't include explicit depth/concurrency checks. ### Action Items | Who | Action | Deadline | |-----|--------|----------| | @CoreRasurae | **Peer review** — complex feature domain | Day 37 |

freemo added a new dependency 2026-03-16 02:42:20 +00:00

#627 Implement @tdd_expected_fail tag handling in Behave environment

freemo added a new dependency 2026-03-16 02:42:20 +00:00

#628 Implement @tdd_expected_fail tag handling in Robot Framework

freemo added a new dependency 2026-03-16 02:42:20 +00:00

#965 refactor(testing): rename tdd_bug/tdd_bug_N tags to tdd_issue/tdd_issue_N across Behave and Robot Framework

freemo commented 2026-03-16 09:32:04 +00:00

Author

Owner

Copy link

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

Day 34 review assignment deadline check. This PR has 0 reviewer activity after 2 days.

Priority note: M3 PRs take precedence. Reviewers should complete M3 reviews first, then address M4+ PRs in milestone order.

Assigned reviewer: Please acknowledge and provide an ETA for your review, or flag if reassignment is needed.

## PM Status — Day 36 (2026-03-16) Day 34 review assignment deadline check. This PR has 0 reviewer activity after 2 days. **Priority note**: M3 PRs take precedence. Reviewers should complete M3 reviews first, then address M4+ PRs in milestone order. **Assigned reviewer**: Please acknowledge and provide an ETA for your review, or flag if reassignment is needed.

hurui200320 was assigned by freemo 2026-03-16 22:19:24 +00:00

freemo commented 2026-03-16 22:19:29 +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 requested reviews from brent.edwards, hamza.khyari 2026-03-17 18:24:18 +00:00

freemo commented 2026-03-17 18:33:46 +00:00

Author

Owner

Copy link

PM Status — Day 37

Reviewers assigned. This PR needs at least 2 approving reviews per CONTRIBUTING.md before merge.

Author: Please ensure this PR is rebased on latest master and all quality gates pass before requesting merge.

---

PM status — Day 37

## PM Status — Day 37 Reviewers assigned. This PR needs at least 2 approving reviews per `CONTRIBUTING.md` before merge. **Author**: Please ensure this PR is rebased on latest `master` and all quality gates pass before requesting merge. --- *PM status — Day 37*

hurui200320 force-pushed test/e2e-wf12-hierarchical from 6e60c9d7d8 to 5a8458b5af 2026-03-18 08:35:56 +00:00 Compare

freemo commented 2026-03-19 04:58:00 +00:00

Author

Owner

Copy link

Code Review — PR #817

(Cannot submit formal approval — self-authored PR.)

E2E test for WF12. Well-structured with proper labels, milestone, and issue linkage. No issues found.

## Code Review — PR #817 *(Cannot submit formal approval — self-authored PR.)* E2E test for WF12. Well-structured with proper labels, milestone, and issue linkage. No issues found.

freemo requested review from CoreRasurae 2026-03-19 05:19:51 +00:00

hurui200320 force-pushed test/e2e-wf12-hierarchical from 5a8458b5af to f90ef0cadd 2026-03-20 06:56:12 +00:00 Compare

hurui200320 added

Priority

Critical

and removed

Priority

Medium

labels 2026-03-20 07:09:35 +00:00

hurui200320 force-pushed test/e2e-wf12-hierarchical from f90ef0cadd to 83b319e679 2026-03-20 08:40:01 +00:00 Compare

hurui200320 force-pushed test/e2e-wf12-hierarchical from 83b319e679 to 69b03188f3 2026-03-20 09:32:52 +00:00 Compare

hurui200320 force-pushed test/e2e-wf12-hierarchical from 69b03188f3 to 0dc73f0a08 2026-03-20 10:46:17 +00:00 Compare

hurui200320 force-pushed test/e2e-wf12-hierarchical from 0dc73f0a08 to 75f70891f6 2026-03-20 11:13:15 +00:00 Compare

hurui200320 referenced this pull request 2026-03-20 11:15:59 +00:00

test(e2e): workflow example 12 — large-scale hierarchical feature implementation (supervised profile) #758

hurui200320 force-pushed test/e2e-wf12-hierarchical from 75f70891f6 to 461defbe9a 2026-03-23 04:11:37 +00:00 Compare

hurui200320 force-pushed test/e2e-wf12-hierarchical from 461defbe9a to a9f2291c18 2026-03-24 05:41:50 +00:00 Compare

freemo removed a dependency 2026-03-26 15:14:38 +00:00

#965 refactor(testing): rename tdd_bug/tdd_bug_N tags to tdd_issue/tdd_issue_N across Behave and Robot Framework

freemo added a new dependency 2026-03-26 15:14:42 +00:00

#965 refactor(testing): rename tdd_bug/tdd_bug_N tags to tdd_issue/tdd_issue_N across Behave and Robot Framework

freemo removed a dependency 2026-03-26 18:28:16 +00:00

#965 refactor(testing): rename tdd_bug/tdd_bug_N tags to tdd_issue/tdd_issue_N across Behave and Robot Framework

hurui200320 force-pushed test/e2e-wf12-hierarchical from a9f2291c18 to 4001d5095e 2026-03-27 10:00:13 +00:00 Compare

hurui200320 force-pushed test/e2e-wf12-hierarchical from 4001d5095e to 7839009bc0 2026-03-30 04:09:52 +00:00 Compare

hurui200320 force-pushed test/e2e-wf12-hierarchical from 7839009bc0 to 7a66ddb9eb 2026-03-30 05:26:06 +00:00 Compare

hurui200320 force-pushed test/e2e-wf12-hierarchical from 7a66ddb9eb to a8c625d1ac 2026-03-30 05:27:13 +00:00 Compare

hurui200320 force-pushed test/e2e-wf12-hierarchical from a8c625d1ac to d24959e961 2026-03-30 05:46:30 +00:00 Compare

hurui200320 merged commit d24959e961 into master 2026-03-30 06:35:03 +00:00

hurui200320 deleted branch test/e2e-wf12-hierarchical 2026-03-30 06:35:03 +00:00

hurui200320 referenced this pull request 2026-03-30 07:12:36 +00:00

feat(plan): implement LLM-powered Strategy Actor #828

hurui200320 referenced this pull request 2026-03-30 07:31:08 +00:00

feat(plan): implement LLM-powered Strategy Actor (#828) #1175

Sign in to join this conversation.

Reviewers

No reviewers

hamza.khyari

brent.edwards

CoreRasurae

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

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

hurui200320

2 participants

Notifications

Subscribe

Due date

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

No due date set.

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!817

No description provided.