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

test(e2e): workflow example 6 — documentation generation from codebase analysis (trusted profile) #792

Closed
freemo wants to merge 1 commit from test/e2e-wf06-doc-generation into master
pull from: test/e2e-wf06-doc-generation
merge into: cleveragents:master
Conversation 5 Commits 1 Files changed 5 +438 -16
freemo commented 2026-03-12 23:10:47 +00:00
Owner
Copy link

Summary

Add end-to-end Robot Framework test exercising specification Workflow Example 6: documentation generation from codebase analysis using the trusted automation profile.

Closes #752

What the test covers

The test exercises the full plan lifecycle with zero mocking:

  1. Fixture setup — creates a temp git repo with three Python source modules (auth.py, models.py, utils.py) and dynamically detects the default branch name
  2. Action creation — YAML config with arguments (doc_types, output_dir), long_description, read_only, reusable, state, and three invariants per the spec (including "Architecture diagrams must reflect actual module dependencies")
  3. Resource & project registration — git-checkout resource with dynamic branch, project linked to resource
  4. Context policy configuration — project context set --view strategize (hot-max-tokens 32000, warm-max-decisions 200, exclude-path, summarize, summary-max-tokens 1500) and --view execute (hot-max-tokens 16000, query-limit 30, summarize)
  5. Plan lifecycle — plan use with --automation-profile trusted (with automation profile verification), two plan execute calls (strategize + execute phases), plan diff, and plan apply --yes ${plan_id} — all with --format plain and 180–300s timeouts
  6. Source-code invariant — byte-identical comparison of all three .py files before/after apply, plus Should Not Contain assertions on diff output
  7. Documentation output assertion — conditional check: if a post-apply git commit exists (LLM produced changes), asserts at least one non-README .md file with non-zero content

Robot file hardening

  • Force Tags E2E in Settings section (replacing per-test [Tags])
  • [Timeout] 25 minutes on the test case
  • timeout=60s on_timeout=kill on all Run Process git and find calls
  • Return code assertions on git log and find subprocesses
  • Get Line Count replacing fragile triple-quoted Evaluate for commit counting
  • $variable syntax in Evaluate expressions (consistent with common_e2e.resource conventions)
  • ${repo} initialized to ${EMPTY} before Skip If No LLM Keys to prevent teardown failures on undefined variable
  • Automation profile verification after plan use via Safe Parse Json Field
  • Comment explaining doc_types required: false workaround with TODO for future revert

Bug fix included

Fixed a pre-existing bug in src/cleveragents/cli/commands/project_context.py where context_set, context_show, context_inspect, and context_simulate called container.session_factory() — a provider that does not exist on the DI Container class. Added _get_session_factory() helper that first tries the container's session_factory (primary path — the production Container defines a session_factory Singleton) and falls back to building one from container.database_url() (safety net matching the pattern in skill.py, tool.py, automation_profile.py).

Unit test coverage for _get_session_factory() fallback paths

Added two Behave BDD scenarios in project_context_cli_coverage_boost.feature covering the previously untested fallback code paths:

  • AttributeError path: when container.session_factory attribute is missing, the function falls back to container.database_url() and builds a sessionmaker
  • None return path: when container.session_factory() returns None, the function falls back to the production database_url path

Both scenarios verify the returned factory produces a valid SQLAlchemy session and assert that database_url was called exactly once (confirming the fallback path was exercised). Temp DB file cleanup is wrapped in try/finally to prevent leaks on assertion failure.

Review fixes applied

  1. _get_session_factory() exception narrowing — Replaced bare try/except AttributeError with getattr(container, "session_factory", None) guard. The previous pattern could silently swallow AttributeError raised inside the provider resolution chain; the new pattern only catches attribute absence.
  2. Temp file leak prevention — Moved context.cb_temp_db_path = db_path immediately after tempfile.mkstemp() / os.close(fd) in both step_get_session_factory_no_attr and step_get_session_factory_returns_none, so cleanup can find the path even if subsequent setup raises.
  3. Engine disposal in cleanup — Added engine.dispose() call (via getattr(factory, "kw", None)) in step_assert_session_factory_valid before deleting temp DB files, preventing pooled connection leaks.
  4. Docstring accuracy — Revised _get_session_factory() docstring to correctly describe the session_factory provider as the "primary path" (used in production) and the database_url fallback as the "safety net", rather than the reverse.

Deferred (acknowledged, not addressed in this PR)

  • Engine created in _get_session_factory() fallback path is never disposed — consistent with existing codebase pattern in skill.py, tool.py, automation_profile.py; track as tech debt
  • _get_session_factory() -> Any return type annotation — consistent with adjacent helpers; could be tightened to sessionmaker[Session] in a follow-up
  • --arg passing in plan use E2E test — documented workaround for UNIQUE constraint bug
  • Strategize context policy --query-limit 50 parameter — acceptable simplification for E2E
  • database_url() failure path test coverage — optional hardening, acceptable deferral
  • New Behave scenarios inherit unnecessary Background setup — low-priority structural concern
  • Moving Extract Plan Id keyword to common_e2e.resource — affects other Robot files, separate ticket recommended
## Summary Add end-to-end Robot Framework test exercising specification Workflow Example 6: **documentation generation from codebase analysis** using the **trusted** automation profile. Closes #752 ## What the test covers The test exercises the **full plan lifecycle** with zero mocking: 1. **Fixture setup** — creates a temp git repo with three Python source modules (`auth.py`, `models.py`, `utils.py`) and dynamically detects the default branch name 2. **Action creation** — YAML config with `arguments` (doc_types, output_dir), `long_description`, `read_only`, `reusable`, `state`, and three invariants per the spec (including "Architecture diagrams must reflect actual module dependencies") 3. **Resource & project registration** — git-checkout resource with dynamic branch, project linked to resource 4. **Context policy configuration** — `project context set --view strategize` (hot-max-tokens 32000, warm-max-decisions 200, exclude-path, summarize, summary-max-tokens 1500) and `--view execute` (hot-max-tokens 16000, query-limit 30, summarize) 5. **Plan lifecycle** — `plan use` with `--automation-profile trusted` (with automation profile verification), two `plan execute` calls (strategize + execute phases), `plan diff`, and `plan apply --yes ${plan_id}` — all with `--format plain` and 180–300s timeouts 6. **Source-code invariant** — byte-identical comparison of all three `.py` files before/after apply, plus `Should Not Contain` assertions on diff output 7. **Documentation output assertion** — conditional check: if a post-apply git commit exists (LLM produced changes), asserts at least one non-README `.md` file with non-zero content ### Robot file hardening - `Force Tags E2E` in Settings section (replacing per-test `[Tags]`) - `[Timeout] 25 minutes` on the test case - `timeout=60s on_timeout=kill` on all `Run Process git` and `find` calls - Return code assertions on `git log` and `find` subprocesses - `Get Line Count` replacing fragile triple-quoted `Evaluate` for commit counting - `$variable` syntax in `Evaluate` expressions (consistent with `common_e2e.resource` conventions) - `${repo}` initialized to `${EMPTY}` before `Skip If No LLM Keys` to prevent teardown failures on undefined variable - Automation profile verification after `plan use` via `Safe Parse Json Field` - Comment explaining `doc_types required: false` workaround with TODO for future revert ### Bug fix included Fixed a pre-existing bug in `src/cleveragents/cli/commands/project_context.py` where `context_set`, `context_show`, `context_inspect`, and `context_simulate` called `container.session_factory()` — a provider that does not exist on the DI `Container` class. Added `_get_session_factory()` helper that first tries the container's `session_factory` (primary path — the production `Container` defines a `session_factory` Singleton) and falls back to building one from `container.database_url()` (safety net matching the pattern in `skill.py`, `tool.py`, `automation_profile.py`). ### Unit test coverage for `_get_session_factory()` fallback paths Added two Behave BDD scenarios in `project_context_cli_coverage_boost.feature` covering the previously untested fallback code paths: - **AttributeError path**: when `container.session_factory` attribute is missing, the function falls back to `container.database_url()` and builds a `sessionmaker` - **None return path**: when `container.session_factory()` returns `None`, the function falls back to the production `database_url` path Both scenarios verify the returned factory produces a valid SQLAlchemy session and assert that `database_url` was called exactly once (confirming the fallback path was exercised). Temp DB file cleanup is wrapped in `try/finally` to prevent leaks on assertion failure. ### Review fixes applied 1. **`_get_session_factory()` exception narrowing** — Replaced bare `try/except AttributeError` with `getattr(container, "session_factory", None)` guard. The previous pattern could silently swallow `AttributeError` raised inside the provider resolution chain; the new pattern only catches attribute absence. 2. **Temp file leak prevention** — Moved `context.cb_temp_db_path = db_path` immediately after `tempfile.mkstemp()` / `os.close(fd)` in both `step_get_session_factory_no_attr` and `step_get_session_factory_returns_none`, so cleanup can find the path even if subsequent setup raises. 3. **Engine disposal in cleanup** — Added `engine.dispose()` call (via `getattr(factory, "kw", None)`) in `step_assert_session_factory_valid` before deleting temp DB files, preventing pooled connection leaks. 4. **Docstring accuracy** — Revised `_get_session_factory()` docstring to correctly describe the `session_factory` provider as the "primary path" (used in production) and the `database_url` fallback as the "safety net", rather than the reverse. ### Deferred (acknowledged, not addressed in this PR) - Engine created in `_get_session_factory()` fallback path is never disposed — consistent with existing codebase pattern in `skill.py`, `tool.py`, `automation_profile.py`; track as tech debt - `_get_session_factory() -> Any` return type annotation — consistent with adjacent helpers; could be tightened to `sessionmaker[Session]` in a follow-up - `--arg` passing in `plan use` E2E test — documented workaround for UNIQUE constraint bug - Strategize context policy `--query-limit 50` parameter — acceptable simplification for E2E - `database_url()` failure path test coverage — optional hardening, acceptable deferral - New Behave scenarios inherit unnecessary Background setup — low-priority structural concern - Moving `Extract Plan Id` keyword to `common_e2e.resource` — affects other Robot files, separate ticket recommended
test(e2e): workflow example 6 — documentation generation from codebase analysis (trusted profile)
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 15s
Details
CI / quality (pull_request) Successful in 18s
Details
CI / e2e_tests (pull_request) Failing after 31s
Details
CI / security (pull_request) Successful in 35s
Details
CI / typecheck (pull_request) Successful in 42s
Details
CI / unit_tests (pull_request) Successful in 3m20s
Details
CI / integration_tests (pull_request) Successful in 4m30s
Details
CI / docker (pull_request) Successful in 14s
Details
CI / coverage (pull_request) Successful in 5m40s
Details
CI / benchmark-regression (pull_request) Successful in 37m59s
Details
51e082ac18
freemo added this to the v3.1.0 milestone 2026-03-12 23:10:52 +00:00
freemo force-pushed test/e2e-wf06-doc-generation from 51e082ac18
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 15s
Details
CI / quality (pull_request) Successful in 18s
Details
CI / e2e_tests (pull_request) Failing after 31s
Details
CI / security (pull_request) Successful in 35s
Details
CI / typecheck (pull_request) Successful in 42s
Details
CI / unit_tests (pull_request) Successful in 3m20s
Details
CI / integration_tests (pull_request) Successful in 4m30s
Details
CI / docker (pull_request) Successful in 14s
Details
CI / coverage (pull_request) Successful in 5m40s
Details
CI / benchmark-regression (pull_request) Successful in 37m59s
Details
to 5ac239661b
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 19s
Details
CI / quality (pull_request) Successful in 24s
Details
CI / security (pull_request) Successful in 30s
Details
CI / typecheck (pull_request) Successful in 39s
Details
CI / e2e_tests (pull_request) Successful in 42s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
2026-03-13 16:21:20 +00:00 Compare
freemo force-pushed test/e2e-wf06-doc-generation from 5ac239661b
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 19s
Details
CI / quality (pull_request) Successful in 24s
Details
CI / security (pull_request) Successful in 30s
Details
CI / typecheck (pull_request) Successful in 39s
Details
CI / e2e_tests (pull_request) Successful in 42s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
to fa81f29c9f
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 19s
Details
CI / typecheck (pull_request) Successful in 33s
Details
CI / security (pull_request) Successful in 36s
Details
CI / e2e_tests (pull_request) Successful in 39s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
2026-03-13 16:22:58 +00:00 Compare
freemo force-pushed test/e2e-wf06-doc-generation from fa81f29c9f
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 19s
Details
CI / typecheck (pull_request) Successful in 33s
Details
CI / security (pull_request) Successful in 36s
Details
CI / e2e_tests (pull_request) Successful in 39s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
CI / integration_tests (pull_request) Has been cancelled
Details
CI / unit_tests (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
to a83d541c01
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 27s
Details
CI / lint (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 36s
Details
CI / typecheck (pull_request) Successful in 42s
Details
CI / e2e_tests (pull_request) Successful in 55s
Details
CI / unit_tests (pull_request) Successful in 2m43s
Details
CI / integration_tests (pull_request) Successful in 3m41s
Details
CI / docker (pull_request) Successful in 48s
Details
CI / coverage (pull_request) Successful in 5m24s
Details
CI / benchmark-regression (pull_request) Successful in 33m37s
Details
2026-03-13 16:24:03 +00:00 Compare
freemo force-pushed test/e2e-wf06-doc-generation from a83d541c01
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 27s
Details
CI / lint (pull_request) Successful in 31s
Details
CI / security (pull_request) Successful in 36s
Details
CI / typecheck (pull_request) Successful in 42s
Details
CI / e2e_tests (pull_request) Successful in 55s
Details
CI / unit_tests (pull_request) Successful in 2m43s
Details
CI / integration_tests (pull_request) Successful in 3m41s
Details
CI / docker (pull_request) Successful in 48s
Details
CI / coverage (pull_request) Successful in 5m24s
Details
CI / benchmark-regression (pull_request) Successful in 33m37s
Details
to 1220de6530
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 18s
Details
CI / lint (pull_request) Successful in 20s
Details
CI / build (pull_request) Successful in 13s
Details
CI / security (pull_request) Successful in 31s
Details
CI / typecheck (pull_request) Successful in 40s
Details
CI / e2e_tests (pull_request) Failing after 1m1s
Details
CI / unit_tests (pull_request) Successful in 4m29s
Details
CI / integration_tests (pull_request) Successful in 4m50s
Details
CI / docker (pull_request) Successful in 35s
Details
CI / coverage (pull_request) Successful in 5m28s
Details
CI / benchmark-regression (pull_request) Successful in 35m9s
Details
2026-03-13 23:19:36 +00:00 Compare
freemo commented 2026-03-14 04:44:26 +00:00
Author
Owner
Copy link

PM Review — Day 34

Status: Mergeable, 0 reviews, M2 (v3.1.0)
Author: @freemo

E2E test for WF06 (documentation generation from codebase analysis). Retroactive M2 coverage.

Action Items

Who Action Deadline
@hurui200320 Peer review Day 37
## PM Review — Day 34 **Status**: Mergeable, 0 reviews, M2 (v3.1.0) **Author**: @freemo E2E test for WF06 (documentation generation from codebase analysis). Retroactive M2 coverage. ### Action Items | Who | Action | Deadline | |-----|--------|----------| | @hurui200320 | **Peer review** | Day 37 |
freemo modified the milestone from v3.1.0 to v3.4.0 2026-03-16 00:32:02 +00:00
freemo commented 2026-03-16 09:34:43 +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.
freemo commented 2026-03-16 22:23:19 +00:00
Author
Owner
Copy link

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

@hurui200320 I am going to have you take over this PR, it is mostly completed but is waiting on https://git.cleverthis.com/cleveragents/cleveragents-core/issues/628 and https://git.cleverthis.com/cleveragents/cleveragents-core/issues/966 One is yours and one is Brent's. Please be sure to get this PR and the two blocking PRs I listed in asap, thanks.
freemo commented 2026-03-17 18:33:41 +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-wf06-doc-generation from 1220de6530
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 18s
Details
CI / lint (pull_request) Successful in 20s
Details
CI / build (pull_request) Successful in 13s
Details
CI / security (pull_request) Successful in 31s
Details
CI / typecheck (pull_request) Successful in 40s
Details
CI / e2e_tests (pull_request) Failing after 1m1s
Details
CI / unit_tests (pull_request) Successful in 4m29s
Details
CI / integration_tests (pull_request) Successful in 4m50s
Details
CI / docker (pull_request) Successful in 35s
Details
CI / coverage (pull_request) Successful in 5m28s
Details
CI / benchmark-regression (pull_request) Successful in 35m9s
Details
to d43865715c
All checks were successful
CI / lint (pull_request) Successful in 17s
Details
CI / typecheck (pull_request) Successful in 58s
Details
CI / security (pull_request) Successful in 58s
Details
CI / quality (pull_request) Successful in 32s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 18s
Details
CI / unit_tests (pull_request) Successful in 3m15s
Details
CI / integration_tests (pull_request) Successful in 4m7s
Details
CI / e2e_tests (pull_request) Successful in 5m51s
Details
CI / docker (pull_request) Successful in 11s
Details
CI / coverage (pull_request) Successful in 6m38s
Details
CI / benchmark-regression (pull_request) Successful in 39m2s
Details
2026-03-18 08:45:57 +00:00 Compare
hurui200320 force-pushed test/e2e-wf06-doc-generation from d43865715c
All checks were successful
CI / lint (pull_request) Successful in 17s
Details
CI / typecheck (pull_request) Successful in 58s
Details
CI / security (pull_request) Successful in 58s
Details
CI / quality (pull_request) Successful in 32s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 18s
Details
CI / unit_tests (pull_request) Successful in 3m15s
Details
CI / integration_tests (pull_request) Successful in 4m7s
Details
CI / e2e_tests (pull_request) Successful in 5m51s
Details
CI / docker (pull_request) Successful in 11s
Details
CI / coverage (pull_request) Successful in 6m38s
Details
CI / benchmark-regression (pull_request) Successful in 39m2s
Details
to 9e4cc43346
Some checks failed
CI / build (pull_request) Successful in 19s
Details
CI / typecheck (pull_request) Successful in 3m55s
Details
CI / security (pull_request) Successful in 4m3s
Details
CI / integration_tests (pull_request) Successful in 6m46s
Details
CI / unit_tests (pull_request) Failing after 14m18s
Details
CI / quality (pull_request) Failing after 14m18s
Details
CI / lint (pull_request) Failing after 14m19s
Details
CI / e2e_tests (pull_request) Failing after 19m17s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / coverage (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Waiting to run
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 1s
Details
2026-03-27 10:37:18 +00:00 Compare
hurui200320 force-pushed test/e2e-wf06-doc-generation from 9e4cc43346
Some checks failed
CI / build (pull_request) Successful in 19s
Details
CI / typecheck (pull_request) Successful in 3m55s
Details
CI / security (pull_request) Successful in 4m3s
Details
CI / integration_tests (pull_request) Successful in 6m46s
Details
CI / unit_tests (pull_request) Failing after 14m18s
Details
CI / quality (pull_request) Failing after 14m18s
Details
CI / lint (pull_request) Failing after 14m19s
Details
CI / e2e_tests (pull_request) Failing after 19m17s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / coverage (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Waiting to run
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 1s
Details
to 2988fe82c0
Some checks failed
CI / build (pull_request) Successful in 22s
Details
CI / lint (pull_request) Successful in 3m19s
Details
CI / quality (pull_request) Successful in 3m43s
Details
CI / typecheck (pull_request) Successful in 3m56s
Details
CI / security (pull_request) Successful in 4m4s
Details
CI / integration_tests (pull_request) Successful in 7m16s
Details
CI / unit_tests (pull_request) Successful in 7m57s
Details
CI / e2e_tests (pull_request) Successful in 12m20s
Details
CI / docker (pull_request) Failing after 15m29s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / coverage (pull_request) Successful in 11m31s
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-27 11:33:09 +00:00 Compare
hurui200320 force-pushed test/e2e-wf06-doc-generation from 2988fe82c0
Some checks failed
CI / build (pull_request) Successful in 22s
Details
CI / lint (pull_request) Successful in 3m19s
Details
CI / quality (pull_request) Successful in 3m43s
Details
CI / typecheck (pull_request) Successful in 3m56s
Details
CI / security (pull_request) Successful in 4m4s
Details
CI / integration_tests (pull_request) Successful in 7m16s
Details
CI / unit_tests (pull_request) Successful in 7m57s
Details
CI / e2e_tests (pull_request) Successful in 12m20s
Details
CI / docker (pull_request) Failing after 15m29s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / coverage (pull_request) Successful in 11m31s
Details
CI / status-check (pull_request) Successful in 2s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 89ec86b3b3
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 27s
Details
CI / lint (pull_request) Successful in 3m42s
Details
CI / quality (pull_request) Successful in 4m15s
Details
CI / typecheck (pull_request) Successful in 4m28s
Details
CI / security (pull_request) Successful in 4m38s
Details
CI / integration_tests (pull_request) Successful in 9m21s
Details
CI / unit_tests (pull_request) Successful in 9m33s
Details
CI / docker (pull_request) Successful in 1m7s
Details
CI / e2e_tests (pull_request) Successful in 13m0s
Details
CI / coverage (pull_request) Successful in 11m22s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Failing after 52m33s
Details
2026-03-27 13:07:30 +00:00 Compare
hurui200320 force-pushed test/e2e-wf06-doc-generation from 89ec86b3b3
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 27s
Details
CI / lint (pull_request) Successful in 3m42s
Details
CI / quality (pull_request) Successful in 4m15s
Details
CI / typecheck (pull_request) Successful in 4m28s
Details
CI / security (pull_request) Successful in 4m38s
Details
CI / integration_tests (pull_request) Successful in 9m21s
Details
CI / unit_tests (pull_request) Successful in 9m33s
Details
CI / docker (pull_request) Successful in 1m7s
Details
CI / e2e_tests (pull_request) Successful in 13m0s
Details
CI / coverage (pull_request) Successful in 11m22s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Failing after 52m33s
Details
to 31065e30c8
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 52s
Details
CI / lint (pull_request) Successful in 3m21s
Details
CI / build (pull_request) Successful in 24s
Details
CI / typecheck (pull_request) Successful in 3m57s
Details
CI / security (pull_request) Successful in 4m9s
Details
CI / helm (pull_request) Successful in 38s
Details
CI / integration_tests (pull_request) Successful in 6m5s
Details
CI / unit_tests (pull_request) Successful in 6m18s
Details
CI / docker (pull_request) Successful in 1m19s
Details
CI / coverage (pull_request) Successful in 8m31s
Details
CI / e2e_tests (pull_request) Successful in 13m12s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 55m42s
Details
2026-03-30 07:27:47 +00:00 Compare
freemo self-assigned this 2026-04-02 06:15:25 +00:00
freemo commented 2026-04-02 17:34:50 +00:00
Author
Owner
Copy link

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

Issue #752 (test(e2e): workflow example 6 — documentation generation from codebase) is the canonical version with full labels (MoSCoW/Must have, Priority/Critical, State/In Review, Type/Testing) and milestone v3.4.0. This issue is an exact title duplicate.

🤖 **Backlog Groomer (groomer-1):** Closing as duplicate of #752. Issue #752 (`test(e2e): workflow example 6 — documentation generation from codebase`) is the canonical version with full labels (`MoSCoW/Must have`, `Priority/Critical`, `State/In Review`, `Type/Testing`) and milestone `v3.4.0`. This issue is an exact title duplicate.
freemo closed this pull request 2026-04-02 17:35:02 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 52s
Required
Details
CI / lint (pull_request) Successful in 3m21s
Required
Details
CI / build (pull_request) Successful in 24s
Required
Details
CI / typecheck (pull_request) Successful in 3m57s
Required
Details
CI / security (pull_request) Successful in 4m9s
Required
Details
CI / helm (pull_request) Successful in 38s
Details
CI / integration_tests (pull_request) Successful in 6m5s
Required
Details
CI / unit_tests (pull_request) Successful in 6m18s
Required
Details
CI / docker (pull_request) Successful in 1m19s
Required
Details
CI / coverage (pull_request) Successful in 8m31s
Required
Details
CI / e2e_tests (pull_request) Successful in 13m12s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 55m42s
Details

Pull request closed

Please reopen this pull request to perform a merge.
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.4.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!792
No description provided.