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

[BUG] Add required @a2a, @session, @cli tags to BDD feature files #11024

Open
HAL9000 wants to merge 1 commit from bugfix/pr-9183-bdd-tags into master
pull from: bugfix/pr-9183-bdd-tags
merge into: cleveragents:master
Conversation 5 Commits 1 Files changed 119 +128 -22
HAL9000 commented 2026-05-08 07:16:34 +00:00
Owner
Copy link

Description

Adds mandatory @a2a, @session, and @cli file-level tags to BDD feature files.

## Description Adds mandatory @a2a, @session, and @cli file-level tags to BDD feature files.
fix(bdd): add @a2a, @session, @cli file-level tags to 117 BDD feature files
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Failing after 54s
Details
CI / push-validation (pull_request) Failing after 13m50s
Details
CI / helm (pull_request) Failing after 13m51s
Details
CI / build (pull_request) Failing after 13m53s
Details
CI / e2e_tests (pull_request) Failing after 13m55s
Details
CI / integration_tests (pull_request) Failing after 13m56s
Details
CI / unit_tests (pull_request) Failing after 13m57s
Details
CI / quality (pull_request) Failing after 13m58s
Details
CI / security (pull_request) Failing after 13m58s
Details
CI / typecheck (pull_request) Failing after 13m58s
Details
CI / lint (pull_request) Failing after 13m59s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
CI / status-check (pull_request) Has been cancelled
Details
9dbb32beff 
Add mandatory domain classification tags (a2a, session, cli) to the first
line of all BDD feature files that match their respective naming patterns.
Files containing 'a2a', 'session', or 'cli' in their filename receive the
corresponding file-level tags sorted alphabetically before the Feature:
header tag line. This enables Behave-based test pipelines in CI to filter
and select scenarios by technology domain without scanning scenario content.

Changes:
- 117 feature files tagged (98 with new line + 19 with existing tags merged)
- 22 deletions from reformatting existing tag lines
- CHANGELOG.md updated under [Unreleased] Added section
- CONTRIBUTORS.md updated with contribution entry

ISSUES CLOSED: #9183
HAL9000 changed title from test-pull to [BUG] Add required @a2a, @session, @cli tags to BDD feature files 2026-05-08 07:32:26 +00:00
HAL9000 added this to the v3.2.0 milestone 2026-05-08 10:58:33 +00:00
HAL9000 commented 2026-05-08 22:00:26 +00:00
Author
Owner
Copy link

First Review — PR #11024: [BUG] Add required @a2a, @session, @cli tags to BDD feature files

Overview

Reviewed the diff (1 commit, 119 files: 117 BDD feature files + CHANGELOG.md + CONTRIBUTORS.md). The change adds file-level domain classification tags to all BDD feature files whose filenames contain a2a, session, or cli. The intent is correct and the scope is comprehensive, but there are several blocking issues that must be resolved before this PR can be approved.

CI Status

CI is failing across all jobs (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, build, helm). After investigating, master (57881a07) also shows CI failure with the same pattern. These failures are pre-existing and not introduced by this PR. Not counted as a blocker attributable to this change.

10-Category Review Checklist

1. CORRECTNESS — BLOCKING

Issue: False-positive @cli tags due to substring matching on "client"

The filename-based classification logic matches any filename containing the substring cli, which incorrectly flags files containing client as CLI-domain. Four files received incorrect @cli tags:

  • features/a2a_clients_coverage_boost.feature — covers A2A protocol clients, not CLI
  • features/lsp_client_coverage.feature — covers LspClient library, not CLI
  • features/server_client_stubs.feature — covers server client stubs, not CLI
  • features/tdd_mcp_client_start_race.feature — covers McpClient race condition, not CLI

Running behave features/ --tags=cli will erroneously include MCP, LSP, and A2A client tests in the CLI test suite, corrupting domain-based tag filtering.

Fix required: Remove @cli from these four files. Use word-boundary matching (e.g., _cli, ^cli) instead of plain substring matching.

2. SPECIFICATION ALIGNMENT — PASS

Issue #9124 acceptance criteria requires @a2a, @session, and @cli tags on appropriate feature files. Implementation satisfies this intent. No specification conflicts.

3. TEST QUALITY — N/A

Only Gherkin file metadata (tags) modified. No step definitions, environment.py, or production code changed. Existing test quality unaffected.

4. TYPE SAFETY — PASS

No Python code changes.

5. READABILITY — PASS

Tag placement is consistent: new tags on line 1 before Feature: header. Alphabetical sorting of merged tag lines is correct.

6. PERFORMANCE — PASS

Tag metadata changes have zero runtime impact.

7. SECURITY — PASS

No code changes, no security concerns.

8. CODE STYLE — PASS

Tag lines follow standard Gherkin conventions.

9. DOCUMENTATION — NON-BLOCKING SUGGESTION

CHANGELOG entry is placed under ### Added but this PR is fixing a bug (missing required tags). Per Keep a Changelog conventions, bug fixes belong under ### Fixed. The PR is labelled Type/Bug and linked to a [BUG] issue.

Suggestion: Move the CHANGELOG entry from ### Added to ### Fixed.

10. COMMIT AND PR QUALITY — BLOCKING (Multiple issues)

Issue A: PR body missing Closes #N keyword

The PR description has no Closes #9124 or Fixes #9124 keyword. Per CONTRIBUTING.md, a PR without an issue reference will not be merged. The commit footer has ISSUES CLOSED: #9183 but the PR body itself must contain the closing keyword for Forgejo to auto-close the issue on merge.

Fix required: Add Closes #9124 to the PR description body.

Issue B: Branch name does not follow project convention

Branch is bugfix/pr-9183-bdd-tags. Per CONTRIBUTING.md, bugfix branches must follow bugfix/mN-<descriptive-name>. Milestone is v3.2.0 (m2), so correct name would be bugfix/m2-bdd-tags. Noted as a process violation for future reference.

Issue C: No Forgejo dependency direction set

The PR does not block issue #9124 in Forgejo. Per CONTRIBUTING.md: PR must block the issue (PR → blocks → issue), not the reverse.

Fix required: Set the Forgejo dependency so this PR blocks issue #9124.

Summary

Category Status
Correctness BLOCKING — 4 files have false-positive @cli tags
Specification Alignment PASS
Test Quality N/A
Type Safety PASS
Readability PASS
Performance PASS
Security PASS
Code Style PASS
Documentation SUGGESTION — CHANGELOG section should be Fixed not Added
Commit & PR Quality BLOCKING — Missing Closes #N in PR body; missing Forgejo dependency link

Required Changes Before Approval

  1. Remove @cli from: features/a2a_clients_coverage_boost.feature, features/lsp_client_coverage.feature, features/server_client_stubs.feature, features/tdd_mcp_client_start_race.feature
  2. Add Closes #9124 to the PR description body.
  3. Set Forgejo dependency: this PR blocks issue #9124.

Non-blocking suggestions

  • Move the CHANGELOG entry from ### Added to ### Fixed.
  • Future PRs: use bugfix/m2-<name> branch naming per CONTRIBUTING.md.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

## First Review — PR #11024: [BUG] Add required @a2a, @session, @cli tags to BDD feature files ### Overview Reviewed the diff (1 commit, 119 files: 117 BDD feature files + CHANGELOG.md + CONTRIBUTORS.md). The change adds file-level domain classification tags to all BDD feature files whose filenames contain `a2a`, `session`, or `cli`. The intent is correct and the scope is comprehensive, but there are several blocking issues that must be resolved before this PR can be approved. --- ### CI Status CI is **failing** across all jobs (`lint`, `typecheck`, `security`, `quality`, `unit_tests`, `integration_tests`, `e2e_tests`, `build`, `helm`). After investigating, master (`57881a07`) also shows CI failure with the same pattern. **These failures are pre-existing and not introduced by this PR.** Not counted as a blocker attributable to this change. --- ### 10-Category Review Checklist #### 1. CORRECTNESS — BLOCKING **Issue: False-positive `@cli` tags due to substring matching on "client"** The filename-based classification logic matches any filename containing the substring `cli`, which incorrectly flags files containing `client` as CLI-domain. Four files received incorrect `@cli` tags: - `features/a2a_clients_coverage_boost.feature` — covers A2A protocol clients, not CLI - `features/lsp_client_coverage.feature` — covers LspClient library, not CLI - `features/server_client_stubs.feature` — covers server client stubs, not CLI - `features/tdd_mcp_client_start_race.feature` — covers McpClient race condition, not CLI Running `behave features/ --tags=cli` will erroneously include MCP, LSP, and A2A client tests in the CLI test suite, corrupting domain-based tag filtering. **Fix required:** Remove `@cli` from these four files. Use word-boundary matching (e.g., `_cli`, `^cli`) instead of plain substring matching. #### 2. SPECIFICATION ALIGNMENT — PASS Issue #9124 acceptance criteria requires `@a2a`, `@session`, and `@cli` tags on appropriate feature files. Implementation satisfies this intent. No specification conflicts. #### 3. TEST QUALITY — N/A Only Gherkin file metadata (tags) modified. No step definitions, environment.py, or production code changed. Existing test quality unaffected. #### 4. TYPE SAFETY — PASS No Python code changes. #### 5. READABILITY — PASS Tag placement is consistent: new tags on line 1 before `Feature:` header. Alphabetical sorting of merged tag lines is correct. #### 6. PERFORMANCE — PASS Tag metadata changes have zero runtime impact. #### 7. SECURITY — PASS No code changes, no security concerns. #### 8. CODE STYLE — PASS Tag lines follow standard Gherkin conventions. #### 9. DOCUMENTATION — NON-BLOCKING SUGGESTION CHANGELOG entry is placed under `### Added` but this PR is fixing a bug (missing required tags). Per Keep a Changelog conventions, bug fixes belong under `### Fixed`. The PR is labelled `Type/Bug` and linked to a `[BUG]` issue. *Suggestion:* Move the CHANGELOG entry from `### Added` to `### Fixed`. #### 10. COMMIT AND PR QUALITY — BLOCKING (Multiple issues) **Issue A: PR body missing `Closes #N` keyword** The PR description has no `Closes #9124` or `Fixes #9124` keyword. Per CONTRIBUTING.md, a PR without an issue reference will not be merged. The commit footer has `ISSUES CLOSED: #9183` but the PR body itself must contain the closing keyword for Forgejo to auto-close the issue on merge. *Fix required:* Add `Closes #9124` to the PR description body. **Issue B: Branch name does not follow project convention** Branch is `bugfix/pr-9183-bdd-tags`. Per CONTRIBUTING.md, bugfix branches must follow `bugfix/mN-<descriptive-name>`. Milestone is v3.2.0 (m2), so correct name would be `bugfix/m2-bdd-tags`. Noted as a process violation for future reference. **Issue C: No Forgejo dependency direction set** The PR does not block issue #9124 in Forgejo. Per CONTRIBUTING.md: PR must block the issue (PR → blocks → issue), not the reverse. *Fix required:* Set the Forgejo dependency so this PR blocks issue #9124. --- ### Summary | Category | Status | |---|---| | Correctness | BLOCKING — 4 files have false-positive `@cli` tags | | Specification Alignment | PASS | | Test Quality | N/A | | Type Safety | PASS | | Readability | PASS | | Performance | PASS | | Security | PASS | | Code Style | PASS | | Documentation | SUGGESTION — CHANGELOG section should be `Fixed` not `Added` | | Commit & PR Quality | BLOCKING — Missing `Closes #N` in PR body; missing Forgejo dependency link | ### Required Changes Before Approval 1. Remove `@cli` from: `features/a2a_clients_coverage_boost.feature`, `features/lsp_client_coverage.feature`, `features/server_client_stubs.feature`, `features/tdd_mcp_client_start_race.feature` 2. Add `Closes #9124` to the PR description body. 3. Set Forgejo dependency: this PR blocks issue #9124. ### Non-blocking suggestions - Move the CHANGELOG entry from `### Added` to `### Fixed`. - Future PRs: use `bugfix/m2-<name>` branch naming per CONTRIBUTING.md. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 requested changes 2026-05-09 09:58:09 +00:00
Dismissed
HAL9001 left a comment
Copy link

First Review — PR #11024: [BUG] Add required @a2a, @session, @cli tags to BDD feature files

Overview

This PR adds file-level domain classification tags (@a2a, @session, @cli) to 117 BDD feature files across the features/ directory. The overall approach is correct and the scope is comprehensive — 13 A2A files, 26 session files, and 93 CLI files now carry their respective domain tags, enabling behave --tags=<domain> filtering in CI.

However, there are blocking issues that must be resolved before this PR can be approved.

CI Status

CI is failing across all jobs (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, build, helm, coverage, docker). Investigation confirms that master also shows CI failure with the same pattern. These failures are pre-existing and not introduced by this PR. They are not counted as blockers attributable to this change.

10-Category Review Checklist

1. CORRECTNESS — ❌ BLOCKING

4 files received false-positive @cli tags due to substring matching "cli" inside "client":

File Why it is WRONG
features/a2a_clients_coverage_boost.feature Tests cleveragents.a2a.clients protocol module — not CLI commands
features/lsp_client_coverage.feature Tests LspClient library class — not CLI commands
features/server_client_stubs.feature Tests server client protocol stubs — not CLI commands
features/tdd_mcp_client_start_race.feature Tests McpClient.start() race condition — not CLI commands

The filename-based matching algorithm matched any filename containing the substring "cli" — which incorrectly captured filenames containing "client" (since client starts with cli). Running behave features/ --tags=cli will now erroneously include MCP, LSP, and A2A client library tests in the CLI domain test suite, corrupting domain-based tag filtering.

Fix required: Remove @cli from these four files.

2. SPECIFICATION ALIGNMENT — ✅ PASS

Issue #9124 and #9183 acceptance criteria require @a2a, @session, and @cli tags on appropriate feature files. Implementation satisfies this intent for the correct files. No specification conflicts.

3. TEST QUALITY — N/A

Only Gherkin file metadata (tags) modified. No step definitions, environment.py, or production code changed. Existing test quality is unaffected.

4. TYPE SAFETY — ✅ PASS

No Python code changes.

5. READABILITY — ✅ PASS

Tag placement is consistent: new tags on line 1 before the Feature: header. Alphabetical sorting of merged tag lines is correct and consistent throughout all 117 files.

6. PERFORMANCE — ✅ PASS

Tag metadata changes have zero runtime impact.

7. SECURITY — ✅ PASS

No code changes, no security concerns.

8. CODE STYLE — ✅ PASS

Tag lines follow standard Gherkin/Behave conventions. Alphabetical ordering is consistent.

9. DOCUMENTATION — ❌ BLOCKING

The CHANGELOG entry is placed under ### Added but this PR is a bug fix (missing required tags — the PR is labelled Type/Bug and references [BUG] issues #9183 and #9124). Per Keep a Changelog conventions, bug fixes must go under ### Fixed, not ### Added.

Fix required: Move the CHANGELOG entry from ### Added to ### Fixed.

10. COMMIT AND PR QUALITY — ❌ BLOCKING

Issue A: PR body missing Closes #N keyword

The PR description contains only:

## Description
Adds mandatory @a2a, @session, and @cli file-level tags to BDD feature files.

There is no Closes #9183 or Fixes #9183 keyword. Per CONTRIBUTING.md, a PR body must contain a closing keyword for Forgejo to auto-close the linked issue on merge.

Fix required: Add Closes #9183 to the PR description body.

Issue B: No Forgejo block dependency set

The PR does not block issue #9183 in Forgejo (confirmed via API: GET /issues/11024/blocks returns empty). Per CONTRIBUTING.md, the PR must block the issue (PR → blocks → issue).

Fix required: Set the Forgejo block dependency so this PR blocks issue #9183.

Note (process, not a hard blocker): Branch name bugfix/pr-9183-bdd-tags does not follow the bugfix/mN-<descriptive-name> convention. Milestone v3.2.0 is M3, so the correct name would be bugfix/m3-bdd-tags. Branches cannot be renamed without rebasing, so this is noted for future compliance.

Summary

Category Status
Correctness ❌ BLOCKING — 4 files have false-positive @cli tags (client libs ≠ CLI)
Specification Alignment ✅ PASS
Test Quality N/A
Type Safety ✅ PASS
Readability ✅ PASS
Performance ✅ PASS
Security ✅ PASS
Code Style ✅ PASS
Documentation ❌ BLOCKING — CHANGELOG entry must be under Fixed, not Added
Commit & PR Quality ❌ BLOCKING — Missing Closes #9183 in PR body; missing Forgejo block dependency

Required Changes Before Approval

  1. Remove @cli from: features/a2a_clients_coverage_boost.feature, features/lsp_client_coverage.feature, features/server_client_stubs.feature, features/tdd_mcp_client_start_race.feature
  2. Move CHANGELOG entry from ### Added to ### Fixed.
  3. Add Closes #9183 to the PR description body.
  4. Set Forgejo block dependency: this PR must block issue #9183.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

## First Review — PR #11024: [BUG] Add required @a2a, @session, @cli tags to BDD feature files ### Overview This PR adds file-level domain classification tags (`@a2a`, `@session`, `@cli`) to 117 BDD feature files across the `features/` directory. The overall approach is correct and the scope is comprehensive — 13 A2A files, 26 session files, and 93 CLI files now carry their respective domain tags, enabling `behave --tags=<domain>` filtering in CI. However, there are **blocking issues** that must be resolved before this PR can be approved. --- ### CI Status CI is **failing** across all jobs (`lint`, `typecheck`, `security`, `quality`, `unit_tests`, `integration_tests`, `e2e_tests`, `build`, `helm`, `coverage`, `docker`). Investigation confirms that `master` also shows CI failure with the same pattern. **These failures are pre-existing and not introduced by this PR.** They are not counted as blockers attributable to this change. --- ### 10-Category Review Checklist #### 1. CORRECTNESS — ❌ BLOCKING **4 files received false-positive `@cli` tags due to substring matching `"cli"` inside `"client"`:** | File | Why it is WRONG | |------|----------------| | `features/a2a_clients_coverage_boost.feature` | Tests `cleveragents.a2a.clients` protocol module — not CLI commands | | `features/lsp_client_coverage.feature` | Tests `LspClient` library class — not CLI commands | | `features/server_client_stubs.feature` | Tests server client protocol stubs — not CLI commands | | `features/tdd_mcp_client_start_race.feature` | Tests `McpClient.start()` race condition — not CLI commands | The filename-based matching algorithm matched any filename containing the substring `"cli"` — which incorrectly captured filenames containing `"client"` (since `client` starts with `cli`). Running `behave features/ --tags=cli` will now erroneously include MCP, LSP, and A2A client library tests in the CLI domain test suite, corrupting domain-based tag filtering. **Fix required:** Remove `@cli` from these four files. #### 2. SPECIFICATION ALIGNMENT — ✅ PASS Issue #9124 and #9183 acceptance criteria require `@a2a`, `@session`, and `@cli` tags on appropriate feature files. Implementation satisfies this intent for the correct files. No specification conflicts. #### 3. TEST QUALITY — N/A Only Gherkin file metadata (tags) modified. No step definitions, `environment.py`, or production code changed. Existing test quality is unaffected. #### 4. TYPE SAFETY — ✅ PASS No Python code changes. #### 5. READABILITY — ✅ PASS Tag placement is consistent: new tags on line 1 before the `Feature:` header. Alphabetical sorting of merged tag lines is correct and consistent throughout all 117 files. #### 6. PERFORMANCE — ✅ PASS Tag metadata changes have zero runtime impact. #### 7. SECURITY — ✅ PASS No code changes, no security concerns. #### 8. CODE STYLE — ✅ PASS Tag lines follow standard Gherkin/Behave conventions. Alphabetical ordering is consistent. #### 9. DOCUMENTATION — ❌ BLOCKING The CHANGELOG entry is placed under `### Added` but this PR is a **bug fix** (missing required tags — the PR is labelled `Type/Bug` and references `[BUG]` issues #9183 and #9124). Per Keep a Changelog conventions, bug fixes must go under `### Fixed`, not `### Added`. **Fix required:** Move the CHANGELOG entry from `### Added` to `### Fixed`. #### 10. COMMIT AND PR QUALITY — ❌ BLOCKING **Issue A: PR body missing `Closes #N` keyword** The PR description contains only: ``` ## Description Adds mandatory @a2a, @session, and @cli file-level tags to BDD feature files. ``` There is no `Closes #9183` or `Fixes #9183` keyword. Per CONTRIBUTING.md, a PR body must contain a closing keyword for Forgejo to auto-close the linked issue on merge. **Fix required:** Add `Closes #9183` to the PR description body. **Issue B: No Forgejo block dependency set** The PR does not block issue #9183 in Forgejo (confirmed via API: `GET /issues/11024/blocks` returns empty). Per CONTRIBUTING.md, the PR must block the issue (PR → blocks → issue). **Fix required:** Set the Forgejo block dependency so this PR blocks issue #9183. **Note (process, not a hard blocker):** Branch name `bugfix/pr-9183-bdd-tags` does not follow the `bugfix/mN-<descriptive-name>` convention. Milestone v3.2.0 is M3, so the correct name would be `bugfix/m3-bdd-tags`. Branches cannot be renamed without rebasing, so this is noted for future compliance. --- ### Summary | Category | Status | |---|---| | Correctness | ❌ BLOCKING — 4 files have false-positive `@cli` tags (client libs ≠ CLI) | | Specification Alignment | ✅ PASS | | Test Quality | N/A | | Type Safety | ✅ PASS | | Readability | ✅ PASS | | Performance | ✅ PASS | | Security | ✅ PASS | | Code Style | ✅ PASS | | Documentation | ❌ BLOCKING — CHANGELOG entry must be under `Fixed`, not `Added` | | Commit & PR Quality | ❌ BLOCKING — Missing `Closes #9183` in PR body; missing Forgejo block dependency | ### Required Changes Before Approval 1. **Remove `@cli`** from: `features/a2a_clients_coverage_boost.feature`, `features/lsp_client_coverage.feature`, `features/server_client_stubs.feature`, `features/tdd_mcp_client_start_race.feature` 2. **Move CHANGELOG entry** from `### Added` to `### Fixed`. 3. **Add `Closes #9183`** to the PR description body. 4. **Set Forgejo block dependency**: this PR must block issue #9183. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
CHANGELOG.md
@ -5,6 +5,16 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
## [Unreleased]
HAL9001 commented 2026-05-09 09:58:08 +00:00
Owner
Copy link

BLOCKING: CHANGELOG entry is under ### Added but this is a bug fix.

This PR adds missing required tags to feature files — the tags were supposed to be there and their absence was a bug (hence Type/Bug, [BUG] in issue titles, fix(bdd): commit type). Per Keep a Changelog conventions:

  • ### Added → for new features
  • ### Fixed → for bug fixes

Fix: Move the entire changelog entry block from under ### Added to a ### Fixed section (create ### Fixed if it does not yet exist in the [Unreleased] block).

Example:

## [Unreleased]

### Fixed
- **BDD feature file tagging** (#9183): Added mandatory `@a2a`, `@session`, and `@cli`
  file-level tags...

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING: CHANGELOG entry is under `### Added` but this is a bug fix.** This PR adds missing required tags to feature files — the tags were **supposed to be there** and their absence was a bug (hence `Type/Bug`, `[BUG]` in issue titles, `fix(bdd):` commit type). Per [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) conventions: - `### Added` → for new features - `### Fixed` → for bug fixes **Fix:** Move the entire changelog entry block from under `### Added` to a `### Fixed` section (create `### Fixed` if it does not yet exist in the `[Unreleased]` block). Example: ```markdown ## [Unreleased] ### Fixed - **BDD feature file tagging** (#9183): Added mandatory `@a2a`, `@session`, and `@cli` file-level tags... ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/a2a_clients_coverage_boost.feature
@ -1,4 +1,4 @@
@phase2 @a2a @coverage-boost
@a2a @cli @coverage-boost @phase2
HAL9001 commented 2026-05-09 09:58:08 +00:00
Owner
Copy link

BLOCKING: False-positive @cli tag — this file tests the A2A client library, not CLI commands.

The filename a2a_clients_coverage_boost.feature contains the substring "cli" as a prefix of "client", but the feature tests cleveragents.a2a.clients (the protocol client module), not any CLI command. Keeping @cli here will pollute behave --tags=cli runs with A2A protocol client tests.

Fix: Remove @cli from the tag line. The @a2a tag is correct and should be kept.

Expected result:

@a2a @coverage-boost @phase2
Feature: A2A clients coverage boost

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING: False-positive `@cli` tag — this file tests the A2A client library, not CLI commands.** The filename `a2a_clients_coverage_boost.feature` contains the substring `"cli"` as a prefix of `"client"`, but the feature tests `cleveragents.a2a.clients` (the protocol client module), not any CLI command. Keeping `@cli` here will pollute `behave --tags=cli` runs with A2A protocol client tests. **Fix:** Remove `@cli` from the tag line. The `@a2a` tag is correct and should be kept. Expected result: ``` @a2a @coverage-boost @phase2 Feature: A2A clients coverage boost ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/lsp_client_coverage.feature
@ -1,3 +1,4 @@
@cli
HAL9001 commented 2026-05-09 09:58:08 +00:00
Owner
Copy link

BLOCKING: False-positive @cli tag — this file tests the LspClient library class, not CLI commands.

The filename lsp_client_coverage.feature contains "cli" as a prefix of "client", but the feature tests LspClient (a library class for LSP protocol communication), not LSP CLI commands. The LSP CLI commands are covered by lsp_cli_new_coverage.feature which correctly received @cli.

Fix: Remove @cli from this file entirely.

Expected result:

Feature: LSP Client coverage

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING: False-positive `@cli` tag — this file tests the `LspClient` library class, not CLI commands.** The filename `lsp_client_coverage.feature` contains `"cli"` as a prefix of `"client"`, but the feature tests `LspClient` (a library class for LSP protocol communication), not LSP CLI commands. The LSP CLI commands are covered by `lsp_cli_new_coverage.feature` which correctly received `@cli`. **Fix:** Remove `@cli` from this file entirely. Expected result: ``` Feature: LSP Client coverage ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/server_client_stubs.feature
@ -1,4 +1,4 @@
@phase2 @a2a @server-stubs
@a2a @cli @phase2 @server-stubs
HAL9001 commented 2026-05-09 09:58:08 +00:00
Owner
Copy link

BLOCKING: False-positive @cli tag — this file tests server client protocol stubs, not CLI commands.

The filename server_client_stubs.feature contains "cli" as a prefix of "client", but the feature covers ServerConnectionConfig and server client protocol interface stubs — not CLI commands. The @a2a tag was already correct and pre-existing.

Fix: Remove @cli from the tag line. Keep @a2a, @phase2, and @server-stubs.

Expected result:

@a2a @phase2 @server-stubs
Feature: Server Client Stubs and Connection Config

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING: False-positive `@cli` tag — this file tests server client protocol stubs, not CLI commands.** The filename `server_client_stubs.feature` contains `"cli"` as a prefix of `"client"`, but the feature covers `ServerConnectionConfig` and server client protocol interface stubs — not CLI commands. The `@a2a` tag was already correct and pre-existing. **Fix:** Remove `@cli` from the tag line. Keep `@a2a`, `@phase2`, and `@server-stubs`. Expected result: ``` @a2a @phase2 @server-stubs Feature: Server Client Stubs and Connection Config ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/tdd_mcp_client_start_race.feature
@ -1,3 +1,4 @@
@cli
HAL9001 commented 2026-05-09 09:58:08 +00:00
Owner
Copy link

BLOCKING: False-positive @cli tag — this file tests McpClient.start() race condition, not CLI commands.

The filename tdd_mcp_client_start_race.feature contains "cli" as a prefix of "client", but the feature is a TDD regression test for the McpClient.start() race condition (bug #10438 — a library-level concurrency bug). This has no CLI involvement.

Fix: Remove @cli from this file entirely.

Expected result:

# This test captures bug #10438 — McpClient.start() race condition.
...
@tdd_expected_fail @tdd_issue @tdd_issue_10438
Feature: TDD Issue #10438 — McpClient.start() race condition...

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING: False-positive `@cli` tag — this file tests `McpClient.start()` race condition, not CLI commands.** The filename `tdd_mcp_client_start_race.feature` contains `"cli"` as a prefix of `"client"`, but the feature is a TDD regression test for the `McpClient.start()` race condition (bug #10438 — a library-level concurrency bug). This has no CLI involvement. **Fix:** Remove `@cli` from this file entirely. Expected result: ``` # This test captures bug #10438 — McpClient.start() race condition. ... @tdd_expected_fail @tdd_issue @tdd_issue_10438 Feature: TDD Issue #10438 — McpClient.start() race condition... ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 commented 2026-05-09 09:58:33 +00:00
Owner
Copy link

Formal peer review submitted (REQUEST_CHANGES) — review ID #8373.

See the review for full details. 3 blocking issues must be resolved before this PR can be approved:

  1. Remove false-positive @cli from 4 client-library feature files
  2. Move CHANGELOG entry from ### Added to ### Fixed
  3. Add Closes #9183 to PR description body and set Forgejo block dependency

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

Formal peer review submitted (REQUEST_CHANGES) — review ID #8373. See the review for full details. **3 blocking issues** must be resolved before this PR can be approved: 1. Remove false-positive `@cli` from 4 client-library feature files 2. Move CHANGELOG entry from `### Added` to `### Fixed` 3. Add `Closes #9183` to PR description body and set Forgejo block dependency --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 requested changes 2026-05-09 10:20:32 +00:00
HAL9001 left a comment
Copy link

First Review

Two blocking issues found. See inline comments and summary below.

Summary

Category Status
Correctness BLOCKING — 4 files have false-positive @cli tags
Specification Alignment PASS
Test Quality N/A
Type Safety PASS
Readability PASS
Performance PASS
Security PASS
Code Style PASS
Documentation SUGGESTION — CHANGELOG section should be Fixed not Added
Commit & PR Quality BLOCKING — Missing Closes #N in PR body; missing Forgejo dependency link

Required Changes

  1. Remove @cli from: features/a2a_clients_coverage_boost.feature, features/lsp_client_coverage.feature, features/server_client_stubs.feature, features/tdd_mcp_client_start_race.feature
  2. Add Closes #9183 to the PR description body.
  3. Set Forgejo dependency so this PR blocks issue #9183.

Non-blocking

  • Move CHANGELOG entry from Added to Fixed (this is a bug fix).
  • Future PRs: use bugfix/m2-name branch naming per CONTRIBUTING.md.

CI Status

CI is failing, but master also fails identically. Pre-existing failures — not introduced by this PR.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

## First Review Two blocking issues found. See inline comments and summary below. ### Summary | Category | Status | |---|---| | Correctness | BLOCKING — 4 files have false-positive @cli tags | | Specification Alignment | PASS | | Test Quality | N/A | | Type Safety | PASS | | Readability | PASS | | Performance | PASS | | Security | PASS | | Code Style | PASS | | Documentation | SUGGESTION — CHANGELOG section should be Fixed not Added | | Commit & PR Quality | BLOCKING — Missing Closes #N in PR body; missing Forgejo dependency link | ### Required Changes 1. Remove @cli from: features/a2a_clients_coverage_boost.feature, features/lsp_client_coverage.feature, features/server_client_stubs.feature, features/tdd_mcp_client_start_race.feature 2. Add Closes #9183 to the PR description body. 3. Set Forgejo dependency so this PR blocks issue #9183. ### Non-blocking - Move CHANGELOG entry from Added to Fixed (this is a bug fix). - Future PRs: use bugfix/m2-name branch naming per CONTRIBUTING.md. ### CI Status CI is failing, but master also fails identically. Pre-existing failures — not introduced by this PR. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
CHANGELOG.md
@ -5,6 +5,16 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
## [Unreleased]
### Added
HAL9001 commented 2026-05-09 10:21:14 +00:00
Owner
Copy link

Suggestion (non-blocking): Move entry to ### Fixed section

This PR fixes a bug (missing required tags on BDD feature files). The PR is labelled Type/Bug and titled [BUG]. Per Keep a Changelog conventions, bug fixes belong under ### Fixed, not ### Added.

Suggestion: Change ### Added → ### Fixed for this entry.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**Suggestion (non-blocking): Move entry to `### Fixed` section** This PR fixes a bug (missing required tags on BDD feature files). The PR is labelled `Type/Bug` and titled `[BUG]`. Per Keep a Changelog conventions, bug fixes belong under `### Fixed`, not `### Added`. **Suggestion:** Change `### Added` → `### Fixed` for this entry. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/a2a_clients_coverage_boost.feature
@ -1,4 +1,4 @@
@phase2 @a2a @coverage-boost
@a2a @cli @coverage-boost @phase2
HAL9001 commented 2026-05-09 10:20:42 +00:00
Owner
Copy link

BLOCKING — Incorrect @cli tag (false positive from substring match)

This file covers A2A Protocol client stubs and validation branches (cleveragents.a2a.clients). It is not a CLI-domain feature. The @cli tag was applied because the filename contains client, which includes the substring cli.

Running behave --tags=cli will incorrectly include this A2A client test in the CLI test suite — corrupting the domain-based filtering that this PR is intended to establish.

Fix: Remove @cli. The correct tag line should be:

@a2a @coverage-boost @phase2

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — Incorrect `@cli` tag (false positive from substring match)** This file covers A2A Protocol client stubs and validation branches (`cleveragents.a2a.clients`). It is **not** a CLI-domain feature. The `@cli` tag was applied because the filename contains `client`, which includes the substring `cli`. Running `behave --tags=cli` will incorrectly include this A2A client test in the CLI test suite — corrupting the domain-based filtering that this PR is intended to establish. **Fix:** Remove `@cli`. The correct tag line should be: ```gherkin @a2a @coverage-boost @phase2 ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/lsp_client_coverage.feature
@ -1,3 +1,4 @@
@cli
HAL9001 commented 2026-05-09 10:20:50 +00:00
Owner
Copy link

BLOCKING — Incorrect @cli tag (false positive from substring match)

This file covers LspClient library code paths. It is not a CLI-domain feature — it tests the LSP language-server client protocol implementation, not any agents lsp CLI command. The @cli tag was applied because the filename contains client (which includes the substring cli).

This file does not cover A2A or session domain concerns either, so no domain tags should be added to this file.

Running behave --tags=cli will incorrectly include this LSP client test in the CLI test suite.

Fix: Remove @cli entirely. The file should start directly with the Feature: header (no file-level domain tag added by this PR).

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — Incorrect `@cli` tag (false positive from substring match)** This file covers `LspClient` library code paths. It is **not** a CLI-domain feature — it tests the LSP language-server client protocol implementation, not any `agents lsp` CLI command. The `@cli` tag was applied because the filename contains `client` (which includes the substring `cli`). This file does not cover A2A or session domain concerns either, so **no domain tags should be added to this file**. Running `behave --tags=cli` will incorrectly include this LSP client test in the CLI test suite. **Fix:** Remove `@cli` entirely. The file should start directly with the `Feature:` header (no file-level domain tag added by this PR). --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/server_client_stubs.feature
@ -1,4 +1,4 @@
@phase2 @a2a @server-stubs
@a2a @cli @phase2 @server-stubs
HAL9001 commented 2026-05-09 10:20:56 +00:00
Owner
Copy link

BLOCKING — Incorrect @cli tag (false positive from substring match)

This file covers ServerConnectionConfig validation and A2A server-client protocol stubs. It is not a CLI-domain feature. The @cli tag was applied because the filename contains client (which includes the substring cli).

Running behave --tags=cli will incorrectly include this A2A server-stub test in the CLI test suite.

Fix: Remove @cli. The correct tag line should be:

@a2a @phase2 @server-stubs

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — Incorrect `@cli` tag (false positive from substring match)** This file covers `ServerConnectionConfig` validation and A2A server-client protocol stubs. It is **not** a CLI-domain feature. The `@cli` tag was applied because the filename contains `client` (which includes the substring `cli`). Running `behave --tags=cli` will incorrectly include this A2A server-stub test in the CLI test suite. **Fix:** Remove `@cli`. The correct tag line should be: ```gherkin @a2a @phase2 @server-stubs ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/tdd_mcp_client_start_race.feature
@ -1,3 +1,4 @@
@cli
HAL9001 commented 2026-05-09 10:21:04 +00:00
Owner
Copy link

BLOCKING — Incorrect @cli tag (false positive from substring match)

This file captures bug #10438 — McpClient.start() race condition in the MCP client library. It is not a CLI-domain feature. The @cli tag was applied because the filename contains client (which includes the substring cli).

This file does not cover A2A or session domain concerns either, so no domain tags should be added to this file.

Running behave --tags=cli will incorrectly include this MCP race-condition test in the CLI test suite.

Fix: Remove @cli entirely. The file should start with the existing comment block and @tdd_expected_fail @tdd_issue @tdd_issue_10438 tags (no file-level domain tag added by this PR).

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — Incorrect `@cli` tag (false positive from substring match)** This file captures bug #10438 — `McpClient.start()` race condition in the MCP client library. It is **not** a CLI-domain feature. The `@cli` tag was applied because the filename contains `client` (which includes the substring `cli`). This file does not cover A2A or session domain concerns either, so **no domain tags should be added to this file**. Running `behave --tags=cli` will incorrectly include this MCP race-condition test in the CLI test suite. **Fix:** Remove `@cli` entirely. The file should start with the existing comment block and `@tdd_expected_fail @tdd_issue @tdd_issue_10438` tags (no file-level domain tag added by this PR). --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 commented 2026-05-09 10:21:19 +00:00
Owner
Copy link

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

--- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Failing after 54s
Details
CI / push-validation (pull_request) Failing after 13m50s
Details
CI / helm (pull_request) Failing after 13m51s
Details
CI / build (pull_request) Failing after 13m53s
Required
Details
CI / e2e_tests (pull_request) Failing after 13m55s
Details
CI / integration_tests (pull_request) Failing after 13m56s
Required
Details
CI / unit_tests (pull_request) Failing after 13m57s
Required
Details
CI / quality (pull_request) Failing after 13m58s
Required
Details
CI / security (pull_request) Failing after 13m58s
Required
Details
CI / typecheck (pull_request) Failing after 13m58s
Required
Details
CI / lint (pull_request) Failing after 13m59s
Required
Details
CI / coverage (pull_request) Has been cancelled
Required
Details
CI / docker (pull_request) Has been cancelled
Required
Details
CI / status-check (pull_request) Has been cancelled
Details
This pull request has changes conflicting with the target branch.
  • CONTRIBUTORS.md
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin bugfix/pr-9183-bdd-tags:bugfix/pr-9183-bdd-tags
git switch bugfix/pr-9183-bdd-tags
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
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.2.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
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.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core!11024
No description provided.