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 9 — session-driven interactive exploration (review profile) #790

Closed
freemo wants to merge 1 commit from test/e2e-wf09-session into master
pull from: test/e2e-wf09-session
merge into: cleveragents:master
Conversation 6 Commits 1 Files changed 3 +378
freemo commented 2026-03-12 23:05:19 +00:00
Owner
Copy link

Summary

E2E test for Specification Workflow Example 9: Session-Driven Interactive Exploration. Exercises the full session lifecycle with the real CleverAgents CLI.

Note: session tell is currently stubbed at the CLI layer (M3 milestone) — the assistant echoes an acknowledgement rather than invoking a real LLM. AC #5 (action creation) therefore always takes the WARN path. Assertions validate the echo response pattern until real LLM integration lands.

Closes #755

Changes

  • robot/e2e/wf09_session.robot — New E2E test that:

    • Creates a temp git repo with a multi-module Python project fixture (auth, routes, models)
    • Registers the repo as a resource and creates a project (with UUID suffix for parallel CI safety)
    • Creates a session with a dynamically selected LLM actor
    • Sends three session tell queries per spec Example 9: codebase overview, auth module deep-dive, and action creation request (the defining differentiator of WF09)
    • Content relevance check — validates the echo response pattern ("Acknowledged") on every session tell call
    • Verifies action creation (AC #5) — soft-checks via action show that the LLM actually created the requested action (logs WARN if LLM didn't create it, since behavior is non-deterministic and session tell is currently stubbed)
    • Verifies accumulated session history (AC #4) — parses session show --format json, asserts message_count >= 6 (3 user + 3 assistant turns) and recent_messages >= 3
    • Exports conversation to JSON via session export with hard assertions on file existence, content validity, JSON structure (session_id, messages keys), session_id value match, individual message structure (role field), and non-empty messages list
    • Uses spec canonical argument order for session export (flag before positional)
    • Traceback/INTERNAL checks on all CLI invocations
    • Test-level timeout ([Timeout] 20 minutes) for CI reliability
    • Diagnostic teardown (WF09 Test Teardown) that logs session state on failure
    • Stale export cleanup — removes previous export file before new export to prevent false passes
    • Uses Skip If No LLM Keys for graceful degradation without API keys

  • .gitignore — Added ca-cow-backup-*/ pattern to prevent copy-on-write sandbox backup artifacts from being committed

  • CHANGELOG.md — Fixed tagging description to accurately reflect Force Tags E2E mechanism

Design Decisions

  • Keyword extraction: Reusable keywords (Create Sample Project Fixture, Create Session With Actor, Verify Session Tell Response, Verify Session History, Verify Session Export) reduce the test case to ~60 lines and improve maintainability
  • Safe Parse Json Field / Extract JSON From Stdout: Uses shared keywords from common_e2e.resource for robust JSON parsing with raw_decode() to handle non-JSON preamble
  • Hard assertions with soft AC #5: All validations use assertive keywords that fail the test on unexpected output. The exception is action creation verification (AC #5), which uses a soft WARN because LLM tool-calling behavior is non-deterministic and session tell is currently stubbed
  • Stubbed session tell documentation: Suite-level and keyword-level documentation explicitly notes that session tell is stubbed (M3) and assertions validate the echo pattern. Comments explain when to update tests for real LLM integration
  • UUID suffix: All resource/project names include a UUID suffix to prevent UNIQUE constraint violations in parallel CI runs
  • Actor selection: Dynamically selects actor based on available API keys (Anthropic preferred for richer conversational output; OpenAI fallback). Comment explains that only Anthropic is checked explicitly — falls through to OpenAI unconditionally since session tell is stubbed and actor choice only affects echo prefix
  • Timeout for action-creation session tell: Uses 300s (vs. default 120s) as forward-compatible for when real LLM integration lands; while session tell remains stubbed the command returns instantly
  • No --project on session create: The CLI's session create does not accept a --project parameter. The project fixture is registered separately so the LLM can discover it via resource/project queries during the conversation.

Quality Gates

Gate Result
nox -e lint Pass
nox -e typecheck Pass
nox -e unit_tests Pass (12831 scenarios, 0 failed)
nox -e integration_tests Pass
nox -e e2e_tests Pass (63 tests, 62 passed, 1 skipped)
nox -e coverage_report Pass (97%)
## Summary E2E test for Specification Workflow Example 9: Session-Driven Interactive Exploration. Exercises the full session lifecycle with the real CleverAgents CLI. **Note:** `session tell` is currently stubbed at the CLI layer (M3 milestone) — the assistant echoes an acknowledgement rather than invoking a real LLM. AC #5 (action creation) therefore always takes the WARN path. Assertions validate the echo response pattern until real LLM integration lands. Closes #755 ## Changes - **`robot/e2e/wf09_session.robot`** — New E2E test that: - Creates a temp git repo with a multi-module Python project fixture (auth, routes, models) - Registers the repo as a resource and creates a project (with UUID suffix for parallel CI safety) - Creates a session with a dynamically selected LLM actor - Sends three `session tell` queries per spec Example 9: codebase overview, auth module deep-dive, and **action creation request** (the defining differentiator of WF09) - **Content relevance check** — validates the echo response pattern ("Acknowledged") on every `session tell` call - **Verifies action creation (AC #5)** — soft-checks via `action show` that the LLM actually created the requested action (logs WARN if LLM didn't create it, since behavior is non-deterministic and session tell is currently stubbed) - **Verifies accumulated session history (AC #4)** — parses `session show --format json`, asserts `message_count >= 6` (3 user + 3 assistant turns) and `recent_messages >= 3` - Exports conversation to JSON via `session export` with **hard assertions** on file existence, content validity, JSON structure (`session_id`, `messages` keys), **session_id value match**, **individual message structure** (role field), and non-empty messages list - Uses spec canonical argument order for `session export` (flag before positional) - **Traceback/INTERNAL checks** on all CLI invocations - **Test-level timeout** (`[Timeout] 20 minutes`) for CI reliability - **Diagnostic teardown** (`WF09 Test Teardown`) that logs session state on failure - **Stale export cleanup** — removes previous export file before new export to prevent false passes - Uses `Skip If No LLM Keys` for graceful degradation without API keys - **`.gitignore`** — Added `ca-cow-backup-*/` pattern to prevent copy-on-write sandbox backup artifacts from being committed - **`CHANGELOG.md`** — Fixed tagging description to accurately reflect `Force Tags E2E` mechanism ## Design Decisions - **Keyword extraction**: Reusable keywords (`Create Sample Project Fixture`, `Create Session With Actor`, `Verify Session Tell Response`, `Verify Session History`, `Verify Session Export`) reduce the test case to ~60 lines and improve maintainability - **`Safe Parse Json Field` / `Extract JSON From Stdout`**: Uses shared keywords from `common_e2e.resource` for robust JSON parsing with `raw_decode()` to handle non-JSON preamble - **Hard assertions with soft AC #5**: All validations use assertive keywords that fail the test on unexpected output. The exception is action creation verification (AC #5), which uses a soft WARN because LLM tool-calling behavior is non-deterministic and session tell is currently stubbed - **Stubbed session tell documentation**: Suite-level and keyword-level documentation explicitly notes that `session tell` is stubbed (M3) and assertions validate the echo pattern. Comments explain when to update tests for real LLM integration - **UUID suffix**: All resource/project names include a UUID suffix to prevent UNIQUE constraint violations in parallel CI runs - **Actor selection**: Dynamically selects actor based on available API keys (Anthropic preferred for richer conversational output; OpenAI fallback). Comment explains that only Anthropic is checked explicitly — falls through to OpenAI unconditionally since session tell is stubbed and actor choice only affects echo prefix - **Timeout for action-creation `session tell`**: Uses 300s (vs. default 120s) as forward-compatible for when real LLM integration lands; while session tell remains stubbed the command returns instantly - **No `--project` on session create**: The CLI's `session create` does not accept a `--project` parameter. The project fixture is registered separately so the LLM can discover it via resource/project queries during the conversation. ## Quality Gates | Gate | Result | |------|--------| | `nox -e lint` | Pass | | `nox -e typecheck` | Pass | | `nox -e unit_tests` | Pass (12831 scenarios, 0 failed) | | `nox -e integration_tests` | Pass | | `nox -e e2e_tests` | Pass (63 tests, 62 passed, 1 skipped) | | `nox -e coverage_report` | Pass (97%) |
test(e2e): workflow example 9 — session-driven interactive exploration (review profile)
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 15s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 18s
Details
CI / e2e_tests (pull_request) Failing after 27s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 1m7s
Details
CI / coverage (pull_request) Successful in 5m31s
Details
CI / unit_tests (pull_request) Successful in 6m45s
Details
CI / integration_tests (pull_request) Successful in 7m2s
Details
CI / docker (pull_request) Successful in 22s
Details
CI / benchmark-regression (pull_request) Successful in 37m6s
Details
24e88366e7 
Add robot/e2e/wf09_session.robot — E2E test for Workflow Example 9
(Session-Driven Interactive Exploration).

The test exercises the full session lifecycle with zero mocking:
- Creates a temp git repo with a sample multi-module Python project
  (src/auth.py, src/routes.py, src/models.py, README.md)
- Registers the repo as a resource and creates a project
- Creates a session via 'session create --actor anthropic/claude-3.5-sonnet'
- Sends multiple conversational queries via 'session tell'
- Verifies accumulated session history via 'session show'
- Exports the conversation to JSON via 'session export'
- Validates the exported JSON structure (schema_version, messages array,
  session_id, message count >= 4)

Tagged [Tags] E2E, uses common_e2e.resource keywords, and skips
gracefully when LLM API keys are absent.

ISSUES CLOSED: #755
freemo added this to the v3.0.0 milestone 2026-03-12 23:05:24 +00:00
freemo force-pushed test/e2e-wf09-session from 24e88366e7
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 15s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 18s
Details
CI / e2e_tests (pull_request) Failing after 27s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 1m7s
Details
CI / coverage (pull_request) Successful in 5m31s
Details
CI / unit_tests (pull_request) Successful in 6m45s
Details
CI / integration_tests (pull_request) Successful in 7m2s
Details
CI / docker (pull_request) Successful in 22s
Details
CI / benchmark-regression (pull_request) Successful in 37m6s
Details
to 038da9f572
Some checks failed
CI / lint (pull_request) Successful in 13s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 25s
Details
CI / build (pull_request) Successful in 13s
Details
CI / security (pull_request) Successful in 35s
Details
CI / typecheck (pull_request) Successful in 36s
Details
CI / e2e_tests (pull_request) Successful in 36s
Details
CI / unit_tests (pull_request) Successful in 2m37s
Details
CI / integration_tests (pull_request) Successful in 3m12s
Details
CI / docker (pull_request) Successful in 55s
Details
CI / coverage (pull_request) Successful in 5m3s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-13 16:15:06 +00:00 Compare
freemo force-pushed test/e2e-wf09-session from 038da9f572
Some checks failed
CI / lint (pull_request) Successful in 13s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 25s
Details
CI / build (pull_request) Successful in 13s
Details
CI / security (pull_request) Successful in 35s
Details
CI / typecheck (pull_request) Successful in 36s
Details
CI / e2e_tests (pull_request) Successful in 36s
Details
CI / unit_tests (pull_request) Successful in 2m37s
Details
CI / integration_tests (pull_request) Successful in 3m12s
Details
CI / docker (pull_request) Successful in 55s
Details
CI / coverage (pull_request) Successful in 5m3s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to 77682e2c43
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 17s
Details
CI / build (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 35s
Details
CI / security (pull_request) Successful in 37s
Details
CI / e2e_tests (pull_request) Successful in 38s
Details
CI / unit_tests (pull_request) Successful in 3m43s
Details
CI / integration_tests (pull_request) Successful in 3m48s
Details
CI / docker (pull_request) Successful in 1m18s
Details
CI / coverage (pull_request) Successful in 5m25s
Details
CI / benchmark-regression (pull_request) Successful in 33m31s
Details
2026-03-13 16:23:59 +00:00 Compare
freemo force-pushed test/e2e-wf09-session from 77682e2c43
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 17s
Details
CI / build (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 35s
Details
CI / security (pull_request) Successful in 37s
Details
CI / e2e_tests (pull_request) Successful in 38s
Details
CI / unit_tests (pull_request) Successful in 3m43s
Details
CI / integration_tests (pull_request) Successful in 3m48s
Details
CI / docker (pull_request) Successful in 1m18s
Details
CI / coverage (pull_request) Successful in 5m25s
Details
CI / benchmark-regression (pull_request) Successful in 33m31s
Details
to 8d8003da4f
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 21s
Details
CI / build (pull_request) Successful in 17s
Details
CI / e2e_tests (pull_request) Failing after 25s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 36s
Details
CI / quality (pull_request) Successful in 1m7s
Details
CI / unit_tests (pull_request) Successful in 3m9s
Details
CI / integration_tests (pull_request) Successful in 3m52s
Details
CI / docker (pull_request) Successful in 11s
Details
CI / coverage (pull_request) Successful in 5m18s
Details
CI / benchmark-regression (pull_request) Successful in 35m17s
Details
2026-03-13 23:19:40 +00:00 Compare
freemo commented 2026-03-14 04:44:25 +00:00
Author
Owner
Copy link

PM Review — Day 34

Status: Mergeable, 0 reviews, M1 (v3.0.0)
Author: @freemo

E2E test for WF09 (session-driven interactive exploration, review profile). Retroactive M1 coverage.

Action Items

Who Action Deadline
@hurui200320 Peer review Day 37
## PM Review — Day 34 **Status**: Mergeable, 0 reviews, M1 (v3.0.0) **Author**: @freemo E2E test for WF09 (session-driven interactive exploration, review profile). Retroactive M1 coverage. ### Action Items | Who | Action | Deadline | |-----|--------|----------| | @hurui200320 | **Peer review** | Day 37 |
freemo modified the milestone from v3.0.0 to v3.6.0 2026-03-16 00:32:10 +00:00
freemo commented 2026-03-16 09:34:32 +00:00
Author
Owner
Copy link

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

Day 34 review assignment deadline check. This PR has 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 reviewed 2026-03-16 16:26:25 +00:00
freemo left a comment
Copy link

PM Day 36: M7 E2E test. Merge conflict. @freemo rebase needed.

PM Day 36: M7 E2E test. Merge conflict. @freemo rebase needed.
freemo commented 2026-03-16 22:23:38 +00:00
Author
Owner
Copy link

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

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

PM Status — Day 37 — Rebase Required

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

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

PM rebase request — Day 37

## PM Status — Day 37 — Rebase Required This PR has **merge conflicts** and cannot be merged in its current state. 42% of all open PRs (21 of 50) have conflicts — this is a project-wide issue that must be resolved. @freemo — Please rebase this PR onto `master` by **Day 39 EOD (2026-03-19)**. If you cannot rebase by then, please post a comment explaining the blocker. --- *PM rebase request — Day 37*
hurui200320 force-pushed test/e2e-wf09-session from 8d8003da4f
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 21s
Details
CI / build (pull_request) Successful in 17s
Details
CI / e2e_tests (pull_request) Failing after 25s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 36s
Details
CI / quality (pull_request) Successful in 1m7s
Details
CI / unit_tests (pull_request) Successful in 3m9s
Details
CI / integration_tests (pull_request) Successful in 3m52s
Details
CI / docker (pull_request) Successful in 11s
Details
CI / coverage (pull_request) Successful in 5m18s
Details
CI / benchmark-regression (pull_request) Successful in 35m17s
Details
to 98310576d3
Some checks failed
CI / lint (pull_request) Successful in 28s
Details
CI / typecheck (pull_request) Successful in 45s
Details
CI / quality (pull_request) Successful in 58s
Details
CI / security (pull_request) Successful in 1m19s
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 2m59s
Details
CI / integration_tests (pull_request) Successful in 4m7s
Details
CI / e2e_tests (pull_request) Failing after 5m10s
Details
CI / docker (pull_request) Successful in 56s
Details
CI / coverage (pull_request) Successful in 6m56s
Details
CI / benchmark-regression (pull_request) Successful in 38m20s
Details
2026-03-18 08:46:38 +00:00 Compare
hurui200320 force-pushed test/e2e-wf09-session from 98310576d3
Some checks failed
CI / lint (pull_request) Successful in 28s
Details
CI / typecheck (pull_request) Successful in 45s
Details
CI / quality (pull_request) Successful in 58s
Details
CI / security (pull_request) Successful in 1m19s
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 2m59s
Details
CI / integration_tests (pull_request) Successful in 4m7s
Details
CI / e2e_tests (pull_request) Failing after 5m10s
Details
CI / docker (pull_request) Successful in 56s
Details
CI / coverage (pull_request) Successful in 6m56s
Details
CI / benchmark-regression (pull_request) Successful in 38m20s
Details
to b4c940bffc
All checks were successful
CI / lint (pull_request) Successful in 25s
Details
CI / typecheck (pull_request) Successful in 50s
Details
CI / quality (pull_request) Successful in 58s
Details
CI / security (pull_request) Successful in 1m4s
Details
CI / build (pull_request) Successful in 24s
Details
CI / helm (pull_request) Successful in 33s
Details
CI / integration_tests (pull_request) Successful in 4m3s
Details
CI / unit_tests (pull_request) Successful in 4m52s
Details
CI / docker (pull_request) Successful in 1m31s
Details
CI / coverage (pull_request) Successful in 11m28s
Details
CI / e2e_tests (pull_request) Successful in 14m56s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 1h0m54s
Details
2026-03-30 08:18:59 +00:00 Compare
hurui200320 force-pushed test/e2e-wf09-session from b4c940bffc
All checks were successful
CI / lint (pull_request) Successful in 25s
Details
CI / typecheck (pull_request) Successful in 50s
Details
CI / quality (pull_request) Successful in 58s
Details
CI / security (pull_request) Successful in 1m4s
Details
CI / build (pull_request) Successful in 24s
Details
CI / helm (pull_request) Successful in 33s
Details
CI / integration_tests (pull_request) Successful in 4m3s
Details
CI / unit_tests (pull_request) Successful in 4m52s
Details
CI / docker (pull_request) Successful in 1m31s
Details
CI / coverage (pull_request) Successful in 11m28s
Details
CI / e2e_tests (pull_request) Successful in 14m56s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 1h0m54s
Details
to 9ae143577f
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 24s
Details
CI / security (pull_request) Successful in 57s
Details
CI / build (pull_request) Successful in 15s
Details
CI / helm (pull_request) Successful in 22s
Details
CI / typecheck (pull_request) Successful in 3m57s
Details
CI / quality (pull_request) Successful in 4m4s
Details
CI / integration_tests (pull_request) Successful in 8m4s
Details
CI / unit_tests (pull_request) Successful in 8m28s
Details
CI / docker (pull_request) Successful in 1m52s
Details
CI / coverage (pull_request) Successful in 12m7s
Details
CI / e2e_tests (pull_request) Successful in 18m18s
Details
CI / status-check (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
2026-03-30 10:28:09 +00:00 Compare
hurui200320 force-pushed test/e2e-wf09-session from 9ae143577f
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 24s
Details
CI / security (pull_request) Successful in 57s
Details
CI / build (pull_request) Successful in 15s
Details
CI / helm (pull_request) Successful in 22s
Details
CI / typecheck (pull_request) Successful in 3m57s
Details
CI / quality (pull_request) Successful in 4m4s
Details
CI / integration_tests (pull_request) Successful in 8m4s
Details
CI / unit_tests (pull_request) Successful in 8m28s
Details
CI / docker (pull_request) Successful in 1m52s
Details
CI / coverage (pull_request) Successful in 12m7s
Details
CI / e2e_tests (pull_request) Successful in 18m18s
Details
CI / status-check (pull_request) Has been cancelled
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
to c2b18f3689
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 23s
Details
CI / lint (pull_request) Successful in 32s
Details
CI / helm (pull_request) Successful in 42s
Details
CI / typecheck (pull_request) Successful in 4m0s
Details
CI / quality (pull_request) Successful in 4m4s
Details
CI / security (pull_request) Successful in 4m11s
Details
CI / integration_tests (pull_request) Successful in 6m8s
Details
CI / unit_tests (pull_request) Successful in 9m41s
Details
CI / docker (pull_request) Successful in 14s
Details
CI / coverage (pull_request) Successful in 11m55s
Details
CI / e2e_tests (pull_request) Successful in 20m42s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 1h4m59s
Details
2026-03-30 11:38:06 +00:00 Compare
freemo self-assigned this 2026-04-02 06:15:25 +00:00
freemo commented 2026-04-02 17:35:19 +00:00
Author
Owner
Copy link

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

Issue #755 (test(e2e): workflow example 9 — session-driven interactive exploration) is the canonical version with full labels (MoSCoW/Must have, Priority/Critical, State/In Review, Type/Testing) and milestone v3.6.0. This issue is an exact title duplicate.

🤖 **Backlog Groomer (groomer-1):** Closing as duplicate of #755. Issue #755 (`test(e2e): workflow example 9 — session-driven interactive exploration`) is the canonical version with full labels (`MoSCoW/Must have`, `Priority/Critical`, `State/In Review`, `Type/Testing`) and milestone `v3.6.0`. This issue is an exact title duplicate.
freemo closed this pull request 2026-04-02 17:35:34 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 23s
Required
Details
CI / lint (pull_request) Successful in 32s
Required
Details
CI / helm (pull_request) Successful in 42s
Details
CI / typecheck (pull_request) Successful in 4m0s
Required
Details
CI / quality (pull_request) Successful in 4m4s
Required
Details
CI / security (pull_request) Successful in 4m11s
Required
Details
CI / integration_tests (pull_request) Successful in 6m8s
Required
Details
CI / unit_tests (pull_request) Successful in 9m41s
Required
Details
CI / docker (pull_request) Successful in 14s
Required
Details
CI / coverage (pull_request) Successful in 11m55s
Required
Details
CI / e2e_tests (pull_request) Successful in 20m42s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 1h4m59s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
CoreRasurae
brent.edwards
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.6.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!790
No description provided.