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

test(integration): workflow example 16 — devcontainer-driven development (supervised profile) #953

Closed
brent.edwards wants to merge 1 commits from test/int-wf16-devcontainer into master
pull from: test/int-wf16-devcontainer
merge into: cleveragents:master
Conversation 10 Commits 1 Files Changed 3
+458
brent.edwards commented 2026-03-14 06:57:38 +00:00
Member
Copy Link
Copy Source

Summary

  • Add Robot Framework integration test (robot/wf16_devcontainer.robot) for Specification Workflow Example 16: Devcontainer-Driven Development
  • Add Python helper (robot/helper_wf16_devcontainer.py) implementing 5 test subcommands
  • Tests cover: devcontainer auto-discovery from .devcontainer/devcontainer.json, project create and link-resource, plan creation with supervised profile, plan execute with devcontainer activation (mocked container runtime), plan apply writing changes to host
  • Also fixes pre-existing test failures discovered during full nox suite verification

Quality Gates

  • nox -s lint — PASS
  • nox -s typecheck — PASS (0 errors)
  • nox -s integration_tests — All 5 WF16 tests PASS
  • Helper file: 377 lines (under 500 limit)

Closes #780

## Summary - Add Robot Framework integration test (`robot/wf16_devcontainer.robot`) for Specification Workflow Example 16: Devcontainer-Driven Development - Add Python helper (`robot/helper_wf16_devcontainer.py`) implementing 5 test subcommands - Tests cover: devcontainer auto-discovery from `.devcontainer/devcontainer.json`, project create and link-resource, plan creation with supervised profile, plan execute with devcontainer activation (mocked container runtime), plan apply writing changes to host - Also fixes pre-existing test failures discovered during full nox suite verification ## Quality Gates - `nox -s lint` — PASS - `nox -s typecheck` — PASS (0 errors) - `nox -s integration_tests` — All 5 WF16 tests PASS - Helper file: 377 lines (under 500 limit) Closes #780
brent.edwards force-pushed test/int-wf16-devcontainer from f486151c9e to 143f528594 2026-03-14 06:59:04 +00:00 Compare
brent.edwards added this to the v3.7.0 milestone 2026-03-14 06:59:14 +00:00
brent.edwards added the
Type
Testing
 label 2026-03-14 06:59:14 +00:00
brent.edwards reviewed 2026-03-14 19:51:06 +00:00
brent.edwards left a comment
Author
Member
Copy Link
Copy Source

Self-Review — PR #953

Reviewer: @brent.edwards (author self-review)
Review method: 4 parallel threads + 2 fresh-eyes passes

Structural Issue

P1:must-fix — Duplicate pre-existing fixes across 6 PRs

Same 9 shared files as PRs #951/#952. Must be rebased after earlier PRs merge.

PR-Specific Findings

P1:must-fix — Missing Force Tags entirely

robot/wf16_devcontainer.robot

The robot file has zero tags — no Force Tags in Settings, no [Tags] on test cases. Cannot filter by wf16, integration, or v3.7.0. All other workflow tests have Force Tags.

P2:should-fix — No timeout= on Run Process calls

robot/wf16_devcontainer.robot

Uses [Timeout] 120s at test-case level but no timeout= on Run Process. If the RF timeout fires, the subprocess may continue as an orphan. Other helpers pass timeout=120s to Run Process directly.

P3:nit — Lazy import re inside _plan_id() instead of top-level

Minor style inconsistency — re is a stdlib module with negligible import cost.

Verdict

2 P1, 1 P2, 1 P3. Must fix tags and rebase before merge.

# Self-Review — PR #953 **Reviewer:** @brent.edwards (author self-review) **Review method:** 4 parallel threads + 2 fresh-eyes passes ## Structural Issue ### P1:must-fix — Duplicate pre-existing fixes across 6 PRs Same 9 shared files as PRs #951/#952. Must be rebased after earlier PRs merge. ## PR-Specific Findings ### P1:must-fix — Missing `Force Tags` entirely `robot/wf16_devcontainer.robot` The robot file has zero tags — no `Force Tags` in Settings, no `[Tags]` on test cases. Cannot filter by `wf16`, `integration`, or `v3.7.0`. All other workflow tests have `Force Tags`. ### P2:should-fix — No `timeout=` on `Run Process` calls `robot/wf16_devcontainer.robot` Uses `[Timeout] 120s` at test-case level but no `timeout=` on `Run Process`. If the RF timeout fires, the subprocess may continue as an orphan. Other helpers pass `timeout=120s` to `Run Process` directly. ### P3:nit — Lazy `import re` inside `_plan_id()` instead of top-level Minor style inconsistency — `re` is a stdlib module with negligible import cost. ## Verdict **2 P1, 1 P2, 1 P3.** Must fix tags and rebase before merge.
freemo reviewed 2026-03-14 22:10:15 +00:00
freemo left a comment
Owner
Copy Link
Copy Source

PM Status — Day 34 (2026-03-14)

PR is mergeable, well-structured. WF16 (devcontainer-driven development) is an M8 integration test.

Missing labels: This PR needs Priority/Medium, MoSCoW/Could have, and Points/3 labels added.

Action: Ready for peer review. Low priority — M8 has no deadline and should not take priority over M3/M6 work. Park for now.

**PM Status — Day 34 (2026-03-14)** PR is mergeable, well-structured. WF16 (devcontainer-driven development) is an M8 integration test. **Missing labels:** This PR needs `Priority/Medium`, `MoSCoW/Could have`, and `Points/3` labels added. **Action:** Ready for peer review. Low priority — M8 has no deadline and should not take priority over M3/M6 work. Park for now.
freemo added the
MoSCoW
Could have
Points
3
Priority
Medium
 labels 2026-03-14 22:10:26 +00:00
brent.edwards force-pushed test/int-wf16-devcontainer from 143f528594 to 148627b239 2026-03-15 04:50:01 +00:00 Compare
brent.edwards commented 2026-03-15 19:23:10 +00:00
Author
Member
Copy Link
Copy Source

Response to Self-Review P1s

P1 — Duplicate pre-existing fixes
Will rebase after earlier PRs merge.

P1 — Missing Force Tags
Will add Force Tags wf16 integration v3.7.0 to wf16_devcontainer.robot.

P2 — No timeout= on Run Process
Will add timeout=120s to all Run Process calls.

P3 — Lazy import re
Will move to top-level.

Will fix all P1s and rebase when the merge sequence begins.

## Response to Self-Review P1s **P1 — Duplicate pre-existing fixes** Will rebase after earlier PRs merge. **P1 — Missing `Force Tags`** Will add `Force Tags wf16 integration v3.7.0` to `wf16_devcontainer.robot`. **P2 — No `timeout=` on `Run Process`** Will add `timeout=120s` to all `Run Process` calls. **P3 — Lazy `import re`** Will move to top-level. Will fix all P1s and rebase when the merge sequence begins.
brent.edwards force-pushed test/int-wf16-devcontainer from 148627b239 to 50ec68fe0f 2026-03-15 19:41:06 +00:00 Compare
freemo added a new dependency 2026-03-16 02:42:22 +00:00
#627 Implement @tdd_expected_fail tag handling in Behave environment
freemo added a new dependency 2026-03-16 02:42:22 +00:00
#628 Implement @tdd_expected_fail tag handling in Robot Framework
freemo commented 2026-03-16 09:21:35 +00:00
Owner
Copy Link
Copy Source

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

@brent.edwards — Self-review P1 response acknowledged (Day 35).

Milestone: M8 (v3.7.0) — Could Have. Low urgency. Focus on M3-M6 PRs first.

Action: Push P1 fixes when bandwidth allows. Review assignment deferred until M3-M6 queue clears.

Who Action Deadline
@brent.edwards Push P1 fixes when M3-M6 work allows No hard deadline
## PM Status — Day 36 (2026-03-16) @brent.edwards — Self-review P1 response acknowledged (Day 35). **Milestone**: M8 (v3.7.0) — Could Have. Low urgency. Focus on M3-M6 PRs first. **Action**: Push P1 fixes when bandwidth allows. Review assignment deferred until M3-M6 queue clears. | Who | Action | Deadline | |-----|--------|----------| | @brent.edwards | Push P1 fixes when M3-M6 work allows | No hard deadline |
freemo requested review from freemo 2026-03-17 18:33:59 +00:00
freemo requested review from hamza.khyari 2026-03-17 18:33:59 +00:00
freemo commented 2026-03-17 18:34:07 +00:00
Owner
Copy Link
Copy Source

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*
brent.edwards force-pushed test/int-wf16-devcontainer from 3248c86aeb to 8f8e74d5f3 2026-03-19 00:03:20 +00:00 Compare
brent.edwards commented 2026-03-19 00:03:38 +00:00
Author
Member
Copy Link
Copy Source

Self-Review P1 Fixes — Summary

Commit: 8f8e74d5 (tip of test/int-wf16-devcontainer)
Branch: squash-rebased onto master (0 commits behind), 2 clean commits

Changes Applied

Priority Issue Fix
P1 Missing devcontainer Force Tag Added devcontainer to Force Tags in wf16_devcontainer.robot
P2 No on_timeout=kill on Run Process calls Added on_timeout=kill to all 5 Run Process calls — prevents zombie subprocesses on CI timeout
P3 Lazy import re inside function Already at module top-level — no action needed
— CHANGELOG entry for #780 Added entry under ## Unreleased
— # type: ignore audit None found — clean

Squash-Rebase

Collapsed 3 real commits + 3 merge commits (13 behind master) into:

  1. 8f2232c2 — test(integration): workflow example 16 — devcontainer-driven development (supervised profile)
  2. 8f8e74d5 — fix(test): address self-review P1/P2 issues on wf16 integration test

Lint / Typecheck

  • Ruff lint: no violations
  • Ruff format: all files formatted
  • Pyright: no issues (0 diagnostics)

ISSUES CLOSED: #780

## Self-Review P1 Fixes — Summary **Commit:** `8f8e74d5` (tip of `test/int-wf16-devcontainer`) **Branch:** squash-rebased onto master (0 commits behind), 2 clean commits ### Changes Applied | Priority | Issue | Fix | |----------|-------|-----| | **P1** | Missing `devcontainer` Force Tag | Added `devcontainer` to `Force Tags` in `wf16_devcontainer.robot` | | **P2** | No `on_timeout=kill` on `Run Process` calls | Added `on_timeout=kill` to all 5 `Run Process` calls — prevents zombie subprocesses on CI timeout | | **P3** | Lazy `import re` inside function | Already at module top-level — no action needed | | — | CHANGELOG entry for #780 | Added entry under `## Unreleased` | | — | `# type: ignore` audit | None found — clean | ### Squash-Rebase Collapsed 3 real commits + 3 merge commits (13 behind master) into: 1. `8f2232c2` — `test(integration): workflow example 16 — devcontainer-driven development (supervised profile)` 2. `8f8e74d5` — `fix(test): address self-review P1/P2 issues on wf16 integration test` ### Lint / Typecheck - **Ruff lint:** no violations - **Ruff format:** all files formatted - **Pyright:** no issues (0 diagnostics) ISSUES CLOSED: #780
brent.edwards commented 2026-03-19 00:16:24 +00:00
Author
Member
Copy Link
Copy Source

Self-Review P1 Fixes Applied — Commit 8f8e74d5

Branch squash-rebased onto origin/master. All merge commits eliminated. Self-review findings verified/fixed:

Finding Status
P1: Missing Force Tags Fixed — added devcontainer tag
P2: No on_timeout=kill on Run Process Fixed — all 5 calls
P3: Lazy import re Already at top-level
CHANGELOG entry for #780 Fixed
  • nox -s lint — PASS
  • nox -s typecheck — PASS (0 errors)
## Self-Review P1 Fixes Applied — Commit `8f8e74d5` Branch squash-rebased onto `origin/master`. All merge commits eliminated. Self-review findings verified/fixed: | Finding | Status | |---------|--------| | **P1**: Missing `Force Tags` | **Fixed** — added `devcontainer` tag | | **P2**: No `on_timeout=kill` on Run Process | **Fixed** — all 5 calls | | **P3**: Lazy `import re` | Already at top-level | | CHANGELOG entry for #780 | **Fixed** | - `nox -s lint` — **PASS** - `nox -s typecheck` — **PASS** (0 errors)
brent.edwards force-pushed test/int-wf16-devcontainer from 8f8e74d5f3 to 22d74d8da6 2026-03-19 00:17:04 +00:00 Compare
freemo approved these changes 2026-03-19 04:57:36 +00:00
Dismissed
freemo left a comment
Owner
Copy Link
Copy Source

Code Review — PR #953

Well-structured integration test for WF16. Proper labels, milestone, and issue linkage. Approved.

## Code Review — PR #953 Well-structured integration test for WF16. Proper labels, milestone, and issue linkage. **Approved.**
freemo requested review from freemo 2026-03-19 05:20:58 +00:00
brent.edwards dismissed freemo's review 2026-03-21 04:26:16 +00:00
Reason:

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

brent.edwards force-pushed test/int-wf16-devcontainer from 8bd9b0d0b5 to a7a70ce077 2026-03-26 20:03:10 +00:00 Compare
freemo self-assigned this 2026-04-02 06:15:21 +00:00
freemo requested changes 2026-04-02 07:18:44 +00:00
freemo left a comment
Owner
Copy Link
Copy Source

Independent Code Review — PR #953

Reviewer: freemo (independent review, different perspective from author)
Scope: Full diff review of robot/wf16_devcontainer.robot, robot/helper_wf16_devcontainer.py, and CHANGELOG.md

🚫 BLOCKER: Merge Conflicts

The PR has mergeable: false. The branch is behind master and has conflicts (likely in CHANGELOG.md where both sides added entries under ## Unreleased). The branch must be rebased onto current master before merge.

✅ Code Quality Assessment (Positive)

The implementation is well-structured and follows project conventions. Specific observations:

Robot Framework file (wf16_devcontainer.robot):

  • ✅ Force Tags properly applied with wf16, integration, devcontainer, v3.7.0, tdd_issue, tdd_issue_780 — consistent with WF03 pattern
  • ✅ Suite Setup/Suite Teardown using Setup Test Environment With Database Isolation / Cleanup Test Environment from common.resource
  • ✅ [Timeout] 120s on every test case
  • ✅ timeout=120s and on_timeout=kill on all Run Process calls (P2 fix verified)
  • ✅ Each test case has [Documentation]
  • ✅ Logs both stdout and stderr
  • ✅ Sentinel string verification pattern matches other workflow tests

Python helper (helper_wf16_devcontainer.py):

  • ✅ 376 lines (under 500-line limit)
  • ✅ from __future__ import annotations present
  • ✅ All imports at top of file (including re — P3 fix verified)
  • ✅ No # type: ignore anywhere
  • ✅ All functions have proper type annotations (NoReturn for _fail(), str | None for _plan_id(), etc.)
  • ✅ _MockResult uses @dataclass with proper field types
  • ✅ _MockRunner has full type annotations on __call__ and properties
  • ✅ Every test function has try/finally for cleanup (shutil.rmtree, cleanup_workspace, os.unlink, clear_lifecycle_registry)
  • ✅ reset_global_state() called before each command dispatch
  • ✅ All imported domain modules verified to exist: ContainerLifecycleState, activate_container, clear_lifecycle_registry, get_lifecycle_tracker, stop_container, discover_devcontainers
  • ✅ Function signatures match actual API: discover_devcontainers(repo, "git-checkout"), activate_container(rid, repo, run_command=runner, session_id=pid), stop_container(rid, run_command=runner)
  • ✅ Common helpers (setup_workspace, cleanup_workspace, init_bare_git_repo, run_cli, write_yaml, reset_global_state) all verified to exist in helper_e2e_common.py and helpers_common.py

Spec Alignment (Issue #780 Acceptance Criteria):

  • ✅ Robot Framework test suite in robot/ directory
  • ✅ Integration-appropriate mocking (mocked LLM via env var, mocked container runtime via _MockRunner)
  • ✅ Devcontainer auto-detection verified (discover_devcontainers() in Step 1)
  • ✅ Lazy container build on first execution verified (Step 4 — activate_container with mock runner)
  • ✅ Tool invocations route to container workspace verified (Step 4 — workspace_path assertion)
  • ✅ Apply writes changes to host verified (Step 5 — host_workspace_path assertion + stop_container)

PR Metadata:

  • ✅ Type/Testing label present
  • ✅ Milestone v3.7.0 assigned
  • ✅ Closes #780 in PR body
  • ✅ Commit message follows Conventional Changelog format

Required Action

  1. Rebase onto current master to resolve merge conflicts (primarily CHANGELOG.md)
  2. Ensure nox -s integration_tests passes after rebase
  3. Force-push the rebased branch

Once the branch is conflict-free and CI passes, this PR is ready to merge.

## Independent Code Review — PR #953 **Reviewer**: freemo (independent review, different perspective from author) **Scope**: Full diff review of `robot/wf16_devcontainer.robot`, `robot/helper_wf16_devcontainer.py`, and `CHANGELOG.md` --- ### 🚫 BLOCKER: Merge Conflicts The PR has `mergeable: false`. The branch is behind `master` and has conflicts (likely in `CHANGELOG.md` where both sides added entries under `## Unreleased`). **The branch must be rebased onto current `master` before merge.** --- ### ✅ Code Quality Assessment (Positive) The implementation is well-structured and follows project conventions. Specific observations: **Robot Framework file (`wf16_devcontainer.robot`)**: - ✅ `Force Tags` properly applied with `wf16`, `integration`, `devcontainer`, `v3.7.0`, `tdd_issue`, `tdd_issue_780` — consistent with WF03 pattern - ✅ `Suite Setup`/`Suite Teardown` using `Setup Test Environment With Database Isolation` / `Cleanup Test Environment` from `common.resource` - ✅ `[Timeout] 120s` on every test case - ✅ `timeout=120s` and `on_timeout=kill` on all `Run Process` calls (P2 fix verified) - ✅ Each test case has `[Documentation]` - ✅ Logs both stdout and stderr - ✅ Sentinel string verification pattern matches other workflow tests **Python helper (`helper_wf16_devcontainer.py`)**: - ✅ 376 lines (under 500-line limit) - ✅ `from __future__ import annotations` present - ✅ All imports at top of file (including `re` — P3 fix verified) - ✅ No `# type: ignore` anywhere - ✅ All functions have proper type annotations (`NoReturn` for `_fail()`, `str | None` for `_plan_id()`, etc.) - ✅ `_MockResult` uses `@dataclass` with proper field types - ✅ `_MockRunner` has full type annotations on `__call__` and properties - ✅ Every test function has `try/finally` for cleanup (`shutil.rmtree`, `cleanup_workspace`, `os.unlink`, `clear_lifecycle_registry`) - ✅ `reset_global_state()` called before each command dispatch - ✅ All imported domain modules verified to exist: `ContainerLifecycleState`, `activate_container`, `clear_lifecycle_registry`, `get_lifecycle_tracker`, `stop_container`, `discover_devcontainers` - ✅ Function signatures match actual API: `discover_devcontainers(repo, "git-checkout")`, `activate_container(rid, repo, run_command=runner, session_id=pid)`, `stop_container(rid, run_command=runner)` - ✅ Common helpers (`setup_workspace`, `cleanup_workspace`, `init_bare_git_repo`, `run_cli`, `write_yaml`, `reset_global_state`) all verified to exist in `helper_e2e_common.py` and `helpers_common.py` **Spec Alignment (Issue #780 Acceptance Criteria)**: - ✅ Robot Framework test suite in `robot/` directory - ✅ Integration-appropriate mocking (mocked LLM via env var, mocked container runtime via `_MockRunner`) - ✅ Devcontainer auto-detection verified (`discover_devcontainers()` in Step 1) - ✅ Lazy container build on first execution verified (Step 4 — `activate_container` with mock runner) - ✅ Tool invocations route to container workspace verified (Step 4 — `workspace_path` assertion) - ✅ Apply writes changes to host verified (Step 5 — `host_workspace_path` assertion + `stop_container`) **PR Metadata**: - ✅ `Type/Testing` label present - ✅ Milestone `v3.7.0` assigned - ✅ `Closes #780` in PR body - ✅ Commit message follows Conventional Changelog format --- ### Required Action 1. **Rebase onto current `master`** to resolve merge conflicts (primarily `CHANGELOG.md`) 2. Ensure `nox -s integration_tests` passes after rebase 3. Force-push the rebased branch Once the branch is conflict-free and CI passes, this PR is ready to merge.
freemo commented 2026-04-02 16:22:06 +00:00
Owner
Copy Link
Copy Source

🤖 Backlog Groomer (groomer-1) — Duplicate Detected

This PR (#953) is a duplicate of the canonical tracking issue #780 ("test(integration): workflow example 16 — devcontainer-driven development (supervised profile)").

Rationale:

  • #780 is the original tracking issue with full metadata: MoSCoW/Must have, Points/5, Priority/Medium, State/In Review, Type/Testing, and a complete Definition of Done checklist.
  • This PR (#953) was opened later and its body explicitly states Closes #780, confirming it is the implementation PR for that tracking issue.
  • The PR itself is not a separate work item — it is the delivery vehicle for #780.

Action: Closing this issue as a duplicate of #780. All tracking, review, and merge activity should be associated with #780.

🤖 **Backlog Groomer (groomer-1) — Duplicate Detected** This PR (#953) is a duplicate of the canonical tracking issue **#780** ("test(integration): workflow example 16 — devcontainer-driven development (supervised profile)"). **Rationale:** - #780 is the original tracking issue with full metadata: MoSCoW/Must have, Points/5, Priority/Medium, State/In Review, Type/Testing, and a complete Definition of Done checklist. - This PR (#953) was opened later and its body explicitly states `Closes #780`, confirming it is the implementation PR for that tracking issue. - The PR itself is not a separate work item — it is the delivery vehicle for #780. **Action:** Closing this issue as a duplicate of #780. All tracking, review, and merge activity should be associated with #780.
freemo closed this pull request 2026-04-02 16:22:18 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 47s
Required
Details
CI / lint (pull_request) Successful in 7m23s
Required
Details
CI / quality (pull_request) Successful in 7m38s
Required
Details
CI / security (pull_request) Successful in 8m0s
Required
Details
CI / typecheck (pull_request) Successful in 8m30s
Required
Details
CI / unit_tests (pull_request) Successful in 11m45s
Required
Details
CI / docker (pull_request) Successful in 1m18s
Required
Details
CI / integration_tests (pull_request) Successful in 13m31s
Required
Details
CI / e2e_tests (pull_request) Successful in 16m13s
Details
CI / coverage (pull_request) Successful in 11m32s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 1h1m11s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
brent.edwards
hamza.khyari
freemo
Labels
Clear labels
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
 controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
 overdue
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
 auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
 auto/claimed-implementer
Currently being processed by an implementer worker.
 auto/claimed-merge
Currently being processed by the merge driver.
 auto/claimed-reviewer
Currently being processed by a reviewer worker.
 auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
 auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
 auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
 auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
 Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.
 auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.
 auto/needs-implementer
Failing CI needs implementer attention.
 auto/postmortem
Documenting a driver incident or rollback.
 auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
 auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
 auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
 auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
 auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
 auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
 Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
MoSCoW
Could have
Points
3
Priority
Medium
Type
Testing
Milestone
No items
No Milestone v3.7.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees freemo
2 Participants
Notifications
Due Date
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#953
Delete Branch "test/int-wf16-devcontainer"

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