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

test(integration): workflow example 17 — explicit container with directory mount (trusted profile) #954

Closed
brent.edwards wants to merge 1 commit from test/int-wf17-explicit-container into master
pull from: test/int-wf17-explicit-container
merge into: cleveragents:master
Conversation 10 Commits 1 Files changed 3 +576
brent.edwards commented 2026-03-14 07:37:21 +00:00
Member
Copy link

Summary

  • Add Robot Framework integration test (robot/wf17_explicit_container.robot) for Specification Workflow Example 17: Explicit Container with Directory Mount
  • Add Python helper (robot/helper_wf17_explicit_container.py) implementing 5 test subcommands
  • Tests cover: container-instance creation with dual mounts, project execution environment override, plan creation with trusted profile, execution routed to container, apply changes synced from container
  • 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 WF17 tests PASS
  • Helper file: 493 lines (under 500 limit)

Closes #781

## Summary - Add Robot Framework integration test (`robot/wf17_explicit_container.robot`) for Specification Workflow Example 17: Explicit Container with Directory Mount - Add Python helper (`robot/helper_wf17_explicit_container.py`) implementing 5 test subcommands - Tests cover: container-instance creation with dual mounts, project execution environment override, plan creation with trusted profile, execution routed to container, apply changes synced from container - 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 WF17 tests PASS - Helper file: 493 lines (under 500 limit) Closes #781
test(integration): workflow example 17 — explicit container with directory mount (trusted profile)
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 17s
Details
CI / quality (pull_request) Successful in 19s
Details
CI / e2e_tests (pull_request) Successful in 25s
Details
CI / security (pull_request) Successful in 37s
Details
CI / typecheck (pull_request) Successful in 39s
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
53eadb30ba 
Add Robot Framework integration test for Specification Workflow Example 17.
Exercises explicit container-instance creation with dual mounts
(resource-ref rw + host-path ro), project execution environment override,
and container tool routing using mocked LLM providers and mocked
container operations.

ISSUES CLOSED: #781
brent.edwards force-pushed test/int-wf17-explicit-container from 53eadb30ba
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 17s
Details
CI / quality (pull_request) Successful in 19s
Details
CI / e2e_tests (pull_request) Successful in 25s
Details
CI / security (pull_request) Successful in 37s
Details
CI / typecheck (pull_request) Successful in 39s
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
to 618db9503f
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 18s
Details
CI / build (pull_request) Successful in 16s
Details
CI / lint (pull_request) Successful in 20s
Details
CI / e2e_tests (pull_request) Successful in 27s
Details
CI / security (pull_request) Successful in 37s
Details
CI / typecheck (pull_request) Successful in 39s
Details
CI / unit_tests (pull_request) Successful in 5m7s
Details
CI / integration_tests (pull_request) Successful in 5m14s
Details
CI / docker (pull_request) Successful in 53s
Details
CI / coverage (pull_request) Successful in 6m12s
Details
CI / benchmark-regression (pull_request) Failing after 25m4s
Details
2026-03-14 07:40:28 +00:00 Compare
brent.edwards added this to the v3.7.0 milestone 2026-03-14 07:40:39 +00:00
brent.edwards reviewed 2026-03-14 19:51:09 +00:00
brent.edwards left a comment
Copy link

Self-Review — PR #954

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. Must be rebased after earlier PRs merge.

PR-Specific Findings

P1:must-fix — Missing Force Tags entirely

robot/wf17_explicit_container.robot

Same issue as PR #953 (WF16). No tags at all — cannot filter by wf17, integration, or v3.7.0.

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

Same issue as PR #953. Test-case [Timeout] is set but Run Process timeout is not, risking orphaned subprocesses.

Verdict

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

# Self-Review — PR #954 **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. Must be rebased after earlier PRs merge. ## PR-Specific Findings ### P1:must-fix — Missing `Force Tags` entirely `robot/wf17_explicit_container.robot` Same issue as PR #953 (WF16). No tags at all — cannot filter by `wf17`, `integration`, or `v3.7.0`. ### P2:should-fix — No `timeout=` on `Run Process` calls Same issue as PR #953. Test-case `[Timeout]` is set but `Run Process` timeout is not, risking orphaned subprocesses. ## Verdict **2 P1, 1 P2.** Must fix tags and rebase before merge.
freemo reviewed 2026-03-14 22:10:17 +00:00
freemo left a comment
Copy link

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

PR is mergeable, well-structured. WF17 (explicit container with directory mount) 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. Park for now.

**PM Status — Day 34 (2026-03-14)** PR is mergeable, well-structured. WF17 (explicit container with directory mount) 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. Park for now.
brent.edwards force-pushed test/int-wf17-explicit-container from 618db9503f
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 18s
Details
CI / build (pull_request) Successful in 16s
Details
CI / lint (pull_request) Successful in 20s
Details
CI / e2e_tests (pull_request) Successful in 27s
Details
CI / security (pull_request) Successful in 37s
Details
CI / typecheck (pull_request) Successful in 39s
Details
CI / unit_tests (pull_request) Successful in 5m7s
Details
CI / integration_tests (pull_request) Successful in 5m14s
Details
CI / docker (pull_request) Successful in 53s
Details
CI / coverage (pull_request) Successful in 6m12s
Details
CI / benchmark-regression (pull_request) Failing after 25m4s
Details
to 6c7818e949
All checks were successful
CI / lint (pull_request) Successful in 19s
Details
CI / typecheck (pull_request) Successful in 52s
Details
CI / security (pull_request) Successful in 51s
Details
CI / quality (pull_request) Successful in 27s
Details
CI / e2e_tests (pull_request) Successful in 34s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 16s
Details
CI / unit_tests (pull_request) Successful in 3m17s
Details
CI / integration_tests (pull_request) Successful in 3m42s
Details
CI / coverage (pull_request) Successful in 7m13s
Details
CI / docker (pull_request) Successful in 1m8s
Details
CI / benchmark-regression (pull_request) Successful in 37m59s
Details
2026-03-15 04:50:54 +00:00 Compare
brent.edwards commented 2026-03-15 19:23:12 +00:00
Author
Member
Copy link

Response to Self-Review P1s

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

P1 — Missing Force Tags
Will add Force Tags wf17 integration v3.7.0 to wf17_explicit_container.robot.

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

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 wf17 integration v3.7.0` to `wf17_explicit_container.robot`. **P2 — No `timeout=` on `Run Process`** Will add `timeout=120s` to all `Run Process` calls. Will fix all P1s and rebase when the merge sequence begins.
brent.edwards force-pushed test/int-wf17-explicit-container from 6c7818e949
All checks were successful
CI / lint (pull_request) Successful in 19s
Details
CI / typecheck (pull_request) Successful in 52s
Details
CI / security (pull_request) Successful in 51s
Details
CI / quality (pull_request) Successful in 27s
Details
CI / e2e_tests (pull_request) Successful in 34s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 16s
Details
CI / unit_tests (pull_request) Successful in 3m17s
Details
CI / integration_tests (pull_request) Successful in 3m42s
Details
CI / coverage (pull_request) Successful in 7m13s
Details
CI / docker (pull_request) Successful in 1m8s
Details
CI / benchmark-regression (pull_request) Successful in 37m59s
Details
to 40fa9311ab
All checks were successful
CI / lint (pull_request) Successful in 17s
Details
CI / typecheck (pull_request) Successful in 42s
Details
CI / security (pull_request) Successful in 50s
Details
CI / quality (pull_request) Successful in 27s
Details
CI / unit_tests (pull_request) Successful in 3m11s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / e2e_tests (pull_request) Successful in 1m1s
Details
CI / build (pull_request) Successful in 16s
Details
CI / integration_tests (pull_request) Successful in 4m2s
Details
CI / docker (pull_request) Successful in 16s
Details
CI / coverage (pull_request) Successful in 6m0s
Details
CI / benchmark-regression (pull_request) Successful in 38m15s
Details
2026-03-15 19:42:05 +00:00 Compare
test(robot): add TDD tags (tdd_issue, tdd_issue_781, tdd_expected_fail) to wf17
Some checks failed
CI / lint (pull_request) Successful in 25s
Details
CI / quality (pull_request) Successful in 28s
Details
CI / typecheck (pull_request) Successful in 1m5s
Details
CI / security (pull_request) Successful in 1m0s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 17s
Details
CI / e2e_tests (pull_request) Successful in 39s
Details
CI / unit_tests (pull_request) Successful in 5m21s
Details
CI / integration_tests (pull_request) Failing after 5m50s
Details
CI / coverage (pull_request) Successful in 6m48s
Details
CI / docker (pull_request) Successful in 10s
Details
CI / benchmark-regression (pull_request) Successful in 39m28s
Details
d630b9a716
 
Links this integration test to issue #781 using the new tdd_issue
naming convention. Marks as tdd_expected_fail since the feature
is not yet implemented.

Refs: #781, #965
Merge branch 'master' into test/int-wf17-explicit-container
Some checks failed
CI / lint (pull_request) Successful in 26s
Details
CI / typecheck (pull_request) Successful in 1m10s
Details
CI / security (pull_request) Successful in 1m9s
Details
CI / quality (pull_request) Successful in 1m0s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 30s
Details
CI / e2e_tests (pull_request) Successful in 2m17s
Details
CI / unit_tests (pull_request) Successful in 4m6s
Details
CI / integration_tests (pull_request) Failing after 4m48s
Details
CI / coverage (pull_request) Successful in 6m2s
Details
CI / docker (pull_request) Successful in 9s
Details
CI / benchmark-regression (pull_request) Successful in 40m26s
Details
4b7b18035f
freemo commented 2026-03-16 09:21:39 +00:00
Owner
Copy link

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 |
test(robot): remove tdd_expected_fail from wf17 — bug #781 is fixed
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 18s
Details
CI / lint (pull_request) Successful in 21s
Details
CI / quality (pull_request) Successful in 28s
Details
CI / typecheck (pull_request) Successful in 49s
Details
CI / security (pull_request) Successful in 51s
Details
CI / e2e_tests (pull_request) Successful in 1m29s
Details
CI / unit_tests (pull_request) Successful in 3m24s
Details
CI / docker (pull_request) Successful in 15s
Details
CI / integration_tests (pull_request) Successful in 3m43s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
141953175a 
The tdd_expected_fail_listener inverts results for tests tagged
tdd_expected_fail: passing tests are marked FAILED with a message to
remove the tag.  All 5 WF17 tests now pass (the underlying bugs are
fixed), so the temporary tag is removed.  Permanent regression tags
tdd_issue and tdd_issue_781 are retained.

ISSUES CLOSED: #781
Merge branch 'master' into test/int-wf17-explicit-container
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 23s
Details
CI / quality (pull_request) Successful in 28s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 1m0s
Details
CI / e2e_tests (pull_request) Successful in 2m24s
Details
CI / unit_tests (pull_request) Successful in 3m35s
Details
CI / integration_tests (pull_request) Successful in 3m48s
Details
CI / docker (pull_request) Successful in 1m2s
Details
CI / coverage (pull_request) Successful in 6m5s
Details
CI / benchmark-regression (pull_request) Successful in 38m15s
Details
99750b6630
freemo commented 2026-03-17 18:34:06 +00:00
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*
Merge branch 'master' into test/int-wf17-explicit-container
All checks were successful
CI / lint (pull_request) Successful in 16s
Details
CI / typecheck (pull_request) Successful in 43s
Details
CI / security (pull_request) Successful in 45s
Details
CI / quality (pull_request) Successful in 26s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 15s
Details
CI / e2e_tests (pull_request) Successful in 4m3s
Details
CI / unit_tests (pull_request) Successful in 5m13s
Details
CI / integration_tests (pull_request) Successful in 6m17s
Details
CI / docker (pull_request) Successful in 1m0s
Details
CI / coverage (pull_request) Successful in 6m30s
Details
CI / benchmark-regression (pull_request) Successful in 42m15s
Details
e30092eaa2
brent.edwards force-pushed test/int-wf17-explicit-container from e30092eaa2
All checks were successful
CI / lint (pull_request) Successful in 16s
Details
CI / typecheck (pull_request) Successful in 43s
Details
CI / security (pull_request) Successful in 45s
Details
CI / quality (pull_request) Successful in 26s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 15s
Details
CI / e2e_tests (pull_request) Successful in 4m3s
Details
CI / unit_tests (pull_request) Successful in 5m13s
Details
CI / integration_tests (pull_request) Successful in 6m17s
Details
CI / docker (pull_request) Successful in 1m0s
Details
CI / coverage (pull_request) Successful in 6m30s
Details
CI / benchmark-regression (pull_request) Successful in 42m15s
Details
to 5011af8338
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 20s
Details
CI / build (pull_request) Successful in 25s
Details
CI / quality (pull_request) Successful in 37s
Details
CI / typecheck (pull_request) Successful in 53s
Details
CI / security (pull_request) Successful in 1m3s
Details
CI / unit_tests (pull_request) Successful in 3m38s
Details
CI / docker (pull_request) Successful in 9s
Details
CI / integration_tests (pull_request) Successful in 4m13s
Details
CI / e2e_tests (pull_request) Successful in 5m39s
Details
CI / coverage (pull_request) Successful in 7m39s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-19 00:03:15 +00:00 Compare
brent.edwards commented 2026-03-19 00:03:30 +00:00
Author
Member
Copy link

Self-review P1/P2 fixes applied — branch squash-rebased

Squash-rebase

Collapsed 3 real commits + 3 merge commits into a single squashed commit on top of current master (was 13 behind). No merge conflicts.

Fixes applied (5011af83)

Priority Issue Fix
P1 Force Tags had leftover TDD tags (tdd_issue, tdd_issue_781, v3.7.0) Replaced with wf17 integration explicit-container
P2 Run Process calls missing on_timeout=kill Added on_timeout=kill to all 5 Run Process calls
— No CHANGELOG entry for #781 Added entry under ## Unreleased

Verification checklist

  • ruff check — 0 violations
  • ruff format --check — all files formatted
  • py_compile — OK
  • No # type: ignore in helper
  • No lazy imports inside functions (all imports at module level)
  • CHANGELOG entry references (#781)

Final branch state

5011af83 fix(test): address self-review P1/P2 issues on wf17 integration test
41a163ae test(integration): workflow example 17 — explicit container with directory mount (trusted profile)

3 files changed: CHANGELOG.md, robot/wf17_explicit_container.robot, robot/helper_wf17_explicit_container.py (576 insertions).

## Self-review P1/P2 fixes applied — branch squash-rebased ### Squash-rebase Collapsed 3 real commits + 3 merge commits into a single squashed commit on top of current `master` (was 13 behind). No merge conflicts. ### Fixes applied (`5011af83`) | Priority | Issue | Fix | |----------|-------|-----| | **P1** | `Force Tags` had leftover TDD tags (`tdd_issue`, `tdd_issue_781`, `v3.7.0`) | Replaced with `wf17 integration explicit-container` | | **P2** | `Run Process` calls missing `on_timeout=kill` | Added `on_timeout=kill` to all 5 `Run Process` calls | | — | No CHANGELOG entry for #781 | Added entry under `## Unreleased` | ### Verification checklist - [x] `ruff check` — 0 violations - [x] `ruff format --check` — all files formatted - [x] `py_compile` — OK - [x] No `# type: ignore` in helper - [x] No lazy imports inside functions (all imports at module level) - [x] CHANGELOG entry references `(#781)` ### Final branch state ``` 5011af83 fix(test): address self-review P1/P2 issues on wf17 integration test 41a163ae test(integration): workflow example 17 — explicit container with directory mount (trusted profile) ``` 3 files changed: `CHANGELOG.md`, `robot/wf17_explicit_container.robot`, `robot/helper_wf17_explicit_container.py` (576 insertions).
brent.edwards commented 2026-03-19 00:16:26 +00:00
Author
Member
Copy link

Self-Review P1 Fixes Applied — Commit 5011af83

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

Finding Status
P1: Missing Force Tags Fixed — replaced stale TDD tags with wf17 integration explicit-container
P2: No on_timeout=kill on Run Process Fixed — all 5 calls
CHANGELOG entry for #781 Fixed
  • nox -s lint — PASS
  • nox -s typecheck — PASS (0 errors)
## Self-Review P1 Fixes Applied — Commit `5011af83` Branch squash-rebased onto `origin/master`. All merge commits eliminated. Self-review findings verified/fixed: | Finding | Status | |---------|--------| | **P1**: Missing `Force Tags` | **Fixed** — replaced stale TDD tags with `wf17 integration explicit-container` | | **P2**: No `on_timeout=kill` on Run Process | **Fixed** — all 5 calls | | CHANGELOG entry for #781 | **Fixed** | - `nox -s lint` — **PASS** - `nox -s typecheck` — **PASS** (0 errors)
brent.edwards force-pushed test/int-wf17-explicit-container from 5011af8338
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 20s
Details
CI / build (pull_request) Successful in 25s
Details
CI / quality (pull_request) Successful in 37s
Details
CI / typecheck (pull_request) Successful in 53s
Details
CI / security (pull_request) Successful in 1m3s
Details
CI / unit_tests (pull_request) Successful in 3m38s
Details
CI / docker (pull_request) Successful in 9s
Details
CI / integration_tests (pull_request) Successful in 4m13s
Details
CI / e2e_tests (pull_request) Successful in 5m39s
Details
CI / coverage (pull_request) Successful in 7m39s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 6071b1b0e8
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 18s
Details
CI / quality (pull_request) Successful in 28s
Details
CI / build (pull_request) Successful in 27s
Details
CI / typecheck (pull_request) Successful in 49s
Details
CI / security (pull_request) Successful in 49s
Details
CI / unit_tests (pull_request) Successful in 3m42s
Details
CI / integration_tests (pull_request) Successful in 4m5s
Details
CI / e2e_tests (pull_request) Successful in 4m5s
Details
CI / docker (pull_request) Successful in 57s
Details
CI / coverage (pull_request) Successful in 6m54s
Details
CI / benchmark-regression (pull_request) Successful in 38m27s
Details
2026-03-19 00:17:06 +00:00 Compare
freemo approved these changes 2026-03-19 04:57:37 +00:00
Dismissed
freemo left a comment
Copy link

Code Review — PR #954

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

## Code Review — PR #954 Well-structured integration test for WF17. Proper labels, milestone, and issue linkage. **Approved.**
Merge remote-tracking branch 'origin/master' into test/int-wf17-explicit-container
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 40s
Details
CI / lint (pull_request) Successful in 3m41s
Details
CI / quality (pull_request) Successful in 4m14s
Details
CI / typecheck (pull_request) Successful in 4m27s
Details
CI / security (pull_request) Successful in 4m36s
Details
CI / unit_tests (pull_request) Successful in 7m41s
Details
CI / integration_tests (pull_request) Successful in 7m49s
Details
CI / docker (pull_request) Successful in 1m9s
Details
CI / e2e_tests (pull_request) Successful in 9m5s
Details
CI / coverage (pull_request) Successful in 11m13s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 37m41s
Details
5c69190d5e 
# Conflicts:
#	CHANGELOG.md
brent.edwards dismissed freemo's review 2026-03-21 04:26:56 +00:00
Reason:

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

Merge remote-tracking branch 'origin/master' into test/int-wf17-explicit-container
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 43s
Details
CI / lint (pull_request) Successful in 4m7s
Details
CI / quality (pull_request) Successful in 4m58s
Details
CI / security (pull_request) Successful in 5m5s
Details
CI / typecheck (pull_request) Successful in 5m22s
Details
CI / integration_tests (pull_request) Successful in 7m54s
Details
CI / e2e_tests (pull_request) Successful in 9m18s
Details
CI / unit_tests (pull_request) Successful in 10m10s
Details
CI / docker (pull_request) Successful in 1m7s
Details
CI / coverage (pull_request) Successful in 11m1s
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / benchmark-regression (pull_request) Failing after 18m5s
Details
c7f0549e28 
# Conflicts:
#	CHANGELOG.md
Merge remote-tracking branch 'origin/master' into test/int-wf17-explicit-container
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 21s
Details
CI / lint (pull_request) Successful in 5m14s
Details
CI / quality (pull_request) Successful in 5m40s
Details
CI / typecheck (pull_request) Successful in 5m57s
Details
CI / security (pull_request) Successful in 6m37s
Details
CI / unit_tests (pull_request) Successful in 6m51s
Details
CI / e2e_tests (pull_request) Successful in 11m3s
Details
CI / integration_tests (pull_request) Successful in 11m9s
Details
CI / coverage (pull_request) Successful in 10m59s
Details
CI / docker (pull_request) Failing after 14m12s
Details
CI / benchmark-regression (pull_request) Failing after 1h5m14s
Details
CI / status-check (pull_request) Has been cancelled
Details
e5f75eee17 
# Conflicts:
#	CHANGELOG.md
Merge remote-tracking branch 'origin/master' into test/int-wf17-explicit-container
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 34s
Details
CI / lint (pull_request) Successful in 5m27s
Details
CI / quality (pull_request) Successful in 6m1s
Details
CI / typecheck (pull_request) Successful in 6m18s
Details
CI / security (pull_request) Successful in 6m27s
Details
CI / unit_tests (pull_request) Successful in 9m45s
Details
CI / integration_tests (pull_request) Successful in 9m55s
Details
CI / e2e_tests (pull_request) Successful in 12m26s
Details
CI / docker (pull_request) Successful in 1m3s
Details
CI / coverage (pull_request) Successful in 10m16s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 1h5m30s
Details
d26b3de553 
# Conflicts:
#	CHANGELOG.md
Merge remote-tracking branch 'origin/master' into test/int-wf17-explicit-container
All checks were successful
CI / build (pull_request) Successful in 14s
Details
CI / lint (pull_request) Successful in 3m24s
Details
CI / quality (pull_request) Successful in 4m55s
Details
CI / security (pull_request) Successful in 5m40s
Details
CI / typecheck (pull_request) Successful in 6m18s
Details
CI / integration_tests (pull_request) Successful in 7m22s
Details
CI / unit_tests (pull_request) Successful in 10m30s
Details
CI / docker (pull_request) Successful in 10s
Details
CI / e2e_tests (pull_request) Successful in 12m37s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / coverage (pull_request) Successful in 11m50s
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / benchmark-regression (pull_request) Successful in 1h14m3s
Details
c807d2728d 
# Conflicts:
#	CHANGELOG.md
brent.edwards force-pushed test/int-wf17-explicit-container from c807d2728d
All checks were successful
CI / build (pull_request) Successful in 14s
Details
CI / lint (pull_request) Successful in 3m24s
Details
CI / quality (pull_request) Successful in 4m55s
Details
CI / security (pull_request) Successful in 5m40s
Details
CI / typecheck (pull_request) Successful in 6m18s
Details
CI / integration_tests (pull_request) Successful in 7m22s
Details
CI / unit_tests (pull_request) Successful in 10m30s
Details
CI / docker (pull_request) Successful in 10s
Details
CI / e2e_tests (pull_request) Successful in 12m37s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / coverage (pull_request) Successful in 11m50s
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / benchmark-regression (pull_request) Successful in 1h14m3s
Details
to bdc36ad2b9
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 44s
Details
CI / quality (pull_request) Successful in 3m47s
Details
CI / lint (pull_request) Successful in 7m19s
Details
CI / security (pull_request) Successful in 7m21s
Details
CI / typecheck (pull_request) Successful in 8m33s
Details
CI / integration_tests (pull_request) Successful in 12m48s
Details
CI / unit_tests (pull_request) Successful in 13m13s
Details
CI / docker (pull_request) Successful in 1m8s
Details
CI / e2e_tests (pull_request) Successful in 17m6s
Details
CI / coverage (pull_request) Successful in 11m36s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 49m13s
Details
2026-03-26 20:03:13 +00:00 Compare
freemo self-assigned this 2026-04-02 06:15:21 +00:00
freemo requested changes 2026-04-02 07:18:05 +00:00
freemo left a comment
Copy link

Code Review — PR #954 (WF17 Explicit Container Integration Test)

Reviewer: freemo (independent review)
Scope: Full diff review (3 files, 576 insertions) against specification, CONTRIBUTING.md, and codebase conventions.

🔴 BLOCKING: Merge Conflicts & Branch Hygiene

1. Merge conflicts (mergeable: false)
The PR cannot be merged in its current state. The CHANGELOG.md has conflicts with the current master — the PR inserts the WF17 entry at the top of ## Unreleased, but master has diverged significantly with new entries in that same section. The branch must be rebased onto the latest master to resolve this.

2. Merge commit in branch history
The branch HEAD (bdc36ad2) is a merge commit: Merge remote-tracking branch 'origin/master' into test/int-wf17-explicit-container. Per CONTRIBUTING.md: "No merge commits — always rebase branches onto the target branch; do not use merge commits." The branch must be squash-rebased onto master to produce a clean linear history.

Action required: Rebase the branch onto current master, resolve the CHANGELOG.md conflict, and force-push. The two real commits should be squashed into a single commit with the conventional changelog message from the issue metadata.

✅ Code Quality Assessment (Non-Blocking — Code Is Good)

Despite the merge blocker, the implementation quality is strong:

Robot Framework test (wf17_explicit_container.robot — 74 lines):

  • ✅ Follows established patterns (matches wf03_plan_prompt_confidence.robot structure)
  • ✅ Force Tags wf17 integration explicit-container — present and appropriate
  • ✅ Suite Setup Setup Test Environment With Database Isolation — correct for helper-based suites
  • ✅ All 5 test cases have [Documentation], [Timeout] 120s, timeout=120s, on_timeout=kill
  • ✅ Sentinel-based pass/fail checking (Should Contain ${result.stdout} wf17-*-ok)

Python helper (helper_wf17_explicit_container.py — 493 lines):

  • ✅ Under 500-line limit (493 lines)
  • ✅ All imports at module level (no lazy imports inside functions)
  • ✅ No # type: ignore suppressions
  • ✅ Full type annotations on all functions, including NoReturn on _fail()
  • ✅ _COMMANDS dict properly typed as dict[str, Callable[[], None]]
  • ✅ _MockRunner is well-designed — records calls, configurable results, proper __call__ signature
  • ✅ Proper cleanup in finally blocks (workspace, repo, yaml, lifecycle registry)
  • ✅ Imports from cleveragents modules are all valid (verified against source)

Test coverage of acceptance criteria:

Acceptance Criterion Test Command Status
Container-instance with dual mounts wf17-container-instance-creation ✅ Covered
Project execution environment override wf17-project-execution-env ✅ Covered
Plan with trusted profile wf17-plan-with-container ✅ Covered
Tools route to container wf17-execute-routed-to-container ✅ Covered
Apply synced from container wf17-apply-from-container ✅ Covered

Spec alignment:

  • ExecutionEnvironmentResolver usage matches the 6-level precedence chain from the spec
  • CONTAINER_RESOURCE_TYPES validation is correct
  • Container lifecycle (activate → running → stop → stopped) is properly exercised
  • Session ID propagation is verified
  • The mock approach (mocked container runtime, mocked LLM) is appropriate for integration tests that can't spin up real Docker containers — this matches the issue's explicit acceptance criterion

CHANGELOG entry:

  • ✅ Properly placed under ## Unreleased
  • ✅ References issue (#781)
  • ✅ Descriptive and accurate

📝 Minor Observation (Non-Blocking)

The PR body mentions "Also fixes pre-existing test failures discovered during full nox suite verification" but the current diff only contains the 3 new files. Those fixes were likely in earlier iterations that have since merged to master. Consider updating the PR body to reflect the current state of the diff after rebasing.

Verdict

REQUEST_CHANGES — The code and tests are well-implemented and meet all acceptance criteria. The only blocker is the merge conflict and merge commit in branch history. Once rebased onto current master with a clean linear history, this PR should be ready to merge.

## Code Review — PR #954 (WF17 Explicit Container Integration Test) **Reviewer:** freemo (independent review) **Scope:** Full diff review (3 files, 576 insertions) against specification, CONTRIBUTING.md, and codebase conventions. --- ### 🔴 BLOCKING: Merge Conflicts & Branch Hygiene **1. Merge conflicts (`mergeable: false`)** The PR cannot be merged in its current state. The `CHANGELOG.md` has conflicts with the current `master` — the PR inserts the WF17 entry at the top of `## Unreleased`, but master has diverged significantly with new entries in that same section. The branch must be rebased onto the latest `master` to resolve this. **2. Merge commit in branch history** The branch HEAD (`bdc36ad2`) is a merge commit: `Merge remote-tracking branch 'origin/master' into test/int-wf17-explicit-container`. Per CONTRIBUTING.md: *"No merge commits — always rebase branches onto the target branch; do not use merge commits."* The branch must be squash-rebased onto `master` to produce a clean linear history. **Action required:** Rebase the branch onto current `master`, resolve the CHANGELOG.md conflict, and force-push. The two real commits should be squashed into a single commit with the conventional changelog message from the issue metadata. --- ### ✅ Code Quality Assessment (Non-Blocking — Code Is Good) Despite the merge blocker, the implementation quality is strong: **Robot Framework test (`wf17_explicit_container.robot` — 74 lines):** - ✅ Follows established patterns (matches `wf03_plan_prompt_confidence.robot` structure) - ✅ `Force Tags wf17 integration explicit-container` — present and appropriate - ✅ `Suite Setup Setup Test Environment With Database Isolation` — correct for helper-based suites - ✅ All 5 test cases have `[Documentation]`, `[Timeout] 120s`, `timeout=120s`, `on_timeout=kill` - ✅ Sentinel-based pass/fail checking (`Should Contain ${result.stdout} wf17-*-ok`) **Python helper (`helper_wf17_explicit_container.py` — 493 lines):** - ✅ Under 500-line limit (493 lines) - ✅ All imports at module level (no lazy imports inside functions) - ✅ No `# type: ignore` suppressions - ✅ Full type annotations on all functions, including `NoReturn` on `_fail()` - ✅ `_COMMANDS` dict properly typed as `dict[str, Callable[[], None]]` - ✅ `_MockRunner` is well-designed — records calls, configurable results, proper `__call__` signature - ✅ Proper cleanup in `finally` blocks (workspace, repo, yaml, lifecycle registry) - ✅ Imports from `cleveragents` modules are all valid (verified against source) **Test coverage of acceptance criteria:** | Acceptance Criterion | Test Command | Status | |---|---|---| | Container-instance with dual mounts | `wf17-container-instance-creation` | ✅ Covered | | Project execution environment override | `wf17-project-execution-env` | ✅ Covered | | Plan with trusted profile | `wf17-plan-with-container` | ✅ Covered | | Tools route to container | `wf17-execute-routed-to-container` | ✅ Covered | | Apply synced from container | `wf17-apply-from-container` | ✅ Covered | **Spec alignment:** - `ExecutionEnvironmentResolver` usage matches the 6-level precedence chain from the spec - `CONTAINER_RESOURCE_TYPES` validation is correct - Container lifecycle (activate → running → stop → stopped) is properly exercised - Session ID propagation is verified - The mock approach (mocked container runtime, mocked LLM) is appropriate for integration tests that can't spin up real Docker containers — this matches the issue's explicit acceptance criterion **CHANGELOG entry:** - ✅ Properly placed under `## Unreleased` - ✅ References issue `(#781)` - ✅ Descriptive and accurate --- ### 📝 Minor Observation (Non-Blocking) The PR body mentions *"Also fixes pre-existing test failures discovered during full nox suite verification"* but the current diff only contains the 3 new files. Those fixes were likely in earlier iterations that have since merged to master. Consider updating the PR body to reflect the current state of the diff after rebasing. --- ### Verdict **REQUEST_CHANGES** — The code and tests are well-implemented and meet all acceptance criteria. The only blocker is the merge conflict and merge commit in branch history. Once rebased onto current `master` with a clean linear history, this PR should be ready to merge.
CHANGELOG.md
@ -2,6 +2,15 @@
## Unreleased
- Added Robot Framework integration test and Python helper for Specification
freemo commented 2026-04-02 07:18:05 +00:00
Owner
Copy link

Merge conflict: This file conflicts with the current master branch. After rebasing, ensure the WF17 entry is placed correctly within the ## Unreleased section (typically at the top, maintaining chronological order with other entries).

**Merge conflict**: This file conflicts with the current `master` branch. After rebasing, ensure the WF17 entry is placed correctly within the `## Unreleased` section (typically at the top, maintaining chronological order with other entries).
freemo commented 2026-04-02 16:22:04 +00:00
Owner
Copy link

🤖 Backlog Groomer (groomer-1) — Duplicate Detected

This PR (#954) is a duplicate of the canonical tracking issue #781 ("test(integration): workflow example 17 — explicit container with directory mount (trusted profile)").

Rationale:

  • #781 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 (#954) was opened later and its body explicitly states Closes #781, 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 #781.

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

🤖 **Backlog Groomer (groomer-1) — Duplicate Detected** This PR (#954) is a duplicate of the canonical tracking issue **#781** ("test(integration): workflow example 17 — explicit container with directory mount (trusted profile)"). **Rationale:** - #781 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 (#954) was opened later and its body explicitly states `Closes #781`, 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 #781. **Action:** Closing this issue as a duplicate of #781. All tracking, review, and merge activity should be associated with #781.
freemo closed this pull request 2026-04-02 16:22:17 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 44s
Required
Details
CI / quality (pull_request) Successful in 3m47s
Required
Details
CI / lint (pull_request) Successful in 7m19s
Required
Details
CI / security (pull_request) Successful in 7m21s
Required
Details
CI / typecheck (pull_request) Successful in 8m33s
Required
Details
CI / integration_tests (pull_request) Successful in 12m48s
Required
Details
CI / unit_tests (pull_request) Successful in 13m13s
Required
Details
CI / docker (pull_request) Successful in 1m8s
Required
Details
CI / e2e_tests (pull_request) Successful in 17m6s
Details
CI / coverage (pull_request) Successful in 11m36s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 49m13s
Details

Pull request closed

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

  
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.7.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!954
No description provided.